coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Prepare approved reporting repair and monthly review inputs

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e738-9e15-7600-87e6-90dec3a7beef
This commit is contained in:
tegwick 2026-09-28 11:22:19 +02:00
parent 9baf6f1829
commit a18d83f74a
16 changed files with 663 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

36
docs/ActivityCoreLoop.md
View file

@ -1,5 +1,10 @@
# Activity-core receipt loop
Current diagnosis (2026-09-28): the first natural daily run fired but failed because
the replacement worker image lacks the domain resolver. A tested repair image is
published and awaits the scoped attended-release exception; prior smoke success
is historical. See [repair evidence](evidence/2026-09-28-reporting-repair.json).
FEP-WP-0008 owns this integration. The initial delivery is deterministic collection
and reporting. Automatic investigation and publication are a separate, outstanding
execution dependency; a weekly report is not evidence of an improvement cycle.
@ -134,3 +139,34 @@ September 27 14:07Z smoke receipt. See [recheck](evidence/2026-09-28-loop-rechec
Enabled schedules and prior smoke success do not prove this recurring execution.
WP-0008 T03 retains cadence/sink diagnosis; no outage cause or live fix is claimed.
The roster remains empty and mutation execution remains unadmitted.
## Diagnosed failure and prepared repair — 2026-09-28
Temporal fired the daily definition at 00:00Z. Worker run
`01a0e54f-c690-7caa-bae6-81cd5ed32416` failed with required context source
`frontend-patterns` not registered. Source `428f2d7` changed the worker from the
frontend overlay to the grant-aware API image; the running image has neither the
resolver module nor its registration. ArgoCD and pod readiness were healthy, so
those probes did not establish domain functionality.
[Diagnosis](evidence/2026-09-28-reporting-diagnosis.json),
[schedule readback](evidence/2026-09-28-reporting-schedules.json), and
[repair contract](../integrations/activity-core/README.md) pin the evidence.
The prepared overlay keeps the current grant-aware base and changes only the
domain resolver and its registration. Hash comparison preserves all other Python
source and the grant identity. The candidate also adds monthly owner-snapshot
health, decisions and measured research effort with unknown counts; it never grants
execution authority. Missing review inputs degrade the report visibly.
58 focused tests and 17 GitOps tests pass. Server dry-run passes for the same nine
resources; the actual resource diff is only the worker image. The published digest
is `afd8a7af73132becba432e7b315d70f88d66676020169d5d8811641304136437`.
The October 1 built-image fixture is 1,699 characters and contains no consumers,
unknown eligible-task denominator and unknown cost observations. This is fixture
proof, not an actual October run. Production promotion remains separately gated.
Hosted discovery is still unregistered (404) and its routed write credential is
unavailable to the current operator session. Public source publication passed.
The [consumer hook](../feedback/ConsumerIntegration.md) is prepared, but no real
consumer was fabricated or enrolled. These obligations remain WP-0008 T01/T02.