[Sycun]

On phones, project header content overflows a fixed 52px header and intercepts tab taps. The desktop minimum height and nested scrollers also prevent reaching the last table row. In the facts table, eight percentage-width columns collapse into phone width while the sticky actions cover other columns, so badges, text and buttons overlap.

Scope application bar sizing, stacking and glass styles to .container > header. Give the mobile project page one vertical scroller with content-sized panels and a bounded graph canvas. Preserve the search icon gutter and alignment. Give fact columns readable widths, let actions scroll with their row, and use the project table wrapper as the single horizontal scroller. Bump the mobile stylesheet cache version.

Validation:

• Offline Chromium tests with real markup, full stylesheets and the tab handler: 7 widths, 3 languages, both themes, long names/descriptions, and 294 tab taps.
• Full page shell: 4 phone sizes, reduced visible viewport heights, safe-area spacing, both themes, and 1/35 rows in facts/assets/conversations/vulnerabilities. Final rows are visible and tappable, native scroll input moves the outer scroller, and graph/settings footers remain reachable.
• Actual fact row renderer with notes/findings, body and confidence badges, link counts, timestamps and four action buttons; includes the real mobile table wrapping helper. Across 3 widths, 3 languages and both themes, badges/actions remain inside their cells and editing/details are reachable after horizontal scrolling.
• Production template/styles combined with the new mobile stylesheet pass the scroll and table regressions.
• The regressions reproduce header overflow, unreachable final rows and squeezed fact columns against the earlier stylesheets.
• 23 existing project facts, folder preview and mobile i18n tests passed for the initial fix; git diff --check passes.

Browser tests require Playwright and Chromium: CHROME_PATH=/path/to/chrome node --test scripts/project-mobile-layout.test.cjs (omit CHROME_PATH for Playwright's Chromium).

UI changes were synced to the local production tree at the user's request, preserving other changes and runtime data. On 2026-10-15, the user confirmed that the latest layout looked correct on their physical iPhone after checking the production UI.