terradart: Skill for Claude Code

Add a beta-only curated resource

Read CONTEXT.md for vocabulary. The beta lane's coordinates live in tool/providers.yaml; its philosophy (filled at the current pin, filtered fixture, no backlog/wave lane) is in AGENTS.md's Current-phase section. Do not hand-edit files under packages/terradart_google_beta/lib/src/ or the source_beta/ fixture — regenerate both.

The beta-only catalog at the current provider pin is filled. Add a resource only when a later pin introduces a new beta-only type (issue / maintainer ask) — do not sweep overlapping GA names into this package. GA resources belong in terradart_google — check the GA schema fixture first; a resource present there is NOT beta-only.

Workflow

Task progress:

• 1. Confirm beta-only. The type must be absent from the GA fixture (packages/terradart_codegen/test/fixtures/wrap/source/schema.json) and present in the google-beta provider. If it exists in GA, stop — curate it in terradart_google instead (terradart-add-curated-resource).
• 2. Re-extract the fixture with the new type added via union — the current set comes from the fixture itself (schema.json keys are the single source of truth; no name list is maintained anywhere else):

  dart tool/extract_schema_subset.dart \
    --provider=hashicorp/google-beta --version=<provider_version.txt> \
    --resources-from=packages/terradart_codegen/test/fixtures/wrap/source_beta/schema.json \
    --resources=<new_type> \
    --out=packages/terradart_codegen/test/fixtures/wrap/source_beta
  

  Requires terraform on PATH and terraform-registry network access (no cloud credentials). If either is missing in your environment, stop and report — never hand-write schema JSON.
• 3. Write the override at packages/terradart_codegen/lib/src/codegen/wrapper_overrides/google_beta/yaml/<type>.yaml. Same axes and rules as GA overrides (Generation Policy binds you: thin overrides, human decisions only, IAM binding/policy curatedDoc authoritative-semantics rule). There is no MM enrichment on this lane (mm: false) — deriveEnums has nothing to derive; hand enums go in prelude.
• 4. Barrels manifest: if the override's outputDir introduces a new barrel, add it to barrels_google_beta.yaml with a doc: (fail-closed — wrap errors without it).
• 5. Regenerate (the --resource-provider pin is mandatory — beta shares the GA google_* type prefix):

  cd packages/terradart_codegen
  dart run bin/terradart.dart wrap \
    --provider hashicorp/google-beta \
    --source test/fixtures/wrap/source_beta \
    --output ../terradart_google_beta/lib/src \
    --overrides-root lib/src/codegen/wrapper_overrides/google_beta/yaml \
    --barrels-manifest lib/src/codegen/barrels/barrels_google_beta.yaml \
    --resource-provider google-beta
  

• 6. Cost-classify the type (policy, apply or not): gcp-cost tools (dart tool/gcp_cost_call.dart in cloud-agent sessions) → record evidence in tool/apply_cost_denylist.yaml per its header format. When unsure, leave unclassified and say so.
• 7. Example coverage: extend examples/beta_leftover_quickstart (or a focused beta example) so the factory appears in a synth, or record a reasoned tool/example_debt.yaml line. dart tool/example_synth_gates.dart reads both GA and beta catalogs — an uncovered new factory fails CI.
• 8. Ledger check: any new beta example must be listed in tool/apply_smoke_skip.yaml under the google-beta-lane section (beta apply policy is not designed; synth + terraform validate only).
• 9. Package test: extend packages/terradart_google_beta/test/synth_test.dart when the new factory has synth-visible behavior worth pinning (provider pin, sealed slots, sensitive fields).
• 10. CHANGELOG: add the factory to packages/terradart_google_beta/CHANGELOG.md under the next version heading.