PAX
← all writing

Station Log — November 8, 2026

Station Log — November 8, 2026

The home site stops declaring VIPs; fort aliases 192.168.0.200 (cutover step 3) (pax-station)

Worked across 5 repo(s) today.

  • burrito-app-server: 1 change(s)
  • heliopause-client: 10 change(s)
  • heliopause-portal: 5 change(s)
  • heliopause-server: 4 change(s)
  • pax-station: 2 feature(s)

2 feature(s) landed.

  • the home site stops declaring VIPs; fort aliases 192.168.0.200 (cutover step 3) (pax-station)
  • sites can declare vipAliases; Caddy's VIP block answers for them (pax-station)

20 other change(s) of note.

  • host/, vps/: the audit citations in the installed files' comments name heliopause-server (was pax-heliopause) (burrito-app-server)
  • the docs stop saying old launchers cross by the pinned bridge (the pilot, 2026-11-08: "are all the docs up to date?"). Since step 3 that is known to be wrong: a launcher before the bridge takes the newest row of the whole list and only then checks its name, so it never reaches the bridge once a newer row carries the new name; it crosses by the portal's old-name row (heliopause-portal withOldNameRows) and installs the renamed release directly. docs/LAUNCHER.md's bridge section says so (and that the rename happened, in v0.391.0); docs/WINDOWS.md says why Windows testers reinstall by hand (the old-name row is Linux-only; such a launcher refuses the new name and unpacks only a pax-helios\ folder); src/updater/signing.odin's RELEASE_PREFIXES comment no longer credits prune-releases.sh; docs/PRODUCT-RENAME.md's step 1 and step 2 plan text gets a note where the plan was wrong, and "The old-name row" says v0.391.0's real copy was there at first and later removed. Comments and docs only, no release (heliopause-client)
  • the product rename's last check is done, on v0.391.0 itself (the pilot, 2026-11-08: "fix it, get the portal and everything to do with heliopause in sync"). The pilot removed v0.391.0's hand-made old-name copy from burrito and fries' staging copy, so the portal's withOldNameRows makes that row, and deployed the portal (v20261108.0.3) and the server (v20261108.0.2, which reports heliopause-server at last). Checked live: /api/releases starts with pax-helios-v0.391.0, then heliopause-client-v0.391.0, same size and SHA-256, the old-name row carrying the new file's time (the generated one); a v0.389.0 install in a throwaway HOME on a private Xvfb took it and upgraded in place in about 57 s, its binaries byte-identical to the release, the old names as links; PLAY started heliopause-client (by /proc//exe; the process is named pax-helios after the link), which reached the v0.391.0 login page and logged to the new folder; the download page reads ./helios/heliopause-client. docs/PRODUCT-RENAME.md records it ("The old-name row", the Record, "Still open"), and CLAUDE.md drops v0.391.5's owed-check paragraph: nothing is owed at the next release. Docs only, no release (heliopause-client)
  • CLAUDE.md carries the one check the product rename still owes (docs/PRODUCT-RENAME.md "Still open"; the pilot, 2026-11-08, closing the rename sessions). The release bullet said "nothing to do at release time", which holds for every release but the first after v0.391.0: that is the first whose old-name row the portal makes live (withOldNameRows; v0.391.0's was a real copy). The bullet now says what to check then (the live list's first two rows, same size and SHA-256; a v0.389.0 install updating itself and PLAY starting heliopause-client), how to stop the test launcher (by /proc//exe, not pidof), and to strike the paragraph and record the check afterwards. Docs only, no release (heliopause-client)
  • the Blender kit's Copy: live goes to burrito and asks for the admin token (heliopause-server v20261107.0.3's hand-off; the pilot, 2026-11-08: finish the rename here). Its live command still sourced ~/.config/pax-heliopause/env, shredded 2026-11-07 (its tokens were pre-rotation), and targeted 127.0.0.1:8137, where nothing has listened on fries since the move (2026-11-04), so it had not worked since then. Now it is the form heliopause-server docs/WALKTHROUGHS.md gives: hudtest.env, then read -rsp 'ADMIN_TOKEN: ' ADMIN_TOKEN; echo (the token pasted from KeePass, no copy on fries), and -server burrito.rya-rattlesnake.ts.net:8137 -token "$ADMIN_TOKEN" over the tailnet (placekit speaks plain ws://). Copy: scratch is unchanged. Checked: heliopause_kit_test.py (537 checks OK under blender --background), its live check now asserting the burrito address, the prompt, the token flag and no pax-heliopause path; the copied command parses under bash -n. Not run against the live server. Tooling only, no release (heliopause-client)

Auto-generated Station Log. 1 agent session(s) · 25 commit(s) across 5 repo(s) · Models: deepseek-v4-pro:cloud · Releases: v20261108.0.4, v20261108.0.3, v20261108.0.2 · Built by Claude · Orchestrated by Hermes