PR #28709 runtime verification
PR head: 39f99d599f46e2e267671200b6e0c92c94793419
Main: e925dd681904f8a1ead0502ecca3f65f5bc28146
Environment: Linux Blacksmith workers; Node v24.22.2; pnpm v12.14.0.
Both checkouts installed with vp i. All checks ran through blacksmith-check.

Scope: scripts/release-smoke.ts only. No web, desktop, mobile, server,
protocol, or provider behavior changes. No dev server or provider turn was
used because none executes this release-smoke script.

Command: node scripts/release-smoke.ts, with an external fs.rmSync observer
that reads the generated lockfile immediately before the script removes its
temporary directory. The observer changes no fixture content or assertions.
The audit collects importer names from every YAML document in the lockfile.

MAIN OUTPUT
Scope: all 38 workspace projects
Release smoke checks passed.
IMPORTER AUDIT {"expected":40,"resolved":38,"missing":["evals","infra/task-cache"]}

PR OUTPUT
Scope: all 40 workspace projects
Release smoke checks passed.
IMPORTER AUDIT {"expected":40,"resolved":40,"missing":[]}

NEGATIVE CHECK
Temporarily added a committed-lockfile importer named
packages/release-smoke-missing-probe, without a corresponding workspace
package, then ran the unchanged release-smoke script. Restored the lockfile
in finally. The command asserted a nonzero exit and this exact diagnostic:
Error: Release smoke did not resolve workspace packages: packages/release-smoke-missing-probe.
MISSING IMPORTER GUARD: rejected omitted importer as expected

NEIGHBORING BEHAVIOR
The successful complete smoke run also executed its existing assertions:
- Six relay-state-output tests passed.
- Server, desktop, web, and contracts versions became 9.9.9-smoke.0.
- Nightly version, tag, and release name matched expected values.
- macOS updater manifest retained both architectures.
- Windows latest, nightly, and preview updater manifests retained both
  architectures, removed source manifests, and preserved debug manifests.
These are script checks using its existing YAML data, not native OS tests.

LIMITATIONS
No native macOS or Windows installer/updater execution, release publication,
or app/client/provider verification. This PR has no app-reachable flow.
No repository source edits, commits, or pushes were needed.