From 2c9f5e95ff0938fdb531f528dd23a4553660bfeb Mon Sep 17 00:00:00 2001 From: Michael Chihlas Date: Fri, 8 May 2026 00:07:51 -0400 Subject: [PATCH] =?UTF-8?q?fix(frontend):=20page-title=20=E2=80=94=20escap?= =?UTF-8?q?es=20+=20propagate=20plan=20taxonomy=20through=20frontend=20typ?= =?UTF-8?q?es?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two fixes that surfaced together: 1. LandingPage.tsx had `—` in a JSX attribute string — JSX attribute strings don't process JS escape sequences, so the literal six-character "—" was rendering in the browser tab title and OG description instead of the intended em dash. Replaced with the literal em dash character. Same pattern was previously valid because every other use of `\u...` in the codebase is inside a JS string (regular `'...'` string literal in TS, or `{...}` expression in JSX), where escapes resolve at compile time. Verified by grep — LandingPage was the only site with the bug. 2. PageMeta default fallback tagline was "Decision Tree Platform" — a stale tagline from before the FlowPilot pivot. Updated to the current "AI-Powered Troubleshooting for MSPs" (matches index.html and brand positioning). Default branch is rarely hit since every page passes a title, but cleaner. While building, hit TS errors that revealed the prior taxonomy commit (team -> enterprise + add starter) didn't propagate through the frontend. Cleared all of them: - types/account.ts, types/admin.ts: Subscription.plan, AdminAccountCreate.plan, InviteCodeCreateRequest.assigned_plan literals updated to the new tax. - types/billing.ts: dropped 'team' from CheckoutPlan (was hybrid old+new). - admin/AccountsPage.tsx, admin/InviteCodesPage.tsx: state-type literals, select onChange casts, and the visible