55be4f3aa0
Earlier v4 r1 wording implied Postgres would re-enter "with Temporal." That was a false equivalence: Temporal worker (M5-Py) runs against its own backing store (`temporal` namespace) and does not touch `my-deepagent`'s `runs` / `run_phases` / `llm_calls` ORM tables, so M5-Py does not force a DB migration. The actual trigger for Postgres is a *second concurrent writer* on the my-deepagent DB, which first appears with FastAPI in M8-Py (and the later web GUI). SQLite WAL allows only one concurrent writer. Changes: - §1.3 Database: replaced "Postgres parked indefinitely" with explicit migration-trigger table (CLI=1 writer → SQLite; Temporal worker=still 1 writer → SQLite; FastAPI=2 writers → Postgres required). Sequencing: v0.2 PR #1 (Postgres baseline regen) lands ahead of M8-Py for a clean cut. - §22 Decision Log: added DR-2 documenting this correction. - §23 Kickoff Order: inserted "v0.2 PR #1 — Postgres migration" between Step-0-purge and M5-Py; annotated M5-Py and M8-Py with their DB implications. Also clarifies that `temporalio` is listed in plan-v4-draft.md but is not yet pulled into `my-deepagent/pyproject.toml`; install happens with M5-Py. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>