Regenerate tri-comparison chart after dockerfile sweep fixes - #1997
Merged
squid-protocol merged 1 commit intoAug 21, 2026
Merged
Conversation
Dockerfile now earns badges on both Functions Found (71/71**, from #1976) and Classes Found (77/77**, from #1974 -- new manual_verification.json class entry, independently re-verified against real source: all 6 aliased stages in generate-files.Dockerfile, the 1 unaliased fallback in syscall.Dockerfile, and the first/last 5 of daemon.Dockerfile's 69 stages). Args Found correctly drops from 52 (the #1973 bug, now fixed) to 0, matching dockerfile's none-granularity expectation. Also applies a validated verdict to a new ledger shape the regen surfaced: fortran/function/args/agree[ctags,tree_sitter]_vs[gitgalaxy] (init_domain, 1 occurrence) -- the same match.start()-corruption bug already root-caused and filed as #1982 while investigating #1973, just now visible in the ledger's own cross-tool tracking. No credit/ debit -- ctags and tree-sitter are both correctly parsing real Fortran grammar GitGalaxy currently mis-anchors, not corroborating each other by coincidence. Updates docs/language_status/dockerfile.md's §9 to reflect all three follow-on issues (#1972, #1973, #1974) as fixed rather than filed.
Contributor
squid-protocol
deleted the
chore/regenerate-tri-comparison-chart-post-dockerfile-sweep
branch
August 21, 2026 02:46
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.
Summary
Regenerates
docs/self_scan/tri_comparison_chart.svgandtri_comparison_points_of_interest.mdnow that all 5 fixes from this session's dockerfile tri-comparison sweep are merged (#1976, #1980, #1985, #1987, #1988).What changed on the chart
71/71**with a G badge (from Fix dockerfile func_start recall: route to Mode A, not brace search #1976, already reflected before this PR).77/77**with a G badge (was empty before dockerfile has no named class (build-stage) extraction -- class_start regex captures the FROM keyword, not the stage alias #1974 -- dockerfile had no named class extraction at all until this session). Newmanual_verification.jsonclassentry, independently re-verified against real source: all 6 aliased stages ingenerate-files.Dockerfile, the 1 unaliased fallback insyscall.Dockerfile(debian:${BASE_DEBIAN_DISTRO}-slim), and the first/last 5 ofdaemon.Dockerfile's 69 stages all match exactly by direct grep cross-check.52to0-- correctly matches dockerfile'snone-granularity expectation now that Mode A (_slice_by_labels) generic args-count search is unbounded, can attribute unrelated text to a function's parameter count #1973's fix is live (previously an unrelatedARGline could get swept into aRUN's greedy body span and misattributed as its own parameter count).Ledger
Applies a validated verdict to one new shape the regen surfaced:
fortran/function/args/agree[ctags,tree_sitter]_vs[gitgalaxy](init_domain, 1 occurrence). This is the same match-boundary bug already root-caused and filed as #1982 while investigating #1973 -- just now visible in the ledger's own cross-tool tracking since #1973's fix correctly bounds the args search (an unbounded search used to reach the real signature anyway by luck; a bounded one anchored at the same corruptedmatch.start()can't). No credit/debit -- ctags and tree-sitter are both correctly parsing real Fortran grammar that GitGalaxy'sfunc_startregex currently mis-anchors, not agreeing by coincidence.Docs
docs/language_status/dockerfile.md§9 updated to reflect #1972/#1973/#1974 as fixed (with PR links) rather than "filed, no PR yet."Docs-only change (no
.pyfiles touched) -- nocrucible_check.py/golden-master reblessing needed.🤖 Generated with Claude Code