v2026.10.6

The operator's traffic report, assets counted as static, party pages that list AB sub-dockets as themselves, and the proxy, replication and metrics images pinned by digest.

• Party pages (/p/<id>, /parties): an AB sub-docket is listed as its own proceeding, not folded into the carrier's series, the same rule alerts already follow. On a production copy Norfolk Southern's list goes from 223 to 406 rows, and the uncaptioned rows from 24 to 6. FD and other families still fold.
• Traffic: docketyard traffic --html PATH [--days N] writes the operator's report as one self-contained file. It is served nowhere and refused under public/. The middleware now reads the path before routing, so /static assets and /data/files downloads count as static instead of other (docs/traffic.md).
• Deploy: compose.yaml pins caddy, litestream and alloy by digest, keeping their tags for the reader. The bootstrap creates data/blobs, data/flags and data/metrics and copies every deploy file. The backup bucket is configuration.
• Fleet tools: pull_blobs.py, ocr_run.py and the backup unit. Nothing on the instance runs them.

Deploying: copy the new infra/deploy/compose.yaml to /srv/docketyard along with the DY_TAG change. No migration (schema 34).

🤖 Generated with Claude Code