Retire the Superset reader setup and the ATOMA dashboard (PD-13)

ATOMA's users use the Petrolyst app; Superset keeps admins, editors and the
app's embedded dashboards. Removed: the "ATOMA Reader" role and its rules
(petrolyst_reader.py, ReaderAccessMixin, reader.css, the head template, the
SQL-hiding patch), the atoma-reader mapping (it now maps to nothing in
Superset), the iframe allowance for the Map tab, and the "atoma" dashboard
with its Fleet/Map tab, D0 and dashboard.css. The bundle holds atoma-overview
and atoma-site only (byte-identical to before); the guest role keeps the
reader's 12 permissions in roles/atoma_guest.py. Brand files now name
petrolyst-web. SPEC marks the retired parts as history.

Checks (local): bundle checks pass; image rebuilt and healthy; import with
column drift 0 and unchanged embedding ids; the production config loads with
OAuth, embedding off, no reader hook; admin sees atoma-site with its tabs and
filter column; the app's browser tests pass 10/10. shellcheck not run (not
installed). Not deployed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

petrolyst-insights/dashboards/atoma/SPEC.md

@@ -1,13 +1,17 @@
-# ATOMA dashboard: Fleet map and Site details
+# ATOMA dashboards: Overview and Site, for the Petrolyst app
 
-**Status: built and tested on a local Superset (P2, 24 Oct 2026); merged into one dashboard with
-the fleet-map view on 28 Oct 2026 (§9); not imported live.**
-- `build_bundle.py` generates the dashboard, every dataset and every chart from this
+**Status (29 Oct 2026, PD-13): two dashboards, `atoma-overview` and `atoma-site` (§10), built and
+tested on a local Superset; not imported live.** The Petrolyst app embeds them, and admins open
+them in Superset with the filter column.
+- `build_bundle.py` generates the dashboards, every dataset and every chart from this
   specification, as one Superset import bundle; `import_bundle.py` imports it (§6).
-- The local tests changed parts of this design. Each change is marked *(P2)* and §8 lists them.
-- The merge of 28 Oct (owner's decisions PD-5 and PD-6, `Petrolist/.context/design-decisions.md`)
-  replaced the Sites Map dashboard by a Fleet tab holding the fleet-map view of petrolyst-platform.
-  Changed parts are marked *(28 Oct)*; §9 lists the results.
+- **Retired 29 Oct (PD-13):** the "ATOMA" dashboard (slug `atoma`) with its Map tab (the React
+  fleet-map view of petrolyst-platform) and Insights tab, its D0 header row, and the Superset
+  reader setup ("ATOMA Reader", `reader.css`). ATOMA's users use the Petrolyst app. §2, §3, §9 and
+  the readers' part of §6 describe them and stay as history. §4's data rules and four tabs are
+  current: they are `atoma-site`'s tabs, without D0 (the app shows the site's header).
+- Earlier changes are marked *(P2)* (local tests of 24 Oct, §8) and *(28 Oct)* (one dashboard
+  with the fleet-map view, §9).
 - Nothing is imported into the live Superset without the owner's go-ahead (phase P3).
 
 **Datasets.** The `public.v_*` views of
@@ -20,8 +24,7 @@ the fleet-map view on 28 Oct 2026 (§9); not imported live.**
 - the site-specific facts left out here (positions, distances, pilot sites) are there too;
 - Q-numbers refer to its §7, and phases P0–P5 to its §8.
 
-One dashboard (two until 28 Oct) replaces the earlier tab-per-site design; nothing in it is
-specific to a site.
+Nothing in the dashboards is specific to a site.
 
 ## 1. Capabilities of the installed Superset 6.1.0
 
@@ -53,7 +56,7 @@ still holds: the view builds the same `?native_filters=` link.
 
 No custom frontend and no patch are needed.
 
-## 2. Navigation flow
+## 2. Navigation flow *(retired, PD-13: history)*
 
 *(28 Oct)* One dashboard, two top-level tabs. *(29 Oct)* They are named **Map** (`TAB-fleet`) and
 **Insights** (`TAB-site`), the dashboard's lenses; earlier text in this document calls them Fleet and
@@ -93,7 +96,7 @@ Until 28 Oct there were two dashboards: "ATOMA - Sites" (slug `atoma-sites`: a d
 filters, a sites list) and "ATOMA - Site Detail" (slug `atoma-site-detail`), linked by "Open site
 detail" and "← Sites map".
 
-## 3. Fleet tab: the fleet-map view *(28 Oct)*
+## 3. Fleet tab: the fleet-map view *(28 Oct; retired, PD-13: history)*
 
 The Fleet tab holds one Markdown block with an iframe of the fleet-map view, a page of
 petrolyst-platform (`views/src/fleet-map/`) served under `/views/` on Superset's own origin. The
@@ -135,7 +138,10 @@ thousands of sites stay fast.
 **Sites without an accepted location** are not plotted. The key counts them, and the Site filter
 in Site details lists every site, placed or not.
 
-## 4. Site details tab (any site)
+## 4. Site details: the four tabs of `atoma-site` (any site)
+
+*(PD-13)* What follows about D0 (the site header row) and the Fleet tab is history: the app shows
+the site's header, and its Map lens replaced the Fleet tab.
 
 **Filters**
 - **Site** (`NATIVE_FILTER-site`):
@@ -248,10 +254,12 @@ is grouped or filtered by `metric` and `population_key` (both in `v_interval`),
 across methods or generator sets. The site's L/h figure itself comes only from a baseline version
 (`v_site`), never from this metric. There is no AVG metric on ratio columns.
 
-**Site details link** *(28 Oct)*. The fleet-map view builds it (petrolyst-platform
-`views/src/shared/deepLink.ts`) from its iframe address: the dashboard path, the Site filter's id
-and the tab. The rison shape is the one the sites list used until 28 Oct, confirmed in P2, and the
-view's tests compare it with that list's Trino output:
+**Site details link** *(28 Oct; history since PD-13)*. The fleet-map view built it
+(petrolyst-platform `views/src/shared/deepLink.ts`, retired) from its iframe address: the
+dashboard path, the Site filter's id and the tab. The Petrolyst app uses the same rison shape for
+the Site filter's preset (`app/src/app/core/site-filter.ts`). The rison shape is the one the sites
+list used until 28 Oct, confirmed in P2, and the view's tests compared it with that list's Trino
+output:
 
 ```
 /superset/dashboard/atoma/?native_filters=<url-encoded:>
@@ -312,7 +320,8 @@ appears on every Superset page, including the stock dashboard list: a capability
 same sign-in *(28 Oct: not built yet; locally it has none)*. No Gamma role until the
 ATOMA-facing edit.
 
-**ATOMA's readers** *(owner, 29 Oct)*. The Superset role **"ATOMA Reader"** (Keycloak client role
+**ATOMA's readers** *(owner, 29 Oct; retired the same day, PD-13: readers use the Petrolyst
+app; kept as history)*. The Superset role **"ATOMA Reader"** (Keycloak client role
 `atoma-reader`) reads the ATOMA dashboard and nothing else.
 - **The role** (`petrolyst-insights/roles/atoma_reader.py`): exactly 12 permissions, set by
   `superset-init` whenever the image changes, and reset by hand with the command in the README.
@@ -357,6 +366,9 @@ ATOMA-facing edit.
 
 ## 7. Acceptance checks
 
+*(PD-13)* Written for the retired ATOMA dashboard. Where they name D0 or the fleet map, the app's
+site header and Map lens take their place (petrolyst-platform's browser tests).
+
 Run in P2 against a local Superset, and repeated as a smoke test in P3.
 
 1. **New site, no new objects.** Count dashboards, charts and datasets in the metadata database.
@@ -425,7 +437,7 @@ The marker palette is unchanged from §3. The dataviz palette check flags slate
 grey, which is intended for "insufficient evidence", and amber at 2.99:1 contrast. The label is
 always also shown as text, in the legend, the tooltip and M3.
 
-## 9. Fleet map results (local, 28 Oct 2026)
+## 9. Fleet map results (local, 28 Oct 2026) *(history)*
 
 Local Superset 6.1.0 rebuilt with the iframe setting, behind a local Traefik that serves Superset
 and the petrolyst-platform read service on one origin (as on the server); the fuel-db of P2.
@@ -547,11 +559,11 @@ These changes have not had an independent inspection (the owner skipped Codex).
 unchanged), sign-in through Keycloak, the server's routing of `/views`, sign-in for the read
 service, thousands of sites, and dark mode.
 
-## 10. The Petrolyst app's dashboards *(PD-12, local trial, 29 Oct 2026)*
+## 10. The Petrolyst app's dashboards *(PD-12, PD-13; local, 29 Oct 2026)*
 
 The Petrolyst app (petrolyst-platform `app/`, PD-12) shows Superset dashboards inside its
-Insights lens, with guest passes from its app service. `build_bundle.py` builds them beside the
-unchanged ATOMA dashboard:
+Insights lens, with guest passes from the Petrolyst server (petrolyst-platform `server/`).
+`build_bundle.py` builds them (since PD-13 the only dashboards in the bundle):
 
 | Slug | Content | Filters (set by the app; Superset's filter column is hidden) |
 |---|---|---|
@@ -569,11 +581,9 @@ unchanged ATOMA dashboard:
   recorded values across sites (`OVERVIEW_METRICS`); per-site rates (L/h, L/day) are never
   averaged; money is grouped by `currency_text`, a missing currency is its own row, and no
   total crosses currencies. `build_bundle.py` checks both.
-- They carry no CSS; `dashboard.css` and `reader.css` are checked against the ATOMA dashboard
-  only.
+- They carry no CSS.
 - `import_bundle.py --embedded-out FILE --embed-domain URL` makes them embeddable from the app's
-  origin and writes `{slug: embedding id}` for the app service; the reader role stays on the
-  ATOMA dashboard only.
+  origin and writes `{slug: embedding id}` for the Petrolyst server.
 - Embedding is switched on in the local stack only (`.local/fmdb-scratch`,
   `superset_config_local.py`); production keeps it off until PD-12's open points are settled.
 - **Checked (local):** a self-signed guest pass opens its own dashboard and nothing else (another