diff-integrity.json

{
  "maxRemovedFraction": 0.25,
  "minRemovedCases": 3,
  "perFileMaxRemovedFraction": 0.5,
  "perFileMinRemovedCases": 3,
  "approvedReductions": [
    {
      "path": "tests/ward-pull-vocabulary.dom.test.tsx",
      "before": 16,
      "after": 15,
      "reason": "Deliberate retirement of the one case rendering <WardModeWorkspace mode=\"exceptions\" />, a mode MERGE 01 turned into a redirect. Its two halves went different ways and both were checked before the case was dropped. The vocabulary rule itself (\"Bed pull expired\", never \"Bed hold expired\") was carried onto the live DelaysScreen in 43c56d6c5, with a control proving the mutation fails that one test by name; re-asserting it here would be a second copy of a live pin. The other half asserted the action label \"Reconfirm or release bed pull\", and DelaysScreen offers no per-item action at all by design - its own footer reads \"Nothing on this screen decides anything\" - so there is no control whose wording could be wrong, and pinning the absence of one would fight the next redesign. Whether that lost capability should return is an owner question, flagged to Ward Lead rather than settled by choosing an assertion. NOTE: 1 case of 16 is below this file's own perFileMinRemovedCases floor of 3, so check:diff-integrity would never have demanded this entry - it is recorded because a retirement that leaves no trace is indistinguishable from a deletion nobody noticed, which is the failure this array exists to prevent.",
      "approvedOn": "2026-09-05"
    },
    {
      "path": "tests/ward-capacity-view.dom.test.tsx",
      "before": 7,
      "after": 4,
      "reason": "7 -> 4 as the gate measures it against the merge base; 13 -> 4 across the whole programme, which is the history the rest of this reason tells. NOTE: the previous version of this entry said before=13, and isApproved() matches on EXACT before AND after - so it matched nothing and the gate was passing on the per-file threshold (3 of 7 removed = 0.43, under the 0.5 ceiling) while appearing to be approved. Corrected 2026-09-06 after reading the gate rather than trusting its OK line. AND THE CORRECTION DOES NOT MAKE THIS ENTRY LOAD-BEARING - measured, not assumed: with the entry deliberately mismatched (after=99) and the ceiling untouched, check:diff-integrity prints the same 'OK  7 -> 4' and the same PASS. At 3 removed of 7 the reduction is under the per-file ceiling, so the gate never demands an approval here at all. This entry is a RECORD, exactly as the ward-pull-vocabulary entry above says of itself - a retirement that leaves no trace is indistinguishable from a deletion nobody noticed, which is the failure this array exists to prevent. The numbers are made exact so that it WOULD carry the file if the ceiling were ever crossed, and so no reader is told this was gate-approved when it was merely under threshold. 13 -> 5, across three commits on 2026-09-05 and 2026-09-06. Every retirement was justified by a mutation or by an owner ruling, never by the subject having merely moved. RETIRED, subject moved to ward-screen.tsx at /ward/[unitId] and proved guarded there by mutation: the Confirmed/Expected breakdown replacing the old Potential lump (Confirmed chip reading the Expected field turns 3 ward-screen cases red); the reconciliation identity and its floor (Held chip pointed at capacity.blocked turns 2 red) - note this narrows coverage, since the retired case looped every unit on one board while WardScreen is one ward per route over five rendered units, accepted because no board can check them all at once any more; and a leave bed never folded into Ready plus its fixture assumption (Ready as available+leaveUsable turns 2 red, and the one usable leave bed is on a rendered unit so the mutation was live not inert). RETIRED because the property is now obeyed and guarded on the live capacity screen: the two zero-as-words cases, since capacity-screen.tsx renders a zero ready count as the word and ward-capacity-screen.dom.test.tsx asserts that claim for every row including both directions on the absence. RETIRED ON THE OWNER'S OWN RULING: the six-figure headline that never shows a sum - he was given the recommendation to leave the strip out and took it; the guard protected a structure that no longer exists, and its reasoning is preserved in the file for whoever ever brings a summary strip back. RE-POINTED rather than retired: 'a expected release must never soften Available now' moved to ward-bed-release.dom.test.tsx, and it was a live hole - rendering Ready as available minus expectedToday left 714 tests green across all 41 files that could catch it while two rendered wards genuinely changed from Ready 2 to Ready 1. The five that remain are four live cases against CapacityScreen (Mental Health Act authorisation on the network view, the coordinator's capacity-refresh control, the excluded-beyond-horizon count, and the split fixture assumption) and ONE STILL POINTED AT THE DEAD MODE ON PURPOSE, so the reachability guard keeps reporting this file: a ward's sex mix and specialling headroom as FIGURES on a network view. The sex-mix SIGNAL is built and guarded separately - the screen now says a ward's records are mid-update when its recorded total and occupancy disagree - but whether the underlying figures belong on a network view is a question the owner has not been asked, and building it would answer it on his behalf. Source hashes d86f1549 (ward-screen.tsx), 9e27492d and 83d3160e (capacity-derivations.ts) and 3e379533 (capacity-screen.tsx) before and after the mutations cited. NOTE ON THE PAIR: 13 -> 5 is the CUMULATIVE reduction across three commits, which is what a reviewer needs to see; any single diff the gate computes matches neither end, and all three steps are under the 50% per-file ceiling so it consults no approval at all. This entry is a record, not a gate condition. RETIRED 2026-09-06, the LAST case in the repository rendering a dead WardModeWorkspace mode: \"shows sex mix and specialling capacity per unit row - both directions\". Two things justify it and neither is that the guard was inconvenient. (1) The sex-mix half stopped being an open question: Ward Lead ruled this screen carries the sex-mix SIGNAL and never the FIGURE - RELEASE_BED raises occupancy without being able to say which sex left, so the honest statement is \"this ward's bed records are mid-update\" - and that ruling is BUILT at b98103167 with ward-capacity-sexmix-release.dom.test.tsx guarding the OPPOSITE of what this case demanded, that no sex-mix figure reaches the screen. A case cannot be re-pointed into a screen a ruling has just cleared. (2) Both underlying clinical properties were proved guarded by MUTATION rather than by grep, because a file list containing the word is not evidence: disabling the specialling gate in ward-flow-reducer.ts (if (false && movement.specialling && ...)) turns 5 cases red across 4 files, among them \"refuses the second one-to-one pull, and names specialling rather than 'no bed'\", source hash cf9a0868 identical either side; blinding the sex-mix occupancy in ward-eligibility.ts (sameSexOccupants = 0) turns a long list red across the eligibility and reducer suites, source hash 10a42eda identical either side. The reachability guard itself was then proved still able to fail: reintroducing a dead-mode render turns it red naming exactly that entry, source hash 000ab6ec identical either side. WHAT THIS COSTS, STATED RATHER THAN GLOSSED: a red case forces a question to be answered and a JSON entry does not. Whether a coordinator should see specialling headroom as a NETWORK FIGURE is still an open product question nobody has ruled on, and retiring this removes the thing that kept asking it. It is recorded here, in the test file's retirement note, and in the message that carried it to Ward Lead - three places, because the guard that used to ask is gone. Retired anyway because a permanently red gate is the worse hazard: it stood over a screen no coordinator can open, so it protected nothing, and a gate everybody knows is red is a gate nobody reads when it goes red for a new reason.",
      "approvedOn": "2026-09-06"
    },
    {
      "path": "tests/sources-mode.dom.test.tsx",
      "before": 28,
      "after": 24,
      "reason": "The four `Sources home` cases rendered SourcesHomeClient, the component this change deletes: /sources joined consolidatedModeHomePaths, so its bare path now forwards to the shared home at /?mode=sources instead of rendering a four-card home of its own. Coverage was RE-POINTED, not dropped, and each of the four was checked to a live pin before it was removed. (1) The hero-copy case asserted the title and subtitle, which came from sharedHomePresentation.sources and are asserted against that same source by tests/shared-home-empty-state.dom.test.tsx and tests/ui-copy.test.ts; the shared home renders them for Sources through the identical lookup. (2) The composer-slot case is obsolete rather than moved: it existed because /sources was registered in standaloneModeHomePaths with a hero placement while rendering the catalogue, which mounts no slot, so the shell portalled its search field at a host that did not exist. This change removes /sources from that list, so no hero slot is claimed at that path and there is nothing left to assert. (3) The four-destination case is pinned better than it was: the same four hrefs are the Sources entry of modeSecondaryNavigationRegistry, walked by tests/route-reachability.test.ts's builderTargets and by the mode-nav contract, so they are now proved reachable from the registry that actually renders them rather than from a card list that duplicated it. (4) The suggested-search case moved into the retargeted /sources describe in tests/consolidated-mode-home-redirect.test.ts, which asserts appModeHomeHref('sources', {query, run}) resolves to /sources/search and that the bare path never renders. The user-visible route into the catalogue that the cards used to provide is now the shared home's ShowAllChip, pinned by a new case in tests/ui-sources.spec.ts. NOTE: 4 of 28 is 14%, well under this file's 50% per-file ceiling and the 25% aggregate, so check:diff-integrity would never have demanded this entry — measured, not assumed: the gate prints `OK  tests/sources-mode.dom.test.tsx  28 -> 24` and PASS with or without it. It is a record, on the convention the two entries above set for themselves: a retirement that leaves no trace is indistinguishable from a deletion nobody noticed, which is the failure this array exists to prevent. The numbers are exact so it would carry the file if the ceiling were ever crossed, and so no reader is told this was gate-approved when it was merely under threshold.",
      "approvedOn": "2026-09-06"
    },
    {
      "path": "tests/document-cover-route.test.ts",
      "before": 6,
      "after": 0,
      "reason": "Deliberate retirement of /api/documents/[id]/cover test suite under #HDAP8N. The answer source drawer stopped rendering a front-page thumbnail, leaving useDocumentCoverImageId and this route without product consumers. Both the route and client hook were pruned along with this test suite.",
      "approvedOn": "2026-09-06"
    },
    {
      "path": "tests/use-document-cover.dom.test.tsx",
      "before": 9,
      "after": 0,
      "reason": "Deliberate retirement of useDocumentCoverImageId hook test suite under #HDAP8N. The answer source drawer stopped rendering a front-page thumbnail, leaving useDocumentCoverImageId without product consumers. Hook, route, and DOM tests were retired together.",
      "approvedOn": "2026-09-06"
    },
    {
      "path": "tests/ui-ward-morning.spec.ts",
      "before": 2,
      "after": 1,
      "reason": "MERGE 02 (owner-approved 2026-09-05) folded the morning bed-state board into CapacityScreen and turned /ward-flow/morning into a real HTTP redirect to /capacity, removing the rail's 'Morning bed state' entry at the same time. RETARGETED, not dropped: the render-and-rail test now proves the redirect lands on the real Capacity page and that the rail can leave and return to it, in place of a headline and a link label that no longer exist. RETIRED: the print test, because CapacityScreen carries no print media rule and no per-site print testid at all - capacity.module.css has none - so there is no real print output left to assert against; inventing print assertions for a screen that renders none would fabricate coverage rather than describe it. The underlying MorningPage component and its print CSS are not left unguarded: tests/ward-morning-page.dom.test.tsx still renders MorningPage directly (not via a route) and covers its print label/note and per-site figure grids at the component level (named in morning-page.tsx's own doc comment as still passing all 20 cases), and tests/ward-morning-print.test.ts still guards the CSS text. Only the real-Chromium, real-PDF-page-count proof this browser test gave (page.pdf() measured with pdf-parse) is lost, because no route can mount the component that behaviour belongs to any more. NOTE: 1 of 2 is exactly this file's own perFileMaxRemovedFraction ceiling of 0.5, and the file's case count is below its perFileMinRemovedCases floor of 3, so check:diff-integrity would never have demanded this entry on the per-file rule either - it is recorded on the same convention the entries above set for themselves: a retirement that leaves no trace is indistinguishable from a deletion nobody noticed.",
      "approvedOn": "2026-09-06"
    },
    {
      "path": "tests/ward-ed-legal-clock.dom.test.tsx",
      "before": 4,
      "after": 1,
      "reason": "Task T1 (docs/ward-flow/plans/2026-09-17-build-plan-legal-clinical.md), on owner answer 1, 17 September 2026, quoted verbatim in docs/ward-flow/owner-answers-2026-09-17.md: 'the timer that starts when a patient arrives is separate to forms. One records time in ED and the other is a forms category.' The four cases this file carried all pinned isCommunityFormed/legalClockReference, ed-screen.tsx dating a form clock from formedAt when earlier than openedAt and from openedAt (the department's own arrival clock) otherwise, published as data-community-formed and data-minutes-legal-clock. Both functions and both attributes are deleted by this task, not repaired, because the merge itself is the defect the owner's note names. Nothing here could be corrected forward: the render this file asserted about no longer exists. REPLACED, not silently dropped: the surviving case proves the negative side of the same separation, across every department's board, that neither deleted attribute has quietly come back. The positive side - that the form-expiry line reads only legalForm.dueAt and the access-target line reads only openedAt, each blind to the other's input - is proved instead in the new tests/ward-ed-form-expiry.dom.test.tsx, which this task also adds, plus the re-pointed assertions in tests/ward-legal-clock-needs-written-time.dom.test.tsx (same count, 6 -> 6, behaviour re-pointed at the same property) and tests/ui-ward-roles.spec.ts:429-508 (edited, not run, per this task's own constraints).",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-morning-page.dom.test.tsx",
      "before": 20,
      "after": 0,
      "reason": "Item 41 (owner answer 41, 17 September 2026): the owner approved retiring the Morning screen outright, not merely redirecting it as MERGE 02 (owner-approved 2026-09-05) had done. Commit f530bcd4e4 deletes src/app/ward-flow/morning/page.tsx, all of src/components/ward-management/morning/ (morning-page.tsx, morning-tour.tsx and both .module.css files) and this suite's four sibling test files together, as one deliberately-red commit whose coupled test/nav edits follow in the next commit on this branch. This file's 20 cases rendered MorningPage directly at the component level - print label/note assertions and per-site figure grids - which is exactly the coverage the 2026-09-06 ui-ward-morning.spec.ts diff-integrity entry above named as 'still passing all 20 cases' and relied on as the reason a browser-level retirement was safe. That component no longer exists on disk at all, so there is nothing left for any test to render, and no replacement was asked for: the owner's ruling is that the screen is gone, not moved. Recorded together with the other three morning-family deletions and the ward-override-surfaces.test.ts reduction below because check:diff-integrity's aggregate rule excuses a drop only when every shrunk file in the diff is individually approved here.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-morning-tour.dom.test.tsx",
      "before": 7,
      "after": 0,
      "reason": "Item 41 (owner answer 41, 17 September 2026), same commit and same ruling as the tests/ward-morning-page.dom.test.tsx entry above: the guided tour of the Morning screen is retired with the screen it toured, not repointed. This file's 7 cases rendered MorningTour (src/components/ward-management/morning/morning-tour.tsx) directly; that module is deleted in f530bcd4e4 along with morning-tour.module.css, and no route or surface mounts a replacement tour. The tour was already PAUSED by owner instruction 2026-08-30 and reachable from nowhere under src/ before this deletion (see the now-removed 'paused morning-tour entry stays unreachable' guard in tests/ward-override-surfaces.test.ts), so nothing about this retirement narrows live coverage of a screen a coordinator could still open.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-morning-tour-paused.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Item 41 (owner answer 41, 17 September 2026), same commit and same ruling as the two entries above: these 2 cases asserted the tour's own paused-by-default behaviour (morning-tour.tsx's PAUSED switch, owner instruction 2026-08-30). The component under test is deleted in f530bcd4e4, so the pause behaviour it pinned no longer exists to be paused or unpaused. Nothing replaces it because nothing renders MorningTour any more.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-morning-print.test.ts",
      "before": 8,
      "after": 0,
      "reason": "Item 41 (owner answer 41, 17 September 2026), same commit and same ruling as the three entries above: these 8 cases read morning.module.css's own @media print block directly, as CSS source text (the same pattern tests/ward-handover-print.test.ts and tests/ward-referrals-print.test.ts use for their own stylesheets), guarding the print output tests/ui-ward-morning.spec.ts's 2026-09-06 diff-integrity entry above named as still covered ('tests/ward-morning-print.test.ts still guards the CSS text') after that file's own browser-level print case was retired. morning.module.css is deleted in f530bcd4e4 along with the component it styles, so there is no stylesheet left on disk to read and no print output left to assert against - the same reasoning that entry already gave for retiring the browser-level print case, now completing for the component-level one. The coupled tests/ui-ward-capacity-morning-moved.spec.ts (renamed from ui-ward-morning.spec.ts) drops its WARD-COVERAGE-POINTER to this file in the same change, so no comment is left claiming coverage that no longer exists.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-override-surfaces.test.ts",
      "before": 19,
      "after": 15,
      "reason": "Item 41 (owner answer 41, 17 September 2026): four cases in the trailing describe block 'ward override-surface guard: the paused morning-tour entry stays unreachable from src/' are removed because the file it read no longer exists to be read. That block existed to catch morning-tour.tsx becoming reachable again after being PAUSED by owner instruction 2026-08-30 - it derived MorningTour's exported name from morning-tour.tsx's own AST and asserted zero src/ importers of it, by design a liveness check over a real file on disk. f530bcd4e4 deletes that file outright, so the surface it watched for revival is gone rather than merely still paused, and a guard reading a path that no longer exists would fail by construction, not by finding anything. The morning-tour.tsx entries in ALLOWED_SURFACES_WITHOUT_OVERRIDE_REASON and DISPATCH_CALLS_WITHOUT_A_LITERAL_TYPE are removed in the same change for the identical reason: each named a construction site or dispatch call inside a file that is no longer on disk for the AST scan to find. NOTE: 4 of 19 is 21%, under this file's own 50% per-file ceiling, so check:diff-integrity would never have demanded this entry on the per-file rule - it is recorded on the convention the entries above already set for themselves, and because it is one of the files the aggregate rule below requires to be individually approved.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-cancel-transport-no-bed-held.test.ts",
      "before": 6,
      "after": 6,
      "reason": "T1 (docs/ward-flow/plans/2026-09-17-build-plan-referrals-transport.md), owner answer 30, 2026-09-17: 'Cancelling transport while a bed is held: no automatic rebooking; a person books again.' No case was removed — the file still carries 6 — but the 'control' test (previously named 'cancelling at pulled (no release) still creates the replacement exactly as before') pinned the OLD bed-held behaviour by name: CANCEL_TRANSPORT installing a fresh `-replacement-N` job and both notices containing the word 'replacement'. That behaviour is exactly what owner answer 30 removes, so the test is rewritten deliberately (not silently) to assert the new one: transport becomes undefined, the new STAGE_TRANSITION_BLOCKERS.transportCancelled blocker is set, and neither notice mentions a replacement. Recorded per this file's own task-rule 'record every rewritten test in diff-integrity.json', matching the convention the entries above already set for themselves: a rewrite that leaves no trace is indistinguishable from a test that quietly stopped meaning what it says. before=after so check:diff-integrity's count-based gate would never have demanded this entry on its own.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-flow-reducer.test.ts",
      "before": 68,
      "after": 68,
      "reason": "T1 (docs/ward-flow/plans/2026-09-17-build-plan-referrals-transport.md), owner answer 30, 2026-09-17. No case removed. 'cancels a transport job without closing the movement' pinned the OLD bed-held CANCEL_TRANSPORT behaviour: it accepted whatever id the reducer wrote for `updated.transport` (which used to be a fresh `-replacement-1` job) and then dispatched TRANSPORT_ACCEPTED directly against it, expecting that to succeed outright with no booking step in between. Owner answer 30 removes the replacement job, so `updated.transport` is now undefined and a bare TRANSPORT_ACCEPTED correctly refuses (`cannot accept transport at the movement's current stage`, the exact rejection this task's own test run first surfaced). Rewritten deliberately to assert the new state (transport undefined, the new STAGE_TRANSITION_BLOCKERS.transportCancelled blocker) and to insert the BOOK_TRANSPORT step item 30 now requires before TRANSPORT_ACCEPTED can succeed again, proving the same widened-to-handover_ready booking path tests/ward-transport-cancel-no-rebook.test.ts covers, from the seeded fixture rather than a hand-built one.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-audit-engine-fixes-2026-09-16.test.ts",
      "before": 16,
      "after": 16,
      "reason": "T1 (docs/ward-flow/plans/2026-09-17-build-plan-referrals-transport.md), owner answer 30, 2026-09-17. No case removed. 'Fix 7: CANCEL_TRANSPORT copies bookedBy onto the replacement job' tested a 2026-09-16 fix whose entire premise — a replacement job existing for `bookedBy` to be copied onto — owner answer 30 removes outright (no branch of CANCEL_TRANSPORT installs a replacement any more). The identity check Fix 7 actually protected (a ward may cancel a job it booked, checked against `transport.bookedBy`) is untouched by owner answer 30 and stays covered by the first cancel in the rewritten test; the second cancel, which used to succeed against the replacement job, now correctly refuses with 'has no transport job to cancel', matching the no-bed-held branch's own long-standing 'refuses a second cancel' case in tests/ward-cancel-transport-no-bed-held.test.ts. Describe block title and 'Fix 7' numbering kept unchanged, matching this file's own header rule that its describe blocks number the 2026-09-16 audit brief exactly; a SUPERSEDED comment above the rewritten case records why its assertions changed.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/ward-route-component-binding.test.ts",
      "before": 41,
      "after": 40,
      "reason": "Item 41 (owner answer 41, 17 September 2026), found on the fix line after the z13 fold (ceb663ff72): PINNED carried a `morning: \"redirect:/ward-flow/capacity\"` row from the 2026-09-05 MERGE 02 fold, when /ward-flow/morning was still on disk as a redirect()-only stub. Item 41 deleted that route's page.tsx outright rather than leaving it as a redirect, so routeFiles()/componentRenderedBy() no longer find any morning entry in `found` at all - the row had become a pin watching nothing, which is exactly the second half of this file's own 'has a pinned row for every route on disk, and no row for a route that is gone' assertion. The it.each-generated case 'route morning renders redirect:/ward-flow/capacity' is not repaired or re-pointed, because there is no route left for any assertion to be true or false about; it is dropped, and the PINNED row it read is removed with it. Nothing about this narrows coverage of a live screen: /ward-flow/morning does not exist for a coordinator to reach, so no binding is left unguarded. NOTE: 1 of 41 is 2%, far under this file's own perFileMaxRemovedFraction ceiling of 0.5 and perFileMinRemovedCases floor of 3, so check:diff-integrity would never have demanded this entry - it is recorded on the convention the entries above already set for themselves: a retirement that leaves no trace is indistinguishable from a deletion nobody noticed.",
      "approvedOn": "2026-09-17"
    },
    {
      "path": "tests/playwright-pr-shards.test.ts",
      "before": 9,
      "after": 0,
      "reason": "PsychSift retirement batch 1 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 to remove the code left over from PsychSift. This PsychSift test only exercised a PsychSift design-study page or component retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ui-accessible-table-mockup.spec.ts",
      "before": 1,
      "after": 0,
      "reason": "PsychSift retirement batch 1 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 to remove the code left over from PsychSift. This PsychSift test only exercised a PsychSift design-study page or component retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ui-document-image-status-mockup.spec.ts",
      "before": 1,
      "after": 0,
      "reason": "PsychSift retirement batch 1 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 to remove the code left over from PsychSift. This PsychSift test only exercised a PsychSift design-study page or component retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ui-v2-answer-safety.dom.test.tsx",
      "before": 73,
      "after": 0,
      "reason": "PsychSift retirement batch 1 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 to remove the code left over from PsychSift. This PsychSift test only exercised a PsychSift design-study page or component retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ci-audit-contracts.test.ts",
      "before": 24,
      "after": 0,
      "reason": "PsychSift retirement batch 2 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 that Railway should not be connected to this local project. This PsychSift test only checked the Railway deploy settings or the Railway webhook retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/railway-config.test.ts",
      "before": 9,
      "after": 0,
      "reason": "PsychSift retirement batch 2 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 that Railway should not be connected to this local project. This PsychSift test only checked the Railway deploy settings or the Railway webhook retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/webhooks-railway-route.test.ts",
      "before": 4,
      "after": 0,
      "reason": "PsychSift retirement batch 2 (docs/ward-flow/plans/2026-09-25-psychsift-retirement.md), owner instruction 25 Sep 2026 that Railway should not be connected to this local project. This PsychSift test only checked the Railway deploy settings or the Railway webhook retired in the same batch; nothing Ward Flow keeps loads, names or visits it. Recover from git history if PsychSift is ever needed again.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ward-morning-rollup.test.ts",
      "before": 23,
      "after": 11,
      "reason": "1b1c5bb2ba (22 Sept) replaced this file with reducer tests for CONFIRM_MORNING_ROLLUP and SEND_WARD_BUZZ. The ward-morning-rollup.ts derivation tests it deleted were restored unchanged on 2026-09-25 as tests/ward-morning-rollup-rules.test.ts, so no coverage is lost; this entry records the move.",
      "approvedOn": "2026-09-25"
    },
    {
      "path": "tests/ui-ward-forced-colors.spec.ts",
      "before": 8,
      "after": 7,
      "reason": "Josh chose \"Retire\" (decision card, project chat, 25 Sept 2026 16:39 UTC) for the check \"does repointing --ward-border under forced colours change what is painted?\". Since 5 Sept a shared token layer sets --ward-border and --ward-divider to the same value on every Ward Flow screen (measured 26 Sept on 662eca1656: both rgba(22,30,40,0.11) normally and both CanvasText under forced colours on search, handover and discharges), so the check could only report \"identical\" and measured nothing; since 22 Sept the search screen also paints no visible --ward-divider border for it to find. Archived word for word with the reason and measurement in docs/history/archive/retired-tests/2026-09-26-forced-colours-ward-border-probe.md.",
      "approvedOn": "2026-09-26"
    },
    {
      "path": "tests/document-flow-routes.test.ts",
      "before": 4,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/document-flow-routes.ts (dead DOCUMENT_SEARCH_ROUTE/DOCUMENT_READER_ROUTE href builders for the no-longer-existing document search modes); its only real importers were app-modes.ts (retired in the same batch) and this test.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/search-navigation-context.test.ts",
      "before": 7,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/search-navigation-context.ts, part of the dead app-modes/tools-catalog/search chain; its only real importer chain was app-modes.ts/document-flow-routes.ts, both retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/search-scope.test.ts",
      "before": 15,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/search-scope.ts, part of the dead app-modes/tools-catalog/search chain; its only real importer was search-navigation-context.ts, retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/owner-scope.test.ts",
      "before": 8,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/owner-scope.ts. owner-scope.ts was the only real caller of env.ts's isDemoMode()/isLocalNoAuthMode() anywhere in src/ (confirmed by rg), so its retirement is what made src/lib/env.ts itself (S-D2) safe to delete in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/catalog-search.test.ts",
      "before": 17,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/catalog-search.ts (ranking/normalising helpers for the dead Tools catalogue search); its only real importer was tools-catalog.ts, retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/catalog-search-drug-name-regression.test.ts",
      "before": 2,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted alongside src/lib/catalog-search.ts, which it exclusively covers a drug-name regression for.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/result-filter-url.test.ts",
      "before": 8,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/result-filter-url.ts, whose only real importer was this, its own dedicated test; orphaned PsychSift search-result code, not reached by any surviving route.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/result-sort.test.ts",
      "before": 3,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/result-sort.ts, whose only real importer was this, its own dedicated test; orphaned PsychSift search-result code, not reached by any surviving route.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/copy-button.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/components/ui/copy-button.tsx, whose only real importer was this test; copy-button.tsx was also the sole real importer of the dead src/lib/ui-copy.ts copyButton export, retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/ward-flow-sandbox.test.ts",
      "before": 4,
      "after": 2,
      "reason": "Two separate reductions since the merge base, both intentional. 4 -> 3 predates this batch (an earlier commit already dropped \"the developer-hub panel says what it is\" case, leaving 3 cases in the working tree before this batch touched the file). 3 -> 2 is this batch: PsychSift leftover retired (Josh, full permission 26 Sept 2026) removed the \"has no clinical tools-catalogue entry\" case and its toolCatalogRecords import, because src/lib/tools-catalog.ts — the only thing that case exercised — was retired in the same batch (S-B1). The two surviving cases (developer-gated prefix list membership; old ward-management route directory is gone) are untouched.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/design-token-contract.test.ts",
      "before": 35,
      "after": 33,
      "reason": "Two separate reductions since the merge base, both intentional. 35 -> 34 predates this batch (an earlier, 26 Sept commit already dropped the factsheet categoryTheme case, per this file's own \"went with PsychSift's factsheets\" comment). 34 -> 33 is this batch: PsychSift leftover retired (Josh, full permission 26 Sept 2026) removed \"declares no semantic member on the CategoryAccent union\", which read src/lib/category-identity.ts by path — that file was retired in the same batch (S-B1), zero real importers of any export (confirmed by rg). The surviving case in this describe block ([data-category-accent] rules in globals.css) does not reference category-identity.ts and is untouched.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/source-badges-off-vocab.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/components/primitive-recipes/clinical.tsx (SourceDesignationBadge/SourceStatusBadge/SourceProvenance/StatusDotMarker and the sourceCard/sourceCapsule* recipes), whose only real importer was this test; ui-primitives.tsx's `export * from \"./primitive-recipes/clinical\"` line was dropped in the same commit.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/source-metadata.test.ts",
      "before": 12,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/source-metadata.ts (clinical source designation/tier classification), whose only real importers were clinical.tsx and source-authority-registry.ts, both retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/source-metadata-browser-safety.test.ts",
      "before": 5,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/source-metadata.ts, alongside its sibling tests/source-metadata.test.ts.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/env-demo-mode.test.ts",
      "before": 6,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/env.ts. env.ts's isDemoMode()/isLocalNoAuthMode() had zero real callers left in src/ once owner-scope.ts (S-B1) was retired in the same batch; src/app/mockups/layout.tsx already carries its own inline mockupsEnabled() and says by its own comment that env.ts's full server contract \"belonged to PsychSift and went with it\".",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/env-mockups-gate.test.ts",
      "before": 4,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/env.ts, for the same reason as tests/env-demo-mode.test.ts.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/env-sentry.test.ts",
      "before": 5,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/env.ts; requireSentryEnv() had zero application callers, only this dedicated unit test.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/env-query-hash-secret.test.ts",
      "before": 2,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/env.ts; requireQueryHashSecret() had zero application callers, only this dedicated unit test.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/env-answer-feedback-warning.test.ts",
      "before": 3,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/env.ts; warnAnswerFeedbackDisabled() had zero application callers, only this dedicated unit test.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/supabase-project.test.ts",
      "before": 9,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/supabase/project.ts (checkSupabaseProjectConfig/assertExpectedSupabaseProjectConfig), whose only real application caller was src/lib/env.ts, retired in the same batch.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/upload-ingress-limits.test.ts",
      "before": 1,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with src/lib/upload-limits.ts (MAX_UPLOAD_MB_CEILING), whose only real importer was env.ts's dead MAX_UPLOAD_MB field, retired in the same batch; next.config.ts's proxyClientMaxBodySize is a literal \"151mb\" and was left unchanged per instruction.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/tsx-server-only-runner.test.ts",
      "before": 4,
      "after": 3,
      "reason": "This reduction since the merge base predates this batch and is recorded here only because this batch's edit touches the same file: an earlier, 25 Sept commit already removed the \"boots the worker image from the server-only-safe esbuild bundle\" case (per this file's own comment, worker/**/Dockerfile.worker/build-worker.mjs went with PsychSift that day), leaving 3 cases before this batch started. This batch's own edit does not change the case count: PsychSift leftover retired (Josh, full permission 26 Sept 2026) dropped only the env.ts `import \"server-only\"` assertion inside the surviving \"keeps the Next server-only marker\" case (src/lib/env.ts was the only file in src/ with that import, and it was retired in the same batch), keeping that case's other assertion on scripts/register-server-only.mjs intact.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/repo-hygiene.test.ts",
      "before": 57,
      "after": 0,
      "reason": "PsychSift leftover retired (Josh, full permission 26 Sept 2026). Whole file deleted with scripts/check-env-parity.mjs and the check:env-parity npm script; this file is entirely env-parity cases (imports only from check-env-parity.mjs) and the script is pinned to the live Railway project and PsychSift's GitHub secrets, and reconciles the env.ts schema retired in the same batch (S-D2).",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/safe-bold.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Owner-approved PsychSift retirement: exact fourteen-file list approved in the acting Codex chat on 27 September 2026. Dedicated tests retire with their unused implementation; no remaining Ward runtime or test consumer was found. Backup: backup/20260927-psychsift-orphans.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/bounded-ttl-cache.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Owner-approved PsychSift retirement: exact fourteen-file list approved in the acting Codex chat on 27 September 2026. Dedicated tests retire with their unused implementation; no remaining Ward runtime or test consumer was found. Backup: backup/20260927-psychsift-orphans.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/restore-focus-unless-moved.dom.test.tsx",
      "before": 3,
      "after": 0,
      "reason": "Owner-approved PsychSift retirement: exact fourteen-file list approved in the acting Codex chat on 27 September 2026. Dedicated tests retire with their unused implementation; no remaining Ward runtime or test consumer was found. Backup: backup/20260927-psychsift-orphans.",
      "approvedOn": "2026-09-27"
    },
    {
      "path": "tests/developer-area-route-guard.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Josh asked on 28 September 2026 for the Ward Flow developer key to be removed. The key gate, its key screen, the signed-cookie helpers (link-access*.ts) and DeveloperAreaRouteGuard went together: the route guard only existed to re-run the key check on client navigation inside the gate, and its sole importer was the deleted gate. This file tested only that guard.",
      "approvedOn": "2026-09-28"
    },
    {
      "path": "tests/ward-legal-limits-not-checked.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Josh requested the removal of the Mental Health Act disclaimer notice ('Not legally checked: these Mental Health Act time limits are typed in and have not been checked against the Act by anyone with legal knowledge. Do not rely on them.') from the top and bottom of all pages across the prototype, and the removal of tests asserting that text. This suite enforced the disclaimer notice presence across ward screens and is retired per request.",
      "approvedOn": "2026-10-04"
    },
    {
      "path": "tests/ward-referral-destinations.dom.test.tsx",
      "before": 25,
      "after": 10,
      "reason": "The 15 removed cases drove the retired full-page New referral form (referral-intake.tsx), deleted with Josh's approval on 8 Oct 2026 when the referral slide-out (option B) became the only place a referral is written. Destination rules the slide-out still has are kept here and in tests/ward-referral-drawer-sheet.dom.test.tsx.",
      "approvedOn": "2026-10-08"
    },
    {
      "path": "tests/ward-top-25-master-list.test.ts",
      "before": 24,
      "after": 0,
      "reason": "Josh approved deleting the hidden Sovereign showcase (/ward-flow/sovereign, sovereign-showcase-screen, top25/ward-top25-cockpit and ward-top25-features.ts) once the Top 25 items moved into the real screens behind their top25-* flags, 15 Oct 2026. This file tested only the showcase helpers in ward-top25-features.ts. Items carried into real screens are covered by the focused tests each Top 25 worker added beside the real module.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-top-25-master-list.dom.test.tsx",
      "before": 7,
      "after": 0,
      "reason": "Josh approved deleting the hidden Sovereign showcase (/ward-flow/sovereign, sovereign-showcase-screen, top25/ward-top25-cockpit and ward-top25-features.ts) once the Top 25 items moved into the real screens behind their top25-* flags, 15 Oct 2026. This file rendered only the showcase cockpit (WardTop25Cockpit and PhoneWalkRoundSheet), both deleted.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-sovereign-production-gate.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Josh approved deleting the hidden Sovereign showcase (/ward-flow/sovereign, sovereign-showcase-screen, top25/ward-top25-cockpit and ward-top25-features.ts) once the Top 25 items moved into the real screens behind their top25-* flags, 15 Oct 2026. This file tested only that the deleted showcase page 404s in production. The route no longer exists at all.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-clinical-values.test.ts",
      "before": 13,
      "after": 9,
      "reason": "Josh approved deleting the hidden Sovereign showcase (/ward-flow/sovereign, sovereign-showcase-screen, top25/ward-top25-cockpit and ward-top25-features.ts) once the Top 25 items moved into the real screens behind their top25-* flags, 15 Oct 2026. The four removed cases drove derivePaperLegalExpiryRadar and deriveEdBreachLadder, which lived only in the deleted features file. The value checks on CLINICAL_VALUES, including paperFormRadarAmber/Edge, stay.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ui-ward-roles.spec.ts",
      "before": 24,
      "after": 22,
      "reason": "Josh approved deleting the hidden Sovereign showcase (/ward-flow/sovereign, sovereign-showcase-screen, top25/ward-top25-cockpit and ward-top25-features.ts) once the Top 25 items moved into the real screens behind their top25-* flags, 15 Oct 2026. The two removed Playwright cases drove the design system showcase page at the deleted route. Every other journey in the file is unchanged.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-mha-calculator.test.ts",
      "before": 23,
      "after": 0,
      "reason": "Retired with the MHA form calculator (Tools review, Josh approved 15 Oct 2026). The calculator ran after-hours and weekend checks, hour caps and reference presets on typed times, which rule D5 forbids. Form times replaces it with typed times only. The typed-time parser and formatter cases moved to tests/ward-form-time-input.test.ts, the Perth-midnight clock case to tests/ward-tools-sheet.dom.test.tsx, and the keyboard case to tests/ward-a11y-keyboard-scroll.dom.test.tsx.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-mha-calculator.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Retired with the MHA form calculator (Tools review, Josh approved 15 Oct 2026). The calculator ran after-hours and weekend checks, hour caps and reference presets on typed times, which rule D5 forbids. Form times replaces it with typed times only. The typed-time parser and formatter cases moved to tests/ward-form-time-input.test.ts, the Perth-midnight clock case to tests/ward-tools-sheet.dom.test.tsx, and the keyboard case to tests/ward-a11y-keyboard-scroll.dom.test.tsx.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-mha-form-caps.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Retired with the MHA form calculator (Tools review, Josh approved 15 Oct 2026). The calculator ran after-hours and weekend checks, hour caps and reference presets on typed times, which rule D5 forbids. Form times replaces it with typed times only. The typed-time parser and formatter cases moved to tests/ward-form-time-input.test.ts, the Perth-midnight clock case to tests/ward-tools-sheet.dom.test.tsx, and the keyboard case to tests/ward-a11y-keyboard-scroll.dom.test.tsx.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-network-figures.dom.test.tsx",
      "before": 5,
      "after": 3,
      "reason": "Renamed from tests/ward-tools-workspace.dom.test.tsx when the old Tools tabs went (Tools review, Josh approved 15 Oct 2026). Its two contact directory cases covered the Tools directory, which was removed. Contacts now reads the On-call directory and is pinned in tests/ward-tools-sheet.dom.test.tsx and tests/ward-bar-figures-telemetry.dom.test.tsx.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-community-figures.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (community/community-figures.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-community-scope.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (community/community-home.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-community-team-hub.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (community/community-team-hub.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-community-teams-table.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (community/community-teams-table.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-device-claim-reason.dom.test.tsx",
      "before": 8,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (escalation/escalation-board.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-ed-home.dom.test.tsx",
      "before": 12,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (ed/ed-home.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-ed-service-bands.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (ed/ed-service-bands.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-escalation.dom.test.tsx",
      "before": 6,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (escalation/escalation-board.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-tracker-leg-badge.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 15 Oct 2026 together with the component it rendered (tracker/live-tracker.tsx), which no route has reached since its redirect landed. Josh approved dead-code deletion on 15 Oct 2026 (repo scorecard, fix list 5.10). The suite was already skipped, so no running coverage is lost. What it covered stays in docs/history/archive/dated-notes/retired-coverage-record-2026-09-06.md.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-transport-page-name.test.ts",
      "before": 7,
      "after": 4,
      "reason": "The three removed cases read tracker/live-tracker.tsx, deleted on 15 Oct 2026 as dead code (no route has rendered it since MERGE 03 made /transport a redirect). The live checks stay: the redirect target, the Movements heading and no Live tracker text in the transport page.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-management-print-coverage.test.ts",
      "before": 12,
      "after": 11,
      "reason": "FIXTURE 2 used ed/ed-home.module.css as its real input, and that stylesheet was deleted on 15 Oct 2026 with its unreachable component. FIXTURE 1 and the TASK 2 negative control still prove a covered non-root edge and an uncovered edge.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-community-viewer-assumption.test.ts",
      "before": 4,
      "after": 3,
      "reason": "The removed case asserted that the FD-23 screen-boundary guard lists community/community-team-hub.tsx. That screen was deleted on 15 Oct 2026 as unreachable dead code (Josh approved dead-code deletion that day). The live team page, community/community-screen.tsx, reads the full referral record, so it cannot replace the entry until that is fixed; the gap was routed to the Engine safety workstream rather than hidden by a weaker assertion.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-sidebar.dom.test.tsx",
      "before": 24,
      "after": 0,
      "reason": "The file tested the old ClinicalRail sidebar (icon rail, labelled panel, phone drawer, counts and attention block). Nothing mounted it after the shared WardBar and WardRail chrome replaced it, and its last live import went when the Tools sheet (#302) took over the demo controls. Josh approved removing ClinicalRail, WardSidebarFooter and WardDemoControls on 15 Oct 2026. Its reachability check for the community index moved to tests/ward-community-index.dom.test.tsx against WardRail, and its D11 sandbox scan moved to tests/ward-nav.test.ts against the live rail.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ci-cache-safety.test.ts",
      "before": 58,
      "after": 2,
      "reason": "Removed the suites that read PsychSift's monorepo .github/workflows/ci.yml (monorepo job routing, the PR-required aggregate's cancelled-vs-failed shell, visual baseline routing and Lighthouse budget routing) and the one case asserting on the deleted setup-node-cached composite action. ci.yml does not exist in BigSimmo/Ward-Flow, so all four suites were describe.skipIf'd on every run and verified nothing; the three composite actions under .github/actions/ were used by no workflow and were deleted in the same change (fix list 6.7 and 5.10, 15 Oct 2026). Ward Flow CI is .github/workflows/ward-flow.yml, whose contracts are enforced by scripts/ward-ci-public/check-contracts.mjs in the static job. The two live cases (no auto-merge workflow, npm cache in ward-flow.yml) remain.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-fold-queue-current.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Tested scripts/ward-flow/fold-queue-current.mjs, which listed READY commits in the retired fold queue. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-trial-merge.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Tested scripts/ward-flow/trial-merge.mjs, which trial-merged the fold queue into the old local ward line. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-flow-chat-control.test.ts",
      "before": 44,
      "after": 0,
      "reason": "Tested scripts/ward-flow/chat-control.mjs, the lead, builder and verifier lease tool. The whole suite was describe.runIf(existsSync(docs/ward-flow/control)) and that folder is absent from this repository, so none of the 44 cases ran here. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-whois-register.test.ts",
      "before": 7,
      "after": 0,
      "reason": "Tested scripts/ward-flow/whois.mjs, which mapped a chat to its folder in the old worktree layout. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-logs-commit.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Tested scripts/ward-flow/logs-commit.mjs, which committed notes in D:/Repos/ward-flow-logs. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-fold-lock.test.ts",
      "before": 13,
      "after": 0,
      "reason": "Tested fold-lock.mjs and fold-preflight.mjs, both already refusing as retired. The three ready-check.mjs remote refusal cases it also carried were RE-POINTED, not dropped: they live on in tests/ward-ready-check-remote-boundary.test.ts, which strips host GIT_* controls so they also run in a cloud container. Removed with the scripts that only served the old Database checkout (fix list 10.11, dead-code deletion approved by Josh on 15 October 2026). Nothing live calls the script, and no current document presents it.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-sidebar-phone-contract.test.ts",
      "before": 8,
      "after": 7,
      "reason": "Retired the one case that read ward-sidebar.module.css. Its component (ClinicalRail) was already gone and no route imported the stylesheet, so the file was deleted (scorecard leftovers item 2, wave F). The mounted rail keeps its own cases in this file. A record, not a gate condition: 1 of 8 is under the per-file floor.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-shell-print-ancestor.test.ts",
      "before": 13,
      "after": 12,
      "reason": "Retired the case pinning the print reset inside ward-sidebar.module.css, deleted with its already-removed component (scorecard leftovers item 2, wave F). The live portalled surfaces stay pinned by the rail case and the two-sided portal set in this file. A record, not a gate condition: 1 of 13 is under the per-file floor.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-statistics-compare-two-tables.dom.test.tsx",
      "before": 20,
      "after": 19,
      "reason": "Retired the case that checked right-alignment rules in statistics-third-edition.module.css. The Compare screen stopped importing that sheet in the v6 rebuild, so the case guarded CSS nothing loads, and the sheet was deleted with nine other unimported stylesheets (fix list 2.4, wave F). The threshold cases in this file were re-pointed to the live statistics-compare.module.css rather than retired. Whether figures on the live Compare tables right-align is listed as a leftover. A record, not a gate condition: 1 of 20 is under the per-file floor.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/applied-filters.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered components/ui/applied-filters.tsx; Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/chip-contract.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered components/ui/chip.tsx; Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/error-state.dom.test.tsx",
      "before": 14,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered components/ui/error-state.tsx; Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/metro-pulse-circle.dom.test.tsx",
      "before": 3,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered components/ui/metro-pulse-circle.tsx; Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ui-v2-components.dom.test.tsx",
      "before": 90,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered the components/ui kit (button, chip, choice, confirm dialog, disclosure, link, page header, pagination, progress, segmented control, select, tabs, text field); Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ui-v2-form-field.dom.test.tsx",
      "before": 12,
      "after": 0,
      "reason": "Deleted with the component it tested on 15 Oct 2026 (screen and component cleanup, PR #343). Nothing in the app imported or rendered components/ui/form-field.tsx; Josh approved deleting the unused components that day.",
      "approvedOn": "2026-10-15"
    },
    {
      "path": "tests/ward-chrome-header-actions.dom.test.tsx",
      "before": 9,
      "after": 0,
      "reason": "Retired describe.skip suite deleted on 16 Oct 2026 together with the unreferenced ward-chrome-header.tsx and ward-chrome-header.module.css components. The live WardCommandBar replaced WardChromeHeader across all screens and is covered by its own active test suites.",
      "approvedOn": "2026-10-16"
    },
    {
      "path": "tests/clean-worktree.test.ts",
      "before": 20,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/clean-worktree.mjs and scripts/worktree-inventory.mjs (worktree reports), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/dependency-drift-check.test.ts",
      "before": 17,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/check-dependency-drift.mjs (an import-closure report nothing ran), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/dependency-report.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/dependency-report.mjs (a digest for a dependency cron that no longer exists; the dependency audit workflow runs npm audit directly), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/final-merge-audit.test.ts",
      "before": 10,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/final-merge-audit.mjs (final-merge audit), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/flake-ledger.test.ts",
      "before": 9,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/flake-ledger.mjs and scripts/classify-playwright-failures.mjs (flake ledger), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/gate-arbiter.test.ts",
      "before": 42,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/gate-arbiter.mjs (advisory gate arbiter), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/gate-receipts.test.ts",
      "before": 34,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/gate-receipts.mjs (local gate receipts that let a repeated run skip), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/merge-loss-audit.test.ts",
      "before": 29,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/audit-merge-loss.mjs (merge-loss audit), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/public-startup-boundary.test.ts",
      "before": 7,
      "after": 4,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/check-base-freshness.mjs (advisory stale-base tripwire); the three freshness cases went, the four sign-out and pre-commit ownership cases stay, was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/test-evidence-identity.test.ts",
      "before": 3,
      "after": 2,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/gate-receipts.mjs; only the receipt case went, the two identity cases for the kept unit gate stay, was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/vitest-result-reuse.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, the receipt-reuse rule vitestRunIsMemoisable in scripts/run-vitest.mjs, removed with gate receipts, was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-drawing-rules.test.ts",
      "before": 15,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/check-drawing-rules.mjs (a checker for historical HTML drawings that nothing ran on a real drawing), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-mutation-harness-reachable.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/mutation-run.mjs (mutation runs), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-mutation-tooling.test.ts",
      "before": 10,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/mutate.mjs (mutation runs), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-ready-check-remote-boundary.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/ready-check.mjs (legacy READY compatibility helper), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-ready-fail-fast.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/ready-check.mjs (legacy READY compatibility helper), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-run-slot.test.ts",
      "before": 11,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/run-slot.mjs (PC run slots), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-select-fold-gate.test.ts",
      "before": 10,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/select-fold-gate.mjs and ready-check.mjs (fold-gate selection), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-selector-default-base.test.ts",
      "before": 1,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/select-fold-gate.mjs and select-journeys.mjs (fold-gate and journey selectors), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-test-batch.test.ts",
      "before": 22,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/ward-flow/test-batch.mjs (receipt-backed test batches), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-verification-plan.test.ts",
      "before": 4,
      "after": 3,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/gate-arbiter.mjs; only the arbiter case went, the three verify-pr-local plan cases stay, was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/worktree-cleanup.test.ts",
      "before": 26,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/worktree-cleanup.mjs (orphan worktree cleanup), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/worktree-inventory.test.ts",
      "before": 14,
      "after": 0,
      "reason": "Tooling clean-up (item 21, 18 October 2026): the subject of these cases, scripts/worktree-inventory.mjs (worktree inventory), was retired because no CI job, git hook, kept script or rule document's safeguard depended on it. No product behaviour or safety gate lost coverage.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/app-announcements-root.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/contextual-back-navigation-contract.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/statistics-v4-primitives-tokens.test.ts",
      "before": 11,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/viewport-fill-contract.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-answer-bar-dock.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-capacity-network-row-de-emphasis.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-chrome-owner.test.ts",
      "before": 11,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-css-important-ratchet.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-delays-spread-lanes.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-design-language-canonical.test.ts",
      "before": 6,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-drawing-match-r2-12.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-hub-bar-colours.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-management-print-coverage.test.ts",
      "before": 11,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-management-print.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-print-ink-specificity.test.ts",
      "before": 1,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-shell-print-ancestor.test.ts",
      "before": 13,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-management-role.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-mockup-tokens-resolve.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-mono-face-earns-its-place.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-primitives-shared.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-raw-colour.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-referral-overdue-selection-css.test.ts",
      "before": 1,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-route-component-binding.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-shell-fill.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-sidebar-phone-contract.test.ts",
      "before": 7,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-static-inline-style-ratchet.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-statistics-pinned-dock.test.ts",
      "before": 1,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-statistics-v3-language.test.ts",
      "before": 10,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-statistics-v4-language.test.ts",
      "before": 15,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-stylesheet-duplicate-block.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-table-min-width.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-table-panel-inset.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-table-phone-swap.test.ts",
      "before": 6,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-table-single-source.test.ts",
      "before": 6,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-handover-print.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-officer-print.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-referrals-print.test.ts",
      "before": 6,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-clinical-rail-token-bridge.test.ts",
      "before": 2,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-delays-type-ranks.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-statistics-grid-tracks-fit-the-container.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-style-drift-ratchet.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Repository clean-up item 20 (owner request, 18 October 2026): retired a test that reads app source or stylesheet text and pins wording, class names, CSS values, token names or file layout, so it breaks on harmless edits without exercising app behaviour. It imports no app module, so no coverage is lost. Clinical, legal, safety, privacy, security, persistence and accessibility guards were kept.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-awol-tracker-status.test.ts",
      "before": 4,
      "after": 3,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-legal-radar-dossier.dom.test.tsx",
      "before": 4,
      "after": 3,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-top25-broadcast-extend.dom.test.tsx",
      "before": 5,
      "after": 4,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-top25-cleaning-reminder.dom.test.tsx",
      "before": 3,
      "after": 2,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-top25-discharge-notices.dom.test.tsx",
      "before": 3,
      "after": 2,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-top25-discharge-prep.dom.test.tsx",
      "before": 3,
      "after": 2,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-top25-edd-drift.dom.test.tsx",
      "before": 3,
      "after": 2,
      "reason": "Feature flag clean-up (item 18, 18 October 2026): the removed case only proved that an always-on top25 feature flag could switch the feature off. The flag and its off path were deleted, so the case has no subject; every assertion about the feature's behaviour stays.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "docs/ward-flow/handover/templates/template-visual.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Docs archive clean-up (item 22, 18 October 2026): the superseded mockup engineering handover folder, including this template test, moved to Git history at main commit 0a469c6 (see docs/ARCHIVE.md). It exercised a handover template, not app behaviour.",
      "approvedOn": "2026-10-18"
    },
    {
      "path": "tests/ward-network-cluster-header.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network screen's service cluster headers, which no longer exist.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-hero-highlight.dom.test.tsx",
      "before": 3,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network screen's hero figures, which no longer exist.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-initial-patient-selection.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases pinned initialNetworkPatientId, deleted with the Network placement workspace.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-queue-count.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network placement queue count; the queue itself is still on Home and Movements.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-referral-clocks.dom.test.tsx",
      "before": 3,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered referral clocks inside the Network placement workspace; the referral screens keep their own clock tests.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-referral-placement.dom.test.tsx",
      "before": 17,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network placement workspace and its schematic diagram; placement for a referral remains covered by the referral match and Home shortlist tests.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-stage-filter.dom.test.tsx",
      "before": 8,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network pipeline stage filter, deleted with the screen.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-network-stage-strip.dom.test.tsx",
      "before": 8,
      "after": 0,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. These cases rendered the Network pipeline stage strip, deleted with the screen.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-data-checker.test.ts",
      "before": 39,
      "after": 35,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. The four removed cases checked the Network map's columnServices list, which the data checker could no longer read even on main and which went with the screen; the wardServiceOrder check and its tests remain.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/ward-management.test.ts",
      "before": 10,
      "after": 8,
      "reason": "Network screen retired (Josh's decision card, 19 October 2026 16:36 UTC): the screen repeated Home and Capacity, its route now redirects to Home and its one unique part, ready beds by road time, moved to Capacity. The removed describe pinned originServiceFit, a Network-only helper deleted with the screen.",
      "approvedOn": "2026-10-19"
    },
    {
      "path": "tests/pressure-strip.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Josh approved deleting the unused pressure strip and flow diagram on 20 October 2026 (project thread, 06:04 UTC, \"Yes, delete those 7 files\"). No route had drawn PressureStrip since the Network screen was retired (19 Oct 2026) or FlowDiagram since the v6 Home (#113, 7 Oct 2026). This file rendered only PressureStrip and was deleted with it; Home's live ED pressure card (home-ed-pressure.tsx) keeps its own tests, including the service-scope foot in ward-coordinator-service-scope.dom.test.tsx.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-flow-diagram-scroll-notice.dom.test.tsx",
      "before": 4,
      "after": 0,
      "reason": "Josh approved deleting the unused pressure strip and flow diagram on 20 October 2026 (project thread, 06:04 UTC, \"Yes, delete those 7 files\"). No route had drawn PressureStrip since the Network screen was retired (19 Oct 2026) or FlowDiagram since the v6 Home (#113, 7 Oct 2026). This file rendered only FlowDiagram's sideways-scroll note and was deleted with the component.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-flow-potential-chip-migration.dom.test.tsx",
      "before": 1,
      "after": 0,
      "reason": "Josh approved deleting the unused pressure strip and flow diagram on 20 October 2026 (project thread, 06:04 UTC, \"Yes, delete those 7 files\"). No route had drawn PressureStrip since the Network screen was retired (19 Oct 2026) or FlowDiagram since the v6 Home (#113, 7 Oct 2026). Its one case rendered FlowDiagram to check it showed Confirmed/Expected rather than the raw potential figure; with the diagram gone there is no surface left for it to check. Hub status wording stays pinned by ward-flow-diagram-status-truthfulness.test.ts.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-act-periods-demo.test.ts",
      "before": 16,
      "after": 0,
      "reason": "Josh approved removing the computed Mental Health Act period countdowns on 20 October 2026 (overall review 20 Oct 2026, section 1 item 1, recorded as D-70, replacing D-29). The file tested only legal-forms/act-periods-demo.ts, which worked out when each Act period would end, picked the under-18 period from age and ordered the Time not written group by share of a computed period. That module is deleted with it, so there is nothing left for these cases to check. The replacement behaviour (only a recorded due time is shown, with 'No deadline recorded' otherwise, and no Act period wording anywhere) is pinned in tests/ward-legal-forms-screen.dom.test.tsx, and the section-citation guard now exempts no file.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-audit-legal-group.test.ts",
      "before": 13,
      "after": 11,
      "reason": "Same owner decision (20 October 2026, D-70). Two cases tested the Act period line beside a typed expiry (audit A3-5) and one the Time not written order by share of a computed Act period (A3-6). The line and the computed order are removed. The A3-6 case is replaced by one that pins the group to arrival order (longest wait in ED first), so the net drop is two.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-priority.test.ts",
      "before": 28,
      "after": 25,
      "reason": "Audit 1, Josh 20 Oct 2026 (D-71): the 0 to 100 points score (operationalScore) was removed as a never-build severity score; the three cases that pinned point values and the flag/tier re-sort have nothing left to test. Wait order and the plain wait reasons are pinned by the remaining cases.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-console-controls.dom.test.tsx",
      "before": 71,
      "after": 68,
      "reason": "Audit 1, Josh 20 Oct 2026 (D-71): the unreachable \"Other wards, ranked\" cockpit panel was removed as a never-build ranked ward suggestion; its three cases tested that panel only.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-shortlist-candidates.test.ts",
      "before": 22,
      "after": 20,
      "reason": "Audit 1, Josh 20 Oct 2026 (D-71): catchment-first tiers were replaced by a fixed order (fit, then service, then name); the two tier-ordering cases no longer describe any behaviour.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-console-record-gender.dom.test.tsx",
      "before": 1,
      "after": 0,
      "reason": "Audit 1, Josh 20 Oct 2026 (D-71): its one case drove a control inside the removed ranked-wards cockpit panel; recording sex when it is missing stays covered by tests/ward-bed-matching-recorded-sex.test.ts and tests/ward-eligibility.test.ts.",
      "approvedOn": "2026-10-20"
    },
    {
      "path": "tests/ward-referral-screens.dom.test.tsx",
      "before": 71,
      "after": 67,
      "reason": "D-77 (Josh, 21 Oct 2026, 'Build all ten, as recommended') replaced the desktop travel-band groups with the phone decision list. The four retired cases pinned the band group headings, their two counts, the counts sitting inside each summary, and the groups opening at desktop width, none of which exists any more. Every ward is still on the screen and still names its travel band; those properties are now pinned by the rewritten RF-001 and band cases in the same file (decisionGroups, renderedUnitIds, expectNetworkOrderInsideEachGroup).",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ward-person-screen.dom.test.tsx",
      "before": 20,
      "after": 0,
      "reason": "Josh approved retiring the hidden governed patient dossier (?view=governed, PersonScreen) on 21 Oct 2026 (UX audit). The screen and its CSS were deleted, so cases that rendered only PersonScreen go with it. Every case rendered PersonScreen. The unknown-id refusal is now asserted on Patient Now in tests/ward-patient-now-screen.dom.test.tsx (Patient not found, no other patient's identity, no id echoed).",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ward-patient-now.dom.test.tsx",
      "before": 6,
      "after": 0,
      "reason": "Josh approved retiring the hidden governed patient dossier (?view=governed, PersonScreen) on 21 Oct 2026 (UX audit). The screen and its CSS were deleted, so cases that rendered only PersonScreen go with it. Every case rendered PersonScreen or its Fact helper; Patient Now has its own absence wording tests.",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ward-patient-placement-fields.dom.test.tsx",
      "before": 5,
      "after": 0,
      "reason": "Josh approved retiring the hidden governed patient dossier (?view=governed, PersonScreen) on 21 Oct 2026 (UX audit). The screen and its CSS were deleted, so cases that rendered only PersonScreen go with it. The R-2026-09-04-A placement rule is now asserted on Patient Now's Details tab in tests/ward-patient-safety-audit-fixes.dom.test.tsx (the two sensitive fields in different groups and not adjacent).",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ward-patient-sensitive-adjacency-css.test.ts",
      "before": 4,
      "after": 0,
      "reason": "Josh approved retiring the hidden governed patient dossier (?view=governed, PersonScreen) on 21 Oct 2026 (UX audit). The screen and its CSS were deleted, so cases that rendered only PersonScreen go with it. It read person.module.css, which is deleted. Patient Now's Details tab keeps the two sensitive fields in separate groups, so CSS reflow cannot make them adjacent within one list.",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ward-address-tab.dom.test.tsx",
      "before": 5,
      "after": 4,
      "reason": "Josh approved retiring the hidden governed patient dossier (?view=governed, PersonScreen) on 21 Oct 2026 (UX audit). The screen and its CSS were deleted, so cases that rendered only PersonScreen go with it. The dropped case checked PersonScreen's tab in the address; the useAddressTab hook cases stay.",
      "approvedOn": "2026-10-21"
    },
    {
      "path": "tests/ui-ward-coordinator.spec.ts",
      "before": 22,
      "after": 18,
      "reason": "Home v7, approved by Josh on 22 Oct 2026, with State bedflow moved to the foot of Capacity unchanged (his decision card, 10:25Z). Four journeys read only State bedflow's patient mode on Home: routes to the shortlist, an ineligible ward's marking, accepted against referred, and the recorded destination at the hub. Capacity chooses no patient, so that mode is no longer on any screen. The card's patient mode keeps component coverage in tests/ward-home-bedflow-fits.dom.test.tsx, and the shortlist halves of the restrictive-ward and voluntary-on-locked journeys stay in this spec.",
      "approvedOn": "2026-10-22"
    },
    {
      "path": "tests/ward-home-offer-undo.dom.test.tsx",
      "before": 3,
      "after": 1,
      "reason": "Home v7, approved by Josh on 22 Oct 2026, with State bedflow moved to the foot of Capacity unchanged. The two retired cases offered a ward from State bedflow on Home and checked its Undo toast. Capacity chooses no patient, so Offer is never shown there, and Home now refers from Placement, which opens the referral sheet. The override sign-off case stays; tests/ward-home-offer-visible.dom.test.tsx still checks what Home shows of an offer.",
      "approvedOn": "2026-10-22"
    },
    {
      "path": "tests/ward-make-room.test.ts",
      "before": 20,
      "after": 0,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z: remove the Make room mock-up; thread reply 13:45Z: record the retired tests). PR #605 deletes the make-room-chains flag, a local-build-only mock-up with preview data that waited since 20 Oct for a design pick, with its panel, preview and chain derivation. This suite tested only the deleted chain derivation and preview.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-feature-flags.test.ts",
      "before": 12,
      "after": 11,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z: remove the Make room mock-up; thread reply 13:45Z: record the retired tests). PR #605 deletes the make-room-chains flag, a local-build-only mock-up with preview data that waited since 20 Oct for a design pick, with its panel, preview and chain derivation. The retired case pinned the make-room flag to local builds; the other flag cases stay.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-review-feedback.dom.test.tsx",
      "before": 4,
      "after": 3,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z: remove the Make room mock-up; thread reply 13:45Z: record the retired tests). PR #605 deletes the make-room-chains flag, a local-build-only mock-up with preview data that waited since 20 Oct for a design pick, with its panel, preview and chain derivation. The retired case rendered the deleted Make room panel; the handover, legal forms and settings cases stay.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-home-phone-sheets.dom.test.tsx",
      "before": 10,
      "after": 0,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z and his thread reply 13:45Z). The suite rendered only HomeWardSheet, the v10 phone ward sheet with Offer, which nothing could open after the phone sheet stopped taking a ward. PR #601 deletes the sheet, its lazy loader and this suite; the phone Since you looked and exceptions sheets keep their own tests.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-flow-diagram-status-truthfulness.test.ts",
      "before": 3,
      "after": 0,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z and his thread reply 13:45Z). The suite covered hubStatusText in flow-status.ts, the State bedflow patient line. No screen has passed State bedflow a patient since Home v7 moved it to Capacity, so the PR removes the patient mode, flow-status.ts and this suite together.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-home-bedflow-fits.dom.test.tsx",
      "before": 2,
      "after": 0,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z and his thread reply 13:45Z). The suite rendered State bedflow with a chosen patient to check its fitting wards and Offer. Capacity, the only caller, always passes no patient, so the patient mode was unreachable and is removed with this suite. The beds-only card keeps its Capacity coverage.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-escalation.test.ts",
      "before": 5,
      "after": 0,
      "reason": "Unfinished features sweep, approved by Josh on 23 Oct 2026 (decision card 13:07Z, and 14:59Z \"Yes go ahead with all recommendations\"). escalationBoard had no production caller and its nowhereEligible list counted movements already holding a bed (A3-3). The PR deletes the function and this suite; the no eligible bed ruling test keeps its own inline check.",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-transport-pickup.test.ts",
      "before": 2,
      "after": 0,
      "reason": "helper unused, deleted with its only test",
      "approvedOn": "2026-10-23"
    },
    {
      "path": "tests/ward-statistics-insight-chart.dom.test.tsx",
      "before": 15,
      "after": 0,
      "reason": "Audit 24-7 CT-26: statistics-insight-chart.tsx was imported nowhere (listed as unreachable in ward-component-reachability since the v6 statistics pages of 7 Oct 2026) and its CSV export carried no synthetic marker. Component, stylesheet and its own test removed together.",
      "approvedOn": "2026-10-24 (Josh, project chat 23:55Z: go ahead with all approvals)"
    },
    {
      "path": "tests/ward-dynamic-island-rollout.contract.test.tsx",
      "before": 106,
      "after": 14,
      "reason": "Dead-code cleanup: shell/ward-dynamic-island.tsx was deleted (its one route use left the ED page on 11 Oct 2026). The 92 removed cases rendered only WardDynamicIsland with hand-built props. The 10 Track B cases that guard live screens stay, and the 4 live screen mounts from the deleted ward-dynamic-island-stress.dom.test.tsx moved here.",
      "approvedOn": "2026-11-01 (Josh, Q96: delete dead code an approved redesign replaced)"
    },
    {
      "path": "tests/ward-ed-presentation-keeps-draft.dom.test.tsx",
      "before": 1,
      "after": 0,
      "reason": "The typed ED presentation editor it tested (EdPresentation) was removed: Q103 (Josh, 1 Nov 2026) replaced the unsaved typed note with the saved fixed list (RECORD_ED_PRESENTATION), which tests/ward-ed-handover-events.test.ts covers.",
      "approvedOn": "2026-11-01"
    },
    {
      "path": "tests/ward-help-ask.dom.test.tsx",
      "before": 11,
      "after": 6,
      "reason": "Retires the five cases that rendered the stand-alone WardHelpAsk box, which no screen imported after the Help redesign of 1 Nov 2026 (the Help sheet's own search replaced it). Josh approved removing the unused Ask view and its test on 2 Nov 2026. The six remaining cases already test the live Help sheet: the clinical-question reply, the closest-topics fallback, returning to results, opening on the tabs, a handed-over question with Show me, and that typed words never reach storage or the address. Usage counting by id stays covered by tests/ward-help-usage.dom.test.tsx and tests/ward-help-tasks.dom.test.tsx.",
      "approvedOn": "2026-11-02"
    },
    {
      "path": "tests/ward-help-search.dom.test.tsx",
      "before": 13,
      "after": 0,
      "reason": "The file tested only WardHelpSearch, the variant-A search box that no screen imported after the Help redesign of 1 Nov 2026; the component is deleted with it (Josh approved retiring the unused Help views and merging the search paths on 2 Nov 2026). The live search is tested by tests/ward-help-search-sheet.dom.test.tsx, tests/ward-help-ask.dom.test.tsx, tests/ward-help-search-index.test.ts, tests/ward-help-search-quality.test.ts and tests/ward-global-search-help.dom.test.tsx.",
      "approvedOn": "2026-11-02"
    },
    {
      "path": "tests/ward-bed-drawer-stay-day.dom.test.tsx",
      "before": 3,
      "after": 2,
      "reason": "Drops the What's new (P102) case, which checked that the release-notes list still held the 27 Oct Stay tile line. The list is capped at 20 and rolls off its oldest line when a new one is added (git-publication.md); Josh approved rolling off the oldest line and updating this check on 2 Nov 2026. The Stay tile behaviour itself stays covered by the file's two remaining cases.",
      "approvedOn": "2026-11-02"
    },
    {
      "path": "tests/ward-network-figures.dom.test.tsx",
      "before": 5,
      "after": 2,
      "reason": "Retires the old NetworkFigures view's cases with the view itself (ward-network-figures.tsx), which the Tools overhaul (#1316, Josh 2 Nov 2026) replaced with Key figures (ward-tool-figures.tsx). Josh approved deleting the replaced pieces (Q353, and again on 3 Nov 2026). Re-pointed rather than lost: the occupancy rule (Tools prints the same occupancy as every other page, and no WF- movement reference) now renders ToolFigures in this file; the Ready-equals-readyBedsNow rule moved to ToolFigures in tests/ward-audit-24-4-counts.dom.test.tsx; the Statistics link access rule moved to ToolFigures in tests/ward-access-dead-ends.dom.test.tsx. Dropped because Key figures no longer shows the figure: the Total beds and figure-category filter, Longest wait, and the Deadline passed total that moved with the shared clock. Those figures live on Statistics, one link away. The statistics presentation case stays unchanged.",
      "approvedOn": "2026-11-03"
    },
    {
      "path": "tests/ward-catchment-resolver.dom.test.tsx",
      "before": 26,
      "after": 24,
      "reason": "The seven cases that rendered the old WardCatchmentResolver view go with the view (ward-catchment-resolver.tsx), which the Tools overhaul (#1316, Josh 2 Nov 2026) replaced with the shared SuburbLookupCard (D-91). Josh approved deleting the replaced pieces (Q353, and again on 3 Nov 2026). Five re-pointed at SuburbLookupCard in this file: opens empty and a quick pick answers, a postcode lists every suburb with Show more, a contested suburb names no single team and draws no team actions, Not found and an unfiled postcode, and Clear. Two dropped because the card has no such feature: the resolver's own heading and the Copy summary button (formatCatchmentSummary keeps its two engine cases here). The engine cases now import ward-catchment-query.ts directly. Under the per-file ceiling, so this is a record rather than a gate condition.",
      "approvedOn": "2026-11-03"
    },
    {
      "path": "tests/ward-ci-budget-recheck.test.ts",
      "before": 26,
      "after": 0,
      "reason": "Retired with the code it tested. Josh ruled to delete the switched-off budget recheck job (D-128 item 6, 10 Nov 2026), so .github/workflows/ward-flow-budget-recheck.yml and scripts/ward-ci-public/budget-recheck.mjs are deleted in the same change. The job had run with if: false, so these cases guarded nothing that ran. Budget prevention still lives in merge-latest-main.mjs and the production build's budget gate, tested by their own suites.",
      "approvedOn": "2026-11-10"
    }
  ]
}