examples/web-project-deno.json template ships phantom npm:affinescript@^12.1.0, replicated across ≥12 repos — the purge phantoms are still propagating via scaffold

[hyperpolymath]

Claim

The examples/web-project-deno.json template ships npm:affinescript@^12.1.0 — a package that has never existed on npm (404 today, exit-code verified) — and is replicated across ≥12 repos of the #658 cohort. Every scaffold instantiation re-propagates a dead specifier.

Evidence (measured 2026-08-31, during #658 re-verification)

• npm view affinescript version → E404 (controls rescript, zod resolve fine). Same for @affinescript/core, @affinescript/runtime, @affinescript/react, affinescript-tea, cadre-tea-router.
• The template file appears in ≥12 of the 13 repos examined for Deno→Bun: all 30 deno.json locations assessed — 18 blocked on npm packages that do not exist #658; phantom specifiers also linger in accessibility-everywhere/tools/stale/.../react/package.json and stale deno.lock files in 7 repos.
• Root cause chain: the ReScript→AffineScript purge renamed npm packages to names that were never published (see the standing Deno→Bun: all 30 deno.json locations assessed — 18 blocked on npm packages that do not exist #658 blocker — publish / git-path / restore is still an unmade owner decision).

Why this is its own issue

#658 tracks the migration blockage. This is the propagation vector: even if every live manifest is cured, the example template re-seeds the phantom on the next scaffold. Template first, copies second — same lesson as #702.

First step

Fix or delete examples/web-project-deno.json in its template source (and decide whether a Deno example belongs in the scaffold at all, given Deno→Bun); then sweep the replicated copies.

Found while re-verifying #658; filed per the discoveries-become-issues rule.