felhom.eu/REPORT-release-rule-prowlarr-2026-10-15.md

# REPORT — the new release rule, and Prowlarr in the live catalog (2026-10-15)

Written in ASD-STE100 Simplified Technical English. Architecture read first: `09-update-architecture.md` (§3, §6.4),
`05-hub-architecture.md` (the floor, §17 tokens), `15-media-library.md` §6 (the links).

## 1. The rule, and the files I changed

The rule is `09` §3 decision 250 (operator, 2026-10-15 11:26 and 11:29):

- A controller release needs no golden.
- Push the image only when it is ready for every box.
- CC raises the floor, with the MinAgent declared, after the release ran on Tester 1, demo-hp and demo-felhom through
  the normal update path, and the box walk is green (`https_only_check.py` included). Not at night, unless the brief says so.
- Agent releases still wait for the operator's vouch.
- The golden is baked weekly. The operator vouches it.
- Decision 7 stands again. Decision 247 („bake first", the same morning) is marked REVERSED. It is not deleted.

Files changed (felhom.eu `e92501f5`, unless named):

- `documentation/architecture/09-update-architecture.md` — decision 250; 247 marked reversed; 7 restored.
- `documentation/architecture/05-hub-architecture.md` — the floor and the golden after decision 250.
- `CLAUDE.md` — the golden-weekly bullet (instruction file; before: „bake before a release").
- `.claude/rules/unprompted-work.md` §3 item 6 — the new text. The same text is in the controller (`e209a8d`), agent
  (`d2053e7`), catalog (`3ff0cf3`) and the workspace root copy (unversioned). The five copies have the same md5.
- `documentation/runbooks/RUNBOOK-manual-build.md`, `publish-train-rules.md`, `target-selection.md`, `nightly-rotation.md`.
- `skills/felhom-build-deploy/SKILL.md` — a new section „Releasing a controller (decision 250)".
- `scripts/golden_currency_gate.py`, `scripts/test_golden_currency_gate.py`, `scripts/repo_gates.py`.
- `CONTEXT.md`, `STATUS.md`, `OPEN-ITEMS.md` (R-468 updated), `CLOSED-ITEMS.md`.

## 2. Can CC raise the floor?

**No, not today. Part B stopped.**

- At the time of Part B, the only route was the operator page. It needs the operator's own password. I did not use it.
  I did no save.
- I read the floor from the hub database (copied with its WAL, from the pod): floor 0.313.0, MinAgent 0.155.0.
- Later the same day, another session built and deployed hub 0.152.0. It adds scoped access tokens (decision 251).
- **What you must do:** make the token „cc-releases" with *Overview: read* + *Releases: floor: write*. Save it on
  DooPlex as `~/.felhom-hub/cc-token` (`chmod 600`). Do not paste it to me. The file does not exist now (I checked).
- After that, the no-op save (0.313.0 / MinAgent 0.155.0) and its read-back can run. The skill gets the steps then.
- Row: R-1051 (BLOCKED on the token).

## 3. The gate

- `golden_currency_gate.py` now judges the golden's AGE.
- It convicts when the newest golden is more than 7 days old and a released controller is ahead of it.
- On a docs-only push it stays advisory.
- Tests: a 3-day-old golden passes; an 8-day-old golden convicts (CASE 18–21). I proved the tests fail with the limit
  set to 0 and to 30.
- **Limit:** the gate works offline. It reads the CHANGELOG and the bake folders. It cannot see the hub's floor or the vouch.

## 4. The weekly golden

- `runbooks/nightly-rotation.md` has a Sunday-night step: bake the golden when the floor is above it.
- The operator vouches it. CC never vouches.
- Row R-1052: the path for a new box is not proven.

## 5. Prowlarr: live, linked, proven how

**Live:** catalog `73b45a6`. Image `lscr.io/linuxserver/prowlarr:version-2.6.5.5623`. Published 2026-10-07 (8 days
old). Digest `sha256:f9151e5b…` in the ladder entry. Config volume only. Setup gate. The first start sets „sign-in
required" and turns usage data OFF (it was ON by default — measured).

**The record:** `onboarding/prowlarr.md`. All 61 checks are done or n/a. All catalog gates pass.

**Proof, by venue:**

- Bench (LXC 9401): the update test passed; the negative control failed, as it must; 10-minute soak 7.6 % of 512 MB;
  0 kills; the data-folder gate is CLEAN.
- 9202 (drill catalog): install window, gate, first account, stranger, 6 wrong passwords, the update, remove, and
  backup → remove → restore → data back.
- 9201 (live catalog, controller 0.313.0):
  - Sonarr first, then Prowlarr: **no link by itself.** „Bekötés most" made it.
  - Radarr after Prowlarr: **linked by itself**, about 60 s later.
  - Prowlarr's own connection test: 200 for both. Its sync command: completed.
  - All three removed without „delete data". 0 containers and 0 volumes left.

**Not as the brief expected:** the box does not link Prowlarr when Prowlarr itself is installed. It links it only when
Sonarr or Radarr starts, or when the household presses the button. The app text and the website card now say this.
Row R-1058 asks for the fix (a controller change; I made no controller change).

**Two more things I found:**

- **R-1057 (security, P3):** a removed app that is restored comes back WITHOUT its setup gate. This is by design. But if
  the backup was made before the first sign-in, the app comes back open, with no account. Measured on 9202.
- **My own test-tool bug:** my first 9202 update emptied the test catalog's Prowlarr settings file. I found it, fixed
  it, and ran the update and the restore again (run 3). The record cites run 3 only.

**Deviation:** I used scratch guest 9202 for the box walk. The brief named only the bench and 9201. 9202 is Tier 0.
It is back on the live catalog (byte-identical settings file); the test mirror is deleted.

**Website:** a Prowlarr card on both apps pages. Every stated app count: 62 → 63. The machine estimator has Prowlarr.

## 6. Wrong claims in the prompt; commits; register; STATUS

**Wrong claims in the prompt:**

1. „CC raises the floor itself" — with the access CC had, it could not. Only the operator's password could (§2).
2. „The gate convicts when the golden is >7 days old while the floor is ahead" — the gate cannot see the floor. It
   compares the golden with the newest released controller in the CHANGELOG (§3).
3. „Confirm the controller links Prowlarr on install" — it does not when Prowlarr comes last (§5, R-1058).

**Commits:**

- felhom.eu: `e92501f5` (Part A–C), `2f1f6c80` (Prowlarr evidence, website, R-1057), and the final commit with this
  report (R-1048 closed, R-1058, STATUS, CONTEXT).
- felhom-controller `e209a8d`, felhom-agent `d2053e7` — the rule file only. No release.
- app-catalog `3ff0cf3` (rule file), `73b45a6` (Prowlarr).
- Drill catalog (test only): `b5bb89c`, `f2b0cc1`, `e985077`, `03b0c0d`, `e917a58`, `ebf3668`.

**Register:** before 153 · opened 5 (R-1051, R-1052, R-1053, R-1057, R-1058) · closed 2 (R-1045, R-1048) · after 158.
The 158 also holds another session's work today: 3 opened (R-1054..R-1056), 1 closed (R-952).

**STATUS.md:** 59 lines.

**Not-walked claims** (`unproven.py --summary`): 35 of 55. No change.

**Teardown:** bench 9401 stopped, 0 containers. 9202: Prowlarr removed, live catalog back. 9201: Prowlarr, Sonarr,
Radarr removed (keeping data); the drive's media folder stays (4.9 MB). Hub: nothing changed by me. Tester 1 and ep0:
not touched.

**Still running from the earlier task:** the Plex claim watcher waits for your code file. An unclaimed, gated Plex waits
on demo-hp 9201.