CC secrets build: register (177 -> 181: R-1130..R-1134 opened, R-1122 closed, R-1118 narrowed), STATUS D13-D16, report

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012qRErfCoiTkvDK9N5XHbzb

STATUS.md

@@ -40,6 +40,7 @@
 - Tester 2 has never made an off-site check (R-862). The scratch box cannot read the drill catalog (R-992).
 
 ## What we work on
+- **CC's secrets** (R-1118): built and installed 2026-10-17 — the store, `sec`, the guards in every CC session, the nightly check. Left: the old credentials file retires after a week with no reader (R-1134), and three answers from you (below).
 - **After 2026-10-18 14:16 UTC** (demo-hp's next clean-up window): check that the old restic (image 0.322.0) still lists and restores demo-hp's store after its first real 0.19.1 prune (`audits/night-restore-2026-10-17/tools/rx.sh`). Everything else of R-1105/R-1107 is done.
 - The power-cut findings still open (R-1004, R-1005, R-1010, R-1012, R-1013).
 - Media apps on every drive (R-1023): live with the 0.313.0 floor — every drive in every media app, a new drive made ready by the box, a pulled drive loses nothing, a safe removal lets go first and the drive comes back by itself.
@@ -59,8 +60,11 @@
 | D10 | R-1125 | Raise the 23 memory requests to what the apps really use? Then an 8 GB box no longer installs the full household set (its sixth app is refused). | **Your call** — values ready | Keep: the box's install check stays optimistic | nothing changes | — |
 | D11 | R-1126 | The tunnel runs before the claim (the claim needs it). Close FileBrowser's first-start window (A), or claim only at home (B)? | **A** — small, no promise changes | B: the claim mail and flow change, the household must be at home | FileBrowser's default is open for ~2 s at its first start | — |
 | D12 | R-1129 | CI has never sent its failure mail (the key is empty in the runner since at least 2026-09-22). Set the key in the four repos? | **Yes** — you set it, or CC with your word (it is a credential) | — | a red CI run or a `--no-verify` push reaches nobody | — |
+| D13 | R-1119 | Remove `export RESEND_API=…` from your `~/.bashrc` (line 88)? The key is in CC's store now (`sec run RESEND_API`). | **Yes** — you, or CC with your word (it is your file) | Keep: every CC command carries the key | the key stays one `env` away from a record; the new guard refuses bare `env`/`printenv`, but not every shape | — |
+| D14 | R-1120 | homelab CC settings let `kubectl get secret -o yaml` run with no prompt. Add an `ask` rule too, or rely on the new guard alone? | **Add the ask rule too** — one line, two layers | Guard only: one layer, already proven | the guard alone refuses it in every session | — |
+| D15 | R-1130, R-1131, R-1132 | Three secrets are in old CC records: the registry password, and the demo-felhom and demo-hp recovery codes (printed today 10:27 by the JARR session, before the guards). Change them? | **Change the registry password; your call on the two demo codes** | Accept: no work; the values stay valid | the three values stay valid while copies sit in records Anthropic's API has seen | — |
+| D16 | R-1134 | Line 20 of the old credentials file is a value with NO name. What is it? | Tell CC the name (CC stores it) or say „drop it” | — | it stays only in the old file, which retires on 2026-10-24 | the old file's retirement |
 | D9 | R-1062 | The N100's USB drive is also its whole-box backup drive. Split it in two anyway? | **No — keep one drive**; the lived-in box keeps its nightly whole-box backup | Split: the box loses its local whole-box backup (or add a second drive first) | it stays one drive; multi-drive tests stay on Tester 1 | — |
-| D10 | R-1118 | Where should CC keep its secrets, so it can use one without ever printing it? (spike 2026-10-17: the guards work; `audits/SPIKE-cc-creds-2026-10-17.md`) | **B — an encrypted file in a private Gitea repo (SOPS + age)**; then you make one empty private repo, CC cannot (its tokens lack the right) | Vaultwarden: one more service to run and back up; the spike's store test would be redone | the plain credentials file stays, and every known leak shape (sourcing it, `printenv`, curl URL echo, `kubectl get secret`) stays open | the build of the broker and guards |
 
 ## Waiting on you — do
 - **Nézd meg a demo-hp-n a Calibre-Web „Adatok és mentés" fülét és a Fájlkezelőt** (`felhom.enkisfelhom.hu`, controller 0.321.0, minden dobozon kiadva). A mentés egy részben, egyszerű szavakkal; a Fájlkezelő nem kér frissítést és nem ajánl „Install app"-ot.