Remove Trino: Superset reads fuel-db directly as fuel_ro (PD-14)

trino/ deleted; the role trino_ro becomes fuel_ro, its password read from a
secret file at connect time; dashboards' SQL and column list for PostgreSQL;
the Compose project is renamed petrolyst, with volumes pinned to their old
names. AGENTS.md points to the architecture context. Not deployed: the next
deploy needs README's one-time steps first.

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

stacks/fuel-monitoring/compose.yaml

@@ -1,9 +1,9 @@
 # Fuel-monitoring analytics: Superset on atoma.petrolyst.com, reading the
-# operational store (fuel-db) through Trino. Run only through deploy/deploy.sh
-# or deploy/rollback.sh: they export SUPERSET_IMAGE_TAG and TRINO_CONFIG_HASH
-# from the release's ARTIFACTS file, and the :? guards below stop Compose from
-# running with either unset.
-name: fuel-monitoring
+# operational store (fuel-db) directly as the read-only role fuel_ro (Trino was
+# removed on 29 Oct 2026). Run only through deploy/deploy.sh or
+# deploy/rollback.sh: they export SUPERSET_IMAGE_TAG from the release's
+# ARTIFACTS file, and the :? guard below stops Compose from running without it.
+name: petrolyst
 
 x-superset-env: &superset-env
   KEYCLOAK_REALM_URL: ${KEYCLOAK_REALM_URL:-https://iam.thedigitalbridge.io/realms/thedigitalbridge}
@@ -15,6 +15,8 @@ x-superset: &superset
     - superset_secret_key
     - superset_db_password
     - keycloak_petrolyst_client_secret
+    # fuel_ro's password, read at connect time (superset_config.py)
+    - fuel_db_ro_password
 
 services:
   superset:
@@ -100,25 +102,6 @@ services:
       timeout: 5s
       retries: 10
 
-  trino:
-    image: trinodb/trino:484
-    env_file:
-      - ${PETROLYST_ROOT:-/opt/petrolyst}/env/fuel-monitoring.env
-    volumes:
-      - ./trino/etc:/etc/trino:ro
-    labels:
-      # Compose cannot see content changes in a bind mount; this label changes
-      # with trino/etc, so exactly a config change recreates the container.
-      petrolyst.config-hash: ${TRINO_CONFIG_HASH:?TRINO_CONFIG_HASH unset - run through deploy/deploy.sh}
-    depends_on:
-      fuel-db:
-        condition: service_healthy
-    networks:
-      - backend
-    restart: unless-stopped
-    mem_limit: 3g
-    # The image's own healthcheck (/usr/lib/trino/bin/health-check) applies.
-
   fuel-db:
     image: timescale/timescaledb:2.31.0-pg17
     environment:
@@ -128,7 +111,7 @@ services:
       TS_TUNE_NUM_CPUS: "2"
     secrets:
       - fuel_db_password
-      - fuel_db_trino_password
+      - fuel_db_ro_password
     volumes:
       - fuel_db_data:/var/lib/postgresql/data
       # A single file, not the folder: the image's own TimescaleDB init scripts
@@ -157,9 +140,14 @@ networks:
   # so fuel-db's loopback port works.
   fuel-db-tunnel: {}
 
+# Created under the project's first name, fuel-monitoring; named explicitly so the
+# data stayed when the project became petrolyst (29 Oct 2026). Compose warns once
+# that they belong to another project; that is expected.
 volumes:
   superset_db_data:
+    name: fuel-monitoring_superset_db_data
   fuel_db_data:
+    name: fuel-monitoring_fuel_db_data
 
 secrets:
   superset_secret_key:
@@ -168,7 +156,7 @@ secrets:
     file: ${PETROLYST_ROOT:-/opt/petrolyst}/secrets/fuel-monitoring/superset_db_password
   fuel_db_password:
     file: ${PETROLYST_ROOT:-/opt/petrolyst}/secrets/fuel-monitoring/fuel_db_password
-  fuel_db_trino_password:
-    file: ${PETROLYST_ROOT:-/opt/petrolyst}/secrets/fuel-monitoring/fuel_db_trino_password
+  fuel_db_ro_password:
+    file: ${PETROLYST_ROOT:-/opt/petrolyst}/secrets/fuel-monitoring/fuel_db_ro_password
   keycloak_petrolyst_client_secret:
     file: ${PETROLYST_ROOT:-/opt/petrolyst}/secrets/shared/keycloak_petrolyst_client_secret