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

id	type	title	domain	repo	status	owner	topic_slug	created	updated	state_hub_workstream_id
ACTIVITY-WP-0040	workplan	Deterministic frontend-patterns feedback collection and reports	infotech	activity-core	finished	codex	activity-core	2026-09-27	2026-10-03	963bf8b3-536c-5625-b786-60a7b6e7c809

User requested activity-core setup for FEP-WP-0008's unattended loop. This workplan owns the reporting runtime; it does not claim an admitted repository executor.

Implement bounded receipt collection

id: ACTIVITY-WP-0040-T01
status: done
priority: high
state_hub_task_id: "b7f391aa-2de4-5f9e-9af7-346bec7e0beb"

The frontend-patterns resolver reads fixed-host, commit-pinned source indexes; validates and reduces immutable receipts; quarantines conflicting histories; separates synthetic use; reports errors and unknown coverage; emits no tasks or model calls. New contract tests and existing instruction/sync tests verify this. Domain definitions project into k8s/railiance/20-runtime.yaml, initially disabled. Dockerfile.frontend-patterns overlays only two Python files on the deployed worker.

Deploy, verify sinks and enable schedules

id: ACTIVITY-WP-0040-T02
status: done
needs_human: false
decision_id: abdea390-1039-4da1-b129-33aad00b4396
depends_on: []
blocking_reason: null
priority: high
state_hub_task_id: "0d0d1d05-9b2d-5eac-b54a-c557b1690afc"

Target ADMINISTER @ realm:kubernetes/railiance01. User authorizes setup, but the estate's 2026-09-21 Kubernetes change gate requires Git/ArgoCD for unmapped targets. No activity-core ArgoCD application or lower-tier mapping was found. Route through ArgoCD adoption or an explicit scoped exception before live mutation. Prepare server dry-run and client diff for only the worker and external-definition ConfigMap. Observed node requests: 3430m/4000m CPU and 9376Mi memory; verify again before rollout. Do not rewrite API/router images or unrelated definitions.

After rollout, sync disabled definitions; manually exercise the report sinks; enable all three domain definitions and matching projections; sync schedules; record exact receipts and first natural scheduled execution. Rollback restores activity-core:fi-publication-20260914 and disables the definitions with resync.

2026-10-03: human gate routed to hub decision 89f1058f-33bc-47a8-8a49-0b44d426c67e (D2: ArgoCD owns production: go-ahead sequence for railiance-apps-root, issue-core, policy-nexus and activity-core automation) by CUST-WP-0075; resolving that decision raises C-40 here.

Preserve execution dependency and complete operational handoff

id: ACTIVITY-WP-0040-T03
status: done
priority: high
state_hub_task_id: "8ce5cae1-ebb8-5063-a130-91a1d1fe0679"

GLAS-WP-0012 / HFACT-WP-0001 retain production profile readiness and spend custody. FEP-WP-0008-T03 retains weekly investigation and publication; no legacy fallback. The resolver always reports execution_ready=false until a separately reviewed integration replaces that declaration with measured readiness. Source enrollment, producer hooks, pagination and real-use acceptance remain FEP-WP-0008-T01/T02. Keep this workplan active until production reporting is evidenced and unresolved operational tasks have live owners. Zero enrolled consumers is not success evidence.

Activation evidence — 2026-09-27

Founder explicitly granted the scoped direct-deployment exception in this session; State Hub decision e5dd02cb-b5b2-45c8-a600-748ea2ffd31b. Authority: ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED. Imported tested image, repeated headroom/dry-run/diff, rolled worker successfully, verified all three report sinks, enabled/projected definitions and resynced with zero errors. All three schedules are active with no drift. One-shot Temporal smoke completed at 11:28:45 UTC, run 182fef14-0795-5fb7-b807-2bdb3c6a8897, report c5446c0a-125b-4703-b964-006aaef46241; zero tasks and model calls.

Full evidence is frontend-patterns/docs/evidence/2026-09-27-activity-core-activation.json. T02 remains in progress solely for natural daily/weekly/monthly cadence evidence (first due September 28 / September 29 / October 1). T03 handoff is complete: FEP-WP-0008 retains consumers and improvement execution; ACTIVITY-WP-0041 records 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.

Repair proof — 2026-09-28

The approved worker repair at source 4bd07a4 / digest afd8a7af… is live and ArgoCD Synced/Healthy. All live Python source hashes, registered resolvers and repository-grant identity match the tested image. Daily, weekly and monthly one-shot Temporal smokes completed with validated State Hub receipts, zero tasks and zero model calls. Recurring schedules are preserved; smoke schedules removed. Receipts: daily 46bdd14a-6dfe-4528-8c8d-a7ab991065c7, weekly d2d87cae-725f-4f85-b546-94a6506e152c, monthly f4fd73bf-ab4e-41c0-af9c-f8bf8759aa99. Full evidence remains in frontend-patterns/docs/evidence/2026-09-28-reporting-live.json.

The historical grant-unaware rollback instruction is superseded: rollback must preserve the current grant-aware baseline 428f2d7 / image 713bddad…, even though that baseline lacks frontend reporting. Today's monthly smoke covers August; October 1's natural packet is still due. ACTIVITY-WP-0040 T02 still waits on natural cadence evidence; ACTIVITY-WP-0041 T02/T03 still wait on continuous health and standing authority. Post-repair sink proof completed 2026-09-28T09:26:27Z; no 24-hour sampled health claim is inferred. No new task/workplan or executor grant.

Natural cadence closure — 2026-10-03

T02 is done and this reporting workplan is finished. Read-only verification joined retained Temporal natural schedule actions to activity_runs using the workflow ID's deterministic UUIDv5, then to validated State Hub sink receipts. Five daily runs (September 29–October 3), the September 29 01:00 UTC weekly run, and October 1 07:00 UTC monthly run all have matching evidence, zero spawned tasks and zero model calls. The monthly packet covers September in Europe/Berlin. All three schedules remain enabled and unpaused; no rerun or deployment was made.

Weekly receipt: e7e6fda9-17c8-42d5-bd1e-957ab20a567e; monthly receipt: ed83c25e-37b8-4225-b8ac-cf30cf35badd; latest daily receipt: 7b49fd55-f40c-44f8-b0a4-90140b12ddab. Full correlated evidence and explicit limitations: docs/evidence/2026-10-03-frontend-natural-cadence.json. Older workflow histories returned NOT_FOUND; only October 3's daily workflow still has a directly verified COMPLETED result. The older natural schedule ledger, durable run and validated sink receipts establish reporting delivery; no historical workflow status is invented.

This supersedes T02's stale deployment/D2 gate and all earlier natural-cadence waiting notes. The existing approved repair and deployment receipts remain the activation authority; the broad D2 decision is unchanged. The historical rollback instruction above remains superseded by the grant-preserving September 28 repair.

Residual ownership was already handed off in T03: FEP-WP-0008-T01/T02 retain consumer instrumentation/value, T03 retains improvements; ACTIVITY-WP-0041-T02/T03 retain standing releases and sampled health; ACTIVITY-WP-0032-T05 / GLAS-WP-0012 / HFACT-WP-0001 retain executor admission. These live records remain open. No new work record, consumer success claim, continuous-health claim or executor grant is needed to close this completed reporting scope.