coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(edge): retry+degrade side-effect POSTs; finish ACTIVITY-WP-0027
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 33s
Details

Browse source 
Consistency sweep and recently-on-scope retry transient 502/503/504 then
return a degraded context snapshot instead of thrashing Temporal.
Document edge-relay resilience. Retire Binky dual-clock host timers after
claim-loop smoke.
This commit is contained in:
tegwick 2026-08-05 17:53:00 +02:00
parent 2b3fc6a556
commit 4e605a6839
6 changed files with 334 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/ACTIVITY-WP-0027-llm-connect-and-run-artifacts.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Hardened llm-connect access + run→artifact links in ops UI"
domain: infotech
repo: activity-core
status: active
status: finished
owner: grok
topic_slug: activity-core
priority: high
@ -276,7 +276,7 @@ links in ops UI without hand-editing DB rows.
```task
id: ACTIVITY-WP-0027-T06
status: todo
status: done
priority: medium
state_hub_task_id: "52f1db5e-23db-4dcd-aaba-71c11deaf09a"
```
@ -296,7 +296,7 @@ fixed or explicitly accepted with a follow-up id.
```task
id: ACTIVITY-WP-0027-T07
status: todo
status: done
priority: low
state_hub_task_id: "245955d4-83bd-4145-b71e-2e6449754e31"
```
@ -336,7 +336,7 @@ Depends on T02 + T04 (minimum).
- [x] rein-aharness on railiance01 does not depend on ad-hoc `kubectl port-forward` for llm-connect
- [x] `https://activity.coulomb.social/ops/ui` shows clickable artefact links for recent FI/Binky successes (API verified; SSO UI serves same payload)
- [x] Contract tests cover join + URL builder; no secrets in responses
- [ ] Remaining caveats (edge 503, Binky timers) either fixed or explicitly deferred with owner
- [x] Remaining caveats (edge 503, Binky timers) either fixed or explicitly deferred with owner
## References
@ -371,3 +371,15 @@ Port-forward deprecated for claim-loop production.
### Remaining
- T06 edge-relay soft-fail for required resolvers
- T07 Binky dual-clock timer retirement after clean claim days
### T06 (2026-08-05)
- `_post_json` retries 502/503/504 + network errors (default 3×)
- Side-effect POSTs degrade after retries (`STATE_HUB_SIDE_EFFECT_DEGRADE=true`)
- Doc: `docs/edge-relay-resilience.md` + runbook pointer
- Tests: degrade + retry success paths
### T07 (2026-08-05)
- Binky claim smoke: ops_run `eeccd98a-…` succeeded via claim loop (manual trigger)
- Prior scheduled claim success: Aug 4 `13fcbed2-…`
- Disabled user timers: `binky-rhythm-daily`, `binky-rhythm-mail`, `binky-rhythm-review`
(units remain on disk for break-glass)