docs: bring the matrix counts and the cursor witness into the prose - #159
Merged
Merged
Conversation
The 0.3.3 figures regenerated to 34 best-effort and 55 detect when cursor's stop cell moved, but the README's alt text and caption still read 33 and 56, so the prose contradicted the image it captioned. The supported-agents table still dated cursor's witness 2026-08-27 rather than the 3.21.18 run. coverage-gaps.md still said fifteen of the sixteen agents had never been witnessed, which the cursor pre_tool and stop witnesses make false, and dialect-families.md counted five grammar renderers two sections after documenting G6. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
jothimani-rajendran
marked this pull request as ready for review
September 23, 2026 20:08
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
2 participants
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 this changes
Documentation only. The 0.3.3 release regenerated the capability-matrix figures when cursor's
stopcell moved from detect to best-effort, but four hand-written passages were never brought along, so the prose now contradicts the data it describes.33 best-effort, 56 detect. The SVG they describe already reads34 best-effort, 55 detect. Corrected to match.2026-08-27. Theverifiedrecord indata/matrix.jsonis nowlive-run-partial · 3.21.18 · 2026-09-23. The row's enforcement cell also now mentions thatstopreturns a follow-up message.pre_toolandstop. Narrowed to fourteen, with cursor's two witnessed gates and its still-openprompt_submitnamed.G6 follow-up message. Now six, G1–G6.No capability claim is widened and no data file changes; this brings the prose up to what the matrix already says.
Claim check
MATRIXrow carries averifiedrecord (version, date, method) — no matrix row changed; the README table now quotes the existing record's datestopbehaviour cited is the existing live witness on 3.21.18 recorded indata/matrix.jsonChecks
pytest -qpasses (1850 passed, 4 skipped)ruff check .andruff format --check .passgit commit -s)Figures were re-rendered to confirm no drift:
git diff --exit-code -- docs/figuresis clean, which is what shows the counts in the images were already correct and only the prose lagged.Notes for the reviewer
The counts were verified by reading the generated SVG rather than by trusting the old prose. Worth considering separately: nothing in CI checks the README's counts against
matrix.py, which is why these drifted while the figure check stayed green.🤖 Generated with Claude Code
https://claude.ai/code/session_01CzNYfzP8ymU3r4JB9Sz8Ha
Generated by Claude Code