docs: record refactor step D5a (PR #95) and the D4b insertion - #96
Merged
Conversation
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
1 participant
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.
Progress-doc-only PR: CLAUDE.md gains the D5a entry — the frozen exec baseline (77 files, hashes in git, graded provenance), the AST-verified runner catalogue, and the feasibility probe whose result inserts a new migration step D4b (per-symbol streaming materialization). Also records the three vacuous mutations written during that work (two by the implementer, one inside a review suggestion) and corrects a long-standing misdiagnosis in this file: pytest's summary line was suppressed by our own duplicate
-q, not by the environment. Merged-PR list gains #94/#95. AGENTS.md kept byte-identical via cp. No code changes.