train 2026-09-23 → main (v2.9.0 + honesty pass + landing links)

[unfoundbox]

What the 2026-09-23 train carries

Carries the full v2.9.0 release plus the honesty fixes and landing work that followed it:

Release train (fc7c738 + earlier)

• v2.9.0 — version bump, CHANGELOG (2.9.0 section + fresh Unreleased), RELEASE_NOTES_v2.9.0.md. Tagged, GitHub-released, wheel built and verified in clean venv.
• CHANGELOG.md — Keep a Changelog format, seeded from docs: CHANGELOG.md #169's groundwork.
• Full test suite locally: 1057 passed (previously 1 env-only failure whose precondition was a stale Aug-15 \.studio_token file in this checkout — moved aside; suite mints nothing, code is clean).

Honesty pass on served surfaces (cd09b64)

Closes BUILD-PLAN Phase 0.4 as specified — logic-only, no layout churn:

• Cockpit: SPOT_RATES hardcoded spot-rate table (rendered as live quotes) — deleted; rate comes from the API or shows — / hr. The invented 28.4 GiB / L40S VRAM fallback — deleted; real probe data or an honest — / — GiB placeholder, with usable_memory + its source travelling on the recommendation payload (model_recommender.py).
• create.js: API failure no longer fabricates mock_<random> job ids and runs a fake tracker; user gets the failure via a real toast (also fixes 7 pre-existing broken showToast calls — create.html didn't load app.js, so no showToast was ever defined there).
• create.js: invented ~$0.01/~$0.04 — LTX-2.5 · undo byte-exact receipts — removed. The 'undo byte-exact' feature does not exist.
• theme.js: system mode now resolves (dark/light) instead of setting a literal data-theme="system" the CSS ignores. Cockpit gains the guarded prefers-color-scheme block so all three states are real.
• app.js / sidebar.js: invented ~$0.75/hr confirm-dialog copy and L40S label are gone; rate comes from the API at launch, not from a client-side table.

Landing (this commit)

• Nav: Docs and GitHub links with an inline octocat icon; footer carries both alongside the registry stat.
• Footer registry stat is now generated from the committed snapshot via api/registry-stats.js (Vercel serverless fn) + a matching dev-mode vite plugin — same registry.json, so human and product never diverge.
• public/registry-snapshot.json sits in the landing bundle so the number lives with the page that shows it.

Independent pending: deploy story

With the landing moved into the monorepo (e2c86d4, 09-02), the boundary between 'pushed to GitHub' and 'live on Vercel' has been non-obvious. The production Vercel deploy (spacepilot.dev) is 28 days old. Once this train lands, the next step is to either (vercel --prod from landing/) or wire the Vercel project to the landing/ dir in this monorepo so every push to main auto-deploys — a separate follow-up.

Tests

• 1057 passing on Mac (the lone red was environmental: a pre-existing .studio_token in the checkout falsely satisfying the config-isolation precondition; moved aside, suite mints nothing, passes).
• Cross-verified on lenovo (clean clone + venv): the same test file, 5/5 pass.
• CI on main-2026-09-23: pending on this train, will run on push.

Per merge-train rules, the final merge of this PR into main is Saurabh's click.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}