Nine test files launch in-process persistent contexts or daemons that
default to the SHARED ~/.gstack/chromium-profile. Two concurrent shard
processes on one profile dir kill each other's browser — observed live
on CI once duration packing recomposed shards: handoff's
launchPersistentContext died 'Target page, context or browser has been
closed' (--user-data-dir=~/.gstack/chromium-profile in the call log)
while a sibling shard's daemon logged 'Chromium process crashed'. Hash
sharding had masked the collision by chance placement; handoff passes
standalone everywhere.
Fix at the runner, not per file: each shard child gets
CHROMIUM_PROFILE=<shard-state>/chromium-profile (the documented env
knob, same isolation idea as the existing per-shard TMPDIR). Files
within a shard run serially, so sharing the per-shard profile is safe;
config.test's resolution-order tests save/restore the env around their
assertions.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The version gate caught a live queue collision (its whole job); same
MINOR bump level, next free slot per bin/gstack-next-version.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The sliced lane's first run (PR #2721) did its job: the planner and
report worked, the manifest governed, and every failure had a name.
Three were fixable on the spot:
- executor + gate-census checkouts get fetch-depth: 0 — files with
SELF-derived selection (the LLM-judge map, routing) walk git at
module load, and selection is deliberately fail-closed on git errors,
so the shallow checkout crashed those shards ('ambiguous argument
main...HEAD'). The manifest still governs WHICH shards run.
- landscape --toc gate: the exact toBe(3) landscape-page count was
font-metric-dependent (3 on Amazon Linux, 2 on ubuntu CI — the same
disease the file's own page-index comment warns about). Now a
comparative invariant: --toc must not CHANGE the landscape count vs
a baseline render.
- paid-run-manifest parse test builds its manifest under EVALS_ALL so
it never walks git (proven with GIT_DIR=/nonexistent).
Remaining first-run failures are newly-exposed rot in gate files that
had never executed in CI (skillify D1 refusal, session-intelligence
context-restore, one tpa-apple-ban retry flake) — being probed
separately; they are the lane WORKING, not the lane failing.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Version + release notes for the audit-and-overhaul branch: every
silently-skipping or never-running test class fixed and tripwired, the
free suite duration-packed with the serial mutator shard dissolved, the
paid lane re-platformed onto the sharded runner (planner/slices/
fail-closed report, parity phase), the weekly all-periodic coverage
contract, eval-budget timeout tiers, and 95 new coverage tests.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
