SCRUM-245 — Jenkins jobs and doc updates¶
Plan ref: OPS-6 (docs/11-admin-plane-plan.md).
What exists¶
| Piece | Notes |
|---|---|
docs/10-communication-schema.md, docs/11-admin-plane-plan.md |
added to the repo (they were untracked files in one checkout). Doc 10 now reflects staging: §8 is the real admin-auth service (login, refresh, logout, me, onboarding, JWKS, /api/admin/users*); §2 gateway_dev's users route, viewer gate, pack upload and rate limits; §6 Patch's manifest and GET /patch/v1/blob/{sha256}; §4 Config's 17 routes; §7 Dashboard routes as they are on staging; each "gap" marked closed (with its ticket) or open. Work still in review is marked "(SCRUM-n, in review)" rather than described |
| "PHP Admin Auth" → admin-auth | docs 00, 01, 02, 05, 06, 08, 09, m1; 16 remaining "PHP" mentions are deliberate history ("originally planned in PHP") or library names |
services/patch/README.md |
"what exists" brought up to date (manifest, reload, blob route were listed as missing) |
Jenkins jobs: otomo-admin_auth, otomo-patch and otomo-dashboard already exist
on the CI host. otomo-adminui and otomo-gateway_dev, which the dispatcher also
targets, do not; creating them is a change on the shared Jenkins and is waiting for the
team's go-ahead. Note that since FIX-201 Jenkins is CI for staging and does not
deploy; the ticket's "push to main deploys" criterion predates that change.
How to verify¶
Spot-checked 8 routes documented in doc 10 against the route tables (all present).How it was built¶
DeepSeek run scoped (Landlock) to docs (301 s, ~54k output tokens, reasoning
effort low). Claude review: spot-checked routes, fixed the stale Patch README the run
reported. Doc 06 §13.1 is also edited by SCRUM-208 (#50); expect a small merge
conflict there, to be resolved in favour of #50's MFA rows.