fix(ci): repair the mobile showcase screenshots workflow

[juliusmarminge]

Summary

The Mobile Showcase Screenshots workflow has been failing since #4802 (failed run). Fixing it surfaced one CI bug and two latent startup races in the showcase harness (previously masked by slower runners):

1. Workflow install filter missed the server package. perf(ci): cut stale runs and redundant setup #4802 switched to pnpm install --filter=@t3tools/mobile... --filter=@t3tools/scripts..., but scripts/mobile-showcase.ts boots the T3 server from apps/server/src/bin.ts, whose package is named t3 and is in neither filter graph. The server crashed with ERR_MODULE_NOT_FOUND: @effect/platform-node and both jobs timed out waiting for the server port. Fixed by adding --filter=t3... to both jobs.

2. environment-id read raced server startup. The server begins listening before its ServerEnvironment layer persists userdata/environment-id; the script read the file once right after waitForPort and died with ENOENT on the fast macOS runner. Now polls for non-empty content with the same timeout discipline as waitForPort.

3. Database seeding raced server migrations. seedDatabase deletes from and reseeds projection tables as soon as the port opens, but migrations weren't done yet — no such table: projection_pending_approvals. Now polls sqlite_master for all seeded tables before touching the database.

Verification

Workflow runs dispatched on this branch:

• Run 1 (after fix 1): Android fully green; iOS exposed race 2.
• Run 2 (after fix 2): Android green again; iOS exposed race 3.
• Run 3 (after fix 3, iOS only): ✅ green.
• Run 4 (all platforms): iOS ✅; Android hit an emulator flake (first capture's 'thread' scene never rendered; app bundled but got no data — same commit passed before and after).
• Run 5 (Android only, same commit): ✅ green — confirms run 4 was a flake.
• Run 6 (all platforms, both appearances): ✅ fully green, both artifact sets uploaded (app-store-connect-screenshots 9.7 MB, google-play-screenshots 6.5 MB).

Also passing locally: pnpm --filter @t3tools/scripts typecheck and pnpm --filter @t3tools/scripts test (197 tests).

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e2492ce3-6522-4f31-8ab7-402a97a39444

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. CI/test fixture changes with an unresolved high-severity comment about a potential race condition in the new schema readiness check. The hasSeedableSchema function may return true before all required columns exist, causing seed failures.

^{You can customize Macroscope's approvability policy. Learn more.}

Dismissing prior approval to re-evaluate 6264868

Dismissing prior approval to re-evaluate 0465c85

[macroscopeapp]

🟠 High scripts/mobile-showcase-environment.ts:402

hasSeedableSchema returns true as soon as all nine table names exist in sqlite_master, but it never checks whether the columns that seedDatabase inserts into are present. Columns like projection_threads.runtime_mode, interaction_mode, and model_selection_json are added by later migrations, so if polling observes the database after the tables are created but before those migrations finish, hasSeedableSchema returns true and seedDatabase then fails with a missing-column error. The readiness check should verify the completed migration version or the specific columns required by the seed inserts, not just table existence.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @scripts/mobile-showcase-environment.ts around line 402:

`hasSeedableSchema` returns `true` as soon as all nine table names exist in `sqlite_master`, but it never checks whether the columns that `seedDatabase` inserts into are present. Columns like `projection_threads.runtime_mode`, `interaction_mode`, and `model_selection_json` are added by later migrations, so if polling observes the database after the tables are created but before those migrations finish, `hasSeedableSchema` returns `true` and `seedDatabase` then fails with a missing-column error. The readiness check should verify the completed migration version or the specific columns required by the seed inserts, not just table existence.