docs

English

日本語

English

日本語

Appearance

Production checklist

Verify Seams release identity, origins, policy, lifecycle recovery, accessibility, observability, and rollback before launch.

Production checklist ​

Complete this list against the exact artifacts and environment that will serve users.

Build and identity ​

  • [ ] Browser SDK, Wallet Server, and hosted assets use 0.42.0. The recovery CLI uses 0.29.0. Record exact package versions and source revisions.
  • [ ] Application and wallet host both use iframe protocol 23.0.0.
  • [ ] An already-open older client shows an upgrade message. After reload, registration and signing complete with the current release.
  • [ ] The docs, application, wallet runtime, workers, and WASM build without uncommitted generated output.
  • [ ] Network, project environment, wallet origin, and RP ID match the target lane.

Security boundaries ​

  • [ ] Exact origin allowlists, CSP, iframe message validation, and request authentication are enabled.
  • [ ] Browser configuration contains no secrets.
  • [ ] Router A/B custody roles have independent credentials and operational authority where strict isolation is claimed.
  • [ ] Challenge, registration, recovery, export, and signing endpoints have appropriate rate and replay controls.

Product flows ​

  • [ ] Registration, unlock, first signing, cancellation, recovery, linked device approval, export, and revocation complete on supported browsers.
  • [ ] Expired sessions, retryable provisioning, transport failure, policy denial, and uncertain broadcast state have clear recovery actions.
  • [ ] Mobile, keyboard, screen-reader, reduced-motion, and 200% zoom checks pass for the wallet surfaces.

Operations ​

  • [ ] Audit events exclude credentials, key material, OTP codes, and tokens.
  • [ ] Alerts identify the affected lane and boundary without exposing secrets.
  • [ ] The team rehearsed backup, restore, rollback, and secret-rotation procedures.
  • [ ] Support can map public error codes to the current troubleshooting runbook.
  • [ ] Each enabled regional home has verified Worker/D1 bindings and Durable Object placement. Routing and directory outages fail safely.
  • [ ] APAC registration and relocation use apac-se. Record actual object locations and database primaries. A placement hint alone is insufficient.
  • [ ] Gateway migration 0081_registration_directory_publications.sql is applied. The scheduled handler resumes pending registration publications, and the queue drains after a successful registration.
  • [ ] Router, both Derivers, and Signing Worker use the same private allocation contract. Expired unused tenant authorizations are fenced before renewal.
  • [ ] One wallet retains the same home across devices and travel. Concurrent wallets can operate in different homes.

Tenant-root release ​

  • [ ] The deployed release includes the intended refresh admission policy. Same-operation retries replay the recorded result. A distinct manual refresh during the hourly cooldown fails before provider work.
  • [ ] Fresh ECDSA and Ed25519 registration and signing pass on the deployed lane, with stable wallet identity across tenant-root refresh.
  • [ ] A/B backup objects and the authoritative identity/activation metadata needed for managed restore are recoverable. Each role can access only its configured backup key through its runtime credential.
  • [ ] Managed restore completes its mandatory forward refresh, and interrupted activation/retirement can resume from recorded checkpoints.
  • [ ] Published security claims match actual administration and key-retention boundaries. Shared KMS versions do not establish per-tenant erasure.

SDK publication does not establish that administrative recovery or portability is enabled in a particular environment. Verify the actual dashboard, signed CLI binary, recovery custody, and destination restore path before offering them. See recovery availability.

Documentation publication ​

  • [ ] Installation, examples, reference, and operations pages agree with release status. Prepared changes are clearly identified.
  • [ ] Compiled examples, internal links, code-fence classification, and the VitePress build pass. Browser evidence includes a repeatable journey.
  • [ ] Staging and production serve the intended docs source revision. Verify the deployed seams-wallet-docs-artifact.json receipt.
  • [ ] Deep links, search, desktop/mobile navigation, dark mode, and diagrams work. Production canonical URLs and the sitemap use the production docs origin.
  • [ ] Staging requests noindex. Retain the previous docs artifact for rollback.