Run: 028 (Vercel Page Audit & Mission #010 Close-Out) · Date: 2026-05-17 · Phase 1 author
The Vercel surface is healthier than the volume suggests: of 85 Next.js pages, only **10 are truly orphaned** from inbound src/ links, and 4 of those (login, auth/callback, archive, listbuild) are legitimately reachable via direct URL / external entry. Of 99 API routes, **~50 have no in-app caller**, but most are webhooks (3), intern-requirements pipeline endpoints (7), and letter-pipeline endpoints (5) consumed by engine/scripts/cron, not orphaned. The 846 static HTML files in `public/` are dominated by `public/crm/` (346) and `public/hrcom/dossiers/` (63) — the dossier duplicates Mission #010 flagged for kill have **not been killed**. Mission #010 is materially complete on shipped artifacts (deal_targets table, SpeakerTranscript, transcript route, three-tab swarm room, Salesfinity hunter rule) but missing two of its named deliverables: `inventory/audit/vercel-kill-list-010.html` was never produced, and `inventory/audit/retirement-log-010.html` was never produced. The five Mission #010 deferred-to-#011 items are **0/5 shipped**: 3 Supabase clients still present (now 5), no `src/lib/http.ts`, 4 of 6 "built-but-unimported" components still effectively dead, no Activity Feed tab on swarm room, no Doppler quote-sweep. BACKLOG MASTER_PLAN.md line 38 correctly flags this as BLK-1 IN PROGRESS — that flag is accurate, not stale.
I judged orphan-ness from src/ link extraction alone. Three blind spots: (1) I did not check `middleware.ts` redirects, sitemap entries, or any external `robots.txt` / OpenGraph paths that might preserve a route's discoverability — a page can be "orphan from src/" but still indexed and bookmarked. (2) The subdomain rewrites in `next.config.ts` (`crm.chapter.guide → /crm/*`, `swarm.chapter.guide → /swarm/*`) mean any file under `public/crm/` or `public/swarm/` is potentially the root of a live subdomain — I cannot tell which of the 346 crm/ files are reachable from `public/crm/index.html`'s navigation without parsing that HTML, and I didn't. (3) I treated "no caller in src/" as an orphan signal for API routes, but webhooks, cron-driven endpoints, and external integrations (Lob, Fireflies, Salesfinity) are called by IPs we don't control. ~12 of the "orphan" API routes are probably live external consumers I'd kill by mistake.
This matches the run #010 pattern Architect originally flagged: "the system was further along than expected; extension, not rebuild" (notebook/2026-05-04__010__vercel-deep-dive.md line 35). Same gap repeated: Mission #010 declared PASS but the named HTML deliverables (`vercel-kill-list-010.html`, `retirement-log-010.html`) never landed, so the close-out verdict was effectively pre-paid on the build artifacts and unpaid on the audit artifacts. Like run #003 (where Mission #003 claimed completion but Stage 2 dial list wasn't yet pushed), the swarm habit of declaring PASS on the runnable subset while leaving the inspection subset as "deferred to handoff script" repeats here. Also matches run #007 where the autopublish-merges-to-main reality was first surfaced — that condition still holds in this run and was correctly excluded from findings per the briefing.
When asked to verdict a prior mission's completion, my old response was to read the notebook's PART 2 verdict and accept its PASS/CONCERNS label. Going forward, I will diff the mission brief's "Required outputs" / "Closing gate" / file-paths against the actual filesystem before accepting any prior verdict — because Mission #010 was marked PASS by audit-quality while two of its named output files were never created.
Generated from 028__architect.md — do not edit this HTML directly.