feat(explorer): every gate as a filterable facet (full weakness picture) - #151
Merged
Conversation
The explorer and report showed only atlas findings + mutation; this adds the mechanical check/prove gates (boundary-tests, cover-the-mirror, no-op-paths, pin-values, prove) so the located-issues are the full weakness picture (205 → 266 on the reference run), with a gate facet to filter by any of them. - payload: generalize the per-node located-issues from rk/fg/sf to a `gates` map, keyed by the same gateOf rule the roadmap list uses (mirrored in the payload, that UI one stays canonical), so the explorer's gate names match the list's chips. Every located-issue source is included; mutation and code-map are dropped. - explorer-encode.js: sumGates / issuesUnder / gateList added (unit-tested); the "located issues" color and size honor the active-gate set. - explorer.js: a gate chip row toggles each gate; the KPI and the issues color/size recompute to the active subset; the dock shows the per-gate split. - report.js: the issues column counts every gate. Gates: tsc, eslint, 895 tests (882 pass, +3 for the gate helpers), pdd check all green. Verified live: 266 located issues across 8 gates, toggling a gate off updates the count and the encoding, no console errors. Co-Authored-By: Claude Opus 4.8 <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
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.
The explorer and report showed only atlas findings + mutation survivors. This folds in the mechanical check/prove gates (boundary-tests, cover-the-mirror, no-op-paths, pin-values, prove), so the located-issues are the full weakness picture — and adds a gate facet to filter by any of them.
On the reference run the located-issues go from 205 → 266 across 8 gates.
Design
rk/fg/sfto agatesmap, keyed by the samegateOfrule the roadmap list uses (mirrored in the payload with a note that the UI one is canonical, so the explorer's gate names match the list's chips). Every located-issue source is included; mutation (the coverage axis) and code-map (context) are dropped.explorer-encode.js—sumGates/issuesUnder/gateListadded (unit-tested); the "located issues" color and size honor the active-gate set.explorer.js— a gate chip row toggles each gate on/off; the KPI and the issues color/size recompute to the active subset; the detail dock shows the per-gate split.report.js— the issues column now counts every gate.Gates
tsc·eslint src bin· 895 tests (882 pass, +3 for the gate helpers) ·pdd checkno blocking findings. Verified live against the reference run: 266 located issues across 8 gate chips,color = located issues, togglingriskoff drops the count 266 → 179 and re-encodes, dock shows the per-gate breakdown, no console errors.🤖 Generated with Claude Code