docs: close operator config migration evidence
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a0291a-1e87-7151-9934-fcbfe3f65eb1
This commit is contained in:
parent
4b908e7189
commit
d6e74a55f6
1 changed files with 5 additions and 5 deletions
|
|
@ -27,11 +27,11 @@
|
||||||
`decision:f3f7c88f9585582a`. Only token length and a truncated fingerprint
|
`decision:f3f7c88f9585582a`. Only token length and a truncated fingerprint
|
||||||
were emitted.
|
were emitted.
|
||||||
|
|
||||||
The operator's persistent `warden.yaml` still contains the two retired keys.
|
The operator's `warden.yaml` was migrated from the two retired keys to the
|
||||||
The live proof used a temporary migrated copy; no operator configuration was
|
compiled `zone_registry_path`. The live proof was then repeated successfully
|
||||||
overwritten. Until those lines are removed, the new loader rejects that file
|
against that real configuration. The new loader continues to reject either
|
||||||
with an explicit migration error rather than silently selecting a second
|
retired key with an explicit migration error rather than silently selecting a
|
||||||
policy source.
|
second policy source.
|
||||||
|
|
||||||
The exception-lifecycle evidence in
|
The exception-lifecycle evidence in
|
||||||
`docs/exception-lifecycle-2026-08-22.md` establishes that expiry is evaluated
|
`docs/exception-lifecycle-2026-08-22.md` establishes that expiry is evaluated
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue