feat: regenerate source code from latest OpenAPI spec

[bwoskow-ld]

Requirements

• I have added test coverage for new or changed functionality
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

Related issues

N/A — regeneration of CLI source code from the latest OpenAPI spec, bringing in new resources and schema changes.

Describe the solution you've provided

Ran make openapi-spec-update to download the latest OpenAPI spec from https://app.launchdarkly.com/api/v2/openapi.json and regenerate cmd/resources/resource_cmds.go.

Three files changed:

• ld-openapi.json — updated spec (3559 lines changed)
• cmd/resources/resource_cmds.go — regenerated CLI resource commands (634 lines changed)
• .pre-commit-config.yaml — added cache-bust comment to force pre-commit environment rebuild for Go 1.26.0 compatibility (1 line added)

Key changes in the spec worth noting:

• AI Configs graduated from beta: ai-configs-beta → ai-configs, beta header notice removed from description
• Release policies expanded: new ProgressiveReleaseConfig, ReleasePolicyStage schemas; GuardedReleaseConfig gained metricKeys, metricGroupKeys, stages, rolloutContextKindKey, metricRegressionThreshold fields; ApplicablePolicy gained flagTagKeys
• Various description/documentation updates across endpoints (contexts, feature flags, environments, etc.)
• New and updated endpoints throughout the spec

Human review checklist:

• Confirm AI Configs beta→GA rename is intentional
• Spot-check new release policy schemas (ProgressiveReleaseConfig, ReleasePolicyStage, expanded GuardedReleaseConfig) look correct
• Verify no unintended endpoint removals in the generated CLI commands
• Decide whether the .pre-commit-config.yaml cache-bust comment should be kept or removed before merge

Describe alternatives you've considered

N/A — this is the standard code generation workflow.

Additional context

Build verified locally with make build — compiles successfully. Fixed missing trailing newline in ld-openapi.json for pre-commit end-of-file-fixer compliance.

The build CI check was initially failing due to a stale pre-commit cache (the cached golangci-lint environment was incompatible with Go 1.26.0, causing the runner to be killed with exit code 143). This was resolved by adding a comment to .pre-commit-config.yaml to invalidate the cache and force a fresh rebuild. All CI checks now pass.

Link to Devin run: https://app.devin.ai/sessions/db52e77ac4c044baa2918e5b0d8f34b0
Requested by: @bwoskow-ld

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[bwoskow-ld]

Aside - we have inconsistently called past PRs like this "features" (1, 2) or "chores" (1, 2). I chose to label this as a feature since we're technically adding new cli resources, but we should aim for consistency moving forward.