Per the sequencing call (adversarial pass first, docs last), the docs
now reflect the design the reviews confirmed.
configuration.md:
- Mutation ledger gains rows for SIGHUP reload, dashboard PATCH,
dashboard reset, and the runtime overlay store, each mapping to the
universal change protocol with what is and is not yet implemented.
- New section 'Implemented runtime reload and config overlay (2026-08)':
the Holder published-snapshot model, the reloadable-field criterion
(a field is reloadable when EVERY consumer re-reads it), SIGHUP
reload semantics, the overlay store (separate -config.sqlite, dotted
keys, denylist, bootstrap degrade), and the PATCH/reset paths.
safe-change-and-recovery.md:
- New section 'Runtime config overlay: degrade paths and recovery'
tabulating the three boot degrade paths and the reload degrade, all
verified by the adversarial passes, plus the three documented
recoveries (--no-config-overlay flag, rm the overlay file, dashboard
reset). Status line notes the overlay subset is implemented while
the full runtime-supervision protocol remains under design.
No new documents, per the constraint.