CI: 'Validate generated files are in sync' is red on main — registry.yaml and registry types are stale

[bokelley]

Not introduced by any open PR. The "Validate generated files are in sync" step of the Generated, Docs & Formatting job fails on main itself — confirmed on run 30587961761 at commit f8f24fb5 (main HEAD at the time of filing).

Any PR opened against main inherits the red check, which makes it useless as a signal and burns reviewer attention re-diagnosing it. Noticed while getting #2421 green — that PR touches no schema or codegen file and fails the same step identically.

Reproduction

npm run sync-schemas:all
npm run generate-types
npm run generate-registry-types -- --sync
git status --short

Yields:

 M schemas/registry/registry.yaml
 M src/lib/registry/types.generated.ts

1,139 insertions / 32 deletions across the two. The upstream registry has grown and the committed copies are stale; nothing else drifts.

Notably clean: ci:docs-check, ci:codegen-strict, ci:doc-links, lint:workflows, and format:check all pass, and npm run generate-types alone produces no drift. It is specifically the registry pair.

Fix

A standalone PR running the three commands above and committing only those two files. Keeping it standalone matters — folding 1,139 lines of generated churn into a feature or security PR makes the real diff unreviewable, and CLAUDE.md already tells reviewers not to read generated files, so it would land unexamined either way.

Worth checking while in there whether schema-sync.yml (the daily job that is supposed to open exactly this PR) is failing or has drifted, since that's the automation meant to prevent this.

[bokelley]

PR #2431 opened with the regenerated registry.yaml + src/lib/registry/types.generated.ts, branched from main at f8f24fb5 so the diff is purely the generator's output.

Blocks #2421, whose only two red checks are this step and the Test & Build rollup that needs it — 28 other checks pass there.

[bokelley]

Triage

Classification: Bug
Bucket(s): schema-sync (no matching label exists — gap noted)
Status: ready-to-implement

What the experts said:

• ad-tech-protocol-expert: additive/non-breaking sync; schema-sync.yml calls sync-schemas not sync-schemas:all — likely the root cause of the drift, must be patched or the problem recurs on the next schema release that touches the version-pinned caches
• code-reviewer: changeset required (TypeScript types changed per CLAUDE.md); workflow root-cause diagnosis confirmed; standalone PR is the right shape

My take: Both experts agree this is a clear non-breaking maintenance fix. The schema-sync.yml workflow patch is equally critical to the generated-file sync — landing the sync alone leaves main vulnerable to the same drift on the next upstream schema release.

Implementation scope:

• Run npm run sync-schemas:all && npm run generate-types && npm run generate-registry-types -- --sync
• Run npm run changeset (patch — TypeScript types changed per CLAUDE.md)
• Patch .github/workflows/schema-sync.yml: replace npm run sync-schemas with npm run sync-schemas:all (the two commands differ and the registry is only covered by the :all variant)
• Changed files: schemas/registry/registry.yaml, src/lib/registry/types.generated.ts, .changeset/<auto>.md, .github/workflows/schema-sync.yml
• Non-breaking: additive-only registry entries; no existing exports removed
• Required checks: npm run ci:quick, npm run ci:schema-check

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01Ttj5LH8pnZkQEdZKzD7Mwh

---

Generated by Claude Code

[bokelley]

Triage

Classification: Bug (CI drift — registry generated files stale on main)
Bucket(s): schema-sync (label absent from repo — flagged in run summary)
Status: deferred

Blocked-on: #2431 — resurfaces on merge

My take: PR #2431 carries exactly the regenerated registry.yaml + types.generated.ts the issue describes; once it merges, the Validate generated files are in sync step should clear for all PRs. The schema-sync.yml automation question raised in the issue body is worth a follow-up if #2431 reveals the daily job is broken or has drifted.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01KdCKNGfxRXCau3HhZgtXS3

---

Generated by Claude Code