Every open pull's preview is one click from the app's studio page #44

Pushed. The tmp directories weren't cleaned up but they're outside the repo and harmless.

The previous attempt (#29) was parked because its preview deploy crashed at boot with database is at schema 22, this build only knows 21 — the branch had fallen 26 commits behind main and never picked up the schema migrations landed since. This push merges origin/main into the branch, which:

• Brings in migrations through schema 22, fixing the boot crash.
• Resolves the resulting conflict in test/studio.test.ts — two unrelated describe blocks (this branch's previews test and main's "studio home does not wait on the decider" test) had landed on the same line; both are kept intact.
• Removes a duplicate previewEnv import in src/web/pages/studio.ts that the merge introduced (main had already added its own previewEnv import for the unrelated "look" feature).

The actual feature — a Previews card on the app's studio page listing every open pull's preview (host, live/starting/not up state, commit, and any note/error from a still-running or failed check) — is unchanged from #29 and still separate from the asks card, as the original risk note called for.

Verified: bun x tsc --noEmit is clean, the full forge.json check suite passes except the same 6 pre-existing failures (git-auth/posix_spawn) that reproduce identically on unmodified main in a scratch worktree, and a local boot (FORGE_SSH_PORT=0) answers /healthz with 200 — confirming the schema-mismatch crash is gone.

Closes #25

Pushed. Cleaning up the leftover temp clone note for the record — it's outside the repo and harmless, same as before.

Merged main into this branch to resolve the conflict in test/studio.test.ts: both sides had added the same two imports (AppsRuntime and getAppByRepo) independently above the conflict marker, so the conflicting duplicate lines were simply dropped, keeping the single copy of each import already present. tsc --noEmit passes and the full check suite runs clean except for 6 pre-existing failures (git-push-auth errors under this sandboxed shell) that I verified also fail identically on plain main — confirmed unrelated to this merge.