Return 410 Gone for legacy workplan-index route (replacement /workplans/index). Add tests, update transition backlog, operator deploy evidence doc, and STATE-WP-0070 progress notes.
2 KiB
2 KiB
railiance01 State Hub deploy — workstream caller migration
Date: 2026-07-09
Workplan: STATE-WP-0070 T01
Blocked: git pull on railiance01 failed with .git/FETCH_HEAD permission denied.
Why
Legacy-meter shows ~150k weekly GET /workstreams/* calls. Local migrations
(≥ b05ca2c) moved fix-consistency and activity-core to /workplans/. The
railiance01 sweep host was still at 050cbbc when checked via SSH.
Target revisions
| Repo | Minimum commit | Notes |
|---|---|---|
state-hub |
7e68f9e |
Caller migrations + identity headers + workplan-index 410 |
activity-core |
5a92923 |
/workplans resolver + progress workplan_id only |
Steps (operator on railiance01)
# 1. Fix checkout permissions if needed (example — adjust user/group)
sudo chown -R "$(whoami):$(id -gn)" ~/state-hub/.git ~/activity-core/.git
# 2. Pull both repos
cd ~/state-hub && git fetch origin main && git pull --ff-only origin main
git log -1 --oneline # expect 7e68f9e or newer
cd ~/activity-core && git fetch origin main && git pull --ff-only origin main
git log -1 --oneline # expect 5a92923 or newer
# 3. Optional: one-shot consistency sweep against workstation hub via tunnel
# (API must reach the hub — typically http://127.0.0.1:8000 through ops-bridge)
statehub fix-consistency --all --remote --api-base http://127.0.0.1:8000
# 4. Verify legacy-meter attribution (from any host with hub API access)
python ~/state-hub/scripts/capture_legacy_meter_evidence.py --days 7
# Expect component bucket state-hub.fix-consistency; declining GET /workstreams/*
Verification checklist
state-hubandactivity-coreat target commits on railiance01- Consistency sweep completes without C-00 automation errors
- Weekly legacy-meter review shows
state-hub.fix-consistency(not onlyunknown) GET /workstreams/*7-day window counts trend down week-over-week
Rollback
git checkout <previous-sha> in each repo; no schema migration involved.