test: cover Code file scope forwarding and recent schema sync contracts

[cursor]

Description

Adds regression tests for recently merged production changes that shipped without dedicated test coverage.

Risky behavior now covered

1. Code file scope forwarding (Forward Code scope for file content APIs #602) — file_content get and blame must forward orgIdentifier/projectIdentifier query params so project-scoped Harness Code repos resolve correctly in QA/prod.
2. Schema sync contracts (chore: auto-sync harness schemas #584) — v0 pipeline/template bundles must retain DeployAwsAgentCoreRevision step definitions and IdentitiesConfig/IdentitySpec common types after auto-sync.
3. Schema sync contracts (chore: auto-sync harness schemas #567) — v1 pipeline/template bundles must retain DynamicStageNodeV1 for dynamic child-pipeline stages.
4. harness_schema path resolution — agents querying bare definition names (DeployAwsAgentCoreRevisionStepNode, IdentitiesConfig, DynamicStageNodeV1) must resolve nested bundled schemas.

Test files added/updated

• Added: tests/registry/repositories-file-scope.test.ts
• Updated: tests/schemas/schema-bundle-contract.test.ts
• Updated: tests/tools/harness-schema-tool.test.ts

Why these tests materially reduce regression risk

• Forward Code scope for file content APIs #602 was a production-only bug fix with no tests; removing the queryParams mapping would silently break scoped file reads/blame again.
• Auto-sync schema PRs can drop upstream step/common definitions; contract tests fail CI before agents lose schema discovery for new CD steps and v1 dynamic stages.
• harness_schema nested lookup tests catch path-resolution regressions that would block pipeline authoring workflows.

Type of Change

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

Checklist

• Targeted pnpm exec vitest run passes (45 tests across 3 files)
• pnpm test passes
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes
• pnpm docs:check passes (not applicable — 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.}