Repository navigation
v0.3.6
addE2eToRunTestsScript anchors the E2E marker to a standalone line — fixes the run-tests.sh clobber.
addE2eToRunTestsScript matched its idempotency marker with a substring includes/indexOf. consort's vendored run-tests.sh documents the E2E-assembly contract in a header comment that quotes the marker verbatim in backticks, so the match landed on that prose mention and slice(0, indexOf) truncated the entire primary-suite body (set -e, REPO_ROOT, the pytest + client-vitest blocks), leaving a hollow, always-exit-0 run-tests.sh. Every refreshSurface → enableE2eForProject since that comment landed (consort 0.4.11) re-clobbered it, so the honest-GREEN + deploy-gate verify ran nothing across recent projects — a red suite could sail through acceptance.
Fix: match (and truncate at) the marker as a standalone line (^…$, multiline), never a substring, so a prose mention is ignored and only the real appended block is the boundary. Plus a fail-closed guard: refuse to write a run-tests.sh that drops the REPO_ROOT/pytest/vitest body an original carried. New regression test feeds a template whose header quotes the marker and asserts the primary body survives.