FE-540: Design mode: commitment and exploration

[lunelson]

feat: enter design mode after scope closure

feat: enable design phase closure proposals

feat: support user-forced design closure

add figma captures to design notes

feat: extract phase-close command vocabulary

feat: project shared force-close availability

feat: persist phase-outcome closure basis

feat: cut workflow projection over to durable closure basis

feat: ship explicit phase-close command union

feat: deepen the shared phase-close module

cleanup and sync

[linear]

FE-540 Design mode: commitment and exploration

Implement the second workflow mode on the new turn and knowledge model. The interviewer walks design forks; the observer captures decisions, assumptions, new constraints, and emerging requirements.

Acceptance

• After confirmed scope closure, the interview enters design mode
• Design turns yield coherent commitments and assumptions
• Design mode can propose design closure

[lunelson]

• FE-580: Collapse remaining shared transport and review-status type duplication #45
• FE-579: Greenfield/brownfield first-screen + exploration #44
• FE-545: Local-first storage; npx distribution #43
• FE-578: UI refinements; design adaptations & alignments #42
• FE-543: Expanded rich fixture scenarios + reviews + replannings #41
• FE-574: Knowledge workspace review surface + lifecycle API #39
• FE-573: Project dashboard workflow state #38
• FE-542: Criteria-review mode #37
• FE-568: Requirements-review mode #36
• FE-540: Design mode: commitment and exploration #35 👈 (View in Graphite)
• FE-572: Canonical knowledge model foundation + cutover seam #34
• FE-539: Explicit phase outcomes and scope closure #33
• FE-567: Phase-aware observer extraction #32
• FE-566: Generic knowledge layer schema and sidebar projection #28
• FE-564: Flexible turn-response model #27
• FE-559: Migrate: @anthropic-ai/claude-agent-sdk query() -> @anthropic-ai/sdk client.messages.stream() #25
• FE-538: Entity sidebar (read-only) #24
• FE-537: Observer agent + entity persistence #23
• FE-558: UI foundation: shadcn/ui + Tailwind 4 + AI Elements #22
• FE-557: Spike: observer extraction fidelity #21
• FE-556: Structured interview: client UI #20
• FE-555: Parts-based persistence + context builders #19
• FE-554: Structured interview: scope phase #17
• FE-553: Multi-project routing #16
• FE-541: Rich chat UI with tool calls and reasoning rendering #15
• FE-552: Drizzle ORM and core extraction #14
• FE-544: Turn tree schema and API #13
• FE-535: SQLite foundation and project persistence #11
• FE-534: Walking skeleton SDK to SSE to React #10
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[augmentcode]

🤖 Augment PR Summary

Summary: Adds “design mode” as the next workflow phase after confirmed scope closure and unifies the phase-closing seam (recommended close + user-forced close) across workflow phases.

Changes:

• Introduces shared phase-close command modeling for data-confirmation (discriminated union) plus helpers for parsing, labels, and force-close policy.
• Extends workflow projection to a richer per-phase state (status, closeability, readiness, closureBasis, proposalPending).
• Persists durable closure provenance via phase_outcome.closure_basis + a new Drizzle migration.
• Updates server /chat handling to accept/validate confirm vs force-close commands and to create confirmed outcomes for forced closes.
• Updates workspace UI to render shared workflow summaries for all phases and to expose a design force-close action; phase summary confirmation now works for both scope and design.
• Adds/updates tests across shared, server, and client layers for mode transitions, closure proposals, forced closes, and force-close validation errors.
• Refreshes planning docs and adds design scratch/image notes assets; removes stale spike scripts.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

src/server/app.ts:199-202 — The phase in the confirm-proposed-phase-closure payload isn’t validated/used when resolving confirmationTarget (lookup is only by proposalTurnId). This allows mismatched phase vs proposal metadata and makes the extra field effectively untrusted/inconsistent if a client sends a crafted payload.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

src/client/routes/InterviewWorkspace.tsx:61 — getWorkflowMetaLabel will show “Not yet closeable” for phases whose status is closed (since closeability is false once closed), which is misleading user-facing state. This could confuse users reviewing already-closed phases in the header.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[lunelson]

Merge activity

• Apr 10, 11:44 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 10, 11:52 AM UTC: Graphite rebased this pull request as part of a merge.
• Apr 10, 11:53 AM UTC: @lunelson merged this pull request with Graphite.