Question
Build ticket (decided by #296): one gating e2e case inherits the launch-benchmark's only real catch — launch a real GitHub repo with a foreign remoteUser uid, end to end.
The retiring CI trend caught exactly one real user-facing bug in its life, #240 (shared-pixi-cache uid mismatch hard-failing the launch) — and it caught it by failing to launch, not by charting. What exposed it was the launch shape, which the gating e2e job's fixture image does not cover: a real repo (blooop/mcp-devtasks) whose devcontainer has a different remoteUser uid and runs pixi install in postCreate.
The slice: add one e2e case that launches a real repo with a foreign uid end to end and gates like the rest of the suite. Reusing blooop/mcp-devtasks is the default (it is the shape that already caught #240); a fixture that pins the same two properties (foreign uid + postCreate exercising the shared pixi cache) is acceptable if a network-fetched repo is judged too flaky for a gate — say which and why in the PR.
Ordering: this blocks the Tier A retirement ticket, so the #240-class coverage never lapses between the bench's deletion and this landing.
Worked via wf-tdd, reviewed via wf-review, per the map's Notes.
Question
Build ticket (decided by #296): one gating e2e case inherits the launch-benchmark's only real catch — launch a real GitHub repo with a foreign
remoteUseruid, end to end.The retiring CI trend caught exactly one real user-facing bug in its life, #240 (shared-pixi-cache uid mismatch hard-failing the launch) — and it caught it by failing to launch, not by charting. What exposed it was the launch shape, which the gating
e2ejob's fixture image does not cover: a real repo (blooop/mcp-devtasks) whose devcontainer has a differentremoteUseruid and runspixi installin postCreate.The slice: add one e2e case that launches a real repo with a foreign uid end to end and gates like the rest of the suite. Reusing
blooop/mcp-devtasksis the default (it is the shape that already caught #240); a fixture that pins the same two properties (foreign uid + postCreate exercising the shared pixi cache) is acceptable if a network-fetched repo is judged too flaky for a gate — say which and why in the PR.Ordering: this blocks the Tier A retirement ticket, so the #240-class coverage never lapses between the bench's deletion and this landing.
Worked via
wf-tdd, reviewed viawf-review, per the map's Notes.