test: cover FME rollout prompt, governance CRUD scopes, infra deep links

[cursor]

Description

Adds regression tests for recently merged high-risk paths that only had partial or no test coverage:

• FME dual-mode scope migration (feat: [FME-17249]: FME dual-mode Harness-native scope migration #806): feature-flag-rollout prompt validates dual-mode scope (workspaceId vs orgId+projectId) and surfaces the Harness-native NYI caveat for steps that still require legacy workspace_id.
• OPA policy multi-scope (feat: allow account and org scope for OPA policies and policy sets #819): policy and policy_set get/create/update/delete now assert resource_scope account/org/project query-param injection — matching existing list tests so CRUD cannot drift from list behavior.
• Infrastructure deep links (feat: [AIPLAT-1334]: Point infrastructure openInHarness at environment Infrastructure section #809): openInHarness falls back to environment_id when the API omits environmentRef, and aliases nested infrastructure.environmentRef on list items.

Type of Change

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

Checklist

• pnpm test passes (targeted: 78 tests in 3 files)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes
• pnpm docs:check passes

Risky behavior now covered

Area	Regression risk
FME rollout prompt scope validation	Agents could invoke rollout workflow without valid scope or miss NYI steps in Harness-native mode
Governance CRUD scope injection	Account/org policies could leak project scope on get/create/update/delete
Infrastructure deep links	Broken openInHarness URLs when API shape varies (nested envRef, missing top-level envRef)

Test files added/updated

• tests/prompts/feature-flag-rollout.test.ts (new)
• tests/registry/governance.test.ts (+90 lines)
• tests/registry/infrastructure.test.ts (+46 lines)

  

[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.}

[thisrohangupta]

Closing as superseded by newer follow-ups #842 and #845, which cover the same FME rollout, governance CRUD, and infrastructure paths against current main.