test: cover schema sync, PR scopeOptional dispatch, and infra deep links

[cursor]

Description

Adds regression tests for recently merged behavior flagged by the test-coverage automation run on PR #813 (auto-sync harness schemas).

Risky behavior now covered

1. Auto-synced v1 schema bundle — locks in upstream schema changes from harness-schema:

   • ai-eval step template alias on UnifiedTemplate
   • Stage-level inputs (replacing removed variables) on UnifiedStageNodeV1
   • Change Advisor advisory gating fields (user-groups, service-accounts, approvers-min-count, block-executor)

2. Pull request scopeOptional dispatch — prevents 404s for account-scoped Code repos:

   • Omits config-default orgIdentifier/projectIdentifier when caller does not pass org_id/project_id
   • Forwards explicit org/project when provided
   • Documents scope guidance on all PR-related resource descriptions

3. Infrastructure deep links (feat: [AIPLAT-1334]: Point infrastructure openInHarness at environment Infrastructure section #809) — openInHarness resolves {environmentIdentifier} from query params when the API response omits environmentRef

Test files added/updated

• tests/schemas/schema-bundle-contract.test.ts
• tests/registry/pull-requests.test.ts
• tests/registry/infrastructure.test.ts

Why these tests materially reduce regression risk

• Schema sync PRs are high-churn generated data; contract tests catch accidental removal of new upstream fields during the next sync.
• PR scope mis-injection was a user-reported failure mode (fix: document org/project scope for pull request resources #724); dispatch tests prove config defaults are not leaked to account-scoped repos.
• Infrastructure deep links are user-facing navigation; the get-path fallback test guards the registry params → deep-link bridge added in feat: [AIPLAT-1334]: Point infrastructure openInHarness at environment Infrastructure section #809.

Type of Change

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

Checklist

• pnpm test passes (targeted: schema-bundle-contract, pull-requests, infrastructure)
• 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 all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ thisrohangupta
❌ cursoragent
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[thisrohangupta]

Closing in impact triage: the schema source changes are already on main; this dirty automated branch is a mixed regression snapshot with no remaining production fix.