generated from coulomb/repo-seed
feat(STATE-WP-0064): add consistency sweep remote-all API endpoint
Expose POST /consistency/sweep/remote-all so activity-core can trigger the workstation ADR-001 remote-all sweep via the bridge tunnel pattern. Records consistency_sweep_remote_all progress events and documents the cutover runbook while the local custodian-sync timer remains interim.
This commit is contained in:
@@ -25,8 +25,13 @@ alongside the per-repo git post-commit hooks).
|
||||
> **Interim local runner (STATE-WP-0063):** units must target the standalone
|
||||
> repo at `/home/worsch/state-hub` and invoke consistency via
|
||||
> `/home/worsch/.local/bin/uv run python …`. The pre-extraction path
|
||||
> `/home/worsch/the-custodian/state-hub` is obsolete. Scheduling moves to
|
||||
> Railiance01 activity-core in `STATE-WP-0064`.
|
||||
> `/home/worsch/the-custodian/state-hub` is obsolete.
|
||||
>
|
||||
> **Cluster runner (STATE-WP-0064):** activity-core on Railiance01 can
|
||||
> trigger the same sweep through `POST /consistency/sweep/remote-all` via
|
||||
> the `consistency_sweep_remote_all` context query. Keep this local timer
|
||||
> enabled during the parallel week; disable it after cutover per
|
||||
> [`docs/consistency-sweep-runbook.md`](../docs/consistency-sweep-runbook.md).
|
||||
|
||||
The all-repo remote sweep has two built-in load guards:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user