docs: reconcile current v0.1 repository state - #259
Conversation
📝 WalkthroughWalkthroughThis PR updates current-facing documentation, classifies historical planning records, and reconciles initiative status. It also records review evidence and clarifies that review and revision lifecycle behavior remains unavailable. ChangesCurrent documentation reconciliation
Estimated code review effort: 2 (Simple) | ~10 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/current_system_data_flow.html`:
- Around line 560-561: Update the “Current checker outcome” paragraph to
distinguish checker outcomes from lifecycle states: state that passing work
yields the checker outcome allow_review, which may transition the task toward
review_pending, while retaining task_setup_blocked as an internal routing
recommendation.
In `@docs/roadmap_status.md`:
- Around line 60-63: Remove the unsupported readiness bullet from its current
roadmap status, or move the entire bullet to the “Integration In Progress”
section. If retaining it in the current section, add exact merged evidence
references for policy identity, AUTH-owned mutation, completed REV catalogues,
and the typed PREP/read handoff.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 7df39a61-1ef6-4188-9824-0d7f25324dd2
📒 Files selected for processing (7)
.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/CHUNK_MAP.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/STATUS.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/chunks/WS-DOCS-001-02-current-state-reconciliation.md.agent-loop/initiatives/WS-DOCS-001-current-v01-documentation/reviews/WS-DOCS-001-02-review-and-trust-bundle.mddocs/current_system_data_flow.htmldocs/historical_planning.mddocs/roadmap_status.md
Chunk
WS-DOCS-001-02— current-state documentation reconciliation.Goal and design
Remove remaining stale calendar framing from current-facing documentation, classify preserved early plans and reviews as history, and reconcile the v0.1 capability ledger. Historical bodies remain unchanged as audit evidence. Checker outcome
allow_reviewis distinct from lifecycle statereview_pending; merged REV/AUTH readiness is bound to PRs #242, #248, #255, and #257 without claiming REV is live.Scope control
Documentation and WS-DOCS-001 records only. No backend, frontend, migration, test, workflow, CI policy, architecture contract, or AUTH/ART/REV/CON/QUAL implementation changes. PRs #149, #138, and #62 are untouched.
Alternatives
Rewriting or deleting historical records was rejected because it would destroy traceability. Treating readiness as live REV behavior was rejected because implementation and release remain separate gates.
Acceptance and test proof
docs/review*.mdfile is historically indexed.No test was added, removed, skipped, or weakened. Passed:
python3 scripts/check_stale_workstream_wording.pypython3 scripts/check_stale_authorization_docs.pypython3 scripts/check_stale_artifact_contracts.pypython3 scripts/check_stale_review_contracts.pypython3 scripts/check_markdown_links.pyPYTHONPATH=. python3 scripts/test_lightweight_agent_gates.pygit diff --checkReviewer results
Docs, senior engineering, QA, and product/operations: PASS. CodeRabbit posted two valid findings; both were repaired and the repair passed focused docs, QA, and product/operations re-review.
CI integrity
No workflow, lane, runner, coverage command, threshold, or package script changed. Hosted checks must pass on exact head
2f94ca77.Risks and follow-up
Historical bodies intentionally retain their original timeline wording, but the historical index prevents them from acting as current authority. REV readiness still does not make its lifecycle available. After this merges, QUAL can be audited separately from current
main.Merge ownership
A maintainer must review and explicitly approve the final exact head. Do not merge until required GitHub checks pass.