docs: record repo-manager as consistency sweep engine
ACTIVITY-WP-0029 keeps the 15-minute schedule in activity-core and treats State Hub as the dual-run adapter until REPO_MANAGER_URL is set.
This commit is contained in:
parent
5331f9af68
commit
1e2199ddc7
1 changed files with 16 additions and 22 deletions
|
|
@ -27,14 +27,13 @@ context_sources:
|
|||
|
||||
## Purpose
|
||||
|
||||
This definition is the activity-core handoff point for
|
||||
`STATE-WP-0064 - Move State Hub consistency sync to Railiance01`.
|
||||
This definition is the activity-core handoff point for the 15-minute
|
||||
ADR-001 reconciliation sweep (STATE-WP-0064, ACTIVITY-WP-0029).
|
||||
|
||||
It schedules the 15-minute ADR-001 reconciliation sweep across all
|
||||
registered repos with local paths on the workstation State Hub host.
|
||||
State Hub owns `scripts/consistency_check.py`, lock semantics, and the
|
||||
`consistency_sweep_remote_all` progress event; activity-core owns the
|
||||
cron schedule and ActivityRun audit trail.
|
||||
activity-core owns the cron schedule and ActivityRun audit trail.
|
||||
**repo-manager** owns the C-rule engine. State Hub
|
||||
`POST /consistency/sweep/remote-all` is the dual-run adapter until
|
||||
`REPO_MANAGER_URL` / `CONSISTENCY_SWEEP_URL` points at repo-manager.
|
||||
|
||||
## Runner Status
|
||||
|
||||
|
|
@ -59,24 +58,19 @@ is skipped rather than replayed as a burst after the host returns.
|
|||
|
||||
## Deterministic State Hub Invocation
|
||||
|
||||
The `consistency_sweep_remote_all` State Hub context resolver issues:
|
||||
The `consistency_sweep_remote_all` resolver issues:
|
||||
|
||||
- `POST /consistency/sweep/remote-all`
|
||||
- payload: `{"max_seconds": 300}`
|
||||
- `POST {sweep_base}/consistency/sweep/remote-all`
|
||||
- payload: `{"max_seconds": 300, "source": "activity-core"}`
|
||||
|
||||
The context source is marked `required: true`. A failed State Hub call
|
||||
fails the activity-core workflow visibly instead of silently binding an
|
||||
empty context. On success, the response is stored in the ActivityRun
|
||||
`context_snapshot` under `consistency_sweep_remote_all`.
|
||||
`sweep_base` is `CONSISTENCY_SWEEP_URL` or `REPO_MANAGER_URL` or
|
||||
`STATE_HUB_URL` (default dual-run adapter). The context source is
|
||||
`required: true`. A failed call fails the workflow visibly. On success,
|
||||
the ActivityRun snapshot includes `engine_owner`, `adapter`, and
|
||||
`sweep_url`.
|
||||
|
||||
State Hub runs `consistency_check.py --remote --all --json` on the
|
||||
workstation host and records a compact progress event with event type
|
||||
`consistency_sweep_remote_all`, including processed repos and skip
|
||||
metadata.
|
||||
|
||||
`STATE_HUB_URL` must point at the workstation State Hub through the
|
||||
ops-bridge tunnel service (for example `actcore-state-hub-bridge`), not
|
||||
at a cluster-local checkout path.
|
||||
`STATE_HUB_URL` (adapter default) must point at the workstation State Hub
|
||||
through the ops-bridge tunnel, not a cluster-local checkout path.
|
||||
|
||||
## Output Contract
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue