generated from coulomb/repo-seed
fix(STATE-WP-0064): parse consistency sweep stdout with skip prefixes
Extract the JSON payload from mixed script output and document Railiance01 kubectl sync steps. Mark T02 done after cluster bridge and resolver canaries.
This commit is contained in:
@@ -92,7 +92,7 @@ Done 2026-06-21:
|
||||
|
||||
```task
|
||||
id: STATE-WP-0064-T02
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "2e9b5b66-a7b1-46a5-8e1f-22e6b5caeff6"
|
||||
```
|
||||
@@ -104,6 +104,18 @@ Trigger one manual ActivityRun. Confirm:
|
||||
- progress or activity-core run history shows success
|
||||
- no duplicate side-effects when local timer also fires (idempotent)
|
||||
|
||||
Done 2026-06-21:
|
||||
|
||||
- Applied `20-runtime.yaml` on Railiance01; `actcore-sync` upserted definition
|
||||
`7c4e9a12-8f3b-4d5e-9c6a-1b2d3e4f5a6b` (paused schedule).
|
||||
- Rebuilt/imported `activity-core:railiance01-prod` with
|
||||
`consistency_sweep_remote_all` resolver.
|
||||
- Bridge proxy POST timeout raised to 360s (30s was aborting sweeps).
|
||||
- Manual canaries: cluster POST via bridge (`exit_code 0`, progress event
|
||||
`65d0bc12-…`) and worker resolver (`exit_code 0`, 1 repo @ 60s budget).
|
||||
- Laptop `make sync-activity-definitions` is not valid against Railiance01 DB;
|
||||
use kubectl `actcore-sync` job instead.
|
||||
|
||||
## T3 — Parallel run and observability
|
||||
|
||||
```task
|
||||
|
||||
Reference in New Issue
Block a user