Close WP-0006 activity-core handoff with resolver smoke evidence
Some checks failed
ci / test (push) Has been cancelled

Update handoff checklist: discover_kaizen_scheduled_repos implemented and live
on coulomb pilot definitions; document remaining weekly-template deferral.
This commit is contained in:
2026-06-18 14:29:45 +02:00
parent 50aa553cea
commit e2aa62e597

View File

@@ -21,22 +21,35 @@ execution (WP-0006)"* and track the boxes there.
## What activity-core must do
- [ ] **Implement resolver** `discover_kaizen_scheduled_repos` per the spec
(hub roster ∩ repos with valid `.kaizen/schedule.yml`).
- [ ] **Add resolver unit tests** using the four fixtures in the spec.
- [ ] **Copy definitions** from `docs/integrations/activity-definitions/`
- [x] **Implement resolver** `discover_kaizen_scheduled_repos` per the spec
(`activity_core/context_resolvers/kaizen.py`).
- [x] **Add resolver unit tests** `tests/test_kaizen_context_resolver.py` (7 passed).
- [ ] **Copy custodian weekly definitions** from `docs/integrations/activity-definitions/`
(`weekly-coach-orientation.md`, `weekly-optimization-review.md`) into the
activity-core catalog path (per ACT-ADR-002).
- [ ] **Register** each definition slug in the activity-core index.
- [ ] **Run** `make sync-activity-definitions` in activity-core.
- [ ] **Wire cron** triggers (Mon 09:00 / 10:00 Europe/Berlin) to the resolver.
- [ ] **Smoke test** against a pilot repo (see below) with the definition still
`enabled: false` (dry-run task creation).
- [ ] **Enable gradually** — flip one definition to `enabled: true` in staging
after the smoke test passes.
- [ ] **Verify runner prerequisites** `kaizen-agentic` on PATH and the Gitea
PyPI extra index if the runner installs from registry (see
[PACKAGE_RELEASE.md](../PACKAGE_RELEASE.md)).
activity-core catalog path (per ACT-ADR-002). *Deferred: coulomb-loop engagement
ships customer-owned daily bootstrap definitions instead (LOOP-WP-0001).*
- [ ] **Register** weekly definition slugs in the activity-core index (when custodian
fleet moves off coulomb engagement copies).
- [x] **Run** `make sync-activity-definitions` — coulomb-loop definitions synced
(`coulomb-hourly-coach-orientation`, `coulomb-hourly-optimization-review`, etc.).
- [x] **Wire cron** triggers — daily stabilize chain on pilot roster (08:0010:00).
- [x] **Smoke test** — resolver dry-run returns 6 `scheduled_runs` on coulomb roster;
`schedule prepare coach` succeeds on `kaizen-agentic` and `the-custodian`.
- [x] **Enable gradually** — coulomb bootstrap definitions `enabled: true` on pilot.
- [x] **Verify runner prerequisites**`kaizen-agentic` on PATH; `KAIZEN_RUNNER_HOST`
set on worker (`bnt-lap001`).
### Supplier closure evidence (2026-06-18)
| Check | Result |
|-------|--------|
| Resolver dry-run (coulomb roster, `cadence: daily`) | 6 runs across 3 pilot repos |
| `tests/test_kaizen_context_resolver.py` | 7 passed |
| `schedule validate` + `prepare coach` | OK on `kaizen-agentic`, `the-custodian`, `activity-core` |
| Live definitions using resolver | `f234bb1a` coach, `097fc027` optimization (enabled) |
**Remaining activity-core item:** optional custodian-fleet weekly templates (`enabled: false`
in kaizen-agentic drafts) when engagement moves beyond coulomb-loop bootstrap copies.
## State Hub team (the-custodian)