diff --git a/workplans/ACTIVITY-WP-0043-state-hub-owner-return-pickup.md b/workplans/ACTIVITY-WP-0043-state-hub-owner-return-pickup.md index 13e9389..8acef69 100644 --- a/workplans/ACTIVITY-WP-0043-state-hub-owner-return-pickup.md +++ b/workplans/ACTIVITY-WP-0043-state-hub-owner-return-pickup.md @@ -4,7 +4,7 @@ type: workplan title: "Owner-return pickup adapter for State Hub STATE-WP-0094-T03" domain: infotech repo: activity-core -status: active +status: blocked owner: claude-activity-core topic_slug: activity-core created: "2026-10-04" @@ -63,10 +63,9 @@ caller asserts paginated collection, and every candidate binds. Tests: ```task id: ACTIVITY-WP-0043-T03 -status: wait +status: done priority: high needs_human: false -blocking_reason: "State Hub C-25 fetches at most 200 replies per counterpart; pagination belongs in state-hub (STATE-WP-0094-T03)" state_hub_task_id: "b23ad89b-baed-5383-ab10-b54cd182dbd5" ``` @@ -81,7 +80,7 @@ id: ACTIVITY-WP-0043-T04 status: wait priority: medium needs_human: true -blocking_reason: "Activation is a separately reviewed founder action" +blocking_reason: "Founder accepted memo 2 (approval 77993081); trials wait for the first live C-25 owner return" state_hub_task_id: "254526ce-5a76-57b3-b7d5-a874518c7b40" ``` @@ -136,3 +135,10 @@ Planner vendored from state-hub `150cb0b` (C-25 source-revision contract); names `source_revision_reason` when it is null. Gaps (in-cluster report producer, structured completeness proof, private-repo Forge reads) are listed in the activation plan. Tests: `tests/test_owner_return_runner.py`. + + +2026-10-04 session close: workplan set to blocked. T03 done: State Hub revision +73 pages C-25 replies. The worker runs owner_return_pickup (image git-34d1dc5, +Argo a86a143); the definition is disabled and the pickup flag is unset. T04 waits +for the first live owner return, then the plan-only run (submit false) and the +founder-reviewed submit run. diff --git a/workplans/ACTIVITY-WP-0044-repo-manager-bounded-freshness-definition.md b/workplans/ACTIVITY-WP-0044-repo-manager-bounded-freshness-definition.md index fd08dac..f87bc09 100644 --- a/workplans/ACTIVITY-WP-0044-repo-manager-bounded-freshness-definition.md +++ b/workplans/ACTIVITY-WP-0044-repo-manager-bounded-freshness-definition.md @@ -4,7 +4,7 @@ type: workplan title: "Repo Manager bounded freshness ActivityDefinition (RMGR-WP-0020-T03)" domain: infotech repo: activity-core -status: active +status: blocked owner: claude-activity-core topic_slug: activity-core created: "2026-10-04" @@ -47,7 +47,7 @@ state_hub_task_id: "0cbbadc8-d217-55a3-bc2a-da81e19ec2a8" ```task id: ACTIVITY-WP-0044-T02 -status: progress +status: done priority: medium needs_human: false depends_on: [RMGR-WP-0020-T01, RMGR-WP-0020-T02] @@ -81,3 +81,9 @@ state_hub_task_id: "9aeaf03d-8269-5fd7-8a15-99c7124f0d5c" Flip `enabled: true` only after the RMGR-WP-0020-T04 manual dry-run/apply fires. Rollback: `enabled: false` (or `status: paused`). + + +2026-10-04 session close: workplan set to blocked. T02 done: rmgr is packaged +into the worker image git-34d1dc5 (pinned repo-manager e77f8b4, isolated venv) +and deployed via Argo a86a143. The definition stays disabled. T03 waits for the +RMGR-WP-0020-T04 trials, which need the read-only Forgejo token.