Trino out of the code; commit messages name bands and rules

The rename step in init.sh and the guard in deploy/lib.sh are gone. README's
procedure is now "Removing the old project"; it keeps the old names until it
has run on the server. Migrations stay here (open point 8), and their README
says so. AGENTS.md adds the commit-message rule. Not deployed: live still runs
Trino.

Bands: 4 (Superset), persistence (docs). Rules: 2.

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

petrolyst-insights/README.md

@@ -16,7 +16,7 @@ and where it runs lives in `stacks/`, `traefik/`, `deploy/` and `host/`.
 | `superset_config.py` | Keycloak sign-in, role mapping, proxy and cookie settings, Redis caches, theme and chart palettes | `/app/pythonpath/` |
 | `petrolyst_security.py` | `PetrolystSecurityManager`: user info and roles from the Keycloak ID token, `/login/` straight to Keycloak, `/logout/` through Keycloak | `/app/pythonpath/` |
 | `roles/` | `atoma_guest.py`: the role "ATOMA Guest" for the Petrolyst app's embedded dashboards, with exactly its permissions; run by hand (see "Embedding") | `/app/petrolyst-roles/` |
-| `assets/branding/` | logos (full colour and white): the wordmark alone for the navbar, and the stacked logo; favicons, app icons; ATOMA's logo, which the Petrolyst app shows in its map's corner (`PETROLYST_OPERATOR_LOGO`) | `/app/superset/static/assets/branding/`, served at `/static/assets/branding/…` |
+| `assets/branding/` | logos (full colour and white): the wordmark alone for the navbar, and the stacked logo; favicons, app icons; ATOMA's logo, which the Petrolyst app shows in its map's corner (the server reads this file itself: `PETROLYST_OPERATOR_LOGO_FILE`) | `/app/superset/static/assets/branding/`, served at `/static/assets/branding/…` |
 | `patches/` | runtime patches, `fix_*.py` with `--verify` (see its README); none at present | `/app/patches/petrolyst/`, applied during the build |
 | `dashboards/` | exported dashboards and import scripts (see its README) | not in the image |
 

petrolyst-insights/dashboards/atoma/SPEC.md

@@ -16,8 +16,7 @@ them in Superset with the filter column.
 
 **Datasets.** The `public.v_*` views of
 `stacks/fuel-monitoring/fuel-db/migrations/0003_bi_views.sql`, read from fuel-db directly (database
-`fuel`, schema `public`) as the read-only role `fuel_ro`. *Until 29 Oct 2026 Superset read them
-through Trino as `fuel.public`; Trino was removed then.*
+`fuel`, schema `public`) as the read-only role `fuel_ro`.
 
 **Design and rationale** live in the fuel-monitoring corpus, in
 `.context/plans/2026-10-24-fuel-db-baseline-dashboard.md`:
@@ -259,7 +258,7 @@ across methods or generator sets. The site's L/h figure itself comes only from a
 (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
+list used until 28 Oct, confirmed in P2, and the view's tests compared it with that list's
 output:
 
 ```
@@ -409,7 +408,7 @@ Run in P2 against a local Superset, and repeated as a smoke test in P3.
 
 ## 8. P2 results (local, 24 Oct 2026)
 
-Local Superset 6.1.0 image built from this repository, Trino 484, fuel-db with migrations
+Local Superset 6.1.0 image built from this repository, fuel-db with migrations
 0001–0003 and the corpus data loaded; browser checks in headless Chrome.
 
 | Check | Result |

petrolyst-insights/superset_config.py

@@ -46,7 +46,7 @@ SQLALCHEMY_DATABASE_URI = URL.create(
 ).render_as_string(hide_password=False)
 
 # --- The data: fuel-db ----------------------------------------------------------
-# Superset reads fuel-db directly as the read-only role fuel_ro (no Trino since 29 Oct 2026);
+# Superset reads fuel-db directly as the read-only role fuel_ro;
 # superset-init registers that connection, "Fuel", without a password. Passwords of data
 # connections come from secret files at connect time, so none is kept in Superset's own
 # database. A connection added in the UI gets no password this way.