Repository navigation
Conversation
memory.md presented four checkpoints (#320, #329, #330, #366) as live lanes with open blockers, and named main HEAD as `a9a67422` from 2026-08-03. All four issues closed in August 2026 as implementation history, and main is at `1967a0a1`. The stale table was not merely out of date, it invited the wrong action: an agent reading it would try to unblock work that was deliberately scoped out. The closing notes say so explicitly - #320 is "intentionally not merge-ready" with no native Windows acceptance claimed, and #366's closeout states that closure is not final epic acceptance evidence. Each row now records the closing date and what closure actually meant, and the standing gap - native Windows acceptance - is stated once rather than implied by four blocker lists. The recovery branch table is untouched; all six branches still exist.
|
Warning Review limit reachedNext included review available in 28 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. Your 66 included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Review configuration: ⚙️ Run configurationConfiguration used: Repository: adamgell/cmtraceopen/.coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
Comment |
The same four-row checkpoint table appears here as in memory.md, with the same stale states - all four issues closed in August 2026 as implementation history, with their recorded blockers scoped out rather than resolved. `soul.md` is the identity file, so an agent reading "NOT merge-ready" and "Hold PR until clean" here has the strongest possible reason to believe those lanes are live and need clearing. Rows now carry the closing date and what closure meant, and the standing gap - native Windows acceptance - is stated once.
memory.md told a reader that Theo's docs-audit phases live at `docs/audit-phase2` and `docs/audit-phase3`. Neither directory exists, and neither was ever committed: git log --all --diff-filter=A on those paths returns nothing. The note that the audits happened is worth keeping; the locations are not, because they send a reader looking for something that is not there.
|
Independent verification at this head. The table's facts all hold; one attribution does not, and for a file described as durable facts that is worth one line. Verified:
That last row is the one I most expected to fail - a checkpoint SHA that resolves to nothing is exactly the failure mode of a table like this - and every one of them is a real object. One attribution to correct. The table says of #320:
The words are real, but they are not in a closing note. #320 has 29 comments, the last on 2026-08-03T22:46:41Z, and the issue closed on 2026-08-05T00:47:30Z - two days later, with no comment. The quoted text is from that earlier checkpoint publication, which also ends "This issue remains open." The distinction matters for a fact table: "the project recorded this at closure" and "the issue closed silently and the decision is inferred afterwards" are different statements, and the second is the true one. Suggest something like "the checkpoint comment of 2026-08-03 says … ; the issue closed two days later with no resolution note", and the summary line becomes "closed without resolution notes; the blockers are recorded as scoped out rather than resolved". Everything else in the table is accurate, including the part that matters most: that a closed checkpoint is not a merged one. |
|
These three PRs edit the same small set of files, and two pairs of them collide. Worth knowing before one is merged, because merging any one makes the others conflict. #688 and #679 both edit the same table. Both touch That is the verified-checkpoints table. In Recommendation: #688 as the survivor on that overlap, because its claims are the ones I checked - the four issues are closed on exactly the dates it states, and every SHA it writes resolves to a real commit. #679's unique parts are worth carrying across: its #679 and #696 both edit
Deleting without that note removes the routes and the reason; the note without the deletion leaves thirteen dead entries above a paragraph saying they are dead. They belong together, and whoever lands second should reconcile rather than drop the other. I have not pushed or closed anything here - which survives each overlap is Adam's call. |
|
#679 fixes the same thing — same two files, same four rows — so worth picking one.
They do not approach the correction the same way, and that matters. #679 credits a landing PR per row — "MERGED via #340" — and that is where its open findings are: #340 merged into This PR's table says Whichever lands, the other should close, and the corrected state should not be merged twice into the same table. |
|
Closing as a duplicate of #679, which corrects the same checkpoint tables in |
…#735) Theo's index routed to three docs-audit notes and Roger's to six SCCM notes. Neither staff directory holds anything but its own index, and none of the nine paths appears in any commit on any ref, so every route led a reader to nothing - with no way to tell "not written yet" from "written somewhere else". Roger's index keeps the empty-state line Theo's already carries, so an index with no routes says so rather than looking incomplete. memory.md's docs-audit line is left alone: PR #688 rewrites it.
Documentation only — no behaviour change.
The problem is worse than staleness
memory.mdis described as "durable facts … loaded every turn for this project", and it presented four checkpoints as live lanes:All four closed as implementation history, and the closing notes say the blockers were scoped out rather than resolved. #320's says it is "intentionally not merge-ready" and claims no native Windows acceptance; #366's closeout states that closure "is not final epic acceptance evidence".
So the table did not merely describe the past — it invited the wrong action. An agent reading it would try to clear blockers on work that was deliberately closed, and #329's row in particular reads as an instruction: "hold PR until clean".
Main HEAD was also named as
a9a67422from 2026-08-03; it is1967a0a1from today.Change
One thing this PR does not fix
The same four-row table appears in
.omp/AGENTS.mdunder "Verified Checkpoints (From PM Charter)", with the same stale states. I have not touched that file — it is the operator's context surface rather than repository documentation, and editing it is not mine to do. Whoever owns it should mirror this change.