From f1c8b5097181c8df937e643a4faa64419d35b2ac Mon Sep 17 00:00:00 2001 From: "@permadeath.com" Date: Tue, 1 Sep 2026 13:29:42 -0400 Subject: [PATCH] docs(zone-scale): stop quoting a stale layout number layout::LAYOUT reads 9, not the 6 the durable-counter entry recorded. Also flags TlsSection::cert_source, declared in config and read by nothing. Change-Id: Ib99eface4f2145e76e0a6fb1364b1d21d2388341 --- plan/tls-sources.md | 10 +++++++++- plan/zone-scale.md | 6 +++--- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/plan/tls-sources.md b/plan/tls-sources.md index 25494a88..033b7a55 100644 --- a/plan/tls-sources.md +++ b/plan/tls-sources.md @@ -30,7 +30,15 @@ hand over a replacement without interrupting anything. ZeroSSL, Buypass, Google Trust Services. Cheap to support and worth having, because a deployment blocked by one authority's rate limits or outage has somewhere to go. -- [ ] **A certificate the operator supplies**, as files. This is the case for +- [ ] **A certificate the operator supplies**, as files. A half-declared + hook for this already exists and is worth knowing about before anything + is built on it: `TlsSection::cert_source` + (`crates/didbot-config/src/sections.rs:90`) is documented as "`acme` or + a path to a fixed pair", and **nothing reads it** — `didbot-dev`'s + `--tls` accepts `plain` or `acme` and nothing else. A deployment that + set `cert_source` to a path today would be silently ignored. Either + wire it as part of this item or delete it; a configuration key that + does nothing is worse than an absent one. This is the case for an existing internal PKI, a corporate authority, or a purchased wildcard, and it is the one that most needs a **reload trigger**: a file that changes on disk is not an event, so it needs a watcher or a signal. diff --git a/plan/zone-scale.md b/plan/zone-scale.md index 75765b51..cd36e3d3 100644 --- a/plan/zone-scale.md +++ b/plan/zone-scale.md @@ -102,9 +102,9 @@ the fix is cheap and knowing when to apply it is not free. *before* returning it — the same check-append-apply order `NameRegistry` already keeps for name claims — and replay resumes the counter past every value a previous run promised. That is a new `Entry` - variant (`CounterAdvanced`), so `layout::LAYOUT` moves to 6 (see that - constant's doc comment for why not 5: two other in-flight branches had - already claimed it independently). `didbot-dev`'s `--names counter` + variant (`CounterAdvanced`), so it bumped `layout::LAYOUT` — which has + moved several times since and reads 9 today, so do not take a number + from this entry. `didbot-dev`'s `--names counter` shares the durable counter with `--names-if-down counter`, and runs in-memory, restarting at zero, without `--data` — the same split every other durable-optional store here makes. -- 2.51.2