memory: snapshot — althing 3.2.0 deployed; uv tool install is a silent no-op

forseti requested the deploy, operator-approved and tagged at c4ede0f.
All three steps landed on nh3-dev and verified: force reinstall to 3.2.0
with seven binaries, herald restart, skill sync.

The durable lesson is the trap in step 1. `uv tool install .` matches on
the source spec rather than its contents, so on a box that already had
the tool installed from that path it prints "already installed" and exits
0 having done nothing. Following the runbook literally would have left
the new binary absent with every command reporting success. Always use
--force when reinstalling from a local path.

Also recorded: the pane-route migration revoked exactly four routes,
verified by splitting on channel= before the restart rather than by
auditing fields (all twelve route files lack the new fields, so a field
audit over-counts). The four affected agents were deliberately not
notified, per the standing rule against unsolicited fleet broadcast, and
that is surfaced to the operator instead.

And this closes an open question from earlier today: the waiter that died
with status "killed" was CC 2.1.257 reaping detached tasks, which is the
premise 3.2.0 exists to address.
This commit is contained in:
vh
2026-09-01 22:15:51 -07:00
parent 46a3c63706
commit 71d97f36b6
2 changed files with 95 additions and 0 deletions
+11
View File
@@ -135,6 +135,17 @@ _As of 2026-09-01 — **the GX10 is on the operator's desk, NOT racked. Standing
instead**, which is the power answer rather than a power triage. Do not relaunch on ana-ml2
without deciding that first. Exactly TWO 3c launches, only one died.
→ `persistent-memory.d/2026-08-27-run3c-launch-count-reconstruction.md`
- **🟢 ALTHING 3.2.0 DEPLOYED on nh3-dev (2026-09-01 22:13).** forseti authored, infra-ops
deployed: `uv tool install --force .` (3.1.2 -> 3.2.0, **7** binaries — `althing-route` is
the new one the SessionStart hook calls by name), herald restart, skill sync. Pane-poking
replaces detached waiters because **CC 2.1.257 reaps detached tasks when the seat sits in
`shell`** — corroborated by our own waiter dying with status `killed` 30 min earlier.
⚠ **`uv tool install .` is a SILENT NO-OP on reinstall** — uv matches the source *spec*, not
its contents; exits 0 having done nothing. **Always `--force` from a local path.**
⚠ 4 pane routes revoked by the new guards (bil-/dvalin-/eitri-/regin-smithy-dev); they
re-declare with `althing-route declare --pid <pid>`. **Deliberately not notified** (no
unsolicited fleet broadcast) — operator's call.
→ `persistent-memory.d/2026-09-01-althing-320-deploy.md`
- **✅ A6000 window CLOSED 2026-09-01 — operator freed ComfyUI's VRAM instead of anyone
stopping it.** ⚠ It was a **model unload, not a stop**: `comfyui` still up 8 days, same pid,
HTTP 200, 18,500 -> 612 MiB. ⚠ **The resulting ~43.8 GB free is a snapshot, not a floor** —