source: .forge/checklists/phase-boundary-checklist.md · generated — edit the markdown, not this file

Empire Teas CRM — Phase-Boundary Checklist

Run once before each delivery phase seals (.claude/rules/tracker.md § Delivery Phase Rules › Sealing a phase), and before /forge-release opens a release. It replaces a full project audit: the CI checks and the mandatory review catch most drift on every PR, and this list covers what they cannot. Keep it short — an item that no longer finds anything is removed, and a new recurring gap is added here, not to a new audit.

Who: the lead, or a developer the lead names. Time: about an hour, at most two. Record: one entry in .forge/engagement-gate-runs.md headed Phase <N> boundary check — <date>, with each item’s result (pass, the fixes made and their PR, or the item carried to .forge/owed.md with an owner). Until that heading exists, every session from two weeks before the phase’s due date opens with a reminder (inject-gate-state.sh).

“Since the last boundary” means since the previous Phase <N> boundary check entry, or 2026-10-05 (the second project audit, .forge/audits/2026-10-05-project-audit-2.md) for the first one.

1. Every decision reached every document (no machine checks this)

  • [ ] List what was decided since the last boundary: new or refined AD rows (.claude/CLAUDE.md, the Date column), PRD revisions and resolved or reopened OQs (.forge/project-prd-history.md), proposal post-issue notes (.forge/client/project-proposal.md header), and lead decisions in .forge/engagement-log.md.
  • [ ] For each one, git grep the wording it replaced, and the AD or OQ id, across .forge/ and .claude/ (the client pack included) and the three app repos’ CLAUDE.md and docs/. Fix every hit that still states the old fact, or add a post-issue note where the proposal states it (.claude/rules/prd.md step 4). Leave dated records as written.

2. The rules are short, current and stated once

  • [ ] Read .forge/active-context.md and .forge/owed.md against tracker.yaml: close finished rows, move stale paragraphs to the engagement log, and give every open row an owner.
  • [ ] For each .claude/rules/*.md, agent and skill file changed since the last boundary (git log --since=<date> --name-only -- .claude): a rule that is wrong is fixed, one stated twice is reduced to one statement and a pointer, and one nothing needs any more is removed (.claude/CLAUDE.md § Compounding Engineering rule 5).
  • [ ] python3 .claude/lib/harness-graph.py --convention — no new unreferenced file, no unlisted skill or command.

3. Live-state copies agree

  • [ ] python3 .claude/lib/check-features-index.py passes, and /forge-doctor reports no drift.
  • [ ] Every feature tracked in this phase only to start early moves on if it is not done: grep -n -E "before Phase <N> seals unless done|through Empire's Phase <N> UAT round" .forge/tracker.yaml lists them (their delivery_phase comments say so — F38-i, and the features started early in Phase 1). A feature whose comment names the UAT round is decided at the end of Empire’s UAT round for the phase, not before (the lead, 2026-11-19), so it can go out in any drop of that round. For each unfinished one: set its delivery_phase to the next phase; move its features.md row to the next phase’s table, its graph node to that phase’s subgraph, and update the Delivery Plan counts and lists; set its spec header’s Delivery phase; and revise every sentence git grep -n 'started early' finds for it (an approved spec by a revision entry, the PRD by a revision in project-prd-history.md). Check that each finished one is in the phase’s acceptance criteria, which is the lead’s rule (2026-11-18; .forge/owed.md), and add any that is missing, with its PRD revision and the client pack, as PRD Rev 100 did.
  • [ ] For each feature done in the phase, the /forge-reflect step that searches for sentences waiting on it was run (its ## Reflect notes say so); if not, run it now — in the harness and in the three app repos’ comments (until <id>, once <id> ships).
  • [ ] The cloud-gated register (.forge/cloud-gated-validation.md) has a §B block for every feature done in the phase, and each open row has an owner before the phase’s UAT.
  • [ ] forge-et-iaac’s dev is reconciled with environments-and-identity.md §4 (the owed.md row names the last commit checked).
  • [ ] The verification matrix in .forge/test-strategy.md § System Verification to V1 Sign-off is current for the phase: each row’s state is updated, and each row due before the phase’s UAT round is either planned into the round’s regression cycle or has an owed.md row with an owner.

4. Exceptions taken during the phase still hold

  • [ ] Review skips and Browser gate: skipped lines on app-repo PRs merged in the phase (gh search prs --repo altrium-io/<repo> --merged ">=<date>" "skip"): each reason still holds, or the work it put off is tracked.
  • [ ] No PR was merged through the admin bypass without its body saying why (.claude/rules/git-conventions.md § Branch Protection).
  • [ ] .trivyignore.yaml in each app repo: no entry expires during the next phase without an owner to renew or fix it.
  • [ ] Known-failure marks in the frontends’ e2e/pageStates.ts / size matrix: each names an open bug, and the bug is still open.

5. Things that expire

  • [ ] Dates that fall due within the next phase: the Entra certificates (environments-and-identity.md §5), the Spring Boot line’s support end (AD #25), the Node and pnpm versions the repos pin, and temporary access grants (repo admin, AWS logins). Each gets an owed.md row with an owner and a date.

6. Lessons

  • [ ] Lessons added in the phase (.forge/lessons.md) each changed a rule, a check or a template, or say why not; the Synced: _pending_ ones are listed for the next upstream harness sync.

Generated from .forge/checklists/phase-boundary-checklist.md by .claude/lib/render-docs-html.js. Markdown is canonical.