# P6-00 — Baseline and design consistency audit

Audit date: 2026-10-11. Source baseline: `9d6d29d` on `codex/ui-redesign-phase4`. This package adopts the owner's current P6-00–P6-05 checkpoint names. The earlier [P6-01 audit](../p6-01/README.md) and [finding register](../p6-01/FINDINGS.md) remain historical evidence; they are not rewritten or relabelled as fresh tests.

## Baseline and method

The [original plan](../../IMPLEMENTATION_PLAN.md), [Phase 3 architecture](../../phase-3/INFORMATION_ARCHITECTURE.md), [design-system architecture](../../phase-3/DESIGN_SYSTEM_ARCHITECTURE.md), [accessibility targets](../../phase-3/ACCESSIBILITY_PLAN.md), [Phase 4 foundation](../../phase-4/README.md), [Phase 5 final acceptance](../../phase-5/p5-15/p5-15-06/README.md) and [all 57 preservation groups](../../phase-5/p5-15/PRESERVATION_ACCEPTANCE.md) establish the scope. Actual implemented Phase 5 scope is CONDITIONAL GO for bounded Phase 6 review; full planned Phase 5 is incomplete. Production remains NO-GO.

Authoritative inherited complete-suite baseline is 1,033 backend / 498 frontend / 148 ordinary browser, plus 49 sidecar, 108 focused AI, 5 revision, 2 real HTTP, security lanes 9/6/1/3, fidelity 16 fixtures/36 pages and settings export 8 fixtures/24 pages. Subsets are not added to complete-suite counts. The parent checkpoint execution manifest supplies fresh baseline runs and Git fetch/synchronisation evidence. This source audit claims no new browser run or human acceptance.

Review combines current component/caller inspection and attributed historical native evidence. [Surface coverage](SURFACES.md) covers every requested area; [prioritised register](FINDINGS.md) separates real usability/semantic defects from intentional variation and Phase 7 migration. Existing dirty company/i18n/toast/browser-test changes were observed and preserved; they were neither discarded nor represented as already validated.

## System consistency conclusion

`theme.ts` remains the single palette, typography, spacing, density, focus and motion authority. PageLayout/PageHeader/PageSection, MUI controls/icons, ViewStateNotice/useViewResource and existing toast/confirm/prompt infrastructure already provide the required shared patterns. No new UI framework, font, token compiler, generic form/save model or component library is justified.

The application title/section scale, tokenized page/card spacing, opt-in Comfortable/Compact data density, keyboard outlines, inverse navigation and semantic alerts are established. Differences on legacy pages alone are approved migration scope. Confirmed current barriers are initials contrast, implicit heading levels, login landmarks, tab/panel relationships, discoverability of modal save failure and language persistence failure. These can be corrected at existing owners without changing domain writes, routing, print geometry or IA.

## Preservation and outcome

All 57 contracts remain in force; inherited reconciliation is 0 PASS / 56 PARTIAL / 0 FAIL / 1 DEFERRED. Applicable correction traces: PRES-E02/E06/E07/E08, J05/J07/J08, W01/W08, C06–C12 and S01/S03/S04. The ordinary passing P2-D01 native package case remains mandatory. P5-13 remains deferred/unqualified and Production-withheld; no model qualification or capability activation belongs here.

Audit outcome: **CONDITIONAL GO for bounded P6-01 corrections**. Screen-reader/device/software-keyboard, Linux font/portrait, Board capacity, historical CV Unsaved/preference contention and production operational evidence remain explicit. Fresh validation, checkpoint commit and remote verification are recorded by the parent in the chronological Phase 6 log. Phase 7 and Phase 8 implementation are excluded.