fix(cobol): exclude LOCAL-STORAGE from func_start capture (#1890) - #2117
Merged
Conversation
PR #2111's regen (part of the #1892 cobol fix) ran with no universal-ctags binary on PATH, so every language silently degraded to a 2-tool (GitGalaxy + tree-sitter) comparison instead of erroring loudly -- exactly the failure mode docs/self_scan/tri_comparison_README.md already warns about (Ubuntu's arduino-ctags shadows the `ctags` binary name). Concretely this dropped cobol's and fortran's ctags bars/badges entirely (cobol lost its "G" full-precision badge and showed a nonsensical 0/168 precision; fortran's ctags bar vanished and gitgalaxy precision read as degraded), and lost ctags data across every other ctags-covered language in the chart. Regenerated with a real universal-ctags on PATH via tests/tools/tri_comparison_chart.py --all --write and tests/tools/tri_comparison_report.py --write. cobol now correctly shows 168 (up from 148, reflecting the real #1892 recall improvement) against ctags' 241, with the "G" badge restored; fortran is back to its prior 138/138 ctags-matched state. No validated ledger status/verdict was touched by the regen (per tri_comparison_ledger.py's own lifecycle rules) -- only last_seen_count/still_reproduces were recomputed from a live gather, which also self-corrected a separate slip: the #1892 fix commit had hand-set still_reproduces=false on cobol/function/existence/agree[ctags]_vs[gitgalaxy] even though that shape's majority cause (ctags mistagging END-IF as a paragraph) is a permanent, structural ctags limitation that still reproduces. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Gemini/Antigravity had zero guidance on the tri-comparison chart/ledger system, which is exactly how PR #2111's regen shipped without a real ctags binary on PATH and went unnoticed. Adds a full section to ANTIGRAVITY.md (the ctags-binary check, the --all-only write rule, the never-hand-edit-ledger-status rule) mirroring what the tri-comparison-ledger-sweep skill already taught Claude, and adds a pointer from CLAUDE.md's existing tri-comparison section. Both now cite docs/self_scan/tri_comparison_README.md as the single canonical regen doc instead of each carrying its own copy of the procedure. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
… and updated ledger rules
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.
Closes #1890. Prevents LOCAL-STORAGE SECTION from being misidentified as a function.