chore: regenerate models from upstream schemas

[stack72]

Summary

Automated regeneration of extension models from upstream provider schemas.

Changes

• aws: 11 files changed
• gcp: 21 files changed

Schema Sources

• AWS: CloudFormation Resource Schema
• GCP: Google Discovery Documents
• Hetzner: Hetzner Cloud OpenAPI spec
• DigitalOcean: DigitalOcean OpenAPI spec

Review Notes

• Files under model/ are auto-generated — review the manifest.yaml diffs for version changes
• CalVer versioning with content-based change detection ensures versions only bump when content changes
• Publishing happens automatically when this PR is merged (via the publish workflow)

[github-actions]

Code Review

Blocking Issues

None.

Notes

This is a legitimate automated schema regeneration PR created by the regenerate-models.yml scheduled workflow. All 32 changed files are in model/ (auto-generated). The workflow runs the existing codegen pipeline (deno task generate:aws, deno task generate:gcp) against freshly fetched upstream schemas — no changes to codegen/ are expected when only the upstream schemas change. Manifest version bumps (CalVer 2026.04.10.1) and releaseNotes entries are consistent with the .ts model file changes.

[github-actions]

Code Review

Blocking Issues

None.

Assessment

All 44 changed files are exclusively under model/ — this is a legitimate automated schema-refresh regeneration. No codegen/, vault/, datastore/, or scripts/ files were touched.

Manifest hygiene verified:

• All manifests carry the # Auto-generated manifest. Re-generate with the appropriate deno task. header
• Version bumps use today's CalVer date (2026.04.11.1) consistently across all 12 changed manifests
• Release notes accurately describe what changed per service (Added vs Updated)
• New GCP aiplatform models (reasoningengines_sandboxenvironmentsnapshots.ts, reasoningengines_sandboxenvironmenttemplates.ts) are properly listed in the manifest models: array

Schema changes are upstream-driven, not hand-edits:

• AWS changes (bcmdataexports, bedrockagentcore, ecs, ses): new optional Zod fields reflecting CloudFormation schema additions
• GCP changes (aiplatform, bigquerydatatransfer, container, dataplex, dataproc, redis, run, saasservicemgmt, workstations): new fields and two entirely new resource types from Google Discovery Documents
• All upgrade entries use identity functions ((old) => old) which is correct for additive/optional field additions

No security issues, type violations, or CLAUDE.md compliance problems found.

[github-actions]

Code Review

Blocking Issues

None.

Assessment

All 44 changed files are exclusively under model/ — this is a legitimate automated schema-refresh regeneration. No codegen/, vault/, datastore/, or scripts/ files were touched.

Manifest hygiene verified:

• All manifests carry the # Auto-generated manifest. Re-generate with the appropriate deno task. header
• Version bumps use today's CalVer date (2026.04.11.1) consistently across all 12 changed manifests
• Release notes accurately describe what changed per service (Added vs Updated)
• New GCP aiplatform models (reasoningengines_sandboxenvironmentsnapshots.ts, reasoningengines_sandboxenvironmenttemplates.ts) are properly listed in the manifest models array

Schema changes are upstream-driven, not hand-edits:

• AWS changes (bcmdataexports, bedrockagentcore, ecs, ses): new optional Zod fields reflecting CloudFormation schema additions
• GCP changes (aiplatform, bigquerydatatransfer, container, dataplex, dataproc, redis, run, saasservicemgmt, workstations): new fields and two entirely new resource types from Google Discovery Documents
• All upgrade entries use identity functions which is correct for additive/optional field additions

No security issues, type violations, or CLAUDE.md compliance problems found.