Skip to content

docs(P-022): reconcile the status surfaces with live #261/#250 state (Checkpoint 0) - #348

Open
PhysShell wants to merge 1 commit into
mainfrom
claude/checkpoint-0-execution-ggdagx
Open

docs(P-022): reconcile the status surfaces with live #261/#250 state (Checkpoint 0)#348
PhysShell wants to merge 1 commit into
mainfrom
claude/checkpoint-0-execution-ggdagx

Conversation

@PhysShell

Copy link
Copy Markdown
Owner

Что и зачем

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:

file was now
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)
docs/proposals/P-022-rust-core-migration.md (row 7b, ×2) the #250 roadmap mirror pending reconciliation mirrored in #250's Still missing list
docs/proposals/P-022-rust-core-migration.md (row 8) blocked by #261 — the production OwnIR executable alone that prerequisite (C-5) is satisfied
docs/proposals/P-022-rust-core-migration.md (preferred queue) the spent "bookkeeping step" note the close itself, past tense
docs/proposals/README.md (P-022 index row) the owner closes #261; step 8 (#262) is blocked by #261 alone + the two mirror tails #261 closed completed; #262 next, prerequisite satisfied; both tails mirrored
rust/README.md (own-cli row) #261 261.B — the owner closes the issue #261 261.B landed; #261 closed completed

Note that row 8 keeps #263's baselines are the evidence prerequisite of the cutover decision unchanged — 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.

Тип изменения

  • feat — новая возможность
  • fix — исправление бага
  • docs — документация
  • refactor / chore / test / ci — без изменения поведения

Как проверено

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:

- the Windows output-behaviour change owed at the Rust cutover (surfaced by #261's
  261.B measurement): Rust emits canonical UTF-8 portably, and native-Windows Python
  byte parity is **not** claimed — recorded in #262 as a declared behaviour change
  rather than a parity gap, with #262 the tracker of record;

Stale-anchor greps on this head, over exactly the three files — all zero:

$ F="docs/proposals/P-022-rust-core-migration.md docs/proposals/README.md rust/README.md"
$ for a in "the owner closes #261 by hand" \
           "the owner closes the issue" \
           "blocked by #261 — the production OwnIR executable alone" \
           "the owner closes #261 by hand after review, and that is a bookkeeping step" \
           "the #250 roadmap mirror pending reconciliation"; do
    printf '%2d x %s\n' "$(grep -o -F -- "$a" $F | wc -l)" "$a"
  done
 0 x the owner closes #261 by hand
 0 x the owner closes the issue
 0 x blocked by #261 — the production OwnIR executable alone
 0 x the owner closes #261 by hand after review, and that is a bookkeeping step
 0 x the #250 roadmap mirror pending reconciliation

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 is state=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-diff confirms 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.py
  • ruff check . и mypy
  • python3 scripts/render_checkpoint_status.py --checkcheckpoint status fragments OK: ... in sync with the evidence (rc 0); no docs/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.

Чеклист

  • изменение покрыто тестом/селфтестом (или объяснено, почему нет) — docs-only status reconciliation; the executable check is the reproducible stale-anchor grep set above plus render_checkpoint_status.py --check
  • README/docs обновлены при необходимости — this PR is the docs update
  • коммиты в conventional-commit стиле (feat:, fix:, docs: …) — docs: reconcile the P-022 status surfaces with live #261/#250 state (Checkpoint 0)

Generated by Claude Code

…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
@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 64863cf9-7129-4980-a65a-6a2d933ca9fd


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

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants