REUSE + STATUS: map the new scripts, correct a second stale "not wired" claim (R-229)
gates / gates (push) Successful in 8s

REUSE.md line 62 claimed hub_confirm_gate.py is "not wired to run (R-29)" -- it is gate 3 of
repo_gates.py, which both the pre-push hook and CI run. Second instance of the same stale-claim
class found today, in a third file.

Added rows for repo_gates.py (the runner), instructions_gate.py, install_workspace.py and
rules_report.py, plus the extension point: a new .claude/rules/*.md is NOT live in the session
that created it -- verify from a fresh session, never from the frontmatter.

STATUS.md: one operator-facing entry -- the assistant's notes had no backup; they do now, with
the same-disk and no-off-site caveats stated rather than implied.
This commit is contained in:
2026-08-06 11:05:33 +02:00
parent a0b50eb48f
commit 415371862d
2 changed files with 16 additions and 1 deletions
+10
View File
@@ -76,6 +76,16 @@ failed until someone walks it end to end with no help from us.
## What shipped recently
- **2026-08-06** — **The assistant's own working notes were on one machine with no copy anywhere.**
Everything the assistant has learned about this system over months — where things live, which traps
cost us an incident — sat in a folder on the build machine that no backup touched and no repository
held. It is now included in that machine's nightly backup. **Two things you should know before
treating that as solved:** the copy lands on the **same physical disk** as the original, so it
survives a mistake but not a dead drive, and the build machine's backups have **no off-site copy at
all**. Also tidied the same day: a quarter of those notes had become unreachable — filed but listed
nowhere, so nothing would ever read them — and the instructions the assistant reads at the start of
every session were cut roughly in half, with a check added so they cannot quietly grow back. Nothing
was deleted. *(R-229, R-230, R-231)*
- **2026-08-05 (late)** — **New machines now get current software again — and the disc image had been
quietly un-updatable for days.** Approving the newer in-house service turned out to be impossible on
its own: the system correctly refuses to publish a set where the pre-built machine image is older