FIRST-TIME-COMMERCIAL-ENTRANCES (Public UX) & TOOL-SPECIFIC-RECOVERY (Dashboard UX)

Release digest

FIRST-TIME-COMMERCIAL-ENTRANCES (Public UX) — Added commercial-first Protocol Teams navigation, a versioned cached Explore Crypto example, and a bounded Labs overview while preserving the existing Vartovii logo, palette, tokens, and component direction.
TOOL-SPECIFIC-RECOVERY (Dashboard UX) — Added an explicit Crypto Retry lookup action, Battle timeout recovery, Assistant soft-delay handling with prompt preservation, and a Forensics-specific failure path without automatic retries.

AUDIT-SCOPE-OFFER-HIERARCHY (Commercial Clarity) — Kept the canonical 750 USDC Audit Scope Readiness Sprint as the public package and documented the 350 USDC Documentation Cleanup as an approved post-fit-check bridge offer with accepted written scope, not a homepage or pricing package.
WORKSPACE-ENTRY-CONTEXT (Dashboard Navigation) — Separated tab-local entry origin from active corporate or crypto workspace mode and kept navigation available during pending requests and recovery states.

CRYPTO-CACHE-FIRST-READS (API Reliability) — Made the production project route return cached snapshots without metadata or live-market network calls, materialize a miss at most once, and preserve the full-service project, source, and harvesters response contract.
ASSISTANT-DUPLICATE-SUBMIT (Cost Boundary) — Prevented repeated submits while the client knows an Assistant request is active and stopped the UI from claiming that a delayed backend operation was cancelled or safe to retry.

Updated canonical sprint and operating documents plus user-facing knowledge-base guidance for public entrances, the Crypto API, Explore freshness, Labs status, and the 350 USDC bridge boundary. Architecture and deployment environment documentation are unchanged because schemas, infrastructure, and runtime configuration remain stable.
Verified 35 Gate 1 public contracts, 59 Gate 2 reliability contracts, 127 broader Crypto regressions, docs and dashboard lint/builds, seven-route prerendering, five targeted Chromium flows, automated axe checks, and manual focus, keyboard, touch-target, reduced-motion, and dark-theme reviews.
Screenshots remain visual evidence rather than accessibility compliance proof. Gate 3 is backend-only and is evidenced by production-router tests rather than a UI screenshot.