docs(xint): correct guide ingest activation contract - #217
Conversation
📝 WalkthroughWalkthroughUpdates WS-XINT-002 planning and status documentation for guide-ingest authorization, including covered Project Manager authority, activation scope and criteria, canonical permission ownership, and completed-state notes for the 04A/04B split. ChangesGuide ingest authorization
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
7c8d153 to
5e2270d
Compare
5e2270d to
35b9bff
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
Workstream PR Trust Bundle
Chunk
WS-XINT-002-04A planning correction - Correct guide-ingest activation contract
Goal
Make the 04A contract executable and fail-closed before implementation by restoring the canonical Project Manager policy surface and exact ART lineage-lock boundary omitted from the original contract.
Intent And Planning Context
What Changed
Why It Changed
Pre-implementation architecture, security, product, QA, CI, and senior reviews found that the original allowed-file boundary could not safely satisfy its own authorization and stale-lineage acceptance criteria.
Design Chosen
Repair the planning contract first, in a planning-only PR, then stack the bounded implementation behind it.
Alternatives Rejected
Scope Control
Allowed Files Changed
Files Outside Stated Scope
Product Behavior
Evidence
Commands Run
Result Summary
All planning-document checks passed. GitHub Agent Gates passed. CodeRabbit generated no actionable comments.
Acceptance Criteria Proof
Test Delta
Tests Added
Tests Modified
Tests Removed Or Skipped
Internal Reviewer Results
Reviewed code SHA: 35b9bff
Reviewed at: 2026-07-28
Reviewer run IDs: pre-implementation 04A review fanout
External Review
CI And Gate Integrity
Remaining Risks
The planning correction does not itself activate guide ingestion. Activation remains isolated in stacked PR #218 and requires its own exact-head CI and external review after retargeting to main.
Follow-Up Work
Merge this planning correction after hosted checks and human approval, retarget PR #218 to main, then rerun CodeRabbit and all hosted checks on the implementation head.
Human Review Focus
Please inspect:
Human Merge Ownership