v0.50.0

Minor Changes

• 19ba2dd: The trace pages are regenerated after each merge and at least hourly, into one directory a host act then serves privately over Tailscale (a11ign/a11ign#3515, the last slice of #3494). src/trace/publish.mjs reads the head of main in every code repository the project declares (one gh api repos/<repo>/branches/main call each) and regenerates only when one moved since its last stamped publication or the stamp is older than --max-age-minutes (default 60); a run that finds neither does nothing and exits 0. It writes map.html (trace -- --map over the last seven days, --calls 300), one row-<n>.html swimlane per row closed most recently in the tracker repository (--recent, default 6, plus any --row <n>) and an index.html linking them, into --out (default ~/.cache/a11ign/trace-pages). Every page is rendered into a staging directory and checked to be non-empty before it replaces the served one; a page that fails to render or to write is listed on the index and makes the run exit non-zero WITHOUT writing the stamp, so the unit shows failed and the next tick retries, never a green run over an empty directory. host/trace-publish.timer.in runs it every ten minutes (OnBootSec=2min, OnUnitActiveSec=10min) and host/trace-publish.service.in runs it as the workers account; both are installed and started by host:install, which makes one run at install (a first publication, or nothing when no head moved). Nothing here opens a port: serving is tailscale serve --bg <out>, run by the host's operator.