fix: fal probe handles IN_PROGRESS + infra-skip; re-enable live queue leg

[jpr5]

What

Proper fix for the fal live queue-lifecycle drift probe (falQueueLifecycleCanary + the live block in src/__tests__/drift/fal-queue.drift.ts, merged #327), and re-enables the live leg that #330 temporarily descoped. Probe-only — no change to aimock's fal.ts core.

The bug (verified live in CI, root cause)

The probe assumed fal jobs sit in IN_QUEUE long enough to cancel for $0. Funded flux/schnell returns status:"IN_PROGRESS" on the submit envelope immediately. By cancel time the job is running/completed, so fal's cancel envelope is {detail:"..."} — no status field. The live leg hard-asserted typeof cancel.body.status === "string" → AssertionError → the collector could not map it → exit-5 quarantine → the drift-live-pr base step (main's code) went red on every PR. #330 was the fast, reversible descope; this is the proper fix.

The fix

1. Lifecycle — state-agnostic submit → status → CANCEL. Accept any 2xx submit and any valid queued/running/completed status (IN_QUEUE or IN_PROGRESS …), never assert the job is specifically queued. Cancel still fires even if the status poll throws (a job is never left running).
2. Envelope shapes / drift — the cancel assertion now requires only a JSON envelope ({status} or {detail}); precise shape grading is left to triangulate against the mock, so a genuine 2xx-wrong-shape still reports critical drift.
3. Infra-skip (folds in fix: fal drift probe skips on 403/locked/infra instead of poisoning baseline #329, which is being closed in favor of this PR) — 401/402/403 (locked/exhausted) /429/5xx raise a distinguished FalCanarySkip → honest ctx.skip, never an InfraError that quarantines the baseline. Includes fix: fal drift probe skips on 403/locked/infra instead of poisoning baseline #329's fal-canary-skip.test.ts guard tests.
4. Re-enable — removes the FAL_LIVE_QUEUE opt-in gate fix: descope fal live-queue drift leg from CI base (unpoison drift baseline) #330 added; the corrected leg runs live in CI again (still gated on FAL_KEY).

Cost safety

Cheapest reliably-available model (fal-ai/flux/schnell), cancel ASAP, the paid response_url result endpoint is never fetched. Residual: at most one sub-cent generation if the model races to completion before the immediate cancel lands.

Red-green proof (local, drives the real canary + real triangulate)

RED captured against pre-fix probe (origin/main @ d43701c):

× RED(a): IN_PROGRESS submit + {detail} cancel — old assert `typeof cancel.body.status === "string"`
    → AssertionError: expected 'undefined' to be 'string'
× RED(b): 403 user-locked at submit
    → rejects with InfraError: "INFRA_ERROR: fal Queue Lifecycle …" (quarantine-causing, not a skip)

GREEN post-fix (src/__tests__/drift/fal-canary-skip.test.ts, 4/4 pass):

• (a) IN_PROGRESS submit + {detail} cancel → canary handles it, triangulate reports no critical → leg passes.
• (b) 403 user-locked → FalCanarySkip (not InfraError); 401/402 also skip.
• (c) guard: 2xx submit whose envelope diverges from the mock → still critical drift (fix did not swallow genuine drift).

Checks (local)

prettier ✓ · eslint ✓ · tsc --noEmit (tests-inclusive) 0 errors ✓ · test:drift 16 passed / 9 skipped ✓ · full suite 4693 passed ✓ · tsdown build ✓

Live validation (corrected leg against funded fal) = CI drift-live-pr on this PR — see checks below.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KamK73Wu5heLxJEogM6hHC

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@copilotkit/aimock@332

commit: d809d1f