fix(web): normalize product typography and technical-number formatting

[jeanduplessis]

Problem

Product screens reconstruct headings, labels, metrics, and code typography with arbitrary sizes and weights. Financial, date, metric, and aligned numeric values often omit mono/tabular formatting.

Remediation action

Apply canonical type-* roles and technical-number formatting throughout audited product UI.

Representative scope

• apps/web/src/components/auth/SignInForm.tsx:63
• apps/web/src/components/organizations/OrganizationInfoCard.tsx:238
• apps/web/src/app/(app)/invoices/InvoicesPageClient.tsx:70
• apps/web/src/components/referrals/KiloPassReferralPageContent.tsx:238
• apps/web/src/app/(app)/cloud/mcp-gateway/McpGatewayListContent.tsx:101
• apps/web/src/components/usage-analytics/UsageAnalyticsDashboard.tsx:573
• apps/web/src/components/security-agent/dashboard/SlaComplianceHero.tsx:99
• apps/web/src/app/(app)/claw/components/billing/WelcomePage.tsx:686
• apps/web/src/app/(app)/wasteland/new/NewWastelandWizardClient.tsx:456
• apps/web/src/app/admin/early-fraud-warnings/EarlyFraudWarningsContent.tsx:41

Acceptance criteria

• Page titles, section headings, body, labels, eyebrows, and code use canonical role utilities without local metric overrides.
• Product UI does not introduce arbitrary 9–15px or oversized 30–48px scales.
• Financial values, timestamps, IDs, counts, percentages, and table metrics use mono and/or tabular-nums according to role.
• Monospace is limited to code, identifiers, metadata, and aligned technical data.
• Heading semantics remain ordered after visual-role changes.