A one-minute-old app's front door leads with a week of zeros and a scary statistic #313

Pushed.

The "This week" card on the studio app page now checks whether the app has any history at all — a shipped change or an agent run, ever, not just in the trailing week — before printing anything. A brand-new app (the exact one-minute-old case in the issue) now shows one quiet line ("Nothing to show yet — it fills in once a change ships or the crew takes a run") instead of Shipped 0 / Runs 0 / Preview … / Spent $0.00; a genuinely quiet week on an app with real history behind it still prints the full panel with zeros, unchanged from before. I kept the card itself rendered rather than removing it, so there's no layout shift.

Two other fixes for the preview-failure line:

• A deploy the forge's own restart cancelled (STOPPED_SUMMARY, #255) is now excluded entirely from previewLatency's failure count and its denominator — it's the forge's own interruption, not the commit's fault. A person's own Cancel still counts.
• The "N of M never reached a preview" ratio now needs at least 5 total deploys behind it (FAILED_RATIO_MIN) before it prints at all, so a young app's first boot or two never reads as a rate ("2 of 2" is gone).

STOPPED_SUMMARY moved from apps/runtime.ts to core/runs.ts so previewLatency could use it without a circular import; both prior importers were updated.

Two existing studio.test.ts fixtures used repos with literally zero history to test "quiet week" wording — that's exactly the bug this issue reports, so I gave them a real (old) run or merge and renamed them to say so. Added new tests for the day-one page (owner and stranger views), the forge-cancelled exclusion, and the low-count threshold. bun x tsc --noEmit and the full bun run check test suite (447 tests) pass.

Closes #274