v0.3.2

v0.3.2

A documentation release. The server behaves exactly as v0.3.1 does — nothing
under src/ has changed between the two, so this is that binary plus a version
string and one comment in the shipped simmer.yaml. If you are on v0.3.1 there is
no functional reason to move; if you are on v0.3.0 or earlier, upgrade for v0.3.1's
fixes, which this release documents properly.

What the documentation now says that it did not:

• The capture's flush policy. A record reaches the file within ten buffered
  lines or 500 ms of quiet, so tail -f on the current bucket keeps up and a
  replay of a range that has just ended finds its last records. These are flushes,
  not fsyncs — on_error: defer remains the only mode that is durable before the
  client is answered. README, DOCKERHUB and the shipped simmer.yaml all say so.

• What to alert on, and what not to. simmer_capture_disk_bytes is the right
  gauge from v0.3.1: incremented as the writer flushes, recounted from the
  directory by each retention sweep. On v0.3.0 and earlier it only moved on the
  hourly sweep, so it read 0 for the whole first hour — measured over a 1-hour
  soak, 0 for 59.9 of the 60 minutes while 904 MB accumulated. Anyone reading these
  docs against an older image is now told to use simmer_capture_bytes_total
  instead, or upgrade, rather than trusting a number that was not moving.

• docs/STATE.md, re-snapshotted. It was taken at the end of phase 11 and
  predated the link proxy, the SQL Server build, the capture, server replay, the
  generalised soak tier and both releases. It now carries both feature sets'
  verification numbers, the current module layout, the known defects — F17 and the
  mssql migration race as fixed, the one-hour memory gate's resolution limit as
  open — and which index serves which query on both backends, verified against the
  planner rather than read off the DDL.

• The test tiers. The capture is not the soak's: SIMMER_CAPTURE=on runs any
  tier with it on, except the acceptance tier, which reads its config from the
  image and so has no generated twin — and now says so instead of running
  uncaptured.

Images, built from b4a6a447190ced9528258e610a30ece710b61bf8:

• Postgres: hikarisystems/simmer:v0.3.2 (linux/amd64, linux/arm64)
• SQL Server: hikarisystems/simmer:v0.3.2-mssql (linux/amd64)

Full Changelog: v0.3.1...v0.3.2