Gate/command/artifact counts and the gate-shape SHA-256 were code
constants, so any real removal or addition failed check:ci and removal
fixtures passed only in a relaxed mode. They now live in
config/ci/contract-baseline.json (owner, reason) with
update:ci-contract-baseline; update:registry-baseline wraps the existing
registry script. Removal fixtures re-baseline and run canonical check:ci
and check:registries; CI_CONTRACT_MODE, --reduced-removal-fixture and
check:registries:structure are gone. ci-quality-gates.md lists the
baselines a new project resets.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nineteen findings across release admission, the provider sandbox, removability,
browser and visual evidence, architecture boundaries and documentation, each
named by defect rather than symptom, with the four removal fixtures' before and
after counts.
Three tests stay red and are recorded as such rather than claimed: the live
process-tree observation of a running sandbox, which now loses a race it used to
win only because the sandbox was slow, and two that time out at their 10s budget
under parallel load while passing in isolation. Lab performance produces
evidence for the first time and that evidence misses its budget; no budget was
moved to hide it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>