terradart: Skill for Claude Code

Ship a TerraDart Wave

Read CONTEXT.md for vocabulary. Generation policy is in AGENTS.md. For each new google_* factory, follow terradart-add-curated-resource first; this skill covers the release boundary around a Wave.

The GA catalog is filled: Waves now originate from new resources the weekly schema bump appends to tool/curation_backlog.yaml, and catalog counts move as increments on the completed baseline. No scheduled agent ships them: the maintainer runs this skill (or asks a cloud agent to) for named backlog entries, and removes each shipped entry from the backlog in the same PR.

A backlog entry whose note: says the schema bump generated its factory already has a default override (from wrap-init, or the lane scaffold on aws / cloudflare) and a published factory: skip wrap-init, polish the override (paramOrder, sealed slots, curatedDoc), and replace its ClassName: awaiting-example: line in tool/example_debt.yaml with an example (or a reasoned entry). Once a release has published the factory, an API change to it is breaking and needs a MIGRATING.md entry.

PR scope

Ship one Wave per PR when possible. Do not bundle:

• unrelated example pubspec.yaml / workspace version-debt sweeps
• release version bumps for a different Wave
• agent-guide-only edits with factory work

If example debt must land with a Wave, limit changes to the quickstart that exercises the new factories. See PR granularity in AGENTS.md.

Wave complete definition

A Wave PR is not done when wrappers and curatedDoc land alone. It is done when:

1. Curated factories — overrides linted, terradart wrap regenerated, API diff reviewed. The migration manifest (packages/terradart_migrate/lib/src/manifest/google.g.dart) regenerates in the same full wrap --migrate-manifest run — wrap --only skips it, and the wrap_check lane fails while it is stale.
2. Runnable example — new examples/<name>_quickstart or extend an existing example so every new/breaking factory appears in synth output. Machine-checked by dart tool/example_synth_gates.dart (synth tfType coverage, API-enablement deps, terraform validate on every quickstart); a factory may instead get a reasoned tool/example_debt.yaml entry, but that is an explicit reviewed decision. For pre-existing debt backfill, see terradart-backfill-examples. IAM binding/policy preference: for new *IamBinding / *IamPolicy when the sibling *IamMember is already curated and already in synth, prefer tool/example_debt.yaml with reason token iam-adjunct-debt: over extending examples solely for coverage. The synth gate enforces the token. If applying the quickstart needs an organization, an entitlement or real external inputs, bills while it exists, or leaves behind something that cannot be deleted (or a name that stays reserved), it must be a gated example (README ## Before you apply section — AGENTS.md Example verification); apply-ability is never a reason for an example_debt.yaml entry. Never terraform apply from an agent session.
3. Breaking changes — MIGRATING.md entry and example updated to the new API.
4. Counts & docs — tool/doc_expectations.dart, catalog_count_test.dart, wrap_command_test.dart, README / package catalog count phrases (do not rebuild a per-factory dump in ## What ships — detail lives on Coverage), agent/website catalog phrases, example pubspec.yaml carets.
5. CI matrix — nothing to wire: the terraform_validate matrix derives from examples/ automatically (tool/select_changed_examples.dart).
6. Verify — terradart-agent-verify (tool/agent_verify.sh).