memory: uv tool --force does not rebuild without --reinstall; althing 3.5.0 out

persistent-memory.md

@@ -345,6 +345,24 @@ below is a live commitment or a known-open risk._
   exist first. Any real adoption push starts with ssh_config coverage, not with the
   allowlist.
 
+- ⚠ **`uv tool install --force .` DOES NOT REBUILD when the version has not moved**
+  (forseti, measured 2026-09-05). `--force` only handles "a tool by this name
+  exists"; `--reinstall` is what rebuilds instead of reusing the cached build keyed
+  on the version string. It prints `Installed 9 executables` over **stale code**
+  with nothing raising its hand — it cost forseti a bug that survived a reinstall
+  AND a re-smoke, because the binary verified against had not changed. **Always
+  `uv tool install --force --reinstall .`**, both flags, every time. Same shape as
+  the `.mcp.json` → built `dist/` trap found today: a deploy surface that reports
+  success while serving the previous artifact. When a fix "does not take", suspect
+  the artifact before the code.
+
+- **althing 3.5.0 released** (forseti) — adds a 9th binary,
+  `althing-operator declare <handle> --description "..."`, restoring the CLI handle
+  declaration v2 had and v3 removed. Deliberately a SEPARATE binary, not a
+  `postbox` subcommand: the invariant is that no SESSION surface exposes an
+  operator verb. Relevant to the pending `ledger-dev` → `svos-dev` rename, which is
+  still the operator's call. nh3-dev not yet upgraded.
+
 ## Recent decisions
 
 - `[2026-09-05]` **A peer's "2.7x serving-stack effect" was a coin flip — the operator rejected it on instinct and the arithmetic backed him.** Each floor was `|b0-b1|` from n=2; the ratio is half-Cauchy, P=0.452. ⚠ The disconfirming evidence sat in brokkr's own sentence, and he named *why*: the claim was his and flattering. → `persistent-memory.d/2026-09-05-floor-claim-n2-retraction.md`