improvement(ui): share public headings and product typography

[BillLeoutsakosvl346]

Summary

• Share the identical 40px heading and subtitle treatment across public chat, file-share and SSO access gates, preserving their content and behavior.
• Centralize typography tokens and replace repeated product font-size/weight declarations with the shared scale. Keep imported rem units and leading where they already match.
• Include the matching workflow-card heading change in the landing page's platform demonstration; other marketing presentation stays unchanged.

Intentional visual differences

This final diff includes typography normalization as well as the public-heading extraction. It is not entirely pixel-identical: workflow and note headings (including the platform demonstration) use 16px instead of 17px; small file-extension/avatar labels use 10px instead of 9px; the upgrade heading uses 28px instead of 30px; and the mobile workspace greeting uses 24px instead of 26px, retaining 28px on desktop. These use existing nearby scale values instead of adding near-duplicate tokens.

Validation

All workspace type checks, lint, import/API audits, generators and the complete EMCN suite pass against the actual target. Existing typography-merging tests cover the shared utility names. The previously captured public-access heading fixtures match in light/dark; that exact-match statement applies to the heading extraction, not the intentionally normalized sizes above. Authenticated flows and every typography consumer were not rechecked in the browser during the stack refresh. Audit tooling and review artifacts are outside the PR.

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 22, 2026 8:06pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no new actionable issue was introduced after the previous review, and the only prior finding was manually resolved with an explanation of the authorized design-system scope.

Summary

The PR introduces a shared public authentication header across chat, file-share, and SSO access gates while preserving their existing copy and presentation. It also centralizes the supporting typography scale and replaces equivalent arbitrary font sizes and weights with named design tokens throughout the application.

• Adds PublicAuthHeader as the common heading and subtitle treatment for public access gates.
• Reuses the component across chat authentication, public file authentication, and SSO forms.
• Defines the expanded typography and weight scale centrally and updates consumers to use named tokens.
• Keeps authentication behavior, validation, and dynamic verification content unchanged.
• The prior global-style concern was manually resolved after the author clarified that these definitions are authorized design-system tokens.

_{Reviews (4) · Last reviewed commit: "improvement(ui): share public authentica..."}

[cubic-dev-ai]

No issues found across 6 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[BillLeoutsakosvl346]

Before / after visual comparison

Public password/auth screens share PublicAuthHeader, preserving the existing heading and subcopy styles.

Left = before; right = after.

Rendered component fixtures with application CSS and local data, rather than authenticated product-page screenshots. These are representative visual examples, not end-to-end behavior coverage.

Current PR head checked at posting: 37fe35014c.

[BillLeoutsakosvl346]

@greptile

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 6 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[BillLeoutsakosvl346]

@greptile

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[BillLeoutsakosvl346]

@greptile Please re-review the current head. The inline response explains the shared definition and the authorized design-system scope.

[cubic-dev-ai]

All reported issues were addressed across 60 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR. The description now covers the complete typography normalization and explicitly records its intended size changes; inline responses distinguish those from the unchanged public-heading extraction.

[cubic-dev-ai]

@cubic-dev-ai review this PR. The description now covers the complete typography normalization and explicitly records its intended size changes; inline responses distinguish those from the unchanged public-heading extraction.

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 60 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}