Skip to content

Release 2.1.210 (2026-08-28)

Bug fixes

  • stage applicator changes before vrg-commit in run_sweep (#2946) run_sweep ran the applicator then invoked vrg-commit without staging, so every real sweep failed with 'no staged changes' (the migration sweep hit this on all 12 repos). The mocked tests hid it because git.run was fully mocked.

Stage the worktree changes with 'git add -A' before vrg-commit, and rename the probe worktree to the repo's issue-- convention (via git worktree move once the issue number is known) instead of the fixed fleet- name.

Add an integration-style test that drives run_sweep against a real throwaway git repo with git.run unmocked, faking only the vrg-* host tools, so the missing-stage regression reproduces the exact production failure and can't return.

Features

  • tighten audit to fenced-only and delete the monolith (#2945) Remove the transitional legacy-superset acceptance arm of _check_gitignore so only a correct base + vergil-managed fence passes, and delete the monolithic src/vergil_tooling/data/gitignore.baseline asset along with its now-dead readers (_load_gitignore_baseline, _gitignore_patterns, _legacy_gitignore_missing, the _GITIGNORE_FENCED_ONLY switch, and the package-data manifest entry).

Freeze the 62 legacy monolith patterns as a literal in the lossless-split invariant test so base + all-fragments is provably equivalent to the old monolith forever: a future fragment edit that drops or invents a pattern now fails CI. Rework the monolith-fixture sync tests to reconstruct an equivalent blob from the module's frozen managed comments and vocabulary, and replace the legacy per-pattern audit tests with fenced-only cases.

Update the config-audit and consuming-repo docs to describe the composed managed fence and fenced-only audit instead of the deleted monolith superset.

Task 10 (final code task) of epic vergil-project/.github#325.

CI Evidence: All gates passed — full audit bundle available. Download →