improvement(ui): share account status headings

[BillLeoutsakosvl346]

Summary

• Share the repeated 32px heading treatment across invitation and email-preference states.
• Preserve each description, heading text, spacing and all loading/error/success behavior.

Type of Change

• Refactor / maintainability improvement

Testing

• Full workspace type checks, lint, repository audits (including import and API validation), generators and docs checks pass.
• External source comparison confirms caller logic and content are unchanged.
• Before/after browser fixtures cover the changed component's styling and interactions. Original and extracted controls have matching computed styles. These are isolated fixtures, not full authenticated product flows.
• Relevant existing tests pass. No landing-page changes or audit tooling included.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 20, 2026 11:52pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding findings.

Summary

Extracts the repeated invitation and email-preference heading markup into InviteHeading, preserving heading text, description content, styling, spacing, and existing state handling.

• Exports the shared heading through the invitation components barrel for external consumers.
• Updates invitation status cards and unsubscribe states to use the shared component.
• No changes have been made since the previous review, and no new findings were identified.

_{Reviews (3) · Last reviewed commit: "chore(ui): export invite heading through..."}

[cubic-dev-ai]

No issues found across 3 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.

[cubic-dev-ai]

No issues found across 4 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.

[cubic-dev-ai]

No issues found across 4 files

Confidence score: 5/5

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

_{Re-trigger cubic}