activity-core/workplans/ACTIVITY-WP-0040-frontend-patterns-feedback.md
tegwick f7e26111f7
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Container Image / build-and-push (push) Successful in 50s
Add bounded frontend-patterns feedback reporting resolver
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3
2026-09-27 13:05:05 +02:00

2.6 KiB

id type title domain repo status owner topic_slug created updated
ACTIVITY-WP-0040 workplan Deterministic frontend-patterns feedback collection and reports infotech activity-core active codex activity-core 2026-09-27 2026-09-27

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

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: wait
priority: high

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.

Preserve execution dependency and complete operational handoff

id: ACTIVITY-WP-0040-T03
status: todo
priority: high

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.