Local release readiness

Contact Capture Release Readiness

Readiness packet only

Readiness Result

  • 1review-only-release-readiness means local evidence can be reviewed by the owner.
  • 2ready-for-owner-release-discussion allows product discussion only, not release execution.
  • !blocked-real-release keeps real packaging, deploy, hosting, DNS, stores, and production behind a separate Strict Control approval.

Evidence Chain

  • 1/mobile-assistant-review-checklist confirms mobile UX review scope.
  • 2/mobile-assistant-launch-decision confirms PWA-first direction and owner decision gates.
  • 3/mobile-assistant-pwa-packaging-review confirms shell assets and cache guardrails.
  • 4/mobile-assistant-pwa-packaging-plan confirms no-effect packaging evidence.
  • 5/mobile-assistant-packaging-target-request asks for the next packaging target without approving it.

Interface Freeze

  • 1/mobile-assistant remains the mobile AI assistant shell.
  • 2/contact-capture/scanner remains the capture and correction surface.
  • 3/operator remains queue, audit, storage, and notification review.
  • 4/product-readiness remains the gate summary before any release work.

Safety Gates

  • 1contact-capture-ocr-provider stays owner-approval-required.
  • 2contact-capture-duplicate-read-adapter stays owner-approval-required.
  • 3contact-capture-durable-result-storage stays owner-approval-required.
  • 4completion-notification-sender stays owner-approval-required.
  • !No gate can be bypassed by a local readiness page.

Verification Commands

  • 1Run npm run verify:local-preview-routes.
  • 2Run npm run verify:mobile-assistant-intent-browser.
  • 3Run npm run verify:mobile-assistant-pwa-packaging-review-browser.
  • 4Run npm run verify:mobile-assistant-release-readiness-browser.
  • 5Run npm run verify:mobile-assistant-packaging-target-request-browser and npm run verify.

Owner Decision Gates

  • 1decision-ocr-provider must be approved separately before live OCR.
  • 2decision-duplicate-read-window must be approved separately before Google Contacts reads.
  • 3decision-durable-storage must be approved separately before database writes.
  • 4decision-notification-sender must be approved separately before Telegram or email sends.

Stop Rules

  • !No package build, native packaging, deploy, hosting change, DNS change, production release, TestFlight, or app-store action.
  • !No live OCR, Google Contacts read/write, n8n/Contacts Agent execution, Telegram smoke test, email send, or calendar action.
  • !No credential/token access, durable write, raw payload storage, service-worker cache expansion, production access, or completion notification.