Stop raising a second scenario to test the first three tests

The canary walked one path on one machine — a mesh comes up, a module
lands, a consumer gets a credential — and stopped the run if it broke.
That path is exactly what the first three tests of the long run walk,
and the long run finishes them about 160 seconds in.

So the gate cost a whole scenario on every passing run to save roughly
45 seconds on a failing one. A scenario is three machines, one of them a
registry that boots a kernel in order to serve files, which is where the
two minutes went.

The test file stays and still runs when it is named. What is gone is
raising it on the way to everything else.

Measured rather than argued: the canary's scenario took 116s of which
60s was standing up a registry, and the run reached the same assertions
without it.

src/lastrun.ts

@@ -50,15 +50,6 @@ export interface Receipt {
  */
 export const endToEnd = "test/integration/mesh.test.ts";
 
-/**
- * canary is the short run that goes first.
- *
- * One machine, three images, one path walked end to end. **A suite that takes forty minutes is a
- * suite you hear from once a day** — and every fault found on 2026-09-01 would have shown up in
- * the first three minutes of it. Running this first means a broken change costs minutes.
- */
-export const canary = "test/integration/canary.test.ts";
-
 /** Where the receipt lives: XDG state, which is for exactly this — data a tool keeps between runs. */
 export function receiptPath(): string {
   const state = process.env["XDG_STATE_HOME"] ?? join(homedir(), ".local", "state");