feat(supabase): the scoped role never stopped a superuser from logging in

pmoves/docker-compose.yml

@@ -581,6 +581,11 @@ services:
     volumes:
     - supabase-db-data:/var/lib/postgresql/data
     - ./supabase/initdb:/docker-entrypoint-initdb.d/pmoves-init:ro
+    # Repo-managed pg_hba. The image ships this at /etc/postgresql/pg_hba.conf --
+    # the container's WRITABLE LAYER, not the data volume -- so an in-container
+    # edit is discarded by the next recreate. Mounting it makes the tailnet
+    # role-scoping durable. See the file's own header for why the rules exist.
+    - ./supabase/config/pg_hba.conf:/etc/postgresql/pg_hba.conf:ro
     networks:
     - pmoves_data
     - pmoves_api  # Services on pmoves_api need DB access

pmoves/supabase/config/pg_hba.conf

@@ -0,0 +1,115 @@
+# PostgreSQL Client Authentication Configuration File
+# ===================================================
+#
+# Refer to the "Client Authentication" section in the PostgreSQL
+# documentation for a complete description of this file.  A short
+# synopsis follows.
+#
+# This file controls: which hosts are allowed to connect, how clients
+# are authenticated, which PostgreSQL user names they can use, which
+# databases they can access.  Records take one of these forms:
+#
+# local         DATABASE  USER  METHOD  [OPTIONS]
+# host          DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostssl       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostnossl     DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostgssenc    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostnogssenc  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+#
+# (The uppercase items must be replaced by actual values.)
+#
+# The first field is the connection type: "local" is a Unix-domain
+# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
+# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
+# non-SSL TCP/IP socket.  Similarly, "hostgssenc" uses a
+# GSSAPI-encrypted TCP/IP socket, while "hostnogssenc" uses a
+# non-GSSAPI socket.
+#
+# DATABASE can be "all", "sameuser", "samerole", "replication", a
+# database name, or a comma-separated list thereof. The "all"
+# keyword does not match "replication". Access to replication
+# must be enabled in a separate record (see example below).
+#
+# USER can be "all", a user name, a group name prefixed with "+", or a
+# comma-separated list thereof.  In both the DATABASE and USER fields
+# you can also write a file name prefixed with "@" to include names
+# from a separate file.
+#
+# ADDRESS specifies the set of hosts the record matches.  It can be a
+# host name, or it is made up of an IP address and a CIDR mask that is
+# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
+# specifies the number of significant bits in the mask.  A host name
+# that starts with a dot (.) matches a suffix of the actual host name.
+# Alternatively, you can write an IP address and netmask in separate
+# columns to specify the set of hosts.  Instead of a CIDR-address, you
+# can write "samehost" to match any of the server's own IP addresses,
+# or "samenet" to match any address in any subnet that the server is
+# directly connected to.
+#
+# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
+# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".
+# Note that "password" sends passwords in clear text; "md5" or
+# "scram-sha-256" are preferred since they send encrypted passwords.
+#
+# OPTIONS are a set of options for the authentication in the format
+# NAME=VALUE.  The available options depend on the different
+# authentication methods -- refer to the "Client Authentication"
+# section in the documentation for a list of which options are
+# available for which authentication methods.
+#
+# Database and user names containing spaces, commas, quotes and other
+# special characters must be quoted.  Quoting one of the keywords
+# "all", "sameuser", "samerole" or "replication" makes the name lose
+# its special character, and just match a database or username with
+# that name.
+#
+# This file is read on server startup and when the server receives a
+# SIGHUP signal.  If you edit the file on a running system, you have to
+# SIGHUP the server for the changes to take effect, run "pg_ctl reload",
+# or execute "SELECT pg_reload_conf()".
+#
+# Put your actual configuration here
+# ----------------------------------
+#
+# If you want to allow non-local connections, you need to add more
+# "host" records.  In that case you will also need to make PostgreSQL
+# listen on a non-local interface via the listen_addresses
+# configuration parameter, or via the -i or -h command line switches.
+
+# TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+# trust local connections
+local all  supabase_admin     scram-sha-256
+local all  all                peer map=supabase_map
+host  all  all  127.0.0.1/32  trust
+host  all  all  ::1/128       trust
+
+# --- Tailnet (Tailscale CGNAT) -------------------------------------------------
+# Step 3.5 of the juicefs-meta cross-node lane (handoff 2026-08-18), added
+# 2026-08-23. That handoff's stated safety property was "the scoped role is what
+# keeps this from being a superuser surface". It is not, on its own: a scoped
+# role changes which credential JuiceFS USES; it does nothing to stop a superuser
+# credential from being ACCEPTED. `host all all 0.0.0.0/0 scram-sha-256` below
+# admits EVERY role -- including pmoves and supabase_admin, both rolsuper and
+# rolbypassrls. Once :5432 is tailnet-published, that is a superuser login
+# surface on the tailnet, which is the exact outcome the lane's ordering exists
+# to prevent.
+#
+# Source IPs survive: Docker's only MASQUERADE rules are `-s <bridge> ! -o
+# <bridge>` (container -> outside). Inbound published-port traffic is pure DNAT
+# with no source rewrite, so a remote peer arrives here as its real 100.x.
+#
+# FIRST MATCH WINS -- these must stay ABOVE the catch-alls that follow.
+host  all  juicefs_meta  100.64.0.0/10        scram-sha-256
+host  all  all           100.64.0.0/10        reject
+host  all  juicefs_meta  fd7a:115c:a1e0::/48  scram-sha-256
+host  all  all           fd7a:115c:a1e0::/48  reject
+
+# IPv4 external connections
+host  all  all  10.0.0.0/8  scram-sha-256
+host  all  all  172.16.0.0/12  scram-sha-256
+host  all  all  192.168.0.0/16  scram-sha-256
+host  all  all  0.0.0.0/0     scram-sha-256
+
+# IPv6 external connections
+host  all  all  ::0/0     scram-sha-256