PAX
← all writing

Station Log — November 7, 2026

Station Log — November 7, 2026

Private site — only enrolled devices get past a Coming soon page (pax-sidelane)

Worked across 12 repo(s) today.

  • burrito-app-server: 2 change(s)
  • heliopause-client: 3 change(s)
  • heliopause-portal: 14 change(s)
  • heliopause-server: 3 change(s)
  • pax-diver: 1 change(s)
  • pax-dragon-hunt: 1 change(s)
  • pax-hermes-vscode: 1 fix(es)
  • pax-moped-killer: 1 change(s)
  • pax-rts-001: 1 change(s)
  • pax-sidelane: 2 feature(s)
  • pax-station: 2 feature(s)
  • repo-template: 1 change(s)

4 feature(s) landed.

  • private site — only enrolled devices get past a Coming soon page (pax-sidelane)
  • Phase 11 L6 — Publisher Checkout keys, unclaimed proceeds, compliance dashboard (pax-sidelane)
  • DB_HOST goes to local HAProxy, Hermes URLs to the fort VIP (cutover step 2) (pax-station)
  • the public entry moves to site fort (cutover step 1) (pax-station)

1 bug fix(es) shipped.

  • the chat panel's default SSH target was the home VIP, which never runs Hermes (pax-hermes-vscode)

27 other change(s) of note.

  • PORTS.md, host/README.md: the audit citations name heliopause-server (was pax-heliopause) (burrito-app-server)
  • Repo rename (heliopause-portal docs/RENAME.md, this repo's note): pax-heliopause -> heliopause-server, pax-portal -> heliopause-portal (burrito-app-server)
  • docs/PRODUCT-RENAME.md — step 1 deployed (the pilot, 2026-11-07) and checked: the live portal reports v20261107.0.14, and its /api/releases (6960 bytes) and /api/news (32842 bytes) are byte-identical to the copies saved before the change; the page still reads ./helios/pax-helios and the newest installer downloads. Docs only, no release (heliopause-client)
  • docs/PRODUCT-RENAME.md — the plan for renaming the product pax-helios -> heliopause-client (the pilot, 2026-11-07: "Next I want the product name changed from pax-helios to heliopause-client. plan it out first", then "go with your recommendations, write the doc and start step 1"). Why it takes more than one release (every installed launcher sees only pax-helios-v… names through release_name_ok; PLAY, the relaunch and the in-place update find the binaries by name; Windows unpacking expects a pax-helios\ folder; players' paths name the old binaries), the new names, what stays (the signature format, LAUNCH_TOKEN, fries' ~/.config/pax-helios, the Odin package and PAX_* variables, the records), and the four steps: 1. the portal accepts both names and pins the bridge; 2. a bridge release still named pax-helios that knows both; 3. the rename release, with the old names left as symlinks, the settings copied once and a rehearsed old -> bridge -> renamed hop before publishing; 4. the docs in the other repos and fries' own install. Windows testers reinstall once by hand when Windows resumes. STATUS: step 1 committed and pushed in heliopause-portal v20261107.0.14 (e13e3c1); its deploy is the pilot's. Docs only, no release (heliopause-client)
  • the repo is heliopause-client (heliopause-portal docs/RENAME.md, this repo's note; the pilot's call, 2026-11-07). The folder and the GitHub repo had already moved, and ~/dev/pax-helios is a symlink until the cleanup step. PATHS: scripts/release.sh's PORTAL_DIR defaults to ~/dev/heliopause-portal (was ~/dev/pax-portal; checked: it resolves to the real folder, not a symlink, and holds scripts/sync-release.sh; no release cut to test it); AGENTS.md's ../heliopause-portal/scripts/sync-release.sh; the Blender scripts' fallbacks: heliopause_kit.py's ~/dev/heliopause-client (the install link, repo_dir, the panel's labels) and its placekit command's cd ~/dev/heliopause-server, and each station_*.py's MODELS. NAMES: the repo's own title (README, CLAUDE.md, PLAN.md), the CI badge, docs/MACOS.md's clone line, and every citation of the other two (pax-heliopause -> heliopause-server, pax-portal -> heliopause-portal) in the docs, scripts and code comments, src/updater/ included (comments only). KEPT: the product name pax-helios (installers pax-helios-v*, binaries, .cfg/.log, ~/.config/pax-helios, src/updater/'s names: installed launchers refuse an installer by any other name; CLAUDE.md, README and src/version.odin now say so), ~/.config/pax-heliopause/env (a runtime path), the Windows box's clone at C:\build\pax-helios (a folder on that box), docs/RELEASE-NOTES and other dated records. The six ship/cockpit .blend files still name /home/admin1/dev/pax-helios/meshy/out/retex/... as their textures' source, but every one of those images is packed into its file (checked in Blender, read-only), so nothing reads that path. No change in the game, so no release. test.sh green (445 + 20 + 17; Windows type-check OK) (heliopause-client)

Auto-generated Station Log. 2 agent session(s) · 34 commit(s) across 12 repo(s) · Models: deepseek-v4-pro:cloud · Releases: v20261107.0.9, v20261107.0.8, v20261107.0.7 · Built by Claude · Orchestrated by Hermes