Sync staged changes (2026-05-19 redo, non-breaking only)

[vaishakdinesh]

Codegen Sync: staging-next -> next

Synced 1 of 5 changed resources from staging-next as of 2026-05-19. The
other 4 are still in the same state that caused them to be deferred from the
previous sync (PR #2768).

Source: origin/staging-next @ 2f2d2b4
Base: origin/next @ ab07b8b

Local Validation (all three gates pass)

Gate	Command	Result
Type check	npx tsc --noEmit	pass
Lint	ESLINT_USE_FLAT_CONFIG=false npx eslint --ext ts,js .	pass
Breaking changes	./scripts/detect-breaking-changes origin/next	pass (exit 0)

Integrated Resources

Resource	Type	Summary
organizations	chore	update codegen output

Deferred: Breaking Changes (need spec-owner confirmation)

Unchanged from previous sync. Same method renames/removals as before.

Resource	Change
api-gateway	discovery.operations.edit() removed
cache	originCloudRegions.create -> update (POST -> PUT)
cache	originCloudRegions.bulkEdit -> bulkUpdate
cache	originCloudRegions.edit removed

Deferred: Codegen Regressions

Unchanged from previous sync. Empty resource classes on staging-next,
methods exist on next, new tests still reference them.

Resource	Root Cause
addressing	RegionalHostnames and Regions classes generated empty
billing	Usage class generated empty (no paygo method)

Shared Changes

• .stats.yml -- spec hash bump, endpoint count unchanged

Intentionally NOT touched:

• .github/workflows/* -- human-owned
• .release-please-manifest.json, CHANGELOG.md, package.json, src/version.ts -- release-please-bot owned
• src/index.ts, src/resources/index.ts, root api.md -- no diff in this sync

Tracker: command-center/.local/sync-typescript-2026-05-19.md (in devstack)