coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ACTIVITY-WP-0044-T02: read freshness-run.v1 results[] from rmgr
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m6s
Details

Browse source 
The repo-manager runner reports per-repository rows under results[], not
receipts[]; the projection counted nothing against the real output.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 692292@bnt-lap001
Assistant-Session: 89c7d8e8-e1b3-47eb-9411-a0ab227fca2f
This commit is contained in:
tegwick 2026-10-04 13:18:33 +02:00
parent d6eb788578
commit b2c6c56132
3 changed files with 29 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/ACTIVITY-WP-0044-repo-manager-bounded-freshness-definition.md
View file

@ -47,10 +47,9 @@ state_hub_task_id: "0cbbadc8-d217-55a3-bc2a-da81e19ec2a8"
```task
id: ACTIVITY-WP-0044-T02
status: wait
status: progress
priority: medium
needs_human: false
blocking_reason: "rmgr freshness run is being built in RMGR-WP-0020-T02; JSON output (receipts[].outcome) assumed from the T01 receipt contract"
depends_on: [RMGR-WP-0020-T01, RMGR-WP-0020-T02]
state_hub_task_id: "e4517812-aec2-57e9-9677-de4a89f3f48f"
```
@ -60,6 +59,14 @@ JSON object with `receipts[]` carrying `repo-manager.freshness-receipt.v1`
outcomes; adjust `normalize_operation_result` if the shape differs. Decide the
worker image/packaging of `rmgr` (no deployment in this workplan).
2026-10-04: RMGR-WP-0020-T01/T02 landed (repo-manager ad1ee3e). Flags match
(`--limit`, `--max-seconds` required, `--dry-run`). The run summary is
`repo-manager.freshness-run.v1` with per-repository rows under `results[]`
(not `receipts[]`); dry-run rows carry only a planned `action`. The projection
now reads `results[].outcome` and reports `result_count`; 35 focused tests pass.
Exit 1 with JSON (a failed attempt) still projects; exit 3/4 without JSON raise.
Remaining: decide how `rmgr` is packaged onto the worker.
## Founder-reviewed activation
```task