test: cover release-management dispatch, rollout prompt, and IaCM provider guards

[cursor]

Description

Adds regression tests for recently merged high-risk paths that lacked dispatch-level or prompt-level coverage.

Risky behavior now covered

• Release Management (feat: [RM-1328]: Add Release Management toolset to default registry #840) — registry.dispatch for release list, release_process create, and release_execution_phase list: RMG gateway base URL, header-based scoping (no accountIdentifier leak), and scope-in-body POST semantics
• RMG path builders — requireReleaseAndPhase guards reject missing release_id, phase_identifier, and activity_identifier before malformed URLs are built
• RMG extractors — releaseStatus field alias, raw array payloads, empty scopes body, default activity sort, task limit clamping, Spring pagination metadata
• FME rollout prompt (feat: [FME-17249]: FME dual-mode Harness-native scope migration #806/feat: wire native FME traffic type and rollout status lists #838) — scope validation, native vs legacy scope interpolation, and native-mode fme_rollout_status caveat
• IaCM provider (feat: add IaCM provider registry create and version update #811) — create/update preflight rejects missing type, id, and version before API calls

Test files added/updated

• tests/prompts/feature-flag-rollout.test.ts (new)
• tests/registry/toolsets/release-management.test.ts
• tests/registry/iacm.test.ts

Why these tests materially reduce regression risk

Release Management is default-on with header-scoped routing and body-carried scope — metadata-only tests missed dispatch wiring bugs that would silently hit the wrong gateway or leak scope params. The rollout prompt drives multi-step FME agent workflows; without tests, dual-mode scope migration could ship broken guidance. IaCM provider version writes are medium-risk infra mutations where missing-field errors must fail before network calls.

Small production fix

Append nativeModeCaveat to the feature-flag-rollout prompt text — the variable was defined in #806 but never included in the rendered message.

Type of Change

• Bug fix (prompt caveat append)
• New feature
• Refactor
• Documentation
• Other (test coverage)

Checklist

• Targeted tests pass (144 tests across 3 files)
• pnpm test passes
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes
• pnpm docs:check passes (no registry/tool count changes)

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}