Extension v0.2.31

The Percolate Postgres extensions, built from
Percolation-Labs/percolate
at 7f35957fa0899115a4ebd145d202088c21a81bc6.

curl -fsSL https://raw.githubusercontent.com/Percolation-Labs/get-percolate/main/install.sh | sh

Or pull the image, which carries the same build:
percolationlabs/percolate-postgres:19-0.2.31

Upgrading an existing database: install the new files, then, as a
role that can act as app_owner,
set role app_owner; alter extension percolate update; -- the
percolate--<old>--0.2.31.sql scripts attached here
are what it runs.

What's Changed

• A release writes its row in one table of published pairs (REM-1085) by @percolating-sirsh in #85
• The harbour sample writes identity through rbac's functions, and docs.yml refuses an insert (REM-1082) by @percolating-sirsh in #86
• docs: the released table is a record, and a mismatch names the remedy (REM-1085) by @percolating-sirsh in #87
• tour: a fresh tag's 404 is waited out, an old tag's fails at once (REM-1155) by @percolating-sirsh in #88
• docs: a first-memory page, and three claims corrected for 0.2.30 (REM-1170, REM-1171) by @percolating-sirsh in #89
• compose: content has a healthcheck, and the quickstart waits for it (REM-1171) by @percolating-sirsh in #90
• coldstart: the refusals ingest.md and install.md describe are checked (REM-1170) by @percolating-sirsh in #91
• bootstrap: the Content Server's role, as the image creates it (REM-1118) by @percolating-sirsh in #92
• parser: a release carries only the upgrade paths into its own version by @percolating-sirsh in #93

Full Changelog: v0.2.30...v0.2.31