@the-portland-company/shell 0.55.0 → 0.57.0

package/CHANGELOG.md

@@ -1,3 +1,73 @@
+## 0.57.0 — 2026-09-30
+
+### Fixed — 10DLC alert no longer auto-redirects on every login (`src/native/chromeActions.tsx`)
+
+The once-per-session `10dlc_registration` alert redirect fired on every
+login because every login is a new browser session (a fresh
+`sessionStorage`), so the full-page `window.location.assign` re-booted the
+app on every single sign-in — visible to the user as a second loading-screen
+blink that always lands on
+`/organization-settings/subscription-billing/text-email`. The auto-redirect
+is removed entirely. The alert still surfaces in the notifications
+bell/panel (unread, like any other alert) — that panel is now the only
+user-visible surface for it.
+
+### Added — Spec overlay top-bar action, Spencer + Ben only (`./native`, `./app-chrome`)
+
+A new `SpecOverlayAction` top-bar control (wired into `ChromeTopBarActions`,
+between DevNotes and Support) shows the live spec/visual-regression status
+of the current page, sourced from the Specs app's overlay API
+(`https://specs.politogyvrm.com/api/overlay/access` and `/api/overlay/status`).
+It renders nothing — no icon, no network noise — for anyone the access
+check doesn't allow; the allow/deny answer is cached in `sessionStorage`
+for the session. When allowed, a "Spec" button shows a rounded
+mismatch-percentage badge (green when the compare passed, red when it
+didn't, a neutral "—" when the page has no compare target yet) and opens a
+480px right-hand drawer with the spec title, "Open spec" / "Compare tab"
+links, and an iframe of the live overlay. Status re-fetches (debounced
+300ms) on route change and org change. All calls are plain
+`fetch(..., { credentials: 'include' })` against the Specs origin — this
+does NOT go through the same-origin chrome proxy `fetchJson`.
+
+### Fixed — de-duped chrome fetches + lazy DevNotes boot fetch (`src/native/chromeActions.tsx`, `src/app-chrome/index.tsx`)
+
+`useChromeOrgs`, `me`, `FuelAction`'s `communications/fuel-status`, and
+`NotificationsAction`'s `notifications` were each fetched 2-4x per page load
+(consumers mounting independently), costing 1-3.5s per redundant call. Added
+a provider-scoped in-flight-promise + 30s-TTL cache
+(`dedupedFetch`/`invalidateChromeCache` on `useNavChrome`) keyed by
+`(path, orgId)`, so concurrent consumers share one request and org switches
+naturally miss the cache. Separately, DevNotes' boot-time reads (tasks,
+task types, task lists, collaborators, app-link status, capabilities — up to
+6.8s cold) are deferred until the DevNotes panel is first opened by wrapping
+the adapter passed into `@the-portland-company/devnotes`'s
+`DevNotesProvider`; the launcher button renders instantly and unblocks the
+gated calls via `onPointerDownCapture` before the click fires. The unread
+badge count still resolves on boot, via `requestIdleCallback` instead of
+blocking it.
+
+## 0.56.0 — 2026-09-30
+
+### Fixed — mode continuity for dual-mode apps (a2p)
+
+a2p (Specs/A2P) is the SMS/MMS delivery engine for BOTH Relationship Mode and
+Campaign Mode, but it was registered `mode: 'campaign'` only, so the
+Relationship tree's "SMS/MMS Blast" row sent users into a2p and the whole left
+nav flipped to the Campaign tree + "Campaign Mode" pill — a jarring identity
+switch for a user who never left Relationship Mode.
+
+`POLITOGY_APPS[app]` now supports an optional `dual: { modes, defaultMode }`.
+a2p declares `dual: { modes: ['relationship', 'campaign'], defaultMode:
+'campaign' }`; its EFFECTIVE mode is resolved per-visit by the new
+`resolveActiveMode` (`src/mode-preference.ts`): `?mode=` query param → the new
+cross-subdomain `politogy_active_mode` cookie → the app's own default. Every
+pinned app and core writes that cookie with its own mode, so arriving at a2p
+after using Relationship Mode elsewhere resolves to Relationship even without
+an explicit `?mode=` link. The Relationship tree's "SMS/MMS Blast" row now
+links straight to a2p with `?mode=relationship` (the dead
+`/relationship/sms-mms-blast/*` core routes are removed); the Campaign tree's
+existing A2P row is unchanged.
+
 ## 0.55.0 — 2026-09-30
 
 ### Fixed — org pill body no longer takes the Mode accent (`./native`)