sync(providers): mirror cp serving-url fixes (kimi-coding /v1 + gemini api-key base_url) #2103
Reference in New Issue
Block a user
Delete Branch "sync/providers-serving-urls"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sync providers SSOT mirror: kimi-coding /v1 + gemini api-key base_url
Byte-syncs
workspace-server/internal/providers/providers.yamlto the controlplane canonical after cp#432, and repinscanonicalProvidersYAMLSHA256.Upstream changes (controlplane SSOT):
/v1— washttps://api.kimi.com/coding/; proxy dials{base}/messages→/coding/messages→ 404. Correct endpoint/coding/v1/messages(verified live: 200 pong). Real proxy-serving bug, found by the new controlplane serving-e2e gate (cp#431).https://generativelanguage.googleapis.com/v1beta/openaiso the OpenAI-protocol api-key arm can serve.Comprehensive testing performed
go test ./internal/providers/...(+ gen) green on the mirror;sync-providers-yamlbyte-match +verify-providers-gensatisfied (registry_gen unchanged — base_url is not in the model-id projection; only providers.yaml + the pinned sha change).Local-postgres E2E run
N/A — providers.yaml data-only mirror sync; no DB/schema path touched.
Staging-smoke verified or pending
Pending: serving verification runs in the controlplane serving-e2e gate (cp#431) once provider keys are activated; kimi
/v1already proven live (200).Root-cause not symptom
Roots: kimi-coding base_url omitted the
/v1segment the gateway requires; the gemini entry had no OpenAI-compat base_url. Both fixed at the SSOT, not worked around downstream.Five-Axis review walked
Correctness (kimi proven live; gemini = documented OpenAI-compat surface), Safety (data-only mirror; no code), Tests (providers green; gate covers serving), SSOT (byte-identical to cp canonical; sha repinned), No backwards-compat shim / dead code.
No backwards-compat shim / dead code added
Confirmed — only the byte-synced manifest + the pinned sha constant change.
Memory/saved-feedback consulted
Followed the providers-SSOT model-add/sync runbook (byte-sync + sha repin + dockerized gen-providers; operator has no go) and the comprehensive-e2e-for-LLM principle that motivated the serving gate.
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack root-cause
/sop-ack five-axis-review
/sop-ack no-backwards-compat
/sop-ack memory-consulted
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack root-cause
/sop-ack five-axis-review
/sop-ack no-backwards-compat
/sop-ack memory-consulted
Providers mirror sync; kimi /v1 proven live, serving-e2e gate covers it. APPROVED.
Data-only providers mirror; no code/secret surface. APPROVED.
/qa-recheck
/security-recheck
Already merged to main. Confirmed as part of CTO staging-dead disposition (#2031-#2103 batch).