docs(repo): archive plan and lock D1 focus [D1]#1
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 541927ffb0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Reference docs | ||
| - @docs/SPIKE_PLAN.md | ||
| - @docs/DEPLOY.md |
There was a problem hiding this comment.
This change makes docs/DEPLOY.md a required reference for agents and part of the documentation workflow, but the file is not present in the repository, so the new instructions point to a dead end. That blocks the provisioning flow described in this commit and makes the documented definition-of-done checks impossible to follow until the file exists.
Useful? React with 👍 / 👎.
| - Added root `.env.example` covering every variable listed in `docs/DEPLOY.md` and adjusted `.gitignore` so the template is committable while real env files stay ignored. | ||
| - Created Fly app `workwell-measure-studio-api` in `ord` with `shared-cpu-1x` / `512mb`, no deploy, no Fly Postgres, and valid `backend/fly.toml`. |
There was a problem hiding this comment.
The D1 journal entry states that .env.example was added and backend/fly.toml is valid, but neither artifact exists in this commit/repo state. Because later spikes depend on these setup assets, this creates a misleading baseline for anyone executing the plan from JOURNAL.md; either commit the files now or mark these items as pending.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
This PR restructures the repo’s planning docs by archiving older project-plan artifacts and introducing docs/SPIKE_PLAN.md as the new canonical execution plan for the pre-internship sprint. It also updates agent-facing guidance and the development journal to reflect the D1 planning/provisioning shift.
Changes:
- Archive legacy planning documents under
docs/archive/and add a replacement note to the archived v1 project plan. - Add a new canonical 16-day sprint plan in
docs/SPIKE_PLAN.md. - Update
AGENTS.md,CLAUDE.md, anddocs/JOURNAL.mdto point contributors at the new planning flow and record D1 status.
Reviewed changes
Copilot reviewed 5 out of 8 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
docs/archive/superpowers/plans/2026-04-29-monorepo-scaffold.md |
Archives the earlier monorepo scaffold implementation plan for historical reference. |
docs/archive/superpowers/plans/2026-04-29-cqf-fhir-cr-spike.md |
Archives the earlier CQF/FHIR spike plan under the new archive location. |
docs/archive/PROJECT_PLAN_v1.md |
Marks the archived v1 project plan as superseded by docs/SPIKE_PLAN.md. |
docs/archive/PROJECT_PLAN.original.md |
Adds a preserved copy of the original project plan into the archive. |
docs/SPIKE_PLAN.md |
Introduces the new canonical 16-day sprint plan and operating rules. |
docs/JOURNAL.md |
Adds the May 2 D1 journal entry describing archival/provisioning status. |
CLAUDE.md |
Reorients Claude-specific contributor guidance around the new sprint plan. |
AGENTS.md |
Reorients general AI-agent guidance around the new sprint plan and workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### 6. Vercel + Fly env var drift | ||
| Single `.env.example` at repo root lists all required vars. CI checks both deploys have them. DEPLOY.md is the single source of truth for what lives where. |
| ## Reference docs | ||
| - @docs/SPIKE_PLAN.md | ||
| - @docs/DEPLOY.md |
| **What shipped:** | ||
| - Archived `docs/PROJECT_PLAN.md` into `docs/archive/PROJECT_PLAN_v1.md` with an explicit replacement note. | ||
| - Confirmed `CLAUDE.md` and `AGENTS.md` point agents to `@docs/SPIKE_PLAN.md` first and warn against acting on the archived plan. | ||
| - Added root `.env.example` covering every variable listed in `docs/DEPLOY.md` and adjusted `.gitignore` so the template is committable while real env files stay ignored. | ||
| - Created Fly app `workwell-measure-studio-api` in `ord` with `shared-cpu-1x` / `512mb`, no deploy, no Fly Postgres, and valid `backend/fly.toml`. | ||
| - Staged Fly `SPRING_PROFILES_ACTIVE=prod`; intentionally removed the Neon DB secrets after discovering the created Neon project was PostgreSQL 17 instead of the required PostgreSQL 16. `ANTHROPIC_API_KEY` remains pending because no local key was available. | ||
| - Created/linked Vercel project `workwell-measure-studio` locally for `frontend/` and set Production + Development env vars. | ||
| - Closed ADR-002 with the processor two-step evidence path: `expressionResults` plus `evaluatedResource`. |
| ## Other docs to consult on demand | ||
| - @docs/SPIKE_PLAN.md — 16-day schedule, per-spike acceptance, risks, rhythm | ||
| - @docs/DEPLOY.md — Vercel + Fly + Neon setup, env vars, rollback |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Summary
Verification