Record WP0035 production rollout
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
parent
26934e25b9
commit
36161d346f
1 changed files with 9 additions and 0 deletions
|
|
@ -306,6 +306,15 @@ Depends on T02–T07 as applicable.
|
|||
worker feature flag, and zero Temporal `TaskExecutorWorkflow` executions.
|
||||
- Compatibility detail is retained in
|
||||
`history/2026-08-23-bounded-operation-compatibility-report.md`.
|
||||
- Production rollout imported image digest
|
||||
`sha256:1a267fed1c5ea09c93d90728336b5c6976df2fbf1b8d757fb8fc89aff8ec5e9c`,
|
||||
applied migration `0009`, strictly synced 27 local/external definitions with
|
||||
zero errors, and rolled API/worker/event-router to Ready. The worker now
|
||||
advertises only `orchestrator-tq`; DB inspection confirms the three admitted
|
||||
operation ids and the retired table/renamed audit column.
|
||||
- Deterministic production status after rollout reports API/DB/Temporal healthy.
|
||||
Natural post-rollout operation evidence remains open: CNPG and SBOM next run
|
||||
2026-08-24; Forgejo prune next run 2026-08-30. No schedule was manually fired.
|
||||
|
||||
## Gap disposition
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue