Files
felhom.eu/REPORT-clock-end-dates-2026-11-11.md
T
admin 978666dde3
gates / gates (push) Successful in 2m2s
lists: the Clock list (70 jobs) and the End-dates list (39 things), 9 register rows, 4 decisions
Read-only review of every job on a timer and of everything that ends on a date,
with measurements from the three test boxes. Nothing ends in the next 14 days.
Register 236 -> 245 (R-1379..R-1387), pointer lines on twelve rows, D76-D79 in
STATUS.md. Part C: felhom-agent's clone address holds no token now; the other
clones wait for the operator's yes. R-1035's 4-week check moved to 2026-11-18
(operator read needed).

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-11-11 11:54:42 +01:00

7.8 KiB

Report — the Clock list, the End-dates list, no token in a repository address (2026-11-11)

Session start 2026-11-11T09:57Z. Read-only on the three test boxes. No release, no build, no deploy, no household mail.

1. Claims in the prompt that turned out wrong

  • "No architecture document lists every timer or every end date" — true. Search S19 (Clock) and S18 (End dates) found no such list. 69 of 70 jobs are mentioned somewhere; no document puts them in one order.
  • The plan file claude/PLAN-architecture-gap-review-2026-11-10.md does not exist. The lists follow the shape of the two lists of 2026-11-10 in documentation/audits/.
  • "The same happened before with another clone (R-925)" — true: three clones held a login and a token in the address (§3, Part C), not one.
  • Not in the prompt, and it shaped the run: the golden gate is red (the newest golden is 8 days old, the limit is 7, no waiver). A push that holds code is refused. This run pushed documents only.

2. Parts

Part State Why
B — the two operator tables done in documentation/audits/end-dates-list-2026-11-11/README.md
B — the End-dates list done 39 things, 312 answers
A — the Clock list done 70 jobs, 560 answers
C — proof on felhom-agent done fetch, pull, push, hook, release dry run, positive control
C — the other clones, the scripts, the CLAUDE.md line not done no answer to the STOP question in 30 minutes; the brief says: change nothing else
C — the helper script in the repository changed scripts/git-credential-sec.sh is on DooPlex's disk, not pushed: the golden gate refuses a code push

3. The lists

End dates (documentation/audits/end-dates-list-2026-11-11/): found 58, in the table 39 · named by no document 2, only mentioned 28 · marks A 268, D 2, K 3, N 39 · worst N: the agent's pin on Proxmox's certificate; Proxmox renews by itself and the agent does not follow (first box about 2028-07-02) · two decisions (D76, D77). Method: it worked; the measurement found the worst gap, no helper did.

Clock (documentation/audits/clock-list-2026-11-11/): found 77, in the table 70 · named by no document 1 · marks A 457, D 0, K 9, N 94 · worst N: the guest-power watchdog gives up and tells nobody · two decisions (D78, D79). Method: it worked for the map; the two meetings of jobs came from the boxes, not from a helper.

Ends in the next 90 days — the full table is in the End-dates README. Short form:

Ends What Renewal proven?
2026-11-10 (past) the golden's 7-day age limit no — you bake or write a waiver
2026-12-23 to 2027-01-28 eleven web certificates (the hub, Gitea, the download and ISO addresses, the website, the three household names and their Cloudflare edges) demo-hp's box: yes (renewed 2026-10-21); the hub's: seen once; the others: not measured
2027-01-17 demo-hp's Tailscale key (date from a document) no — yours; Tailscale does not run there today
not known CC's hub token (90 days) no — the date is on the hub's token page

Nothing ends within 14 days. The one date already past is the golden's.

Part C. Clones with a credential in the address (names only): git/felhom-agent, git/cc-secrets, clones-plugmeter-2026-10-13/felhom-agent. 13 other clones: no. No extraHeader, no insteadOf, no script and no skill writes a credential into an address. The fix: the address holds no login; the clone's own credential helper is scripts/git-credential-sec.sh, which answers from the environment of sec run GITEA_GIT_TOKEN -- git …. The proof on felhom-agent: fetch, pull, the push of commit 91a2924 through the pre-push hook (all gates OK, PUSH RC=0), a dry run of the release script's two git steps, then git remote -v and git config --get-regexp with no secret in them. The operator's answer: none by 10:50 UTC, so the two other clones are as they were. Token to rotate: the Gitea token of login kisfenyo (printed on 2026-11-10). Put the new one in the store only, as GITEA_GIT_TOKEN. The cc-secrets clone holds login admin's token in its address; it was not printed in this run. The clear-text file ~/.git-credentials (3 lines) and the global store helper still serve the other clones; this run did not touch them.

4. Machines, and what changed

Read: demo-hp, Tester 1, the N100 — host and guest each. Public reads: the TLS certificates of public names. Not read: DooPlex's workloads, ep0, the hub's database, any account.

No box was changed, with one thing to name: the script that read the night's times wrote one mktemp file in each guest's /tmp and removed it. No job was started, no setting written.

Changed on DooPlex, file by file: git/felhom-agent/.git/config (address without login; credential.helper; credential.username) · new file git/felhom.eu/scripts/git-credential-sec.sh (untracked) · one new entry GITEA_GIT_TOKEN in the sec store (cc-secrets commit 8bdcf3a; a copy of the token the clone already used, no token made, rotated or deleted) · the files of this commit.

Deviations: (1) one probe git push --dry-run --no-verify on felhom-agent; nothing was pushed, and the real push ran the hook. (2) felhom-agent's REPORT.md was not overwritten for its documents-only commit. (3) Questions 4 to 7: the main session read every helper answer by eye, and it opened the pointers by eye only for a part (below).

5. Commits, CI, register

  • felhom-agent 91a2924ad0d5e8e5601c2a0c261be390826a465e — CI run 2624: Success (read from the public Actions page).
  • felhom.eu — this commit; its CI result is in the chat note, by hash.
  • cc-secrets 8bdcf3a (the store entry).
  • The 4-week search check of R-1035 came due today and stopped the push gate. Only the operator can read it, so its date moved to 2026-11-18, with the reason in the row (the gate's own rule allows this).
  • Register: before 236, after 245, opened 9 (R-1379 to R-1387), closed 0. Dated pointer lines on R-401, R-468, R-924, R-925, R-1186, R-1189, R-1206, R-1260, R-1293, R-1294, R-1301, R-1361; a moved-date line on R-1035.

6. Documents read; cells by eye and by tool

Architecture: 01-topology-and-trust.md, 03-host-agent.md, 04-control-plane-authorization.md, 05-hub-architecture.md, 06-offsite-connectivity.md, 07-backup-architecture.md, 08-alarm-ladder.md, 09-update-architecture.md, 11-os-updates.md, 13-threat-model.md, _recovery-inventory-2026-07-28.md; and cc-secrets/ARCHITECTURE.md for Part C.

List Cells Main session's own words (read by eye) Pointers opened by eye Pointers opened by tool
End dates 312 85 (every D, K, N; 41 A) part all 259, dead 0
Clock 560 138 (every K, N; 35 A) 70 all 896, dead 0 (one dead helper pointer dropped)

Document edits in place: none. Instruction-file edits: none. Text about a protected machine that looks stale and was not edited: the hub-database copy alarm, 13 h or 26 h (in R-1387). The system poster: no fact in its facts file changed; nothing to do.

7. Observations outside the scope

  • The agent unit and its design document disagree (Restart, watchdog) — FILED: R-1387.
  • A comment in the controller says 14 days where the code keeps 30 — FILED: R-1387.
  • Stale line cites in 07-backup-architecture.md:455-457 — FILED: R-1387.
  • tailscale.md says "both nodes"; Tailscale does not run on demo-hp and Tester 1 today — FILED: R-1387.
  • Threat model and recovery inventory differ on the hub bearer's rotation — FILED: R-1387.
  • The golden gate is red — FILED: pointer line on R-468; a "do" in STATUS.md.
  • The N100's whole-guest backup starts 5 minutes later each day — FILED: R-1385.
  • MEMORY.md is at its size limit — NOT-A-FINDING: known; the gate warns only.