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

[cursor]

Description

Adds regression tests for recently merged production paths that lacked coverage:

• tests/prompts/feature-flag-rollout.test.ts — dual-mode scope validation for the FME rollout prompt (feat: [FME-17249]: FME dual-mode Harness-native scope migration #806): rejects missing/partial scope, verifies legacy workspace_id vs Harness-native org_id/project_id interpolation, and surfaces the NYI caveat for native mode.
• tests/registry/governance.test.ts — extends multi-scope coverage beyond list to get/create/update/delete for policy and policy_set at account/org/project scope (feat: allow account and org scope for OPA policies and policy sets #819).
• tests/registry/infrastructure.test.ts — deep-link fallbacks when environmentRef is nested or only available via query param (feat: [AIPLAT-1334]: Point infrastructure openInHarness at environment Infrastructure section #809).

Risky behavior now covered

1. Agents invoking the rollout prompt without valid scope get a clear error instead of generating broken MCP call instructions.
2. Account/org scoped OPA policy CRUD no longer relies solely on list-path tests — write paths are pinned.
3. Infrastructure openInHarness links stay correct when API responses omit top-level environmentRef.

Validation

pnpm test tests/prompts/feature-flag-rollout.test.ts tests/registry/governance.test.ts tests/registry/infrastructure.test.ts
# 78 tests passed

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other — test coverage

Checklist

• pnpm test passes (targeted files)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes
• pnpm docs:check passes

  

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