Accept Deploy-owned route registry provenance metadata #82

New issue

Closed

opened 2026-08-05 04:31:56 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-05 04:31:56 +00:00

Owner

Blocks coilyco-bridge/deploy#316.

Observed live failure

Deploy PR coilyco-bridge/deploy#318 merged as 9b35feee5b44997fd9298f960ee5d23634dcdd59.
Deploy CI run 3886 and Agent Proxy image publish run 3887 succeeded for that commit.
The guarded ser8 rollout applied Agent Proxy image a44c1999e2174b8d3a52cc06cee1d00d2dd2ffa8 and the new route registry.
Both LiteLLM and direct gateway modes entered CrashLoopBackOff during startup.
The loader rejected the registry source object because evaluation_routes_sha256 and service_routes_sha256 are unsupported fields.
The automatic direct-mode rollback could not recover because it retained the same incompatible route ConfigMap.
Ops restored Deploy revision d89d39700e06c2486dfb9b61d1db5669bc4693d4 with previously deployed image c7daaeea9cb3531dc2a68f2a795facc29e58cb51 in direct mode. Kubernetes rollout, /healthz, and non-empty model discovery passed.
The Sirens Echo SSM parameter was not changed.

Ownership

Agent Proxy owns the strict route-registry loader. Deploy owns the generated runtime registry. The two schemas must agree before the current Deploy registry can roll out.

Acceptance

The owning Agent Proxy loader accepts the tracked deploy.agent-proxy-routes/v1 source object, including its service and evaluation input digests, while continuing to reject genuinely unknown fields.
The loader's own fixtures cover this source shape.
Agent Proxy publishes a new immutable image after its repository validation passes.
The current Deploy main registry is validated through the owning loader or schema surface instead of a second parser.
A guarded ser8 rollout reaches Ready and exposes sirens-echo/default through model discovery.
Deploy issue 316 remains the operator-owned SSM cutover and Sirens Echo inference/readiness verification.

Blocks https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/316. ## Observed live failure * Deploy PR https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/318 merged as `9b35feee5b44997fd9298f960ee5d23634dcdd59`. * Deploy CI run 3886 and Agent Proxy image publish run 3887 succeeded for that commit. * The guarded ser8 rollout applied Agent Proxy image `a44c1999e2174b8d3a52cc06cee1d00d2dd2ffa8` and the new route registry. * Both LiteLLM and direct gateway modes entered `CrashLoopBackOff` during startup. * The loader rejected the registry source object because `evaluation_routes_sha256` and `service_routes_sha256` are unsupported fields. * The automatic direct-mode rollback could not recover because it retained the same incompatible route ConfigMap. * Ops restored Deploy revision `d89d39700e06c2486dfb9b61d1db5669bc4693d4` with previously deployed image `c7daaeea9cb3531dc2a68f2a795facc29e58cb51` in direct mode. Kubernetes rollout, `/healthz`, and non-empty model discovery passed. * The Sirens Echo SSM parameter was not changed. ## Ownership Agent Proxy owns the strict route-registry loader. Deploy owns the generated runtime registry. The two schemas must agree before the current Deploy registry can roll out. ## Acceptance * The owning Agent Proxy loader accepts the tracked `deploy.agent-proxy-routes/v1` source object, including its service and evaluation input digests, while continuing to reject genuinely unknown fields. * The loader's own fixtures cover this source shape. * Agent Proxy publishes a new immutable image after its repository validation passes. * The current Deploy `main` registry is validated through the owning loader or schema surface instead of a second parser. * A guarded ser8 rollout reaches Ready and exposes `sirens-echo/default` through model discovery. * Deploy issue 316 remains the operator-owned SSM cutover and Sirens Echo inference/readiness verification.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-05 04:31:57 +00:00

coilyco-ops referenced this issue from a commit

2026-08-05 04:42:25 +00:00

fix(routes): accept Deploy registry provenance