docs: route durable prune inventory ownership
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
parent
293ef9dc77
commit
df34afd26a
1 changed files with 5 additions and 0 deletions
|
|
@ -347,6 +347,11 @@ Depends on T02–T07 as applicable.
|
||||||
- Temporal reports the schedule enabled and unpaused. T08 remains `progress`
|
- Temporal reports the schedule enabled and unpaused. T08 remains `progress`
|
||||||
until the next natural apply fire (2026-09-06 03:30 UTC) produces successful
|
until the next natural apply fire (2026-09-06 03:30 UTC) produces successful
|
||||||
State Hub evidence; the schedule was not manually fired.
|
State Hub evidence; the schedule was not manually fired.
|
||||||
|
- State Hub message `868a2326-cdad-4256-be4c-7cd6c8ec4b5b` asks
|
||||||
|
railiance-platform to move the generated protection inventory onto a durable
|
||||||
|
checkout-independent path and refresh it through the platform image-rollout
|
||||||
|
lifecycle. That residual must preserve multi-cluster over-protection and the
|
||||||
|
existing apply refusal when the inventory is absent or empty.
|
||||||
|
|
||||||
## Gap disposition
|
## Gap disposition
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue