@the-portland-company/shell 0.78.0 → 0.80.0

package/CHANGELOG.md

@@ -1,3 +1,20 @@
+## 0.80.0
+
+The URL-state helper. Specs cited: Reference/UI-Platform "URL state" (decided 2026-10-06, Spencer) and Global Rules → URL State. Until now the page said the helper "ships in a shell minor release" and no app could carry `section=` without concatenating by hand.
+
+- **`@the-portland-company/shell/url-state`** (pure, server- and client-safe): `readUrlState`, `writeUrlState`, `buildSearch`, `normalizeUrlState`, `historyMode`, `slugify`, `URL_STATE_KEYS`, `URL_STATE_MODES`.
+- Reads and writes `?mode=&page=&tab=&section=&org_id=` in the fixed order, keeps every feature parameter after them in its own order, writes a full org uuid as its 7-character tail, and refuses a feature parameter that names a base key.
+- `normalizeUrlState(search, { page, mode?, tabs?, sections?, org_id? })` fills a missing default and corrects an unknown `tab` or `section` to the first one, reporting whether the URL needs a replace. `historyMode(prev, next)`: `push` for a `mode`, `org_id`, `page` or `tab` change, `replace` for a `section`-only change or a normalization.
+- Section tracking on scroll (debounced replace) and the scroll-into-view on load are the consuming app's to wire with this helper; the shell's own frame does not touch the URL.
+
+## 0.79.0
+
+Battleground and District Data on their own hosts. Specs cited: Reference/UI-Platform "Dashboard, Battleground and District Data are three features in two Modes" (decided 2026-10-12), Specs/Left-Navigation §9.2, §13 ("Measured 2026-10-12") and §14.
+
+- **Registry.** `battleground` origin → `https://battleground.politogyvrm.com`, `districts` origin → `https://districts.politogyvrm.com` (both `mode: 'campaign'`, unchanged otherwise).
+- **Left bar.** The Campaign tree's Battleground and District data rows link to those hosts (`.../battleground`, `.../districts`, org carried as before).
+- **Served by** the dashboard deployment (politogy-dashboard #47), which answers at the new hosts and, with `CAMPAIGN_HOSTS_LIVE`, redirects its old `dashboard.politogyvrm.com/battleground` and `/districts` paths there permanently. Release this and flip that flag together.
+
 ## 0.78.0
 
 Dashboard, Battleground and District Data are three features in two Modes; no Polls row in the Relationship left bar. Specs cited: Reference/UI-Platform "Dashboard, Battleground and District Data are three features in two Modes" (decided 2026-10-12, Ben), Specs/Left-Navigation §9.1 and §9.2.

package/dist/app-chrome.cjs

@@ -2171,6 +2171,8 @@ var SIGNS_ORIGIN = "https://signs.politogyvrm.com/";
 var POLLS_ORIGIN = "https://polls.politogyvrm.com/";
 var SETTINGS_ORIGIN = "https://settings.politogyvrm.com/";
 var DASHBOARD_ORIGIN = "https://dashboard.politogyvrm.com/";
+var BATTLEGROUND_ORIGIN = "https://battleground.politogyvrm.com/";
+var DISTRICTS_ORIGIN = "https://districts.politogyvrm.com/";
 var AUTH_ORIGIN = "https://auth.politogyvrm.com/";
 var PETITION_MODE_ORIGIN = "https://petition-mode.politogyvrm.com/";
 function applyHiddenItems(items, hidden) {
@@ -2377,15 +2379,11 @@ function standardPolitogyNav(opts) {
       // Battleground is the Campaign landing page; there is no Campaign
       // Dashboard row, and Voter Contact and Tribes have no row.
       { kind: "section", label: "Race data" },
-      // Battleground is its own Campaign Mode app (registry key
-      // `battleground`), not part of the Dashboard. It is served from the
-      // dashboard deployment only until battleground.politogyvrm.com is live
-      // (Reference/UI-Platform, decided 2026-10-12).
-      { label: "Battleground", icon: icon("crosshair"), href: withOrg(`${DASHBOARD_ORIGIN}battleground`) },
-      // District Data is its own Campaign Mode app (registry key
-      // `districts`); served from the dashboard deployment until
-      // districts.politogyvrm.com is live.
-      { label: "District data", icon: icon("landmark"), href: withOrg(`${DASHBOARD_ORIGIN}districts`) },
+      // Battleground is the Campaign Mode landing page, its own app on its own
+      // host (registry key `battleground`; Specs/Left-Navigation §9.2, §13, §14).
+      { label: "Battleground", icon: icon("crosshair"), href: withOrg(`${BATTLEGROUND_ORIGIN}battleground`) },
+      // District Data is its own Campaign Mode app on its own host (registry key `districts`).
+      { label: "District data", icon: icon("landmark"), href: withOrg(`${DISTRICTS_ORIGIN}districts`) },
       { kind: "section", label: "Research" },
       {
         label: "Polling",
@@ -4551,17 +4549,14 @@ var POLITOGY_APPS = {
   // hosts org settings & billing (Specs/Organization-Settings).
   dashboard: { title: "Dashboard", origin: "https://dashboard.politogyvrm.com", storagePrefix: "dashboard" },
   // Battleground (the Campaign Mode landing page) and District Data are
-  // Campaign Mode features, each its own app (Specs/Left-Navigation §9.2;
-  // Reference/UI-Platform, decided 2026-10-12). They are never rendered with
-  // `app="dashboard"`: that frame is the Relationship rail, which is how they
-  // came to show inside Relationship Mode. Their hosts are decided
-  // (UI-Platform, 2026-10-12): battleground.politogyvrm.com and
-  // districts.politogyvrm.com. Neither is live yet, so the pages are still
-  // served from the dashboard deployment and the origin below is that host.
-  // When a host goes live, change its origin here and its row's href in
-  // standardNav in the same release.
-  battleground: { title: "Battleground", origin: "https://dashboard.politogyvrm.com", storagePrefix: "battleground", mode: "campaign" },
-  districts: { title: "District Data", origin: "https://dashboard.politogyvrm.com", storagePrefix: "districts", mode: "campaign" },
+  // Campaign Mode features, each its own app on its own host (Specs/Left-
+  // Navigation §9.2, §13, §14; Reference/UI-Platform, decided 2026-10-12).
+  // They are never rendered with `app="dashboard"`: that frame is the
+  // Relationship rail. The dashboard deployment serves these hosts
+  // (politogy-dashboard #47) and redirects its old /battleground and
+  // /districts paths here; the rows' hrefs in standardNav move together.
+  battleground: { title: "Battleground", origin: "https://battleground.politogyvrm.com", storagePrefix: "battleground", mode: "campaign" },
+  districts: { title: "District Data", origin: "https://districts.politogyvrm.com", storagePrefix: "districts", mode: "campaign" },
   settings: { title: "Settings", origin: "https://settings.politogyvrm.com", storagePrefix: "settings" },
   petitions: {
     title: "Petitions",