R-106/R-109 audit + registers: shipped at agent 0.118.1, plus R-125

Adds the full audit: Part 0's three answers, the pre/post recipe for both boxes,
the on-disk proof that `local` froze at the 2026-07-28 target move while
felhom-backup kept running, all seven red-proofs, and the three publish
observables.

R-125 filed: v0.118.0's R-106 half shipped INERT. Two tests ran the real
Collector.Collect() but both injected a fakeObserver, and the break was one layer
below in mergeConfig, which dropped the pbs namespace. The recipe still said
"root" — now with namespace_state "resolved" beside it, confident and wrong.
Caught by live validation, not by the green suite. Fixed in 0.118.1; filed for
the doctrine point that a production-path claim must name the seam it injects at.

REPORT-r106-r109-recipe-completeness.md

@@ -2,7 +2,12 @@
 
 Non-overwritten sibling per `CLAUDE.md:82-87` — the shared `REPORT.md` holds R-117 and is not touched.
 
-Shipped: **agent v0.118.0** (`felhom-agent` `1c8a67e`) + **hub v0.83.0**. Neither half is useful alone.
+Shipped: **agent v0.118.0 → v0.118.1** (`felhom-agent` `1c8a67e`, `6b5dade`) + **hub v0.83.0**
+(`felhom.eu` `acfc2b7`). Neither half is useful alone.
+
+**Read §3 first if you read nothing else:** v0.118.0's R-106 half shipped INERT and live validation is
+what caught it — the recipe still said `"root"`, now with `namespace_state: resolved` beside it. Full
+account in the audit §6, filed as **R-125**.
 
 ## Part 0 — the answers, before the fix
 
@@ -96,9 +101,23 @@ symptom the task is named for (the recipe is incomplete), and the worst instance
 (c) it is in the *same two structs* R-109 forced me to edit, and leaving one of three known keys off a
 drop-list I was already correcting would be indefensible. It is filed as R-122 with a SHIPPED disposition.
 
-## 3. The before/after recipe — same box, quoted
+## 3. The before/after recipe — both boxes, quoted
 
-Full text in `documentation/audits/R106-R109-recipe-completeness-2026-07-30.md` §5.
+```
+demo-felhom  BEFORE  "namespace":"root"           backup_target absent   offsite_restic absent
+             AFTER   "namespace":"demo-felhom"    backup_target {resolved, felhom-backup, /mnt/hdd_1}
+                                                  offsite_restic {u629488-sub1…}
+demo-hp      BEFORE  "namespace":"root"           backup_target absent   offsite_restic absent
+             AFTER   "namespace":"demo-hp"        backup_target {resolved, felhom-backup, /mnt/nvme-1tb}
+                                                  offsite_restic {u629488-sub3…}
+```
+
+The two boxes DISAGREEING is the point — nothing is hardcoded. And the ambiguity was not theoretical:
+on both boxes `felhom-backup` holds an archive from **07-30 04:36** while `local` stops at
+**07-28 17:5x**, frozen at the target-move date. The recipe now names the live one.
+
+Full evidence, all seven red-proofs and the publish observables:
+`documentation/audits/R106-R109-recipe-completeness-2026-07-30.md`.
 
 ## 4. Findings filed (none of them fixed except R-122, see §2)
 
@@ -106,10 +125,12 @@ Full text in `documentation/audits/R106-R109-recipe-completeness-2026-07-30.md`
 |---|---|
 | **R-122** | `AssembleDRRecipe` allow-list dropped `offsite_restic` for the feature's whole life — **FIXED here**, hub v0.83.0 |
 | **R-123** | R-105 and R-106 were `READY` in `ROADMAP.md` with no `OPEN-ITEMS.md` row — referenced only inside R-109's prose. Registered here |
+| **R-125** | v0.118.0 shipped an inert R-106 because the "production path" test injected `fakeObserver` one layer below the break — **FIXED** in v0.118.1; filed for the doctrine point (name the seam you inject at) |
 | **R-124** | The recipe spells PBS's root namespace `"root"`, but the PBS API spells it `""` and there is no namespace literally named `root` — a restorer pasting it into `pct restore --ns root` would fail. Pre-existing wire convention, deliberately unchanged; documented at `PBSRootNamespace` |
 
 ## 5. Not done, and why
 
 - **R-105, R-108, D5** — out of scope by the task's §6. R-108 blocks D5; starting either would leave both half-done.
 - **The backup machinery** — untouched. This corrects the record, not the doing.
-- **demo-felhom's agent was not upgraded past what the deploy step covers** — see the audit §6.
+- **`sess-f` (0.116.0) and `drill-r50` (0.113.0) were not upgraded** — neither was named as a venue, and `drill-r50` is fenced by the task's §6.
+- **R-124 not fixed** — changing the wire's spelling of the root namespace mid-R-106 would shift the field's meaning during the fix meant to make it trustworthy.