docs(lifecycle): make protected authority code-current

[seonghobae]

Scope

Repairs stale lifecycle authority wording after the protected #574 → #577 → #578 → #579 → #580 lineage.

• docs/external-extension-lifecycle-recovery.md now distinguishes protected source authority from still-unproven production deployment, activation-authority integration, remote performance/recovery acceptance, and immutable release authority.
• docs/CONTEXT_MAP.md now records the protected append-only lifecycle repository and SQLite Worker Durable Object binding/runtime through Wire external-extension lifecycle persistence into the Worker runtime #580 instead of describing feat(tool-capability): persist external-extension lifecycle evidence #574 as an active Draft.
• test/lifecycle-documentation-authority.test.ts prevents these two canonical documents from regressing to the superseded Draft/candidate wording and keeps source authority separate from deployment/release claims.

Authority boundary

Noema still owns only Tool Capability / State / Checkpoint / Policy-Approval integration / Recovery lifecycle authority. AppGuardrail, quarantine-sandbox-runtime, EgressWeave, Keyverse, contextual-orchestrator, Context Graph, and consumer domain truth remain their canonical owners. This PR changes no provider routing, security/quarantine/outbound authority, runtime activation path, or mutable sibling dependency.

Verification contract

This is a documentation-authority repair, not production acceptance. Merge only on the unchanged exact head after application CI, reviewer-ci, the inherited central Security Scan, and patch-validator-image are GREEN. #561 remains open for the production activation-authority adapter and real deployed Durable Object performance/contention/storage/recovery evidence. #36/#575 remain governed by immutable release acceptance rather than source prose.

Related: #5, #36, #561, #575, #580.

Summary by CodeRabbit

• 문서

  • 외부 확장 수명주기 및 복구 관련 문서가 보호된 소스 권한을 기준으로 갱신되었습니다.
  • 프로덕션 배포, 활성화 권한 연동, 원격 성능·복구 검증이 아직 보장되지 않음을 명확히 했습니다.
  • 새로운 활성 상태 전환은 활성화 권한 연동이 제공되기 전까지 안전하게 차단됩니다.
  • 관련 아키텍처 결정은 실제 런타임 검증 전까지 제안 상태로 유지됩니다.

• 테스트

  • 문서가 후보 권한과 프로덕션 권한을 혼동하지 않는지 자동으로 검증합니다.

[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: 580190eb-75ce-41e8-a87a-607bdb22e976

📥 Commits

Reviewing files that changed from the base of the PR and between 12272f3 and 56aa05d.

📒 Files selected for processing (3)

• docs/CONTEXT_MAP.md
• docs/external-extension-lifecycle-recovery.md
• test/lifecycle-documentation-authority.test.ts

---

📝 Walkthrough

Walkthrough

외부 확장 수명주기 문서가 보호된 main 소스와 SQLite 기반 Worker Durable Object 런타임을 반영하도록 갱신되었습니다. 새 테스트는 후보 권위 문구의 제거와 프로덕션 배포·불변 릴리스 권위의 분리를 검증합니다.

Changes

외부 확장 수명주기 문서 권위 갱신

Layer / File(s)	Summary
보호된 소스 설명과 문서 검증 docs/CONTEXT_MAP.md, docs/external-extension-lifecycle-recovery.md, test/lifecycle-documentation-authority.test.ts	문서가 PR #574, #577, #578, #579, #580을 통한 보호된 main 소스와 SQLite 기반 Worker Durable Object 바인딩을 설명합니다. 문서는 프로덕션 배포, 활성화 권한 어댑터, 원격 수용 기준 및 불변 릴리스 권위를 설정하지 않는다고 명시합니다. 테스트는 이전 후보 권위 문구와 Draft #574`` 문구의 부재를 검증합니다.

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

✨ 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/lifecycle-protected-authority

---

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.}