Allow TestFigSpec snapshot updates without ext-registry core review

[Copilot]

Summary

Simple extension registry PRs often need a companion TestFigSpec.ts snapshot update when registry-backed commands change. The core-review gate treated that file as out-of-scope and blocked the PR.

The problem

ext-registry-check only allowed edits to registry.json / registry.dev.json on the no-core-review path. Any other changed file failed with:

PR changes files outside the extension registries (...), which requires core review:
cli/azd/cmd/testdata/TestFigSpec.ts

Change

• Allowlist cli/azd/cmd/testdata/TestFigSpec.ts as a companion non-registry path in diffChangedFiles
• Keep requiring core review for any other non-registry file
• Cover both paths in unit tests

Behavior at a glance

PR files	Core review required?
Registry only (simple bump)	No
Registry + TestFigSpec.ts	No (new)
Registry + TestFigSpec.ts + anything else	Yes

[azure-pipelines]

Azure Pipelines:
20 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
22 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟡 Not ready to approve

The allowlist also exempts snapshot deletions and renames from core review.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Allows generated FigSpec snapshots to accompany simple extension registry updates without core review.

Changes:

• Allowlist TestFigSpec.ts.
• Add positive and negative policy tests.

File summaries

File	Description
.github/scripts/src/ext-registry-check.js	Adds the snapshot-path exception.
.github/scripts/test/ext-registry-check.test.js	Tests allowed and disallowed companion changes.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Balanced

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[github-actions]

🔗 Linked Issue Required

Thanks for the contribution! Please link a GitHub issue to this PR by adding Fixes #123 to the description or using the sidebar.
No issue yet? Feel free to create one!

[Copilot]

🟡 Not ready to approve

Dev-registry-only PRs can bypass review without triggering snapshot validation.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Balanced

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[Copilot]

🟢 Ready to approve

The implementation matches the stated behavior and covers the relevant edge cases.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Balanced

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[JeffreyCA]

/check-enforcer override