docs(recovery): classify #616 as protected authority

[seonghobae]

Problem

#616 is now protected source at main@a318ca0f9a6268e014ebd71f3e08b8fe773d9f5b, but the moving recovery baseline and OPERABILITY text still stopped at #612/#614. That left canonical docs behind code: post-mutation Cloudflare status verification is protected source, while controlled production recovery rehearsal remains unproven.

Documentation regression

Test-only exact 4534c4bc1732e9503b26476133a89a1f0da44ce7 tightened the executable documentation contract to require #616 classification, mutation-acknowledgement vs fresh post-mutation provider-status separation, lowercase UUID canonical identity, ADR-0018 Proposed, and the remaining production-rehearsal gap. Its hosted application CI reached release tests but was cancelled by the subsequent documentation repair push, so it is retained as the test-first predecessor but not claimed as a terminal hosted RED.

Causal repair

Current exact 38b3b56837d875d19ae458f3f5491951ad7afb1c changes only canonical documentation plus that executable documentation regression:

• the moving baseline records protected fix(recovery): verify exact provider state after mutation #616 exact da8461f1..., updates the recovery lineage to fix(recovery): preserve pre-deployment traffic authority #612/fix(recovery): canonicalize UUID authority identities #614/fix(recovery): verify exact provider state after mutation #616, and keeps deploy: preserve pre-deployment traffic authority in rollback evidence #611 open for immutable release + controlled rehearsal evidence;
• OPERABILITY treats the create-deployment response as mutation acknowledgement only and requires fresh post-mutation provider status to confirm the newly created recovery deployment and exact canonical distribution before command success;
• ADR-0018 remains Proposed; source integration is not promoted to deployment/recovery/SLO/release evidence.

No recovery source behavior, foreign-owner authority, provider routing, gate, or deployment mutation is changed by this PR.

Current gate

Every documentation mutation invalidates predecessor workflow evidence. Current-head exact 38b3b568... must independently reach terminal applicable application CI, reviewer-ci, Security Scan and patch-validator-image, with clean fresh review/thread/base checks, before normal merge.

Summary by CodeRabbit

• 문서

  • Cloudflare Worker 복구 절차가 배포 후 제공자 상태를 새로 조회해 복구 배포 ID와 트래픽 분포를 검증하도록 업데이트되었습니다.
  • 복구 승인 기준과 운영 증거에 사후 검증 요구사항이 반영되었습니다.
  • 보호된 배포 복구 문서에 관련 실패 조건과 미완료된 복구 리허설 상태가 명시되었습니다.

• 테스트

  • 최신 병합 이후의 복구 상태 검증 기준에 맞게 문서 검증 테스트가 업데이트되었습니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: c8544496-8fa8-4855-abab-565a814d1e3b

📥 Commits

Reviewing files that changed from the base of the PR and between a318ca0 and 38b3b56.

📒 Files selected for processing (3)

• docs/OPERABILITY.md
• docs/product-technical-gap-baseline.md
• test/documentation-recovery-authority-current.test.ts

---

📝 Walkthrough

Walkthrough

Worker 복구 문서가 배포 생성 응답을 권위 있는 활성 상태로 사용하지 않도록 갱신되었습니다. 복구 성공 전에 새 배포 UUID와 canonical 트래픽 분포를 provider 상태 조회로 검증합니다. 기준선과 문서 테스트가 PR #616의 변경 내용을 반영합니다.

Changes

Worker 복구 권위 검증

Layer / File(s)	Summary
복구 사후 검증 계약 docs/OPERABILITY.md, docs/product-technical-gap-baseline.md, test/documentation-recovery-authority-current.test.ts	복구 절차가 create-deployment 응답을 mutation acknowledgement로 처리합니다. 복구 성공 전에 fresh provider status read로 새 배포 UUID와 canonical version/percentage distribution을 검증합니다. 관련 수락 기준과 문서 테스트도 갱신되었습니다.
보호된 근거 상태 갱신 docs/product-technical-gap-baseline.md	보호된 history와 ADR 0018 상태에 PR #616을 반영합니다. recovery authority gap의 보호 소스 목록을 갱신하고, GitHub Releases 0건 상태를 유지합니다.

Estimated code review effort: 2 (Simple) | ~15 minutes

Change: Other

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/recovery-post-mutation-protected-20260911

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Current-head review on 38b3b56837d875d19ae458f3f5491951ad7afb1c: the three-file documentation/test delta correctly classifies protected #616 post-mutation provider-status verification without promoting source integration to controlled recovery/release evidence. The moving baseline keeps ADR-0018 Proposed, issue #611 open, and foreign/provider authority outside Noema. Fresh applicable CI, reviewer-ci, Security Scan, and patch-validator-image are all terminal GREEN; no inline review threads are present. No additional valid source/DDD/authority/test/documentation finding found in this exact head.