feat(dev): add isolated worktree cells

[kyle-compute]

Summary

• add a root scripts/dev launcher that owns one isolated cell per worktree
• start per-cell Postgres and MinIO, run both Alembic trees, and launch the hosted backend and Next frontend
• make process ownership, lifecycle locking, port conflicts, browser origins, readiness, and cleanup explicit
• require one private Clerk development credential file and fail on invalid rendered-app startup
• add a positive cloud-control-plane gate so local cells cannot reach shared Modal state, spawn remote builds, or tear down remote handles

Validation

• 20 passed: launcher, GKE/Modal boundary, and cancellation parity tests
• 5 passed: core cancellation-harvest contract against a core-only migrated Postgres database
• Ruff checks passed for all changed Python files
• Docker Compose configuration validated
• live blank-database smoke ran both migration stacks and backend startup
• invalid Clerk smoke reached the real React route, failed visibly, rejected a concurrent lifecycle command, and left no processes or containers behind

Remaining draft acceptance

• successful sign-in with real Clerk development credentials
• two simultaneously running linked-worktree cells

The broader representative-data and scenario roadmap is in draft PR #1260.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
oddish-app	Ready	Preview	Aug 14, 2026 3:03am

[github-actions]

Oddish preview

Commit: 7fcda4fee4a4cc770c8c8a4b0625a761a29cf554

Surface	Link	Target
Frontend	https://pr-1259.oddish.app	Vercel preview for 7fcda4f
Backend	oddish-pr-1259	oddish-pr-1259
Database	project fhaxbnlqtcjfqjtzmkew	project fhaxbnlqtcjfqjtzmkew

Vercel deployment URL: https://oddish-63kybucrf.oddish.app

Plan:

• Frontend deploy: true
• Backend deploy: true
• Migrations: false

This comment is updated by the PR Preview workflow.