Repair router frontdoor route boundaries and service prefixes

This commit is contained in:
master
2026-03-10 12:28:48 +02:00
parent 6f808c3b3d
commit 1b6051662f
9 changed files with 223 additions and 5 deletions

View File

@@ -133,6 +133,12 @@ First-party Stella APIs are expected to flow through router transport; reverse p
external/bootstrap surfaces that cannot participate in router registration yet (for example OIDC browser
flows, Rekor, and static/platform bootstrap assets).
The local route table also carries a small set of explicit precedence rules that must stay ahead of the
generic `^/api/v1/{service}` matcher. Platform-owned surfaces such as `/api/v1/aoc/*` and
`/api/v1/administration/*` resolve directly to `platform`, and browser compatibility prefixes such as
`/doctor/*` and `/scheduler/*` strip the frontdoor prefix before dispatch so the target services still
receive their canonical `/api/v1/doctor/*` and `/api/v1/scheduler/*` paths.
```bash
# Default frontdoor route table
ROUTER_GATEWAY_CONFIG=./router-gateway-local.json \