@mason-data/cli 0.7.0 → 0.8.0

package/README.md

@@ -1,60 +1,66 @@
 # @mason-data/cli
 
-The `mason` command points [Mason](https://masondata.ai) at the Postgres your app already uses, copies the tables you
-add, keeps the copy current, and serves it to BI tools and your app over the Postgres protocol. Every command works the
+The `mason` command points [Mason](https://github.com/embeddable-hq/mason-data) at the Postgres your app already uses, syncs the tables you
+add, keeps them up to date, and serves them to BI tools and your app over the Postgres protocol. Every command works the
 same for you and for a coding agent (Claude Code, Codex, …): it prints for a person, or with `--json` as data, and its
 exit code says how it went ([for coding agents](#for-coding-agents)).
 
 There is nothing to clone or build: install this package and run `mason`. It needs Node 22.13 or later and nothing
-else — no Docker, no database of its own; `mason doctor` checks this machine and says what is missing. On a terminal
+else — no Docker, no database of its own, and nothing downloaded after `npm install`: Mason's postgres and inet
+extensions come with it, as an optional dependency for your platform (`@mason-data/extensions-<platform>`, 17–31 MiB
+to download; installing with `--omit=optional` leaves them out, and the first sync then downloads them).
+`mason doctor` checks this machine and says what is missing. On a terminal
 its output is coloured and wrapped to the window, and a command that takes a moment shows a spinner; piped,
 redirected, with `--json` or with `NO_COLOR` set, it is plain text.
 
 **A Mason project is your app's folder.** `mason init` makes it one: its sources file in `mason/sources/` — the
-database and the tables to copy — yours to commit; this machine's copy of your data and Mason's state in `.mason/`,
+database and the tables to sync — yours to commit; this machine's synced data and Mason's state in `.mason/`,
 both rebuilt from that file. Every other command works
-anywhere in the folder, as git does. `mason destroy` removes the copy and the state. ([Cleaning up](#cleaning-up))
+anywhere in the folder, as git does. `mason destroy` removes the synced data and the state. ([Cleaning up](#cleaning-up))
 
 ```sh
 npm i -g @mason-data/cli
 cd my-app
 mason doctor                         # Node, memory, ports: what is missing, and what to do
-mason init                           # this folder becomes a project, on the database in .env's DATABASE_URL (checked first)
+mason init                           # this folder becomes a project, on the database .env names (checked first)
 mason tables                         # the tables: rows, keys, added; a table's columns with `mason tables orders`
 mason add orders customers           # add them to the sources file (--columns id,status: those only)
-mason start                          # Mason in the background, copying them, then returns
-mason wait                           # until every added table is copied and served
+mason start                          # Mason in the background, syncing them, then returns
+mason wait                           # until every added table is synced and served
 mason user add metabase              # a user for a BI tool: its password, printed once, and the URL to paste
-mason ui                             # the status page and the users, in your browser
+mason ui                             # the status, tables, users and statements, in your browser
 ```
 
 `mason init` takes the database's URL as an argument too (`mason init postgres://user:password@localhost:5432/your_app`);
-without one it reads `DATABASE_URL` from the folder's `.env.local`, `.env` or the shell. The sources file it writes says
-`url: ${DATABASE_URL}`, and the URL itself stays in `.env` (init writes the line there when you gave the URL as an
-argument or it was only in the shell, and gitignores that file): change it there when the password changes. The
-database is required.
+without one it reads `MASON_DATABASE_URL`, else `DATABASE_URL`, each from the folder's `.env.local`, `.env` or the
+shell — set `MASON_DATABASE_URL` to aim Mason at a database other than the one your app's `DATABASE_URL` names. The
+sources file it writes names the variable it read, `url: ${DATABASE_URL}` or `url: ${MASON_DATABASE_URL}` (given a URL
+as an argument, `MASON_DATABASE_URL` when your app's `DATABASE_URL` names another database), and the URL itself stays
+in `.env` (init writes the line there when you gave the URL as an argument or it was only in the shell, and gitignores
+that file): change it there when the password changes. The database is required.
 
 **No database at hand?** `mason init demo && mason start`, in a new folder, makes a project on a demo database Mason
 hosts itself — a small shop (`customers`, `products`, `orders`, `order_items`; the first three added, `order_items`
 left for your first `mason add order_items` after `mason start`), kept in `.mason/demo/`, served on a port of this machine, with a new order every few seconds (`MASON_DEMO_CHANGE_MS`, default 5000) so
-`mason status` shows the copy keeping up. Nothing to install. It is read by polling only (it has no change log), and
-`mason destroy` removes it with the copy.
+`mason status` shows the synced data keeping up. Nothing to install. It is read by polling only (it has no change log), and
+`mason destroy` removes it with the synced data.
 
 ## The project: its sources file, in your app
 
 ```
 my-app/
-  .env                    the database's URL (DATABASE_URL), as your app has it (gitignored)
-  .mason/                 this machine's: Mason's key, the copy of your data, its state and logs (gitignored)
-  mason/sources/app.yml   the database and the tables Mason copies — commit it
+  .env                    the database's URL (DATABASE_URL, as your app has it, or MASON_DATABASE_URL) (gitignored)
+  .mason/                 this machine's: Mason's key, the synced data, its state and logs (gitignored)
+  mason/sources/app.yml   the database and the tables Mason syncs — commit it
   mason/mason.yml         the Mason version the project is written for — commit it: production runs that version
 ```
 
-The sources file is named for the database (`app.yml` above) and lists what Mason copies, one entry per table:
+The sources file is named for the database (`app.yml` above) and lists what Mason syncs, one entry per table:
 
 ```yaml
 kind: postgres
 url: ${DATABASE_URL}          # a variable from .env.local, .env or the shell; a literal URL is allowed for local dev
+database: production          # optional: the database name a tool connects with (none: mason)
 tables:
   orders:                     # a bare name is in `public`; `billing.invoices` names its schema
     columns: [id, customer_id, status, amount, created_at, payload]
@@ -62,12 +68,14 @@ tables:
   events:
     exclude: [raw_body]       # every column but these
   sessions:
-    key: [tenant_id, id]      # only for a table with no primary key: the unique columns to copy it by
+    key: [tenant_id, id]      # only for a table with no primary key: the unique columns to key it by
 ```
 
-- An entry is `{}` (every column), `columns:` (those; the primary key is always copied), `exclude:` (every column but
+- An entry is `{}` (every column), `columns:` (those; the primary key is always synced), `exclude:` (every column but
   those) — never both — and, for a table with no primary key, `key:`: the columns that tell its rows apart, which it is
-  copied by (polling only: logical replication cannot apply a change by them). A table with a primary key refuses `key:`.
+  keyed by (polling only: logical replication cannot apply a change by them). A table with a primary key refuses `key:`.
+- A tool connects with the database name `mason`. A tool moving from your Postgres changes its host, port and database
+  name, or `database:` keeps the name it has, so it changes only its host and port.
 - Column types are not in the file: Mason reads them from the database at every start.
 - `url:` is `${NAME}`, read from `.env.local`, `.env` or the shell — or a literal URL, for a database on your machine.
 - One source per project for now, and `postgres` is its only kind.
@@ -77,11 +85,11 @@ tables:
   mistakes on one report, each with its key and the way out (`did you mean …?`).
 
 `mason init --folder <dir>` puts `sources/` elsewhere in the folder (`--folder .` for the folder itself). Keep it in
-your app's repo, so a schema change and the tables that copy it travel together. A teammate who clones the repo runs
+your app's repo, so a schema change and the tables that sync it travel together. A teammate who clones the repo runs
 `mason init` once: the sources file is kept, and `.mason/` is per machine.
 
 **A project an older Mason made** (its tables listed in `mason/models/`) is refused by `mason start`; nothing is
-migrated. `mason init` in it writes the sources file alone — its `.mason/` and copy kept — then `mason add` each table
+migrated. `mason init` in it writes the sources file alone — its `.mason/` and synced data kept — then `mason add` each table
 again and remove `mason/models/`.
 
 ## Commands
@@ -89,22 +97,24 @@ again and remove `mason/models/`.
 | Command | What it does |
 |---|---|
 | `mason help [<command> \| <guide>]` | The commands by step, one command's usage, or one of the guides, offline: `mason help agent` (driving Mason from a coding agent: the commands in order, `--json` and its shapes, exit codes, failures) and `mason help production` (the road from a laptop to production: the image, its settings, Docker Compose, logical replication, upgrades). |
-| `mason doctor` | Checks what Mason needs here — Node 22.13+, memory, Mason's ports — and in a project's folder its database; with Mason running for it, the run itself: whether every added table is copied, the statements refused or slow in the last day. Every failing line says what to do; it ends with the next command. |
-| `mason init [<postgres url>]` | Makes this folder a project: checks it can read the database (nothing is written when it cannot; `--skip-check` writes anyway), writes `.mason/config.json` (Mason's key, never the URL) and `mason/sources/<database>.yml` (keeping a sources file already there), adds the URL to `.env` when it was not there, and adds `.mason/` and that `.env` to `.gitignore`. The URL from the argument, else `DATABASE_URL` in `.env.local`, `.env` or the shell. `--name` sets the project's name (default: the folder's) — the database name a tool connects to — `--folder` where its files go, `--remote` allows a database on another machine. Refuses a folder already in a project, but for one with no sources file (an older Mason's), whose sources file alone it writes. |
-| `mason start` | Starts Mason for this folder's project in the background and returns once it is up. Run it again any time: it says so when Mason is already running. `--replication` reads the database's change log as production does (below); `--poll` goes back. `--self-signed-tls` serves the Postgres API over TLS; `--attach` stays in the foreground. |
+| `mason doctor` | Checks what Mason needs here — Node 22.13+, memory, Mason's ports — and in a project's folder its database; with Mason running for it, the run itself: whether every added table is synced, the statements refused or slow in the last day. Every failing line says what to do; it ends with the next command. |
+| `mason init [<postgres url>]` | Makes this folder a project: checks it can read the database (nothing is written when it cannot; `--skip-check` writes anyway), writes `.mason/config.json` (Mason's key, never the URL) and `mason/sources/<database>.yml` (keeping a sources file already there), adds the URL to `.env` when it was not there, and adds `.mason/` and that `.env` to `.gitignore`. The URL from the argument, else `MASON_DATABASE_URL`, else `DATABASE_URL`, each in `.env.local`, `.env` or the shell (the sources file names the one read). `--name` sets the project's name (default: the folder's), which its replication slot is named for; `--database` the database name a tool connects with (default `mason`, none written); `--folder` where its files go, `--remote` allows a database on another machine. Refuses a folder already in a project, but for one with no sources file (an older Mason's), whose sources file alone it writes. |
+| `mason start` | Starts Mason for this folder's project in the background and returns once it is up. Run it again any time: it says so when Mason is already running. Each table is kept current as its `sync:` in the sources file says (`off`, `poll <interval>` or `replication`). `--self-signed-tls` serves the Postgres API over TLS; `--attach` stays in the foreground. |
 | `mason tables [<table>…] [--all]` | The tables this user can read against the sources file, one line each: rows, primary key, whether added (and with which columns), and why a table cannot be added yet (no primary key: the `--key` to add it by). Name a table (or pass `--all` for every one) for its columns: each one's type, what it references, and whether `mason add` would leave it out as a secret. It reads the project's database itself, so Mason need not be running. |
-| `mason add <table>… [--columns …] [--include …] [--key …]` | Copies tables into Mason, each one an entry of the sources file: every column (`orders: {}`), or `--columns id,status,created_at` for those (one table at a time; the key is written with them). Columns that look like secrets (`password`, `token`, `api_key`, `private_key`, …) are left out, named, and written as `exclude:`; `--include password_hash` adds one. `--key tenant_id,id` adds a table with no primary key, copied by those columns. Adding a table again with other columns changes its entry. Mason need not be running: the entry is checked against the database as the run checks it, and the copy begins at `mason start` (with Mason running, at once). |
-| `mason remove <table>…` | Takes tables out of the sources file — each one's entry, every other byte as it was — and Mason drops their copies: at once when it is running, else at the next `mason start`. Mason need not be running. |
-| `mason wait [--timeout <s>]` | Waits until every added table is copied and served, showing every added table on a line of its own: 100% for the finished ones, in the order they finished, and a bar for each still copying (rows, %, rate, time left) at the bottom. Exit 0 ready, 1 a copy failed (printed, with what to do), 124 timed out (default 600 s). |
+| `mason add <table>… [--columns …] [--include …] [--key …] [--sync …]` | Syncs tables into Mason, each one an entry of the sources file: every column (`orders: {}`), or `--columns id,status,created_at` for those (one table at a time; the key is written with them). Columns that look like secrets (`password`, `token`, `api_key`, `private_key`, …) are left out, named, and written as `exclude:`; `--include password_hash` adds one. `--key tenant_id,id` adds a table with no primary key, keyed by those columns. `--sync "poll 30s"` (or `off`) writes how it is kept current after its first sync on its entry; on a table already added, `--sync` alone changes that line and nothing else. Without it the entry follows the file's `sync:`, but a table over 1,000,000 rows under a file that polls is written `sync: off` and said, and a frequent poll of tens of millions of rows is warned of with an estimate of its cost. Adding a table again with other columns changes its entry. Mason need not be running: the entry is checked against the database as the run checks it, and the first sync begins at `mason start` (with Mason running, at once). |
+| `mason remove <table>…` | Takes tables out of the sources file — each one's entry, every other byte as it was — and Mason drops their synced data: at once when it is running, else at the next `mason start`. Mason need not be running. |
+| `mason wait [--timeout <s>]` | Waits until every added table is synced and served, showing every added table on a line of its own: 100% for the finished ones, in the order they finished, and a bar for each still syncing (rows, %, rate, time left) at the bottom. Exit 0 ready, 1 a first sync failed (printed, with what to do), 124 timed out (default 600 s). |
 | `mason user add\|list\|remove <name>` | The users of the Postgres API: a name and a password that does not expire, as a BI tool's datasource form asks for them or an app's `DATABASE_URL` carries them. `add` prints the password once with the URL; `remove` refuses the next connection at once and ends the sessions it holds at their next statement, without a restart. |
-| `mason mcp [--url <url>]` | An MCP server on stdio for Claude Code, Claude Desktop and other agents (below): the tables Mason serves with each copy's rows and how current it is, a table's columns, a statement's rows with their Postgres types or Mason's refusal with its way out, and EXPLAIN — connected as a `mason user` (`MASON_URL`, else `--url`), beside `mason start` or a `mason serve` elsewhere. |
-| `mason ui` | Opens the running Mason's web page in your browser: what `mason status` says, refreshed every 2 s, and the users of `mason user` (add one, its password shown once; remove one). It prints the URL with the run's token, which the page trades for a cookie on the first visit; `--no-open` prints it only, `--json` is `{ url, port }`. `mason start`'s alone: `mason serve` serves no page. |
-| `mason status` | What Mason is doing: the database and how its changes are read, the project folder, the copy's file, the Postgres API and how it listens, each table's copy, the statements answered slowly in the last day and the ones refused or failed, each with its reason. In replication mode, where the stream is. |
-| `mason sync <table>…` | Makes the copy of these tables current now: a table over the sync's row limit (1,000,000 rows) is copied and served but kept current only so, or by replication. |
-| `mason logs [-n <lines>] [-f] [--start] [--requests [--failed]]` | Mason's log: every copy, poll and statement, with warnings and errors and their reasons; `-f` follows it, `--start` shows what `mason start` printed instead. `--requests` is the request log: every statement a tool sent, when, the outcome and SQLSTATE, how long, the rows, the tool and the user; `--failed` only the refused and failed ones. |
-| `mason stop` | Stops Mason for this project. The copy and the state stay: the next `mason start` resumes in seconds. |
-| `mason destroy` | Removes this project's copy of the data (its file) and Mason's state in `.mason/`, stopping Mason first if it runs — and, for a project started with `--replication`, its slot and publication on the database. Your files, `.mason/config.json` and the users stay: the next `mason start` copies the tables again. |
-| `mason serve` | Mason for a server or a container: `mason start --attach` configured by the environment alone, its state in one folder (a volume), its log on stdout, `GET /healthz`, a clean stop on SIGTERM. `mason serve --help` lists every setting with its default. |
+| `mason mcp [--url <url>]` | An MCP server on stdio for Claude Code, Claude Desktop and other agents (below): the tables Mason serves with each one's rows and how current it is, a table's columns, a statement's rows with their Postgres types or Mason's refusal with its way out, and EXPLAIN — connected as a `mason user` (`MASON_URL`, else `--url`), beside `mason start` or a `mason serve` elsewhere. |
+| `mason ui` | Opens the running Mason's web page in your browser: the Overview (what `mason status` says), the Tables (add, remove or sync one), the Users of `mason user` (add one, its password shown once; disable, enable or remove one) and Observability (the statements, usage over time, the sync's events), refreshed while the tab is open. It prints the URL with the run's token, which the page trades for a cookie on the first visit; `--no-open` prints it only, `--json` is `{ url, port }`. `mason start`'s alone: `mason serve` serves no page. |
+| `mason status` | What Mason is doing: the database and how its changes are read, the project folder, the synced data's file, the Postgres API and how it listens, each synced table, the statements of the last day and week (each outcome, the completed ones' average, p50 and p95 time, the rows and bytes sent), the ones answered slowly in the last day and the ones refused or failed, each with its reason. In replication mode, where the stream is. |
+| `mason sync <table>…` | Brings these synced tables up to date now, by one poll each: a table whose `sync:` is `off` is kept current only so (from cron, before a report), a polled one is polled now as well as at its interval. In replication mode the stream keeps every table current, and it says where the stream is. |
+| `mason logs [-n <lines>] [-f] [--start] [--requests [<filters>]] [--events [--failed]] [--running]` | Mason's log: every sync, poll and statement, with warnings and errors and their reasons; `-f` follows it, `--start` shows what `mason start` printed instead. `--requests` is the request log: every statement a tool sent, when, the outcome (ok, refused, failed, cancelled) and SQLSTATE, how long, the rows and bytes sent, the tool and the user; `--failed` only the ones not answered, `--outcome`, `--since` / `--until` (`2h`, `7d`, an ISO time), `--user` and `--client` narrow it, and `--before` reads the page before. `--events` is the sync's events: each first sync, poll, catch-up or stream that failed, the database out of reach, a table current again, each sync asked by hand (mason sync, the page's Sync now), and each restart of the run (`--failed` only the failures). `--running` lists the statements running now, by session. |
+| `mason cancel <session>` | Stops the statement a session of the Postgres API is running, as the client's own cancel would: the client is told 57014, its session goes on, and the request log keeps it as cancelled. `mason logs --running` lists the sessions. |
+| `mason usage [--since 7d] [--step 1h]` | What Mason did over time, from a sample a minute kept `MASON_HISTORY_DAYS` days: the statements and their p95, the rows and bytes sent, the synced data's size and rows, the stalest table, the stream's lag, the memory; then each synced table's own size. |
+| `mason stop` | Stops Mason for this project. The synced data and the state stay: the next `mason start` resumes in seconds. |
+| `mason destroy` | Removes this project's synced data (its file) and Mason's state in `.mason/`, stopping Mason first if it runs — and, when a table was replicated, its slot (and its publication, when Mason made it) on the database. Your files, `.mason/config.json` and the users stay: the next `mason start` syncs the tables again. |
+| `mason serve` | Mason for a server or a container: `mason start --attach` configured by the environment alone, its state in one folder (a volume), its log on stdout, `GET /healthz`, `GET /metrics` (Prometheus, numbers only), a clean stop on SIGTERM. `mason serve --help` lists every setting with its default. |
 
 Every command documents itself: `mason --help` lists them, and `mason <command> --help` (or `mason help <command>`) says
 how to use one, with examples. Every command but `help` and `mcp` (whose stdout is the MCP protocol's) takes `--json`. A command means the project of the folder it
@@ -112,47 +122,56 @@ runs in, or the nearest one above it.
 
 ## What `mason start` does
 
-1. **It only reads the database** — the one the sources file names. Mason polls it with `SELECT` statements. It does not
-   need `wal_level = logical`, a replication slot, a publication or the `REPLICATION` attribute, and it creates none of
-   them. When you stop it, nothing is left behind on the database. A table over 1,000,000 rows is copied and served but
-   kept current only by `mason sync` or by replication, and `mason status` says so on its line. (`--replication` is the
-   exception, said below: it reads the change log, as production does, and makes its own slot.)
-2. **It copies each added table** into a DuckDB file in `.mason/`, a range of pages at a time, a few in parallel, one
-   Postgres backend each, smallest table first; a copy that stops continues with the ranges it did not commit. The table
-   is served the moment its copy lands; the copy runs beside the polls, never instead of them.
+1. **It only reads the database** — the one the sources file names, with `SELECT` statements. It does not need
+   `wal_level = logical`, a replication slot, a publication or the `REPLICATION` attribute, and it creates none of
+   them. When you stop it, nothing is left behind on the database. After its first sync each table is kept current as
+   the sources file's `sync:` says — at the top for every table, on an entry for that one: `off` (the default, and what
+   `mason init` writes) reads it again only at `mason sync <table>`; `poll 30s` polls it every 30 seconds, each poll a
+   scan of the table, the next one at least four times the last one's time later. Changing a table's `sync:` keeps its
+   synced data and catches it up by one poll. `mason status` says each table's sync and when it was last synced, on its line.
+   (`sync: replication` is the exception: that table is read from the change log, as production does, through one slot
+   Mason makes and a publication carrying the replicated tables alone — its own, or the one `publication:` at the top
+   of the file names, never altered. The slot is dropped, verified gone, once no table is replicated.)
+2. **It syncs each added table** into a DuckDB file in `.mason/`, a range of pages at a time, a few in parallel, one
+   Postgres backend each, smallest table first; a first sync that stops continues with the ranges it did not commit. The table
+   is served the moment its first sync lands; it runs beside the polls, never instead of them.
 3. **It serves the Postgres API** on 5433, or on the next port free on every address when something holds 5433 (often a
    second Postgres; `mason start` says what held it) — and records it: every later start listens on the same port, so a
    tool's saved connection keeps working, and refuses, naming what holds it, rather than move. `MASON_PG_PORT=55433` in
    your shell names the port, or moves the project to it (said). It listens on 127.0.0.1 unless `MASON_PG_HOST` names
    another address; off this machine it needs TLS (`--self-signed-tls`, or `MASON_PG_TLS_CERT` / `MASON_PG_TLS_KEY`).
-4. **It runs in the background**, copying what the sources file names: `mason add` and `mason remove` change it at once,
+4. **It runs in the background**, syncing what the sources file names: `mason add` and `mason remove` change it at once,
    a hand edit (or an add or remove made while Mason was stopped) at the next `mason start`.
 
-Mason's own settings (`MASON_POLL_MS`, `MASON_DUCKDB_MEMORY`, `MASON_COPY_PARALLEL`, …) set in your shell reach Mason.
-A copy reads `MASON_COPY_PARALLEL` chunks at once (default 3), each sized to take about `MASON_COPY_CHUNK_SECONDS` to
+Mason's own settings (`MASON_DUCKDB_MEMORY`, `MASON_COPY_PARALLEL`, …) set in your shell reach Mason. How often a
+table is polled is its `sync:`, never a setting: `MASON_POLL_MS` set refuses the start, naming the line to write.
+A first sync reads `MASON_COPY_PARALLEL` chunks at once (default 3), each sized to take about `MASON_COPY_CHUNK_SECONDS` to
 read (default 12) at the rate it measures on your connection, so `mason wait` moves every few seconds even over a slow
-link, and a copy that stops reads at most those chunks again.
-A JSON value your queries keep reading (`payload ->> 'customer_id'`) is stored as a column of the copy and read from
+link, and a first sync that stops reads at most those chunks again.
+A JSON value your queries keep reading (`payload ->> 'customer_id'`) is stored as a column of the synced table and read from
 there (`mason status` lists them); `MASON_STORE_JSON_PATHS=off` turns that off.
 
 ## `mason start` options
 
 | Option | What it does |
 |---|---|
-| `--replication` | Read the database's changes from its change log (logical replication), as production does, instead of polling. It needs `wal_level = logical` and a user that may replicate, and makes its own publication and slot (`mason_dev_<project>_<source>`, the source the sources file's name; past 63 bytes, a prefix and a hash) on the database. The project keeps the mode until `--poll`; a switch keeps the copies and catches each table up by one poll. `mason stop` leaves the slot (it holds WAL until the next start); `mason destroy` and `--poll` drop it. |
-| `--publication <name>` | With `--replication`: a publication the database owner made (else `PG_PUBLICATION`), read as it is, verified to carry every added table and column, never created, altered or dropped. A read replica needs one. |
-| `--poll` | Read them with `SELECT` again (the default). |
 | `--self-signed-tls` | The Postgres API requires TLS, from a certificate made for this project in `.mason/` (served again by every later start with the flag); clients connect with `sslmode=require`. |
 | `--port <n>` | The port the `mason` commands reach it on (default 4039, or the next free one). |
 | `--attach` | Stay in the foreground: the terminal shows Mason's progress, and Ctrl-C stops it. |
 
-A database on another machine needs `mason init --remote`, which records that you mean it: the copy leaves the
-database's network, and each added table under the row limit is read whole every few seconds (`--replication` reads only
-its changes). Point it at a read replica, never the primary your app writes to.
+`--replication`, `--poll` and `--publication` are gone: each answers with the line to write at the top of the sources
+file (`sync: replication`, `sync: poll 5m`, `publication: <name>`) and exit 2, and starts nothing. A project that
+streams, with no `sync:` anywhere in its file, is refused with its slot kept: `sync: replication` keeps streaming,
+`sync: off` or `sync: poll <interval>` confirms the drop. One with a recorded publication needs `publication: <name>`,
+or `publication: null` for Mason's own.
 
-**When the database moves.** Mason records the Postgres server it copied from. The same database on a new server (a
-restore, a move to another host) is read again at the next `mason start`: every row is compared with the copy, and only
-what changed is written. A different database is refused: `mason destroy`, then `mason start`, copies it.
+A database on another machine needs `mason init --remote`, which records that you mean it: the synced data leaves the
+database's network, and each polled table is read whole at its `sync:` interval (`sync: replication` reads only its
+changes). Point it at a read replica, never the primary your app writes to.
+
+**When the database moves.** Mason records the Postgres server it synced from. The same database on a new server (a
+restore, a move to another host) is read again at the next `mason start`: every row is compared with the synced data, and only
+what changed is written. A different database is refused: `mason destroy`, then `mason start`, syncs it.
 
 ## For coding agents
 
@@ -188,10 +207,10 @@ and says `mason user add claude`.
 
 | Tool | Arguments | What it answers |
 |---|---|---|
-| `tables` | none | each table Mason serves, named as a statement writes it (`public.orders`, `public."Clients"`): `rows_about` (the copy's estimate), `kept` (how it is kept current, as `mason status` says it) and `kept_current_by` (`polling`, `logical replication`, `copying again`, or null when nothing keeps it current now) |
+| `tables` | none | each table Mason serves, named as a statement writes it (`public.orders`, `public."Clients"`): `rows_about` (the synced table's estimated row count), `kept` (how it is kept current, as `mason status` says it) and `kept_current_by` (`polling`, `logical replication`, `copying again`, or null when nothing keeps it current now) |
 | `describe` | `table` (as `tables` names it, or a bare name in `public`) | its columns with their Postgres types and NOT NULL, its primary key, its foreign keys, comments, and the same rows and `kept` |
 | `query` | `sql`, `max_rows` (200, at most 10,000), `timeout_ms` (30,000, at most 300,000) | `columns` (name, Postgres type), `rows` as Postgres's text, `truncated` when `max_rows` cut it; a refusal is a tool error with the SQLSTATE, message, DETAIL and HINT (the way out) |
-| `explain` | `sql`, `analyze`, `timeout_ms` | Mason's EXPLAIN: each copy read with its rows and how current it is, the SQL it runs, the plan |
+| `explain` | `sql`, `analyze`, `timeout_ms` | Mason's EXPLAIN: each synced table read with its rows and how current it is, the SQL it runs, the plan |
 
 Its resources are `mason://help/agent` and `mason://help/mcp` (the two pages `mason help` prints). Every statement it
 runs is in the request log under `application_name` `mason-mcp/<the client's name>` (`mason logs --requests`), a query
@@ -203,9 +222,9 @@ comes before `--env`, which takes every value after it):
 
 ```sh
 mason user add claude                    # the URL, printed once
-claude mcp add mason --env MASON_URL="postgres://claude:<password>@127.0.0.1:5433/shop" -- mason mcp
+claude mcp add mason --env MASON_URL="postgres://claude:<password>@127.0.0.1:5433/mason" -- mason mcp
 # or on its command line, where ps shows it to this machine's users and claude mcp add prints it
-claude mcp add mason -- mason mcp --url "postgres://claude:<password>@127.0.0.1:5433/shop"
+claude mcp add mason -- mason mcp --url "postgres://claude:<password>@127.0.0.1:5433/mason"
 ```
 
 Claude Desktop, in `claude_desktop_config.json`. The app often starts a server without your shell's `PATH`, where
@@ -218,7 +237,7 @@ neither `mason` nor the `node` its first line asks for is found: name both by th
     "mason": {
       "command": "/absolute/path/to/node",
       "args": ["/absolute/path/to/mason", "mcp"],
-      "env": { "MASON_URL": "postgres://claude:<password>@127.0.0.1:5433/shop" }
+      "env": { "MASON_URL": "postgres://claude:<password>@127.0.0.1:5433/mason" }
     }
   }
 }
@@ -226,17 +245,17 @@ neither `mason` nor the `node` its first line asks for is found: name both by th
 
 ## Cleaning up
 
-Three things exist once a project has run: your **files** (the sources file, in your app), the **copy of your data** (a
+Three things exist once a project has run: your **files** (the sources file, in your app), the **synced data** (a
 file in `.mason/`) and **Mason's state** (`.mason/`: its settings, logs and the request log). Each way of cleaning up
 keeps a different set:
 
 | You want | Run | Keeps |
 |---|---|---|
 | Pause | `mason stop` | the data, the state, your files: the next `mason start` resumes in seconds |
-| Copy the data again, or free its disk | `mason destroy` | your files, `.mason/config.json` and the users: the next `mason start` copies everything again |
+| Sync the data again, or free its disk | `mason destroy` | your files, `.mason/config.json` and the users: the next `mason start` syncs everything again |
 
 Restarting the machine is a `mason stop` that nobody ran: the next `mason start` resumes. In a demo project
-(`mason init demo`) the demo database is state too: `mason destroy` removes it with the copy, and the next `mason start`
+(`mason init demo`) the demo database is state too: `mason destroy` removes it with the synced data, and the next `mason start`
 seeds it again.
 
 ## Requirements
@@ -245,7 +264,7 @@ seeds it again.
 
 - Node 22.13 or later. The SQL parser (`libpg-query`), the catalog (`PGlite`) and the engine (DuckDB) ship as
   WebAssembly or prebuilt binaries: no native build, no Python or compiler needed.
-- Memory: the copy may use half the container's memory limit by default, else half the machine's RAM
+- Memory: the engine may use half the container's memory limit by default, else half the machine's RAM
   (`MASON_DUCKDB_MEMORY=4GB` sets it; `mason doctor` says it). Sizing a server:
   [deploy/mason-data/README.md#memory](https://github.com/embeddable-hq/mason-data/blob/main/deploy/mason-data/README.md#memory).
 - Postgres 13 or later. Each table needs a primary key, or a `key:` in the sources file (polling only).
@@ -256,14 +275,14 @@ seeds it again.
 project's `.mason/config.json`, which a browser cannot send — or, for its web page (`mason ui`), the cookie the run's token is traded for on the first visit (HttpOnly, SameSite=Strict, its Host and every change's Origin checked). The Postgres API takes a user's password (`mason user`): a
 MAC over its name keyed by the project's API key, so rotating the key removes every user at once. Off loopback the Postgres API is TLS or refused.
 
-What a project keeps on this machine (the database URL, the API key, the run's token, the copy, its log and request
+What a project keeps on this machine (the database URL, the API key, the run's token, the synced data, its log and request
 log) is in its `.mason/`, readable by your user only and gitignored by `mason init`.
 
 ## In production
 
 Only the project folder travels — `mason/`, with `mason.yml` naming the Mason version it is written for. Production runs
 it as one container, `ghcr.io/embeddable-hq/mason-data`, with `mason serve`: the same run, configured by the environment,
-its copy on one volume, reading Postgres's change log (`MASON_CHANGES=replication`) or polling it. `mason help
+its synced data on one volume, each table read from Postgres's change log or polled as its `sync:` says. `mason help
 production` is the road, offline; `deploy/mason-data/` in the repo is the Compose file and its walkthrough.
 
 Apache-2.0.

package/dist/src/api/error.js

@@ -16,3 +16,6 @@ export class ApiError extends Error {
         this.code = code;
     }
 }
+/** The code of a DISABLED `mason user`'s refused login or session (src/duck/users.ts): the listener answers it 28000, as
+ *  Postgres answers a role without LOGIN, never 28P01 — its password was right. */
+export const USER_DISABLED = "user_disabled";