[RedStar071]

Summary

Related to #5. Third layer of the v2 stack, on top of #72: the sign-in pages get the two-column layout from the reference you shared.

• Sign-in, sign-up, device approval and invitation pages share one shell: the form on the left with the Code Zero mark, and on wide screens a green checkerboard panel with a short pitch and the running version.
• Below 64rem only the form shows, so phones and tablets get a single column with no sideways scroll.
• Form controls in this layout are 44 px tall, button-styled links included, and labels drop the uppercase micro style to match the reference.
• The narrative copy lives in packages/i18n (EN and IT) and the colours come from the shared tokens, so both themes and both languages follow the switches.
• On the split layout the page gives back the scrollbar gutter tokens.css reserves, which otherwise left a canvas-coloured strip beside the panel where scrollbars are not overlaid.

Why

The old screen was a small bordered card in the middle of an empty page. The split layout gives the product a recognisable first screen without touching how sign-in works: capabilities, OAuth visibility, submission and error handling are unchanged.

Verification

• aube run check:repo
• aube run lint:ci
• aube run typecheck
• aube test
• aube run build

Safety and compatibility

• I added or updated deterministic tests for changed behavior.
• I preserved observe mode as read-only, or explained the policy change above.
• Runtime commands and target-repository writes remain inside the runner boundary.
• I did not expose secrets, tokens, personal data, or untrusted output in logs.
• I updated documentation and Agent Skills when workflows or boundaries changed.

Presentation only: no auth policy, API or data change. packages/ui/DESIGN.md records the checkerboard as a registered texture and the 44 px auth controls.

Agent context

• Agent/tools used: Codex (GPT) and Claude Code (Claude Opus 5.5) in T3 Code, with a review subagent.
• What the agent did, and what you changed or verified yourself: the agents built the layout from my reference image, reviewed it, and checked a production build in Chromium across 375, 768 and 1280 px, both themes and both languages, plus a wrong-password and a successful sign-in. I supplied the reference and the scope.

Reviewer notes

• The mark is drawn as a single-colour accent mask, so the two-tone favicon colouring does not carry over. Say if you want the original colours.
• The layout scopes a few overrides to its own pages (label-upper, button heights). It keeps the dashboard density untouched, but it couples the layout to those shortcut names.
• The :focus-visible, :-moz-focusring selector list in tokens.css is dropped by Chromium because of the unknown pseudo-class. That predates this PR; the new brand link carries focus-ring so it is not affected.

🤖 AI disclosure: Wolfstar Agent Kit modified this description. My AI open-source policy.

Confidence Score: 5/5

No identified issues block merging this presentation-only change; rendered behavior across browsers and viewport sizes has not been independently verified.

_{Reviews (2) · Last reviewed commit: "Merge branch 'feat/v2-auth' into feat/au..." · Reviewed by Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
agent-zero-marketing	Ready	Preview	Oct 18, 2026 8:36pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
agent-zero-docs	Skipped		Oct 18, 2026 8:36pm UTC

[coldtea-pr-lens]

• Redraw · drawn at f548124, the branch has moved on

Architecture

Data flow

No data-flow sequence changed in this PR.

Review

✨ Nothing flagged · reviewed f548124

Tip

After a push, tick Redraw to draw the latest commit

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs as before
• Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion

_{Thanks for using PR Lens! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out on X, Bluesky, Mastodon, Reddit or LinkedIn}

Dismissed because a newer commit was pushed; Greptile will re-review the current head.