From 784f6eb6dc35afb2c2858341397e4296fd87918c Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Sat, 5 Sep 2026 06:51:18 -0700 Subject: [PATCH] =?UTF-8?q?memory:=20Ledger=E2=86=92SVOS=20vault=20move=20?= =?UTF-8?q?done=20=E2=80=94=20svos/env.sh=20in,=20stale=20ledger/env.sh=20?= =?UTF-8?q?to=20trash?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `secret` CLI has no rename, so this was re-put + rm. Stored nh3-dev/development/svos/env.sh from the live file (sha 7253633d4155, verified on read-back) and retired nh3-dev/development/ledger/env.sh (sha feb418634e10, id 3a2af37c-c5aa-4f46-9178-f4fb6008a753, soft-deleted to trash and recoverable). The two shas differ: the vaulted copy was a 2026-08-11 snapshot and the live file had drifted since without ever being re-vaulted. Recorded because the lesson generalises — the vault goes stale unless `secret backfill` is re-run. Gitea corviduo/ledger deliberately NOT renamed. It is ledger-dev's repo; the answer they needed is that 1.26.1 writes a repo_redirect on a same-org repo rename, org/user renames do not redirect, the redirect dies if anything re-creates the old path, and both the repo and the org carry zero webhooks. --- persistent-memory.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/persistent-memory.md b/persistent-memory.md index 2e03b42..26baae0 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -158,10 +158,20 @@ below is a live commitment or a known-open risk._ 941 MiB/s ran at 1.4 MiB/s with the link up and pbs-ana answering in 11 ms. Nightly 21:00, `all 1`. Worth its own investigation. -- **ledger-dev asked about the Ledger→SVOS rename** (gitea repo rename cost, and - moving `nh3-dev/development/ledger/env.sh` in the vault — the `secret` CLI has no - rename, so it is re-put + delete). **Unanswered, no deadline**, nothing moves until - the operator fixes the strings. +- **Ledger→SVOS rename: vault side DONE, gitea side is ledger-dev's to execute.** + Name settled as `svos`, `~/development/ledger` → `~/development/svos`. Vault moved + 2026-09-05 (`secret` has no rename, so re-put + `rm`): stored + `nh3-dev/development/svos/env.sh` (sha 7253633d4155, verified on read-back), + retired `nh3-dev/development/ledger/env.sh` (sha feb418634e10, id + 3a2af37c-c5aa-4f46-9178-f4fb6008a753) — `secret rm` is a SOFT delete to trash, so + it is recoverable. ⚠ The two shas differ: the vaulted copy was a 2026-08-11 + snapshot and the live file had drifted un-vaulted since. **The vault goes stale + unless `secret backfill` is re-run.** Gitea `corviduo/ledger` (id 70) NOT renamed — + their repo, their call; answered that 1.26.1 writes a `repo_redirect` on a + same-org repo rename (upstream #807), that org/user renames do NOT redirect + (#9531), that the redirect dies if anything re-creates the old path, and that the + repo and org both carry 0 webhooks. Handle `ledger-dev` → `svos-dev` is an + operator action at the post office. - **Open commitment to vastblue-dev:** a dedicated CI runner, gated on their first client-premises release cut (U10, unscheduled). Ping expected when U10 is scheduled.