QA-1: design QA the shipped A′ shell against ia-concepts.html#c-aa

[jpapiez]

Part of #2410 (epic: iOS navigation redesign — A′ · Two Hats, adaptive).
Wave 3 — final gate. Blocked by #2416, #2417, #2418, #2419, #2420, #2421, #2423.

Scope

Design QA the shipped result against the approved concept: mobile/docs/design/ia-concepts.html, section id="c-aa" — the P_SOLO / P_FLOOR / P_OVER tab sets, pModeBar(), pOversightHub(), pFarm(), pInventory(), and the p-settings screen.

This is a verification pass, not an implementation issue. Its output is a findings list and follow-up issues, not a large PR. Small copy and spacing corrections may be fixed in place.

Checklist

Structure

• Simple shell is exactly Attention · Farm · Inventory · Oversight, with no mode control anywhere.
• Floor mode is exactly Attention · Farm · Tasks · Inventory.
• Oversight mode is exactly Overview · Fleet · Jobs · Upkeep · Reports.
• The Oversight hub's four sections and their rows match the concept, in order.
• The same destinations are reachable in both shells. Nothing exists in one and not the other.

Chrome

• Server chip leading, account button trailing-last, mode control pinned, on every root of both modes.
• Pushed screens carry none of the three.
• Exactly one scan affordance per screen. Inventory has the nav-bar icon and not a full-width button.
• The harvest attention item's primary action is a full-width Scan bin.

Copy

• Settings → Navigation Automatic states what it read, in plain language, e.g. "1 account, 1 bay, shift planning off. That is the simple layout."
• The unknown-shape case reads honestly rather than inventing counts.
• The upgrade offer card matches the approved copy and is inline, dismissible, and only on the Oversight root.
• The advanced-controls toggle names the real risk rather than saying "advanced".

Accessibility — mobile/PRODUCT.md commits to these; verify rather than assume

• Every interactive element ≥ 44pt.
• VoiceOver can reach and operate the mode control, the account button, the scan affordances, and the offer card, with sensible labels and hints.
• Dynamic Type at the largest accessibility sizes does not clip the nav bar, the mode control, or the tab bar.
• Contrast fixes from A11Y-1: fix three WCAG contrast failures in ThemeColors (pfError, pfWarning, pfButtonPrimary) #2413 are visually acceptable in both themes.
• Reduce Motion is respected by any shell-transition animation.

Devices

• iPhone compact, both shells, light and dark.
• iPad: two sidebar sections, no mode control, both orientations, and Split View / Slide Over collapsing to compact.

Regression

• None of the 14 previously-orphaned destinations is unreachable again.
• No dead ends: every screen offers a way onward or back.
• No "Coming Soon" placeholder remains reachable.

Acceptance criteria

• Every box above is checked or has a filed follow-up issue linked from this one.
• Findings are recorded with screenshots for anything visual.
• A short written verdict on whether the shipped result honours the A′ thesis — same destinations either way, growth expands the structure rather than relocating it.

Do not

• Redesign. If the concept looks wrong once built, file it and say so; do not quietly ship a fourth structure.

[github-actions]

📋 Assigned to 🎨 Newt (Designer (Industrial UI))

Issue: #2426 — QA-1: design QA the shipped A′ shell against ia-concepts.html#c-aa

🎨 Newt will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
🎨 Newt, work on issue #2426

[jpapiez]

📱 Mobile fallback triage

• Owner: 🎨 Newt
• Classification: type:chore
• Priority: priority:p3
• First step: Run the final cross-device design and accessibility QA only after all required shell children have landed.