From f36af682e4dea1e5c9e5f562a73502c552b1fe54 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 3 Jul 2026 19:19:52 +0200 Subject: [PATCH] Reevaluate blocked workplans WP-0008/0009/0010/0015 Unblock lifecycle statuses after daily triage trust evidence closed (06-28 through 07-03 clean scheduled runs). Finish WP-0010, return WP-0008/0009/0015 to active with accurate wait reasons, and document the scheduled-wait vs hard-blocker distinction. --- .../ACTIVITY-WP-0008-weekly-coding-retro.md | 12 +++++++-- .../ACTIVITY-WP-0009-intent-gap-closure.md | 17 +++++++++--- ...WP-0010-daily-triage-llm-reconciliation.md | 27 +++++++++++++++---- ...-0015-adopt-statehub-beachhead-endpoint.md | 11 +++++--- 4 files changed, 53 insertions(+), 14 deletions(-) diff --git a/workplans/ACTIVITY-WP-0008-weekly-coding-retro.md b/workplans/ACTIVITY-WP-0008-weekly-coding-retro.md index 794cb3d..5453dc6 100644 --- a/workplans/ACTIVITY-WP-0008-weekly-coding-retro.md +++ b/workplans/ACTIVITY-WP-0008-weekly-coding-retro.md @@ -4,11 +4,11 @@ type: workplan title: "Weekly Coding Retrospection schedule (Saturday evenings)" domain: custodian repo: activity-core -status: blocked +status: active owner: codex topic_slug: custodian created: "2026-06-07" -updated: "2026-06-17" +updated: "2026-07-03" state_hub_workstream_id: "7387fc50-1f2c-471a-9d85-bb085cbd0b63" --- @@ -107,3 +107,11 @@ specs because that weekly read model has zero suggestions. The schedule remains disabled until a non-empty weekly read model, or an explicit operator decision that a zero-suggestion dry-run is an acceptable enablement proof, confirms correct routing and no duplicate target tasks on re-run. + +2026-07-03 reevaluation: `AGENTIC-WP-0010` remains finished and the resolver +smoke still works, but State Hub still has only the 2026-06-07 weekly +`coding_retro` read model (`ec20ac1c`, `window.days=7`) with zero suggestions. +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`. diff --git a/workplans/ACTIVITY-WP-0009-intent-gap-closure.md b/workplans/ACTIVITY-WP-0009-intent-gap-closure.md index 1eb0686..b573dfc 100644 --- a/workplans/ACTIVITY-WP-0009-intent-gap-closure.md +++ b/workplans/ACTIVITY-WP-0009-intent-gap-closure.md @@ -4,11 +4,11 @@ type: workplan title: "Intent gap closure" domain: custodian repo: activity-core -status: blocked +status: active owner: codex topic_slug: custodian created: "2026-06-16" -updated: "2026-06-18" +updated: "2026-07-03" state_hub_workstream_id: "d64cfbba-6da7-4737-afb9-866afa0e9cda" --- @@ -38,7 +38,7 @@ The preserved analysis lives in: ```task id: ACTIVITY-WP-0009-T01 -status: wait +status: done priority: high state_hub_task_id: "7012e4fd-2530-49b7-9c2f-1d949809a144" ``` @@ -73,6 +73,12 @@ fixture smoke passed. The remaining work is the activity-core / Railiance runtime reconciliation and daily-triage evidence collection path captured in `ACTIVITY-WP-0010`. +2026-07-03 closeout: `ACTIVITY-WP-0010` and `ACTIVITY-WP-0006-T03` now record +three consecutive clean scheduled daily triage runs (2026-06-28 through +2026-06-30, streak continuing through 2026-07-03) with matching State Hub +progress, working-memory notes, and calibration feedback. The scheduled-run trust +gap is closed. T01 is done. + ## Promote Issue-Core Task Emission Safely ```task @@ -100,6 +106,10 @@ Current wait reason: production Railiance currently uses null-sink audit mode; live issue-core credentials/access and duplicate-handling are not yet verified for this repo. +2026-07-03 reevaluation: this is an external-credential gate, not a workplan +blocker. Keep T02 at `wait` with `blocking_reason` describing the issue-core +approval path; the workplan returns to `active`. + ## Resolve Review-Required Contract Drift ```task @@ -231,7 +241,6 @@ Agent-actionable closure is complete for T03, T04, T05, and T06. Remaining waits: -- T01 waits on real scheduled daily triage run evidence. - T02 waits on issue-core production endpoint/credentials and duplicate-handling approval. diff --git a/workplans/ACTIVITY-WP-0010-daily-triage-llm-reconciliation.md b/workplans/ACTIVITY-WP-0010-daily-triage-llm-reconciliation.md index d385bfb..3e99006 100644 --- a/workplans/ACTIVITY-WP-0010-daily-triage-llm-reconciliation.md +++ b/workplans/ACTIVITY-WP-0010-daily-triage-llm-reconciliation.md @@ -4,11 +4,11 @@ type: workplan title: "Daily Triage LLM Reconciliation And Evidence" domain: custodian repo: activity-core -status: blocked +status: finished owner: codex topic_slug: custodian created: "2026-06-18" -updated: "2026-06-27" +updated: "2026-07-03" state_hub_workstream_id: "f2c73ac6-13f0-4005-82cc-76c7c9f9c8b9" --- @@ -135,7 +135,7 @@ Hub handoff message `9a074b7c-4b87-4e3c-a6bf-e1fe5580daa8` asks ```task id: ACTIVITY-WP-0010-T03 -status: wait +status: done priority: high state_hub_task_id: "10e0df77-c230-4a82-b720-23c66bd17c0a" ``` @@ -173,11 +173,17 @@ Done when: after the WP-0016 code/schema/runtime-prompt deployment due the 2026-06-26 and 2026-06-27 malformed-output failures. +2026-07-03 closeout: `ACTIVITY-WP-0016` is finished and scheduled +`daily_triage` progress from **2026-06-28 through 2026-07-03** all show +`output_validated=true` with working-memory notes. The `railiance-cluster` +inbox reply (`e360e38f`, 2026-07-01) confirms the live runtime, provider Secret +presence, and in-namespace fixture smoke. T03 is done. + ## Collect Three Clean Scheduled Runs ```task id: ACTIVITY-WP-0010-T04 -status: wait +status: done priority: high state_hub_task_id: "dc6b9482-cf43-4fc5-994b-dcd7dea47db7" ``` @@ -204,11 +210,17 @@ Done when: Railiance runtime prompt and max_tokens changes, run a live smoke, then restart the three-consecutive-scheduled-run gate from zero. +2026-07-03 closeout: post-`ACTIVITY-WP-0016` scheduled runs on **2026-06-28, +2026-06-29, and 2026-06-30** (`6a44d6dd`, `1dfb47c9`, `ac3d71a0`) are three +consecutive clean scheduled successes with matching State Hub progress and +working-memory notes. The streak continued through 2026-07-03. Calibration +feedback was already recorded when `ACTIVITY-WP-0006-T03` closed. T04 is done. + ## Close Handoff State ```task id: ACTIVITY-WP-0010-T05 -status: wait +status: done priority: medium state_hub_task_id: "ecc57e21-1716-4daa-aba6-d8a6d824e4ed" ``` @@ -223,3 +235,8 @@ Done when: - any temporary `needs_human` flags created for the llm-connect provider/config handoff are cleared or replaced by a narrower follow-up; - this workplan is marked `finished`. + +2026-07-03 closeout: `ACTIVITY-WP-0006-T03` already records the three-run +calibration evidence. `ACTIVITY-WP-0009-T01` is updated in the same pass. +No temporary `needs_human` flags remain for the llm-connect provider/config +handoff. T05 is done; this workplan is `finished`. diff --git a/workplans/ACTIVITY-WP-0015-adopt-statehub-beachhead-endpoint.md b/workplans/ACTIVITY-WP-0015-adopt-statehub-beachhead-endpoint.md index 2398848..75b8963 100644 --- a/workplans/ACTIVITY-WP-0015-adopt-statehub-beachhead-endpoint.md +++ b/workplans/ACTIVITY-WP-0015-adopt-statehub-beachhead-endpoint.md @@ -4,11 +4,11 @@ type: workplan title: "Adopt State Hub Beachhead Endpoint" domain: infotech repo: activity-core -status: blocked +status: active owner: claude topic_slug: activity-core created: "2026-06-24" -updated: "2026-06-24" +updated: "2026-07-03" state_hub_workstream_id: "bbc07f9e-9323-4b2b-b556-c33b37d0b228" --- @@ -19,10 +19,15 @@ Carries the **blocked remainder** of [[ACTIVITY-WP-0014]] T05. The in-repo half client-side adoption that depends on the state-hub-owned **beachhead** capability (per-machine read cache + write outbox) existing first. -**Blocked on:** the state-hub beachhead (proposal sent to the `state-hub` agent, +**Waiting on:** the state-hub beachhead (proposal sent to the `state-hub` agent, 2026-06-23). Do not build queue/cache logic in activity-core — see [[statehub-beachhead-principle]]. +2026-07-03 reevaluation: no state-hub-owned beachhead endpoint is available yet. +`CUST-WP-0054` now tracks a files-first dev beachhead, but activity-core client +adoption still depends on the state-hub capability shipping first. Both tasks +remain `wait` on external delivery; the workplan is `active`, not `blocked`. + ## Point STATE_HUB_URL at the beachhead ```task