[daliu]

Corrected the staging release success output and added a read-only way to verify an uncertain deployment without another build.

Officer impact: Officers request one safe staging check and receive dated proof rather than retry a deployment or share credentials.
Officer documentation: docs/officers/STAGING_COMMUNITY.md, docs/officers/SYSTEM_MAPS.md, OPERATIONS_RUNBOOK.md, GITHUB_ISSUES.md.
Deployment evidence: No new deployment is needed or authorized for this tooling-only change. Existing native communityActions v4/source b6a8fd5/91,793-byte archive SHA-256 47f11b8bec7f5ae58281c9029a015e9cc751a04e5ad3eafe3234441fa3a963db passed read-only checks; both profiles remain v2/v1/source2843388. The new exact-main verification command and unchanged Hosting marker will be checked after merge/all-six CI, recorded under #722.

Scope / review

• Fix final output's undefined digest with actual bundle.digest; provider-free reproduction and exact serializer regression.
• No-arg release retains its fixed staging scope; exact verify mode checks existing owner/runtime/zero-key/MFA/resource/access/archive/profile inventory without writes. Unknown/extra args stop before credentials.
• Read-only transport refuses all deployment/IAM/Auth/data/foreign requests before network access; only signed source-download URL generation is POST. Native source provenance and exact downloaded bytes, not labels, qualify the result. Archive stream is bounded and receives no credential/header.
• Closed safe phase enum, private branded errors, no raw exception/cause/body/URL/token output. No blind retry or guard bypass.
• Existing source gates strengthened with final green-main readback; existing deployment end verification reused and conditional invoker policies denied, never silently stripped.
• No Functions/Rules/frontend/runtime bundle, lockfile/dependency/workflow, resource/IAM/schema/migration, billing or production/payment change. Historical failures are not relabelled successes; source bug is confirmed but individual caught historical exceptions were not stored.

Validation

• Before implementation: existing 7 tests passed; 25 new assertions failed due to missing behavior.
• node --test tests/staging-profile-authority.test.js: 51 pass, zero skips on Node22.
• Existing full ten-file release/workflow/security contract suite: 189 pass, zero skips on Node22.
• Non-mutating frontend lint: 126 files /113 reviewed legacy errors /6 warnings, unchanged.
• Bundle remains 91,793 bytes /47f11b8bec7f5ae58281c9029a015e9cc751a04e5ad3eafe3234441fa3a963db; git diff --check passes.
• Hosted existing six-job PR/main CI and new read-only command remain acceptance gates; no added CI job or local bulk runtime suite for unchanged runtime source.

Officer screen-only review: request a read-only staging check, keep production/payments untouched, read dated issue result, stop on any failure, and escalate to Dave. Specialist still verifies source/CI/provider and performs any later approved repair. No new member fixture or credential is needed.

Refs #722. Do not auto-close before native command and handoff evidence. Broad backend/production/payment parents remain open.

[netlify]

✅ Deploy Preview for luminous-fox-7c393f ready!

Name	Link
🔨 Latest commit	9f337fe
🔍 Latest deploy log	https://app.netlify.com/projects/luminous-fox-7c393f/deploys/6acdc5790139075548c9f1e4
😎 Deploy Preview	https://deploy-preview-723--luminous-fox-7c393f.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.