Ward Flow — synthetic bed-flow prototype (DRAFT, not for merge)

AGENTS.md

@@ -1007,3 +1007,51 @@ Durable notes for Cursor Cloud agents (see `docs/agents-guide.md` and `docs/test
 - Requires Node >=24.15.0 <25 / npm 11.x (installed via nvm, symlinked to `/usr/local/cargo/bin`).
 - Offline verification: `npm run lint`, `npm run typecheck`, `npm run test`, `npm run verify:cheap`, and `npm run verify:pr-local` all pass without secrets.
 - For authorized GitHub work, use the connected GitHub connector/MCP tools as primary interface (`BigSimmo` write access).
+
+# Commit as you go — the thing that loses work here is interruption, not carelessness
+
+Work sitting uncommitted is the only work this repository can lose. Commit when a change becomes
+coherent, **not when the task ends** — a task in this project routinely spans hours, several agents,
+a blocked gate and four other conversations.
+
+**The trigger to watch is being interrupted, and it does not feel like risk at the time.** The
+observed failure, 2026-08-29: seven files were formatted, the verifying test run was refused because
+another worktree held the machine-wide lock, and attention moved to answering other sessions. The
+files sat uncommitted for an hour, through a dozen unrelated commits, and were found only because an
+unrelated status check happened to list them. Nothing about that hour felt like carrying risk. **The
+work was finished and the mind had moved on — that combination is the hazard.**
+
+## The rule
+
+**Before you turn from your own work to anything else — answering another session, waiting on a lock,
+investigating a tangent, reporting to the user — either commit what you have, or state in your next
+message exactly what is uncommitted and why.** Saying it out loud is what makes it recoverable; a
+silent working tree is not a memory.
+
+- **Commit each coherent unit** — a module and its test, a fix and its proof, a document. Not the
+  whole task.
+- **A formatting pass is a commit**, not a loose end to tidy later. It is the change most often
+  orphaned, because it feels finished the moment it is written.
+- **Waiting is not a reason to hold a commit.** If a gate is blocked, commit the work and record the
+  gate as unrun. An unverified commit is recoverable; an unwritten one is not.
+- **Never `git add -A`** — another agent may share this worktree, and the wildcard commits their
+  in-flight edits under your message.
+- **Mutation testing requires committing first.** Restoring a tracked file with `git checkout --`
+  also discards any uncommitted fix inside it, and `git checkout --` has no effect at all on an
+  untracked file — it leaves the mutation in place and reports an error most drivers never read.
+
+## Why this matters more here than in an ordinary repository
+
+**A worktree under `.claude/worktrees` has twice been removed mid-session on this machine** by
+unrelated cleanup sessions. A commit is what makes that survivable: the branch ref and the objects
+live in the shared repository at the top level, not in the worktree folder, so losing the folder
+costs nothing but a fresh checkout. **An uncommitted file is the only thing that does not survive it.**
+
+## When you genuinely cannot commit
+
+The pre-commit hook refuses whenever other unstaged or untracked files exist under `src/components/`
+or `tests/` — so while a concurrent agent is mid-write, you cannot commit even work of your own that
+is entirely disjoint. That is correct behaviour and must not be worked around.
+
+**When it blocks you, say so in your next message and name the files.** Then commit the moment the
+tree is yours again. The failure mode is not the block; it is forgetting that the block happened.

data/repo-awareness-snapshot.json

@@ -1,8 +1,8 @@
 {
   "version": "repo-awareness-snapshot-v1",
   "captured_revision": {
-    "sha": "59bb01b3e5c6b5c846053d2916d3e780ea38bbb1",
-    "committed_at": "2026-08-27T05:20:05+00:00"
+    "sha": "e5fb7e9909414014187ba0fbbb30531af06e80d9",
+    "committed_at": "2026-08-29T20:40:59+08:00"
   },
   "routes": {
     "modes": [
@@ -893,6 +893,11 @@
         "file": "src/app/mockups/ward-flow/page.tsx",
         "area": "mockup"
       },
+      {
+        "path": "/mockups/ward-flow/board/[unitId]",
+        "file": "src/app/mockups/ward-flow/board/[unitId]/page.tsx",
+        "area": "mockup"
+      },
       {
         "path": "/mockups/ward-flow/capacity",
         "file": "src/app/mockups/ward-flow/capacity/page.tsx",
@@ -928,6 +933,11 @@
         "file": "src/app/mockups/ward-flow/handover/page.tsx",
         "area": "mockup"
       },
+      {
+        "path": "/mockups/ward-flow/morning",
+        "file": "src/app/mockups/ward-flow/morning/page.tsx",
+        "area": "mockup"
+      },
       {
         "path": "/mockups/ward-flow/movements",
         "file": "src/app/mockups/ward-flow/movements/page.tsx",
@@ -938,6 +948,11 @@
         "file": "src/app/mockups/ward-flow/network/page.tsx",
         "area": "mockup"
       },
+      {
+        "path": "/mockups/ward-flow/out-of-area",
+        "file": "src/app/mockups/ward-flow/out-of-area/page.tsx",
+        "area": "mockup"
+      },
       {
         "path": "/mockups/ward-flow/patients/[patientId]",
         "file": "src/app/mockups/ward-flow/patients/[patientId]/page.tsx",
@@ -948,6 +963,16 @@
         "file": "src/app/mockups/ward-flow/queue/page.tsx",
         "area": "mockup"
       },
+      {
+        "path": "/mockups/ward-flow/referrals",
+        "file": "src/app/mockups/ward-flow/referrals/page.tsx",
+        "area": "mockup"
+      },
+      {
+        "path": "/mockups/ward-flow/referrals/new",
+        "file": "src/app/mockups/ward-flow/referrals/new/page.tsx",
+        "area": "mockup"
+      },
       {
         "path": "/mockups/ward-flow/search",
         "file": "src/app/mockups/ward-flow/search/page.tsx",
@@ -968,6 +993,11 @@
         "file": "src/app/mockups/ward-flow/ward/[unitId]/page.tsx",
         "area": "mockup"
       },
+      {
+        "path": "/mockups/ward-flow/wards",
+        "file": "src/app/mockups/ward-flow/wards/page.tsx",
+        "area": "mockup"
+      },
       {
         "path": "/mockups/warning-consolidation",
         "file": "src/app/mockups/warning-consolidation/page.tsx",
@@ -1397,9 +1427,9 @@
     ],
     "counts": {
       "modes": 15,
-      "pages": 195,
+      "pages": 201,
       "product_pages": 55,
-      "mockup_pages": 140,
+      "mockup_pages": 146,
       "redirects": 17,
       "api": 58
     }
@@ -3161,6 +3191,26 @@
         "section": "superpowers",
         "catalogued": false
       },
+      {
+        "path": "docs/superpowers/plans/2026-08-27-ward-flow-phase-6-morning-page.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/plans/2026-08-27-ward-flow-phase-7-front-door.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/plans/2026-08-28-ward-flow-phase-8-distance.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/plans/2026-08-28-ward-flow-ward-board.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
       {
         "path": "docs/superpowers/rag-upgrade/canonical/approval-matrix.md",
         "section": "superpowers",
@@ -3446,6 +3496,26 @@
         "section": "superpowers",
         "catalogued": false
       },
+      {
+        "path": "docs/superpowers/specs/2026-08-27-ward-flow-phase-6-morning-page-design.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/specs/2026-08-27-ward-flow-phase-7-front-door-design.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/specs/2026-08-28-ward-flow-phase-8-distance-design.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
+      {
+        "path": "docs/superpowers/specs/2026-08-28-ward-flow-ward-board-design.md",
+        "section": "superpowers",
+        "catalogued": false
+      },
       {
         "path": "docs/testing.md",
         "section": "root",
@@ -3461,6 +3531,11 @@
         "section": "root",
         "catalogued": true
       },
+      {
+        "path": "docs/ward-flow-autonomous-session-2026-08-28.md",
+        "section": "root",
+        "catalogued": false
+      },
       {
         "path": "docs/ward-flow-clinician-check.md",
         "section": "root",
@@ -3476,6 +3551,31 @@
         "section": "root",
         "catalogued": false
       },
+      {
+        "path": "docs/ward-flow-editing-guide.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-fold-procedure.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-handover-2026-08-28.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-handover-2026-08-29.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-handover-after-phase-7.md",
+        "section": "root",
+        "catalogued": false
+      },
       {
         "path": "docs/ward-flow-phase-2-kickoff.md",
         "section": "root",
@@ -3766,6 +3866,26 @@
         "section": "root",
         "catalogued": true
       },
+      {
+        "path": "docs/ward-flow-phase-8-9-questions.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-phase-8-decisions.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-phase-8-mutation-coverage-limits.md",
+        "section": "root",
+        "catalogued": false
+      },
+      {
+        "path": "docs/ward-flow-phase-9-decisions.md",
+        "section": "root",
+        "catalogued": false
+      },
       {
         "path": "docs/ward-flow-phase-handoff.md",
         "section": "root",
@@ -3867,9 +3987,9 @@
       }
     ],
     "counts": {
-      "documents": 480,
+      "documents": 498,
       "catalogued": 106,
-      "uncatalogued": 374,
+      "uncatalogued": 392,
       "sections": 19
     }
   },

docs/codebase-index.md

@@ -381,7 +381,7 @@ it) from clinical discovery entirely.
 - **Route/role map:** `docs/ward-management-mode-map.md`
 - **Model:** `src/components/ward-management/ward-clock.ts` (the only module that reads the
   wall clock), `ward-model.ts` (domain types only), `ward-eligibility.ts` (the eight
-  placement gates), `ward-sites.ts` (17 sites, 8 emergency departments, 22 units),
+  placement gates), `ward-sites.ts` (17 sites, 8 emergency departments, 23 units),
   `ward-movements.ts` (48 movements, 6 bed releases), `ward-derivations.ts` (shared pure UI
   derivations)
 - **Surfaces:** `ward-management-console.tsx` (command), `ward-management-modes.tsx` (mode
@@ -436,7 +436,63 @@ it) from clinical discovery entirely.
   escalation board and unlike the frozen handover, reads the live `useWardFlow()` clock on every
   render. Renders an explicit "No matches" note rather than an empty table when nothing fits. This is
   the page's own single search composer — Ward Flow routes never mount the shared global shell
-  composer, so nothing else on the page competes with it)
+  composer, so nothing else on the page competes with it), `referrals/referral-intake.tsx` (Phase 7
+  Task 4, spec "The front door": the referral intake form — `/mockups/ward-flow/referrals/new`;
+  one form for every source (community, crisis service, police, ambulance, inter-hospital),
+  phone-first with `min-h-12` tap targets; every picker is a `<select>` derived from a runtime
+  list in `ward-model.ts` (`COHORTS`, `HOME_REGIONS`, `REFERRAL_SOURCES`, `SEXES`,
+  `URGENCY_LEVELS`) or from `wardSites` itself, never a hand-written array; no free-text input
+  anywhere. Dispatches `RECEIVE_REFERRAL` with the fixed `role: "community"`; a reducer refusal
+  surfaces as a visible `Rejection` (`ward-referral-intake-rejection`) rather than being
+  swallowed. Not yet linked from the rail/panel/drawer nav — recorded in
+  `WARD_NAV_INTENTIONALLY_UNLISTED` (`ward-nav.ts`) pending Task 6), `referrals/referral-board.tsx`
+  and `referrals/referral-match.tsx` (Phase 7 Task 5, spec "The front door": the coordinator's
+  referral board and match view — `/mockups/ward-flow/referrals`. The board lists queued referrals
+  first (urgency tier, then longest-waiting first — `referralQueueOrder`, `ward-referrals.ts`),
+  then recently decided ones, with "waiting since" rendered prominently on every queued row
+  (`referralWaitLabel`). Selecting a queued referral opens the match view, keyed on the referral's
+  own id: every unit in the network via `referralCandidates` (never truncated, sorted or ranked —
+  site-table order throughout), each either accepting the referral or carrying its single reason
+  (`matchReason`) — a forensic bed is shown with its own badge and is never offered; an age band
+  with no unit anywhere in the network reads as a structural fact ("No youth unit exists in this
+  network"), never as an operational "no bed available"; a unit that has never confirmed its
+  capacity states that plainly ("has never confirmed its allocatable bed count"), never a
+  fabricated number or a bare zero. Dispatches `ACCEPT_REFERRAL`/`DECLINE_REFERRAL`
+  with role `coordinator`; a reducer refusal (including the failing gate's own name) surfaces as a
+  visible `Rejection` rather than being swallowed. Not yet linked from the rail/panel/drawer nav —
+  recorded in `WARD_NAV_INTENTIONALLY_UNLISTED` (`ward-nav.ts`) pending Task 6),
+  `out-of-area/out-of-area-board.tsx` (Phase 8 Task 5, spec D8-3: the out-of-area ledger —
+  `/mockups/ward-flow/out-of-area`, a `board` entry in `WARD_NAV` beside Handover, Escalation,
+  Discharges, Morning and the referral board. Renders `outOfAreaLedger` (`ward-referrals.ts`) and
+  recomputes nothing: one row per person currently in a bed the invented travel-time table places
+  three hours or more from home or reachable only by air, showing home region, unit, band label and
+  elapsed time since arrival — no countdown, no target, no threshold colour. Entries render in the
+  records' own order with no comparator anywhere in the file; a sort by elapsed time would read as
+  a repatriation ranking nobody has decided. The ledger's two counts are stated as two separate
+  sentences that share no denominator — people out of area, and admissions the table cannot place
+  at all, the second roughly twelve times the first on the seeded records — with no fraction,
+  percentage or progress element permitted by test. Both
+  `INVENTED_OUT_OF_AREA_THRESHOLD_NOTICE` and `SYNTHETIC_TRAVEL_TIMES_NOTICE` are imported from
+  `ward-distance.ts` and rendered whole, above the entries. The only ward screen that reads the
+  admission seed, and it does so as a default parameter: `Admission` is not in reducer state and no
+  event creates or ends one, so the screen states in its own words that the list is seeded and is
+  not a live count),
+  `wards/ward-index.tsx` (Phase 8: the ward index — `/mockups/ward-flow/wards`, a `role` entry in
+  `WARD_NAV` above the single seeded ward example. One page listing every ward in the network,
+  grouped under its health service in `wardServiceOrder` and linking each ward to
+  `/mockups/ward-flow/ward/[unitId]`. It exists because that dynamic route served 23 wards while
+  exactly one — `ward-nav.ts`'s `rph-adult-secure` example — was named by a concrete href anywhere
+  in the source, so 22 ward screens could be reached only by typing an address. Enumerated from the
+  provider's live `units`, never a hand-written list and never `allUnits()` directly
+  (`UNITS_FIXTURE_ALLOWLIST` in `tests/ward-flow-single-source.test.ts`); the service is derived per
+  unit via `siteByCode`, and a unit whose site code resolves to nothing renders in an explicit
+  "Not placed in a health service" group rather than being dropped from every group. Deliberately
+  carries NO bed figure, count, availability or occupancy — an owner decision, guarded by test: an
+  index that grew a bed column would be a second surface answering the capacity board's question in
+  wording that can drift. Nothing sorts, ranks or truncates. The 23-of-23 coverage claim is
+  established in `tests/ward-nav.test.ts` by rendering the page and comparing the links inside its
+  `<main>` against `allUnits()` by set equality — not by that file's source scan, which counts
+  concrete hrefs only and deliberately refuses to read a `.map()` builder as coverage)
 - **State layer (Phase 3):** `ward-flow-provider.tsx` (`WardFlowProvider`/`useWardFlow`, mounted at
   `src/app/mockups/ward-flow/layout.tsx`), `ward-flow-reducer.ts` (the one mutation path),
   `ward-flow-events.ts` (event/role table)
@@ -448,7 +504,9 @@ it) from clinical discovery entirely.
   (both sections and their empty states), `tests/ward-patient-search.test.ts` (`searchMovements`,
   including the closed-movement exclusion proven against both a real and a constructed fixture case),
   `tests/ward-patient-search.dom.test.tsx` (the single-composer shape, live results, and the
-  "No matches" empty state)
+  "No matches" empty state), `tests/ward-referral-screens.dom.test.tsx` (Phase 7 Task 4: every
+  picker offers its full runtime list, no free-text input anywhere, the fixed community role, and
+  the rejection surface on a real reducer refusal)
 
 ### Developer hub (`src/app/mockups/development/`, `src/lib/developer-area/`)
 

docs/design-system/adoption-manifest.json

@@ -626,7 +626,8 @@
         "tests/medication-interaction-surfaces.dom.test.tsx",
         "tests/privacy-ui.test.ts",
         "tests/ui-forms-section-nav.spec.ts",
-        "tests/ui-v2-components.dom.test.tsx"
+        "tests/ui-v2-components.dom.test.tsx",
+        "tests/ward-governance-thin-sample.test.ts"
       ],
       "baseline": {
         "targetLayer": "v2",

docs/outstanding-issues-inbox/354316f3-74f7-4d2b-a3f0-91bac3fb18e6.json

@@ -0,0 +1,14 @@
+{
+  "version": 2,
+  "id": "354316f3-74f7-4d2b-a3f0-91bac3fb18e6",
+  "createdOn": "2026-08-29",
+  "action": "add",
+  "payload": {
+    "pri": "P2",
+    "type": "issue",
+    "summary": "Ward Flow network diagram has no @media print block and prints zero unit nodes",
+    "detail": "Pre-existing, NOT caused by the ward board fold or Phase 8 — recorded before the fold so it is not later attributed to the merge. Found by the Phase 8 visual pass (branch claude/ward-flow-phases-6-7-design, reported DONE_WITH_CONCERNS at 7f2a024b9) and deliberately left unfixed to avoid widening that task's scope. The whole-network diagram renders no unit nodes at print time in either mode, because the component ships no @media print rules at all. This matters more than an ordinary print bug: the ward board branch is building print-time work under decision DB-10 (the printed morning sheet, current at print time), and Ward Flow's stated purpose is to be shown to WA clinicians, where someone will press Print. Owner of the fix is whoever owns DB-10. Ward suite was 898 passed across 62 files with this defect present, so no test sees it — it is only visible by printing.",
+    "source": "WARD - Repo Change session, 2026-08-29, relayed from the Phase 8 visual pass",
+    "issueUlid": "01M15Y9HKFWCJGYBB6Y9Z91JNJ"
+  }
+}

docs/scripts-index.md

@@ -1,6 +1,6 @@
 # Scripts index
 
-Curated map of `scripts/` (278 files) and the `package.json` script surface (280 entries),
+Curated map of `scripts/` (280 files) and the `package.json` script surface (280 entries),
 grouped by purpose. This is orientation, not an exhaustive per-file listing — the authoritative
 command list is `package.json`, and `npm run docs:check-scripts` verifies every `npm run <x>`
 referenced in docs resolves to a real script. `npm run docs:update` refreshes the exact counts above.