docs(M296): three-month-break closeout + M-counter M280→M296#264
Merged
Conversation
…unter M280 -> M296
Operator-directed three-month break begins. V1_004 still open but
empirically narrowed; bench-side smoke confirms non-Coder Qwen3-30B-A3B-
Instruct-2507 emits clean tool_call JSON (categorically different from
Coder family), but bench-level partial refutation: F1 emits 8 Markdown
turns with tool_use_count=0. Second-order constraint identified — apr
code's multi-turn prompt context (rendered history + "### Continue:")
self-recursively reinforces Markdown pattern.
Adds:
- evidence/phase-6/m296-three-month-break-closeout-2026-05-22.md — the
comprehensive resumption-playbook closeout (~3000 LOC).
- evidence/under-contract-30b-instruct-2507-partial-2026-05-22/ — F1
captures from the M294 dispatch (driver_error at turn 8, tool_use=0).
- evidence/under-contract-7b-coder-partial-2026-05-22/ — Qwen2.5-Coder-7B
partial (17/20, 0 oracle_passed, hypothesis-3 refutation evidence).
- evidence/under-contract-30b-sub-bench-b-partial-2026-05-21/ — M291
sub-bench B partial (9 fixtures, pattern-shift evidence).
- evidence/under-contract-30b-instruct-tainted-2026-05-22/ — artifacts
from killed smoke-test interruptions (3 driver_errors due to my kills).
- Various M270/M280-era partial archives backfilled into the repo.
Bumps M-counter M280 -> M296 on all 5 surfaces:
- README.md (At-a-glance table)
- CONTRIBUTING.md (status line)
- docs/specifications/claude-code-parity-apr-poc.md (Status + Completeness header)
- docs/specifications/completeness-assessment.md (H-level stamps)
- docs/specifications/status-snapshots.md (Status snapshot blockquote + Run 1 row)
Adds M296 row + M286-M295 rollup row to docs/specifications/milestones-m101-m111.md.
Three resumption paths scoped in the closeout evidence doc:
(a) investigate render_history + per-turn prompt construction
(b) post-decode Markdown -> tool_call parser in apr code
(c) V1_005 against different model class on Lambda Labs GPU
Project state: no in-flight benches, no orphan processes, book live at
paiml.github.io/claude-code-parity-apr. V1_004 still open.
Doc-drift detector: 17/17 classes clean.
Refs:
- M286 evidence/phase-6/m32d-shipped-2026-05-20.md
- M287 evidence/phase-6/m32d-bench-pattern-2026-05-20.md
- M288-M290 v1004-3knob-{dispatch-recipe,plumbing-shipped}-2026-05-20.md + v1004-followup-snapshot
- M291 v1004-sub-bench-b-pattern-shift-2026-05-21.md
- M292 v1004-agent-text-loop-detector-2026-05-21.md
- M293 + M294 + M295 PR trail (CCPA#259-263)
Co-Authored-By: Claude Opus 4.7 <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.
Summary
Operator-directed three-month break begins. V1_004 still open but empirically narrowed.
Headline finding from this session (M286-M295)
Through 12 PRs across the V1_004 chain, four candidate variables were tested as the load-bearing one behind 0%-tool_call emission on Phase 6 fixtures:
<tool_call>examplesBench-level partial refutation
F1 of the non-Coder Instruct bench:
driver_errorat turn 8, tool_use_count=0, 8 Markdown turns. The smoke-vs-bench divergence surfaces a second-order constraint: apr code's multi-turn prompt context (rendered history with previous turn's Markdown + "### Continue:" suffix) self-recursively reinforces the Markdown distribution even on a finetune that emits tool_call JSON in 1-shot smoke.Three resumption paths
Scoped in
evidence/phase-6/m296-three-month-break-closeout-2026-05-22.md:render_history+ per-turn prompt constructionWhat this PR ships
evidence/phase-6/m296-three-month-break-closeout-2026-05-22.md— comprehensive resumption playbook.gitignore— exclude.claude/runtime artifactsProject handoff state
Test plan
bash scripts/check-doc-drift.sh— 17/17 drift classes cleanpgrepCross-references
evidence/phase-6/m32d-shipped-2026-05-20.mdevidence/phase-6/m32d-bench-pattern-2026-05-20.mdevidence/phase-6/v1004-sub-bench-b-pattern-shift-2026-05-21.mdevidence/phase-6/v1004-agent-text-loop-detector-2026-05-21.md🤖 Generated with Claude Code