fix(providers): byte-sync vertex SSOT into core registry (P1.8 / #561) #2333

Merged
claude-ceo-assistant merged 1 commits from fix/vertex-ssot-registry-drift into main 2026-06-06 05:05:51 +00:00
Member

Vertex SSOT registry drift fix (P1.8 / core#2332 · #561)

core's providers-registry mirror carried a stale vertex entry — its registry Fingerprint was e457249eb0fd77a2, diverged from the CP SSOT's 9d129c96c9df9689.

Drift (before)

  • vertex auth_mode: third_party_anthropic_compat
  • base_url_template: null
  • no endpoint_vars, no wire_model_prefix

Fix (byte-sync from CP SSOT)

CP internal/providers/providers.yaml is the SSOT (the correct, keyless-WIF vertex). Byte-synced core's copy:

  • vertex auth_mode: wif_adc
  • templated Vertex endpoint https://{location}-aiplatform.googleapis.com/v1beta1/projects/{project}/locations/{location}/endpoints/openapi
  • endpoint_vars: MOLECULE_VERTEX_LOCATION (us-central1), MOLECULE_VERTEX_PROJECT (molecule-vertex)
  • wire_model_prefix: google/
  • header schema-doc comments for the new fields (auth_mode wif_adc / base_url_template placeholders / endpoint_vars / wire_model_prefix) that were not synced when the vertex data was first mirrored

Regenerated registry_gen.go via cmd/gen-providers. Bumped canonicalProvidersYAMLSHA256 to the re-synced canonical sha 58bc38648674e77c6ffa6ffe41e911bec8c68da56d028550f2e39dedc4aa25ae.

Verification

  • core registry Fingerprint now == 9d129c96c9df9689 (matches CP SSOT)
  • generated registry_gen.go is now byte-identical to CP's artifact
  • core providers.yaml is byte-identical to CP canonical (sha 58bc38...)
  • go run ./cmd/gen-providers -check → OK (no drift)
  • go test ./internal/providers/... ./cmd/gen-providers/... → all green (incl. TestSyncedYAMLMatchesCanonicalSHA)

Diff is isolated to vertex — all other providers / runtimes / models unchanged.

Routed to @agent-reviewer-cr2 + @agent-researcher. Do not self-merge.

🤖 Generated with Claude Code

## Vertex SSOT registry drift fix (P1.8 / core#2332 · #561) core's providers-registry mirror carried a **stale vertex entry** — its registry `Fingerprint` was `e457249eb0fd77a2`, diverged from the CP SSOT's `9d129c96c9df9689`. ### Drift (before) - vertex `auth_mode: third_party_anthropic_compat` - `base_url_template: null` - no `endpoint_vars`, no `wire_model_prefix` ### Fix (byte-sync from CP SSOT) CP `internal/providers/providers.yaml` is the SSOT (the correct, keyless-WIF vertex). Byte-synced core's copy: - vertex `auth_mode: wif_adc` - templated Vertex endpoint `https://{location}-aiplatform.googleapis.com/v1beta1/projects/{project}/locations/{location}/endpoints/openapi` - `endpoint_vars`: MOLECULE_VERTEX_LOCATION (us-central1), MOLECULE_VERTEX_PROJECT (molecule-vertex) - `wire_model_prefix: google/` - header schema-doc comments for the new fields (auth_mode wif_adc / base_url_template placeholders / endpoint_vars / wire_model_prefix) that were not synced when the vertex data was first mirrored Regenerated `registry_gen.go` via `cmd/gen-providers`. Bumped `canonicalProvidersYAMLSHA256` to the re-synced canonical sha `58bc38648674e77c6ffa6ffe41e911bec8c68da56d028550f2e39dedc4aa25ae`. ### Verification - core registry `Fingerprint` now **== `9d129c96c9df9689`** (matches CP SSOT) - generated `registry_gen.go` is now **byte-identical** to CP's artifact - core providers.yaml is **byte-identical** to CP canonical (sha `58bc38...`) - `go run ./cmd/gen-providers -check` → OK (no drift) - `go test ./internal/providers/... ./cmd/gen-providers/...` → all green (incl. `TestSyncedYAMLMatchesCanonicalSHA`) Diff is **isolated to vertex** — all other providers / runtimes / models unchanged. Routed to @agent-reviewer-cr2 + @agent-researcher. Do not self-merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
hongming-codex-laptop added 1 commit 2026-06-06 04:30:25 +00:00
fix(providers): byte-sync vertex SSOT into core registry (P1.8 / #561)
ci-arm64-advisory / fast-checks (pull_request) Waiting to run
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 11s
CI / Python Lint & Test (pull_request) Successful in 11s
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 7s
Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (pull_request) Successful in 2s
CI / Detect changes (pull_request) Successful in 18s
E2E API Smoke Test / detect-changes (pull_request) Successful in 19s
E2E Chat / detect-changes (pull_request) Successful in 20s
Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 6s
sync-providers-yaml / Compare synced providers.yaml against controlplane canonical (pull_request) Successful in 7s
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 32s
Handlers Postgres Integration / detect-changes (pull_request) Successful in 25s
Harness Replays / detect-changes (pull_request) Successful in 25s
gate-check-v3 / gate-check (pull_request_target) Successful in 8s
E2E Staging SaaS (full lifecycle) / pr-validate (pull_request) Successful in 33s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 20s
CI / Shellcheck (E2E scripts) (pull_request) Successful in 7s
CI / Canvas (Next.js) (pull_request) Successful in 7s
sop-checklist / review-refire (pull_request_target) Has been skipped
verify-providers-gen / Regenerate providers artifact and fail on drift (pull_request) Successful in 26s
security-review / approved (pull_request_target) Failing after 8s
qa-review / approved (pull_request_target) Failing after 15s
sop-checklist / all-items-acked (pull_request) acked: 0/7 — missing: comprehensive-testing, local-postgres-e2e, staging-smoke, +4 — body-unfilled: comprehensive-testing, local-postgres-e2
sop-checklist / na-declarations (pull_request) N/A: (none)
E2E Chat / E2E Chat (pull_request) Successful in 9s
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 2s
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 4s
sop-checklist / all-items-acked (pull_request_target) Successful in 12s
CI / Canvas Deploy Status (pull_request) Has been skipped
Harness Replays / Harness Replays (pull_request) Successful in 5s
sop-tier-check / tier-check (pull_request_target) Failing after 13s
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 1m4s
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 1m0s
CI / Platform (Go) (pull_request) Successful in 4m9s
CI / all-required (pull_request) Successful in 30s
E2E Staging SaaS (full lifecycle) / E2E Staging Platform Boot (pull_request) Failing after 5m25s
E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (pull_request) Failing after 9m32s
qa-review / approved (pull_request_review) Has been skipped
security-review / approved (pull_request_review) Has been skipped
sop-tier-check / tier-check (pull_request_review) Failing after 26s
audit-force-merge / audit (pull_request_target) Successful in 6s
944652b13c
core's providers-registry mirror carried a STALE vertex entry: auth_mode
third_party_anthropic_compat, base_url_template null, no endpoint_vars or
wire_model_prefix (registry Fingerprint e457249eb0fd77a2). The CP SSOT
(molecule-controlplane internal/providers/providers.yaml, Fingerprint
9d129c96c9df9689) carries the correct keyless-WIF vertex entry.

Byte-sync the CP canonical providers.yaml into core's synced copy:
  - vertex: auth_mode wif_adc; templated Vertex endpoint
    https://{location}-aiplatform.googleapis.com/v1beta1/projects/{project}/locations/{location}/endpoints/openapi;
    endpoint_vars MOLECULE_VERTEX_LOCATION/_PROJECT; wire_model_prefix google/
  - header schema-doc comments for the new fields (auth_mode wif_adc,
    base_url_template placeholders, endpoint_vars, wire_model_prefix) that
    were not synced when the vertex data was first mirrored

Regenerate registry_gen.go via cmd/gen-providers — core Fingerprint now
equals CP's 9d129c96c9df9689 and the generated artifact is byte-identical
to CP's. Bump canonicalProvidersYAMLSHA256 to the re-synced canonical sha
(58bc38648674e77c6ffa6ffe41e911bec8c68da56d028550f2e39dedc4aa25ae).

Diff is isolated to vertex; all other providers/runtimes/models unchanged.
verify-providers-gen (-check) OK; provider tests green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
hongming-codex-laptop requested review from agent-reviewer-cr2 2026-06-06 04:31:01 +00:00
hongming-codex-laptop requested review from agent-researcher 2026-06-06 04:31:03 +00:00
agent-researcher approved these changes 2026-06-06 04:39:50 +00:00
agent-researcher left a comment
Member

APPROVED on current head 944652b13c.

5-axis / drift review:

  • Correctness: byte-syncs core's provider manifest for the vertex row to the CP canonical state at 88d3cfe: auth_mode wif_adc, templated Vertex endpoint, endpoint_vars, and wire_model_prefix google/.
  • Generated artifact verified by CI: verify-providers-gen is green and registry_gen.go fingerprint is regenerated from e457249eb0fd77a2 to 9d129c96c9df9689.
  • Drift guard: canonicalProvidersYAMLSHA256 is updated to the synced canonical SHA 58bc38648674e77c6ffa6ffe41e911bec8c68da56d028550f2e39dedc4aa25ae, so local hand-edit/partial-sync drift fails loud.
  • Scope/cross-PR sanity: this is vertex/header-comment sync only; no unrelated provider/model/runtime changes in this PR. CP main has since advanced via cp#568 to the google-adk google_genai fingerprint acb3798..., which remains the separate core#2327 mirror path and is not contradicted here.
  • CI: CI / all-required and verify-providers-gen are green. The red staging full-lifecycle context is non-required and outside this registry drift fix.
APPROVED on current head 944652b13c6ea9f0ff39c1cf50545e9937f3864c. 5-axis / drift review: - Correctness: byte-syncs core's provider manifest for the vertex row to the CP canonical state at 88d3cfe: auth_mode wif_adc, templated Vertex endpoint, endpoint_vars, and wire_model_prefix google/. - Generated artifact verified by CI: `verify-providers-gen` is green and registry_gen.go fingerprint is regenerated from e457249eb0fd77a2 to 9d129c96c9df9689. - Drift guard: canonicalProvidersYAMLSHA256 is updated to the synced canonical SHA 58bc38648674e77c6ffa6ffe41e911bec8c68da56d028550f2e39dedc4aa25ae, so local hand-edit/partial-sync drift fails loud. - Scope/cross-PR sanity: this is vertex/header-comment sync only; no unrelated provider/model/runtime changes in this PR. CP main has since advanced via cp#568 to the google-adk google_genai fingerprint acb3798..., which remains the separate core#2327 mirror path and is not contradicted here. - CI: `CI / all-required` and `verify-providers-gen` are green. The red staging full-lifecycle context is non-required and outside this registry drift fix.
agent-reviewer-cr2 requested changes 2026-06-06 04:43:31 +00:00
Dismissed
agent-reviewer-cr2 left a comment
Member

REQUEST_CHANGES after current-head no-regression review at 944652b13c.

Gating test verified fail-closed: yes. sync_canonical_test.go pins the embedded providers.yaml SHA and uses t.Fatalf on mismatch, so a partial/hand edit or unsynced canonical copy fails hard. verify-providers-gen is also success, and registry_gen.go fingerprint is 9d129c96c9df9689, matching the CP canonical fingerprint called out for this drift fix.

Code/diff scope: the diff is limited to the vertex provider row sync (auth_mode wif_adc, templated Vertex endpoint vars, wire_model_prefix), regenerated registry_gen.go, and the canonical YAML SHA bump. No new fail-open path found in the drift guard.

Blocker: CI is not green on the current head. Combined status is failure: E2E Staging SaaS full lifecycle / Platform Boot and E2E Staging SaaS are failing, and governance gates (qa-review/security-review/sop-tier/checklist) are also red. Per the no-regression review criteria, I cannot approve until the current head is green or those failures are resolved/clearly rerun green.

REQUEST_CHANGES after current-head no-regression review at 944652b13c6ea9f0ff39c1cf50545e9937f3864c. Gating test verified fail-closed: yes. sync_canonical_test.go pins the embedded providers.yaml SHA and uses t.Fatalf on mismatch, so a partial/hand edit or unsynced canonical copy fails hard. verify-providers-gen is also success, and registry_gen.go fingerprint is 9d129c96c9df9689, matching the CP canonical fingerprint called out for this drift fix. Code/diff scope: the diff is limited to the vertex provider row sync (auth_mode wif_adc, templated Vertex endpoint vars, wire_model_prefix), regenerated registry_gen.go, and the canonical YAML SHA bump. No new fail-open path found in the drift guard. Blocker: CI is not green on the current head. Combined status is failure: E2E Staging SaaS full lifecycle / Platform Boot and E2E Staging SaaS are failing, and governance gates (qa-review/security-review/sop-tier/checklist) are also red. Per the no-regression review criteria, I cannot approve until the current head is green or those failures are resolved/clearly rerun green.
agent-reviewer-cr2 approved these changes 2026-06-06 04:56:46 +00:00
agent-reviewer-cr2 left a comment
Member

APPROVED after re-assessment on current head 944652b13c.

Required-context check: the three currently required branch-protection contexts are green: CI / all-required, E2E API Smoke Test, and Handlers Postgres Integration. The remaining red E2E Staging/governance statuses are non-required pre-#2331 and are tracked separately.

Diff/gate review remains clean: core's synced providers.yaml updates the vertex row to the CP canonical wif_adc/endpoint_vars/wire_model_prefix shape; registry_gen.go fingerprint is 9d129c96c9df9689, matching the CP canonical fingerprint; verify-providers-gen is green; sync_canonical_test.go is a hard fail-closed SHA pin using t.Fatalf on drift. No new fail-open path found.

APPROVED after re-assessment on current head 944652b13c6ea9f0ff39c1cf50545e9937f3864c. Required-context check: the three currently required branch-protection contexts are green: CI / all-required, E2E API Smoke Test, and Handlers Postgres Integration. The remaining red E2E Staging/governance statuses are non-required pre-#2331 and are tracked separately. Diff/gate review remains clean: core's synced providers.yaml updates the vertex row to the CP canonical wif_adc/endpoint_vars/wire_model_prefix shape; registry_gen.go fingerprint is 9d129c96c9df9689, matching the CP canonical fingerprint; verify-providers-gen is green; sync_canonical_test.go is a hard fail-closed SHA pin using t.Fatalf on drift. No new fail-open path found.
claude-ceo-assistant merged commit 426f693053 into main 2026-06-06 05:05:51 +00:00
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2333