Complete release dispatch groundwork and mark remaining work blocked

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e429-436c-73f1-9144-bac4336c06e8

workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md

@@ -4,13 +4,13 @@ type: workplan
 title: "Adopt the Glas profile-driven execution contract"
 domain: infotech
 repo: activity-core
-status: active
+status: blocked
 flavor: implementation
 owner: claude
 topic_slug: activity-core
 priority: medium
 created: "2026-08-21"
-updated: "2026-09-04"
+updated: "2026-09-27"
 related:
   - ACT-ADR-006
   - ACTIVITY-WP-0026
@@ -299,3 +299,15 @@ was requested or copied, and the disabled pilot remains untouched.
 - [x] `approach_hint` cannot override or substitute for a profile ref, proven by test
 - [x] Normalized Glas evidence is visible in production status
 - [ ] One definition proven on railiance01 end to end
+
+## Loose-end review — 2026-09-27
+
+T05 remains blocked outside this repository. Current owner evidence supersedes
+the September 4 description: sand-boxer has implemented owner-mediated execution
+and protected runtime placement, but GLAS-WP-0012 remains blocked. The original
+1.0.0 pilot profile is still explicitly blocked; 1.1.1 is unverified and needs
+its updated runtime and combined production proof. Native credential admission,
+provider execution and profile readiness remain owner gates. Do not rerun the
+old pilot or silently change its profile. Resume T05 after Glas supplies an
+admitted profile and matching railiance01 runtime/credential evidence. Workplan
+state is now blocked; the four completed implementation tasks remain done.

workplans/ACTIVITY-WP-0040-frontend-patterns-feedback.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Deterministic frontend-patterns feedback collection and reports"
 domain: infotech
 repo: activity-core
-status: active
+status: blocked
 owner: codex
 topic_slug: activity-core
 created: "2026-09-27"
@@ -35,7 +35,7 @@ Dockerfile.frontend-patterns overlays only two Python files on the deployed work
 
 ```task
 id: ACTIVITY-WP-0040-T02
-status: progress
+status: wait
 priority: high
 state_hub_task_id: "0d0d1d05-9b2d-5eac-b54a-c557b1690afc"
 ```
@@ -88,3 +88,13 @@ FEP-WP-0008 retains consumers and improvement execution; ACTIVITY-WP-0041 record
 the permanent GitOps/adoption/standing-authority work needed to prevent exceptions.
 Do not close this workplan until cadence evidence is observed or explicitly handed
 off to another live task. No real-consumer value or autonomous edits are claimed.
+
+## Loose-end review — 2026-09-27
+
+T02 is now wait and the workplan blocked on natural cadence evidence. The
+September 27 activation/sink smoke already completed the deployable repo work;
+first daily/weekly/monthly executions are due September 28 / September 29 /
+October 1. A manual rerun cannot satisfy this acceptance condition. Resume T02
+when the three natural executions have matching run/report/sink receipts. Keep
+existing schedules enabled and retain FEP-WP-0008 ownership of consumer value
+and improvement execution. No new task or artificial success evidence was created.

workplans/ACTIVITY-WP-0041-gitops-adoption.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Remove recurring deployment exceptions through governed GitOps adoption"
 domain: infotech
 repo: activity-core
-status: active
+status: blocked
 owner: codex
 topic_slug: activity-core
 created: "2026-09-27"
@@ -44,7 +44,7 @@ server-dry-run the proposed managed set; no unintended spec change or pruning.
 
 ```task
 id: ACTIVITY-WP-0041-T02
-status: progress
+status: wait
 priority: high
 state_hub_task_id: "af09865d-8cc9-5571-9c34-20ae679a1e4e"
 ```
@@ -67,7 +67,7 @@ one-time governance decision.
 
 ```task
 id: ACTIVITY-WP-0041-T03
-status: progress
+status: wait
 priority: high
 state_hub_task_id: "8e2b4ed9-d455-5367-85d9-8e4222ce75f3"
 ```
@@ -191,3 +191,29 @@ T03 remains progress for admitted identity/custody, authenticated isolated Kuber
 verification, real build/review/retention issuers, production invariant probes,
 Temporal observer/dispatcher registration and evidence sinks. The implemented
 observer cannot retroactively assert the earlier soak interval. See docs/release-broker.md.
+
+## Loose-end implementation and blockers — 2026-09-27
+
+Completed another repo-side portion of T03: `release_dispatch.py` supplies a
+Temporal workflow and explicitly constructed dedicated worker for resuming an
+already-admitted ledger release. Requests carry only its ID; source, transport,
+keys and sinks come from trusted worker configuration. Durable transition audit
+acknowledgements survive restart, repeat the same event ID after a lost response,
+and export only normalized facts. Nonterminal audit outages do not prevent
+rollback; terminal completion waits for audit delivery. Adapter errors are
+sanitized before reaching Temporal history. The ordinary worker remains unchanged.
+
+Tests cover restart, lost publication and audit responses, rollback, unknown IDs,
+identity disablement and Temporal sandbox construction. The image CI test target
+includes the new suite. This is isolated implementation evidence, not authenticated
+Kubernetes proof or production activation.
+
+T02 and T03 are now wait and the workplan blocked. T02 cannot close before the
+September 28 16:06:22 Berlin observation eligibility and healthy owner evidence
+(RPF-WP-0048-T02). T03 still requires admitted identity/custody, real independent
+receipt issuers, bounded production report/schedule probes, authenticated isolated
+transport/denial/rollback proof, and deployment/registration of the observer,
+dispatcher and audit sink. Local code cannot supply those trust inputs. The new
+worker factory neither enables a schedule nor grants an identity; deployment and
+continuous health observation must be established through the existing owner lane.
+No new workplan/task, production mutation or authority expansion was introduced.