@the-portland-company/shell 0.24.0 → 0.25.0

package/CHANGELOG.md

@@ -1,3 +1,73 @@
+## 0.25.0 — 2026-07-23
+
+### Added — `PolitogyAppFrame`: one component owns the whole app frame
+
+Shipping the same package at the same version was never enough: the package
+exported PRIMITIVES and every app hand-assembled them in its own ~150-line
+`Shell.tsx`, so identical inputs were never guaranteed and production drifted.
+Apps now render
+
+```tsx
+<PolitogyAppFrame app="forms" pathname={pathname} linkComponent={Link}
+                  session={{ userId, email, role, accountName, accountId }}
+                  onSignOut={signOut}>{children}</PolitogyAppFrame>
+```
+
+and pass **nothing** about the chrome — no nav, breadcrumbs, title, mode, user
+menu, footer or theme. What an app cannot pass, it cannot drift on.
+`POLITOGY_APPS` is the single per-app registry (title / origin / storage key).
+
+### Added — brand-driven app icons (`./app-icons`)
+
+`politogyAppIcons(app)` resolves favicons from `GET /api/icons/<app>` at runtime
+(60s revalidate) for use in Next `generateMetadata()`, ending at the VRM Core
+logo when an app has no icon of its own. Never throws.
+
+### Fixed — Surveys sub-menu rendered entirely active
+
+`standardPolitogyNav` gave Surveys / Canvas / Results the **identical href**
+(`https://surveys.politogyvrm.com/surveys`), so on surveys.politogyvrm.com every
+child matched active-detection and the whole sub-menu lit up race-red. Canvas
+and Results are survey-scoped routes with no id-less destination, so the group
+now carries only the reachable list route. A regression test asserts no two
+sibling nav items anywhere in the standard nav share an href.
+
+### Fixed — theme kept reverting to Light
+
+A theme picked on Politogy ID (which has no chrome-API session) only reached the
+cookie; the next app's reconcile then read the **stale** profile value from
+`GET me` and overwrote the user's fresh choice. A choice is now marked pending
+(`politogy_theme_pending`, cross-subdomain) until it is written to the profile,
+and the first app that can reach the chrome API pushes it UP instead of pulling
+the stale value down.
+
+### Fixed — an email is never rendered as a user's name
+
+Identity is resolved by the package from the chrome API (`useChromeIdentity`),
+with the app's session claim as a pre-hydration fallback only. Forms passed
+`user.name ?? user.email`, so a user with no name set saw their email in the
+top-right and the "add your name" affordance never fired.
+
+### Fixed — the mode pill is no longer hardcodable
+
+`useChromeMode()` derives the current mode from the org's entitlements and the
+USER'S selection (persisted cross-app as `vrm.activeMode`); the argument is now
+only a pre-entitlement fallback. Apps passed the literal `'relationship'`.
+
+### Fixed — breadcrumbs are derived, not hand-built
+
+`deriveBreadcrumbs()` builds **Dashboard › Sub › Item** from the same nav tree
+the sidebar renders. Polls previously rendered a lone "Polls" crumb under a
+"Polls" title ("Polls / Polls").
+
+### Fixed — apps no longer declare chrome CSS variables
+
+`chrome.css` now emits the app-surface aliases (`--color-bg`, `--color-surface`,
+`--color-panel`, `--color-border`, `--color-text`, `--color-accent`,
+`--skeleton-*`, …) in light and neutral-black dark. Every app had defined its
+own fallback palette and they had drifted — surveys' accent was `#C8102E` where
+every other app was `#E63946`.
+
 ## 0.11.3 — 2026-07-20
 
 ### Fixed (native — token contract + client boundary)