Privacy page: fix notched back control + three redesign directions

[BigSimmo]

Summary

• Fix the /privacy back-control safe-area bug: the page sits outside the search shell and was painting the back arrow under the status bar / Dynamic Island on notched phones. The page now owns max(safe-area-top) top padding with a 48px back row.
• Add three elevated redesign directions grounded in Clinical White / Sky Graphite (governance copy unchanged):
  1. Quiet ledger (recommended) — one continuous reading surface, amber Important spine, hairline sections, sticky chrome
  2. Trust map — Sydney / Singapore / OpenAI processing chips + icon section cards
  3. Indexed brief — phone section chips + desktop TOC rail
• Runnable study: /mockups/privacy-page-directions
• Combined desktop+phone comps: public/mockups/privacy-page-redesign-2026-08/

01 Quiet ledger
02 Trust map
03 Indexed brief

Verification

• npx vitest run tests/privacy-ui.test.ts tests/navigation-back-button.dom.test.tsx — 7 passed
• Full unit suite via verify:pr-local — Test Files 475 passed (475) / Tests 4971 passed | 4 skipped (4975)
• ALLOW_BUILD_WITH_DEV_SERVER=1 npm run build — passed (/privacy and /mockups/privacy-page-directions present; client bundle secret surface check passed)
• npm run ensure — Clinical KB at http://localhost:4461; /privacy and /mockups/privacy-page-directions return 200
• Browser proof of mockup frames + mobile /privacy header safe-area row
• UI verification not run: full Chromium gate deferred; focused browser proof of changed owner only
• Provider gates not run: no OpenAI/Supabase behaviour change

Risk and rollout

• Risk: Low-medium. Production change is layout padding on /privacy only; redesign directions are mockup/design-scratch until a direction is chosen. Governance wording is unchanged.
• Rollback: Revert the commit; mockup routes 404 in production already.
• Provider or production effects: None

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed — no CDS behaviour change; layout/chrome and design-scratch mockups only

Notes

• Choose a direction before adopting the full redesign into production /privacy.
• Recommended default: 01 Quiet ledger, optionally borrowing the processing-map strip from 02.
• Live interactive review: /mockups/privacy-page-directions after npm run ensure.

_{To show artifacts inline, enable in settings.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f24f4077-4516-458b-a8ca-610683938ae9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #7808 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

[BigSimmo]

Closing as part of an open-PR review sweep, with the production fix preserved.

What was salvaged: the src/app/privacy/page.tsx safe-area change — the one production fix in here — is now #1621 on a fresh branch off current main, green on its focused gates (privacy-ui + privacy tests, 23 passed; lint and Prettier clean). It did not need to wait on the rest of this PR.

Why the rest is being closed rather than revived:

• 28 commits behind main, untouched since 2026-08-02.
• Red the whole time, on the type-scale gate rather than anything about the design: text-[10px] in src/components/privacy-page-directions-mockups.tsx:150 needs a named @theme step.
• It commits ~4.2 MB of PNG screenshots (3 files) into the repo.

The three redesign directions themselves are not being judged here — if you want to take one forward, it is cleaner to open it fresh against current main with the type-scale fix applied and the screenshots kept out of git, than to rebase 28 commits of drift.

Related: #1580 is closed in the same sweep for the same staleness reason (its blocker was bundle budget, +10.1% against a 10% tolerance). The reason a mockups-only PR can fail Build at all is now written down in AGENTS.md/CLAUDE.md, and the underlying metric question is tracked as ledger #237.

---

Generated by Claude Code