Skip to content

Pin scb-check 0.1.3 and remove legacy slop rules - #21

Open
Mike-7777777 wants to merge 3 commits into
SprocketLab:mainfrom
Mike-7777777:pin-scb-check-version
Open

Pin scb-check 0.1.3 and remove legacy slop rules#21
Mike-7777777 wants to merge 3 commits into
SprocketLab:mainfrom
Mike-7777777:pin-scb-check-version

Conversation

@Mike-7777777

@Mike-7777777 Mike-7777777 commented Jul 28, 2026

Copy link
Copy Markdown

Fixes #19.

What changed

  • Pin the checkpoint invocation to uvx scb-check==0.1.3 and record scb_check_version in checkpoint metrics.
  • Use the scb-check report as the sole source for verbosity, erosion, clone, and flagged-LOC checkpoint metrics.
  • Delete the in-repository AST-grep runner, rule models, rule YAML files, legacy composite helpers, and rule-specific tests.
  • Remove legacy AST-grep artifacts and fields from quality output, extraction, backfill, consolidation, summaries, dashboards, and the diff viewer.
  • Replace legacy violation trends and checkpoint deltas with scb-check verbosity metrics.
  • Update the metrics and command documentation for the single scb-check path.
  • Add coverage that asserts the exact scb-check==0.1.3 command and recorded version.

Validation

  • uv run pytest -q tests/metrics tests/dashboard/graphs/scatter_test.py tests/entrypoints/commands/test_variance.py tests/entrypoints/commands/test_backfill_reports.py — 482 passed.
  • Exact version test — 1 passed.
  • Full suite — 1663 passed, 21 skipped, 7 infrastructure failures because the local slop-code:python3.12 Docker image is unavailable (exit 125).
  • git diff --check — clean.
  • Repository audit — no remaining references to the removed AST-grep/slop-rule system outside benchmark problem data.

Mike-7777777 and others added 2 commits July 28, 2026 11:13
The composite quality scores come from `uvx scb-check`, which had no
version constraint, so verbosity was computed by whatever release uvx
resolved at run time. On a fixed input, scb-check 0.1.3 reports 2.42x
the verbosity of 0.1.0/0.1.1/0.1.2/0.2.0; erosion is unaffected.

Pin the version at the call site and store it under scb_check_version on
every checkpoint that scb-check successfully measured, so results stay
comparable and past runs stay interpretable. Checkpoints where scb-check
fails keep their existing behaviour and record no version.
@gabeorlanski gabeorlanski changed the title Pin scb-check version and record it with checkpoint metrics Pin scb-check 0.1.3 and remove legacy slop rules Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Quality metrics resolve scb-check at run time with no version pin; verbosity is not reproducible across versions

2 participants