Add weekly coding retro dry-run scheduler script
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Build and Publish Container Image / build-and-push (push) Failing after 1m3s

Wire ACTIVITY-WP-0008 dry-run helper and update retro activity definition,
runbook, and workplan notes.
This commit is contained in:
tegwick 2026-07-09 00:29:25 +02:00
parent f314bfc7f2
commit f171bb037a
4 changed files with 129 additions and 6 deletions

View file

@ -4,11 +4,11 @@ type: workplan
title: "Weekly Coding Retrospection schedule (Saturday evenings)"
domain: custodian
repo: activity-core
status: active
status: finished
owner: codex
topic_slug: custodian
created: "2026-06-07"
updated: "2026-07-03"
updated: "2026-07-08"
state_hub_workstream_id: "7387fc50-1f2c-471a-9d85-bb085cbd0b63"
---
@ -80,7 +80,7 @@ repo with the coding-retro/improvement/automated labels. It remains
```task
id: ACTIVITY-WP-0008-T03
status: wait
status: done
priority: medium
state_hub_task_id: "9dcbebe7-13dd-4957-9a72-858418049aef"
```
@ -115,3 +115,12 @@ No newer weekly publish exists yet. This is a **time-controlled wait** on the
next Saturday 19:00 Europe/Berlin publish (or an operator decision to enable on
the zero-suggestion proof), not a hard blocker. Workplan status returns to
`active`; T03 stays `wait`.
**2026-07-08 closeout:** Operator-approved zero-suggestion enablement proof.
Railiance live dry-run at 21:26 UTC fired two consecutive manual triggers for
`weekly-coding-retro` (`e6034924-7ace-5dd6-9693-deb50efe8346`). Both workflows
completed cleanly with `tasks_spawned=0` against the weekly
`coding_retro` read model `ec20ac1c` (`window.days=7`, zero suggestions). The
definition is now `enabled: true` with the Saturday 19:00 Europe/Berlin Temporal
schedule upserted. Runbook updated to record zero-suggestion weekly read models
as an acceptable enablement proof when duplicate re-runs stay clean.