#3936 budget type has no Budget argument, so it cannot create a budget

The @swamp/aws/budgets/budget type has no Budget global argument, so it cannot create a budget. AWS::Budgets::Budget lists Budget (a BudgetData object: BudgetType, TimeUnit, BudgetLimit, and so on) as its only required property. The type exposes only NotificationsWithSubscribers and ResourceTags, and the generated source defines no BudgetData schema at all.

Steps to reproduce

In a fresh repo with @swamp/aws/budgets 2026.10.24.1 pulled (budget type version 2026.10.23.1):

swamp behavior create @swamp/aws/budgets/budget monthly \
  --global-arg 'Budget={"BudgetType":"COST","TimeUnit":"MONTHLY","BudgetLimit":{"Amount":20,"Unit":"USD"}}'

Output:

Error: Unknown global argument(s) for type '@swamp/aws/budgets/budget': Budget. Valid arguments are: name, accessKeyId, secretAccessKey, sessionToken, region, NotificationsWithSubscribers, ResourceTags

Leaving Budget out, the definition validates (7/7), but there is then no way to give the budget amount, type or period, which Cloud Control requires to create the resource.

Expected

The type accepts a Budget argument matching the BudgetData definition in the AWS::Budgets::Budget schema (aws cloudformation describe-type --type RESOURCE --type-name AWS::Budgets::Budget), and create can make a budget.

Notes

• Checked against the current main of swamp-club/swamp-extensions (model/aws/budgets/extensions/models/budget.ts, version 2026.10.23.1): GlobalArgsSchema has no Budget field. Also present in 2026.10.14.1.
• The file is auto-generated (deno task generate:aws). The update method passes ["BudgetName", "NotificationsWithSubscribers"] as its property names, but no schema in the file defines BudgetName, which lives inside BudgetData. That suggests the generator read the nested BudgetData definition but dropped the top-level Budget property that wraps it. Possibly because the property has the same name as the resource; unconfirmed.
• The sibling budgets-action type is not affected.
• Earlier, a local copy of the type with a Budget field added validated and created a real budget through Cloud Control. BudgetLimit.Amount had to be a number, not a string.

Suggested fix

Have the AWS generator emit the top-level Budget property, and its BudgetData sub-schemas, for AWS::Budgets::Budget, then regenerate the type. If the cause is the property-named-like-the-resource case, other generated types with the same pattern may be missing a property too, so a generator-level check would be worth adding: every property in the CloudFormation schema's required list appears in the generated arguments.

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

• Extension: @swamp/aws/budgets@2026.10.24.1
• swamp: 20261025.171252.0-sha.b6a26393
• OS: darwin (aarch64)
• Deno: 2.9.8
• Shell: /bin/zsh