docs(agent-runtime): record protected procedural integration

[seonghobae]

Scope

Repair the procedural-graph doctoring authority after protected integration of #585 and #586. This lane changes documentation authority only; it does not promote ADR 0017, create release/deployment evidence, or grant graph activation authority.

RED → causal repair

Test-first exact d05dfcbacb4d06384eb1727ca14215de5d778bd8 added an executable documentation regression requiring the adoption record to distinguish protected source integration from rollout acceptance. The protected adoption record still said Noema must “complete #585 and #586”. That predecessor generation was cancelled after the causal successor landed, so it is not claimed as hosted terminal RED.

Current exact 66475ab1111d56349319071d3865205a74c7bff9 records #585/#586 as protected source and separately keeps ADR 0017 Proposed, activationAuthorized: false, immutable release/deployment, authenticated evaluation, durable promotion/revocation, shadow/canary, rollback and product-outcome evidence open. Historical repair evidence was retained.

Current verification

Current-head COMMENT review found no new valid finding in the two-file patch. Fresh application CI 34439973117, reviewer-ci 34439973151, central Security Scan 34439973124, and patch-validator-image 34439973201 exist for this exact head and are currently queued/non-terminal. Predecessor GREEN is not reused and Draft remains correct.

Separate docs-to-code debt remains in canonical PRD/TRD/ARCHITECTURE/OPERABILITY/TEST_STRATEGY/product technical baseline where protected #585/#586 source is still described as active/candidate or otherwise not fully current. This PR does not claim that broader convergence is complete.

Acceptance

• record feat(agent-runtime): add advisory procedural graphs and guarded candidate screening #585/feat(agent-runtime): gate procedural guidance by execution lifecycle #586 as protected source, not active candidate work;
• preserve activationAuthorized: false and Proposed ADR 0017;
• keep release/deployment/shadow/canary/Policy-Approval/durable-history gaps explicit;
• do not rewrite historical test or repair evidence;
• current exact-head application CI, reviewer-ci, central Security Scan and patch-validator-image must all be terminal passing before normal merge.

Summary by CodeRabbit

• 문서

  • 보호된 main에 병합된 소스(#585, #586)를 기준으로 절차 문서를 업데이트했습니다.
  • 소스 준비 및 완료 증거 기준을 통합 커밋 기준으로 정리했습니다.
  • 롤아웃 승인과 릴리스·배포·평가·롤아웃 권한이 별도임을 명확히 했습니다.
  • 현재 활성화 승인은 이루어지지 않은 상태로 기록했습니다.

• 테스트

  • 문서에 병합된 소스와 롤아웃 승인 분리가 정확히 반영되었는지 검증하는 테스트를 추가했습니다.

[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: f88df115-0620-474a-8995-c0cacafb06f1

📥 Commits

Reviewing files that changed from the base of the PR and between ae525cd and 66475ab.

📒 Files selected for processing (2)

• docs/doctoring/procedural_graph_adoption.md
• test/documentation-current-trust-authority.test.ts

---

📝 Walkthrough

Walkthrough

문서는 #585와 #586의 보호된 main 병합 증거를 추가합니다. 소스 통합과 릴리스·배포·롤아웃 권한을 분리합니다. 테스트는 문서 문구와 activationAuthorized: false 상태를 검증합니다.

Changes

절차적 소스 권한

Layer / File(s)	Summary
보호된 소스 증거 및 권한 기준 docs/doctoring/procedural_graph_adoption.md	보호된 main의 #585와 #586 병합 커밋 및 검사를 기록합니다. 소스 준비 종료 기준을 갱신합니다. 소스 통합이 릴리스·배포·평가·롤아웃 권한을 증명하지 않음을 명시합니다.
권한 분리 문서 검증 test/documentation-current-trust-authority.test.ts	문서의 병합 소스 문구와 activationAuthorized: false를 검증합니다. 이전 완료 지시문이 제거되었는지도 확인합니다.

Estimated code review effort: 1 (Trivial) | ~5 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/procedural-graph-protected-status-20260910

---

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: the patch is documentation-only and preserves Noema ownership boundaries. It records #585/#586 as protected source without promoting ADR 0017, activationAuthorized, release/deployment, Policy/Approval, durable promotion, canary, rollback, or product-outcome authority. The executable regression fails conceptually on the predecessor wording and is satisfied by the causal adoption-record change. Historical repair evidence remains intact. Separate valid docs-to-code debt remains in canonical PRD/TRD/ARCHITECTURE/OPERABILITY/TEST_STRATEGY/product baseline where #585 is still described as active/candidate; this PR does not claim that broader convergence is complete.