runPackedContractMatrix: coverage check requires a fixture for app routes, contradicting the docs

[ScriptedAlchemy]

Observed (agent-bundle 105c65d)

contract.ts documents: "Route id -> fixture. Every compiled non-app route on the server must be covered" and "MCP Apps are not registered at this level".

Running runPackedContractMatrix over a packed server with one MCP App (src/mcp/hauler/apps/dashboard.tsx) with fixtures for all six tools only:

Contract matrix reported 1 violation(s) at the packed-stdio proof level.
  - app:hauler/dashboard / coverage: compiled route has no fixture entry

Adding 'app:hauler/dashboard': {} makes it pass, and the report then shows coverage/surface-completeness/sweep: passed for the app (it does read the ui:// resource). So the packed level does cover apps — which is good — but the docs and the ContractMatrixOptions.fixtures comment say otherwise, and ContractRouteFixture has no way to express "resource route, no input" other than an empty object.

Request

• Either exempt app routes from the coverage check at every level, or (better, since the sweep is useful) update the docs to say apps are covered and accept {}.
• Consider a typed { kind: 'resource' } fixture or an apps: 'auto' option so consumers don't have to enumerate app route ids by hand.

Related: cancellation check wording

tool:hauler/hauler_await / cancellation: aborted callTool settled without throwing or rejecting. fired because my fixture aborted at 50ms a call that had already returned (the awaited ticket was finished). That's a fixture mistake, but the message reads like a route bug. If the call settles before abortAfterMs elapses, report not-applicable with reason "invocation completed before abort; use an input that stays in flight" instead of failed.

[ScriptedAlchemy]

Fixed in #417 (squash-merged as c8504ba).

What changed

• Code and docs now agree: MCP App routes are covered at every boundary that registers app resources (packed-stdio, packed-deleted-source, host-install, dev-epoch) — surface-completeness requires the compiled ui:// URI in listResources and sweep reads it — and remain not-applicable at mcp-in-memory.
• New apps: 'auto' | 'explicit' option (default 'auto') on ContractMatrixOptions, PackedContractMatrixOptions, DevEpochContractMatrixOptions, InstalledHostContractMatrixOptions. With 'auto' an app route needs no fixture entry: coverage passes with reason app route auto-covered (apps: "auto"): the sweep reads its compiled MCP App resource URI. — so the app:hauler/dashboard / coverage: compiled route has no fixture entry violation from the report no longer occurs. 'explicit' restores the old requirement.
• Typed { kind: 'resource' } fixture (ContractResourceFixture; ContractRouteFixture.kind?: 'resource') for resource/app routes; legacy {} still accepted; a resource fixture on a tool/prompt route is a coverage failure. The dev-epoch fixture validator accepts kind.
• Cancellation wording: the check now tracks whether the abort timer fired before the call settled. Settled-before-abort → not-applicable with invocation completed before abort; use an input that stays in flight past <abortAfterMs>ms. (your hauler_await case). failed('aborted callTool settled without throwing or rejecting.') is reported only when the abort was delivered while the call was in flight.
• An auto-swept app whose readResource rejects is recorded as an app:<id> / sweep failure inside the aggregated ContractMatrixViolationError (Codex review finding).
• JSDoc in contract.ts, README "Contract matrix" section (per-level app coverage + cancellation paragraphs), and the agent-bundle/test level table state exactly what happens per level. Changeset: .changeset/401-contract-matrix-app-coverage.md (agent-bundle: patch).

Tests (packages/agent-bundle/tests/projection/contract-matrix.test.ts, 8 new; tests/packed-stdio-projection.test.ts updated)

• packed matrix over a server with an app route and no app fixture passes; app reported coverage passed (auto-covered) + surface-completeness + sweep passed — also exercised by the real packed-deleted-source journey, whose fixtures no longer list app:harness/panel
• explicit { kind: 'resource' } accepted for app and resource routes (apps: 'explicit')
• apps: 'explicit' without an app fixture → coverage violation
• rejected auto-covered app read → aggregated sweep failure
• mcp-in-memory keeps apps not-applicable even with apps: 'explicit' and an app fixture
• { kind: 'resource' } on a tool route → coverage violation
• cancellation: settles before abort → not-applicable "invocation completed before abort; use an input that stays in flight"
• cancellation: abort delivered in flight, call settles without rejecting → still failed

CI green on the merged head (Verify, Release gates incl. the packed matrix, Host install proofs, Examples check); Codex reviewed the final SHA with no open threads.