From cd71b2bbe268c64df91fd32977f4afb1731ac810 Mon Sep 17 00:00:00 2001 From: Lucas Berger Date: Fri, 5 Jun 2026 16:01:46 -0400 Subject: [PATCH] docs(phase-02): record follow-up todos (dev-run docs, traceability, DST spot-check) --- .planning/STATE.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.planning/STATE.md b/.planning/STATE.md index 0a56671..1614c46 100644 --- a/.planning/STATE.md +++ b/.planning/STATE.md @@ -70,7 +70,9 @@ Recent decisions affecting current work: ### Pending Todos -None yet. +- **Fix `docs/deployment.md` local-dev command** — the documented dev run is wrong: the API dev script (`node --watch dist/index.js`) does NOT load `.env`, and `DB_HOST` defaults to `localhost` with an empty password. Correct local-dev command is: `pnpm --filter @familysync/api build && set -a; source .env; set +a && DEV_AUTH_BYPASS=true DB_HOST=localhost pnpm --filter @familysync/api dev` (+ `pnpm --filter @familysync/pwa dev`). Consider adding `--env-file=.env` to the dev script so this is automatic. (Surfaced during Phase 2 UAT.) +- **REQUIREMENTS.md traceability gap** — phase.complete flagged 6 REQ-IDs in the body missing from the Traceability table: CAL-09, CAL-10, CAL-11, CAL-12, DISP-01, DISP-02. Add them to keep traceability in sync (likely Phase 4/5/display requirements). +- **DST spring-forward spot-check (Phase 2)** — recurring/DST is implemented and code-verified (VTIMEZONE before expansion + local display TZ), and operator approved general times; navigating to March 2026 to eyeball the spring-forward transition is a recommended future spot-check. ### Blockers/Concerns