docs(P-022): reconcile the status surfaces with live #261/#250 state (Checkpoint 0) - #348
Open
PhysShell wants to merge 1 commit into
Open
docs(P-022): reconcile the status surfaces with live #261/#250 state (Checkpoint 0)#348PhysShell wants to merge 1 commit into
PhysShell wants to merge 1 commit into
Conversation
…Checkpoint 0) After #261 was closed completed, the reconciliation was issue-only, so the git-tracked status surfaces still described #261 as about-to-close and #262 as blocked by it, while the live issues said otherwise. This makes the tree agree with the already-existing live primary state. Docs-only; no Stage-1 implementation and no Stage-1 claim. docs/proposals/P-022-rust-core-migration.md row 7b: "the owner closes #261 by hand" -> #261 closed completed 2026-09-08 (PR #347, 206e9c7); row 7b: both declared-difference tails (invalid UTF-8, Windows A/B/C) now state that #250 mirrors them, replacing "the #250 roadmap mirror pending reconciliation"; row 8: "blocked by #261" -> the #261 prerequisite (C-5) is satisfied; preferred queue: the spent "the owner closes #261 by hand after review, and that is a bookkeeping step" note is replaced by the close itself. docs/proposals/README.md P-022 index row: the same two mirror tails, and "the owner closes #261; step 8 (#262) is blocked by #261 alone" -> #261 closed completed, #262 next with its prerequisite satisfied. rust/README.md own-cli row: "#261 261.B - the owner closes the issue" -> "#261 261.B landed; #261 closed completed". The Windows A/B/C tail may state "mirrored" here only because the concise referential mirror was added to live #250 first and re-read from GitHub to prove it present in primary state, before this tree change was prepared. Historical rationale is untouched: no measurement narrative, no C-1..C-5 recap, no ruling prose, no generated fragment and no other file is modified. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CYLNQy6tLXqsV1CbuNqsSb
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Что и зачем
Checkpoint 0 — a standalone, docs-only repair of drift that already exists on
main. After #261 was closed completed, the reconciliation was issue-only, so the git-tracked status surfaces still describe #261 as about-to-close and #262 as blocked by it, while the live issues say #261 is closed. This makes the tree agree with the already-existing live primary state.It contains no Stage-1 implementation and makes no Stage-1 claim. No code, no fixtures, no workflows, no generated fragments. Three files, status language only; historical rationale (the measurement narratives, the C-1..C-5 recap, the ruling prose) is deliberately untouched.
Ordering note — why the Windows tail may say "mirrored" here. An issue edit and a git commit are not atomic, so a docs commit writing "mirrored" while live #250 still lacked the mirror would re-create the exact drift this checkpoint removes. The concise referential Windows A/B/C mirror was therefore added to live #250 first and then re-read from GitHub to prove it present in primary state; only after that proof was this tree change prepared. The invalid-UTF-8 tail needed no such gate — #250 already carried it.
What changed, by anchor:
docs/proposals/P-022-rust-core-migration.md(row 7b)the owner closes #261 by hand206e9c7)docs/proposals/P-022-rust-core-migration.md(row 7b, ×2)the #250 roadmap mirror pending reconciliationdocs/proposals/P-022-rust-core-migration.md(row 8)blocked by #261 — the production OwnIR executable alonedocs/proposals/P-022-rust-core-migration.md(preferred queue)docs/proposals/README.md(P-022 index row)the owner closes #261; step 8 (#262) is blocked by #261 alone+ the two mirror tailsrust/README.md(own-clirow)#261 261.B — the owner closes the issue#261 261.B landed; #261 closed completedNote that row 8 keeps
#263's baselines are the evidence prerequisite of the cutover decisionunchanged — this PR removes a stale blocker, it does not claim #262 is unconditionally clear.No merge authority is claimed or implied by this PR. Per the standing discipline: open, drive the exact head to a fresh PASS, stop. Merge only under a separate owner instruction bound to the exact reviewed head SHA; a green PR is not merge authority.
Тип изменения
Как проверено
The check for a docs reconciliation is a set of reproducible greps plus a re-read, not "looks right".
Primary-state proof (gates the Windows flip). Live #250 re-read from GitHub after the issue edit; the mirror is present in its Still missing list, and the body is otherwise byte-identical to its pre-edit image:
Stale-anchor greps on this head, over exactly the three files — all zero:
The full anchor is matched for the bookkeeping note rather than the bare word, so a future historical paragraph is not a false trigger. A repo-wide grep for the same anchors also returns zero, so no fourth surface was left behind.
Reconciled phrases present and truthful (each checked against live GitHub, not against prose):
#261 closed completed 2026-09-08 (PR #347, 206e9c7)×1 — live #261 isstate=closed,state_reason=completed,closed_at=2026-09-08T15:18:25Z, closed by PR #347;mirrored in #250's Still missing list×4 — live #250 carries both tails;#261 261.B landed; #261 closed completed×1.Diff review.
git diff --word-diffconfirms the changed words are exactly the status language above and nothing else; markdown table pipe-counts are unchanged on every edited row; only three files are touched.python tests/run_tests.pyruff check .иmypypython3 scripts/render_checkpoint_status.py --check→checkpoint status fragments OK: ... in sync with the evidence(rc 0); nodocs/generated/fragment is touched by this PR.The Python suites were not run locally: this PR changes no Python, no fixture and no generated fragment. CI runs on every push and is the gate.
Связанные issue
Refs #250, #261, #262. Closes nothing — Checkpoint 0 is a precondition for #262's Stage 1, not a step of it.
Чеклист
render_checkpoint_status.py --checkfeat:,fix:,docs:…) —docs: reconcile the P-022 status surfaces with live #261/#250 state (Checkpoint 0)Generated by Claude Code