[kodes-agency]

What changed

• docs/operations/backup-and-lifecycle.md section 1 no longer marks the beta database's backups unverified or quotes the August inspection. It records what was found in Railway on 2026-11-04: point-in-time recovery is on for Postgres in closed-beta-v2 (restore window about four weeks per Railway's documentation, no restore point earlier than 2026-11-04), daily and weekly backups are on, and a restore into a separate service reached the chosen moment, accepting connections 36.5 minutes after the request for about 15.5 hours of log. A restore can lose about one minute of data. It also adds two handling notes for restored copies, and says that the app's own restore-verify still binds to cell-us and was not used.
• docs/BETA.md sections 6 and 7 replace their two UNVERIFIED markers with the same finding, and the change log gets a line. A test holds those two passages and the backup record to each other.
• docs/adr/0073-reply-voice-and-shared-reply-templates.md gets a dated note that agency adoption was dropped on 2026-10-30, so the consequence about rewriting the import script no longer applies.

What the rehearsal did not show: it tested the data restore only. It did not time a full restore to operational state, did not measure a worst case, and did not test erasure replay, which does not run today. The docs say so.

How it was tested

• src/shared/db/beta-database-documents.test.ts fails with the backup record updated and docs/BETA.md unchanged, and passes with both updated.
• Vitest (unit project) on the 14 non-integration test files that read or cite these documents: 14 files, 235 tests pass.
• prettier --check on the three changed files passes.
• The four *.integration.test.ts files that match the search only name docs/BETA.md in comments, so they were left to CI.

🤖 Generated with Claude Code

[ecc-tools]

ECC Tools / Security Evidence

Commit: 0a97526719d59fa356975a24d06a88c94b0e50a8

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 3 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: 0a97526719d59fa356975a24d06a88c94b0e50a8

PR taxonomy clear (success)

Scanned 3 changed file(s). No taxonomy bucket signals were detected.

Scanned 3 changed file(s).

No PR taxonomy bucket signals were detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: 0a97526719d59fa356975a24d06a88c94b0e50a8

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 3 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: 0a97526719d59fa356975a24d06a88c94b0e50a8

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 3 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.