Repository navigation
docs: record what became of the self-audit's batch - #397
Merged
Merged
Conversation
The 2026-09-15 closeout, its index line, the audit folder's REVIEW and README, and the ROADMAP row for #339 still described the batch as open and unreleased. v0.26.0 shipped it the next day: sixteen fixed (fourteen with a test that fails on the previous code, #362 pinned at the source, #364 as documentation), #363 closed as designed, #372 delivered as the test-windows job, whose first run confirmed 6.1 and 6.3 (#393, #394), left 6.2 and 6.4 passing, and found eight POSIX-shaped expectations (#395). The Open section now names the Windows batch and the order to take it in. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
What
The repository's own record of the 2026-09-15 self-audit stopped at "nothing was released, #355–#372 open". The next day's v0.26.0 shipped the batch, so this brings the record up to date in the five places that describe it:
docs/history/2026-09-15-self-audit-closeout.md— an Outcome — 2026-09-16 section (what was fixed and how each was proven, Orchestrator write guard is off after a session resume until /codecarto-open #363 closed as designed, the Windows job's first run and what it settled, the two self-corrections fix: lock ticket numbers are bakery numbers, not the wall clock #379 and refactor: the module graph points one way, pinned by a test #391, release verification) and an Open section that names the Windows batch (atomicWriteFile: rename over an existing file fails with EPERM on Windows under concurrent writers #393, Tests: eight expectations assume POSIX paths and fail on Windows #395, Pi write guard refuses a legitimate .codecarto/ write on Windows #394) in the order to take it and the fact that each is proven by thetest-windowslog rather than locally.docs/history/README.md— the index line says where the batch went.self-audit/…/REVIEW.md— an Outcome section mapping the finding IDs to what happened (4.2 → Orchestrator write guard is off after a session resume until /codecarto-open #363 as designed, 5.1 → Child-session guard omits the configured library root its comment claims #364 as documentation, 6.1 → atomicWriteFile: rename over an existing file fails with EPERM on Windows under concurrent writers #393, 6.3 → Pi write guard refuses a legitimate .codecarto/ write on Windows #394, 6.2/6.4 passing on Windows, Tests: eight expectations assume POSIX paths and fail on Windows #395).self-audit/…/README.md— one sentence pointing at it.ROADMAP.md— the Split core/broadside.ts (4,300 lines) into modules #339 row reads Shipped (0.26.0), with Module graph: index.ts <-> dashboard-writer.ts cycle; state.ts imports upward from client.ts #371/refactor: the module graph points one way, pinned by a test #391 done rather than pending.Docs only; suite 939/939 unchanged.
🤖 Generated with Claude Code