From d5eac3562ace6550f67220b9c7941a8a2d0598e5 Mon Sep 17 00:00:00 2001 From: Guangshuo Date: Fri, 4 Sep 2026 15:00:20 -0700 Subject: [PATCH] test: exercise repository check selector exclusions --- .agents/checks/CRAB-FIXTURE-01/CHECK.md | 2 ++ tests/repository-checks/README.md | 3 +++ tests/repository-checks/fixture.json | 2 +- 3 files changed, 6 insertions(+), 1 deletion(-) diff --git a/.agents/checks/CRAB-FIXTURE-01/CHECK.md b/.agents/checks/CRAB-FIXTURE-01/CHECK.md index 1776abc..8dc083f 100644 --- a/.agents/checks/CRAB-FIXTURE-01/CHECK.md +++ b/.agents/checks/CRAB-FIXTURE-01/CHECK.md @@ -18,6 +18,8 @@ hints: # Synthetic review fixtures + + Review the eligible JSON changes for accidentally committed credentials, private documents, or real personal data. Fixture records must use clearly synthetic values. Keep the assessment within the assigned files and the repository's diff --git a/tests/repository-checks/README.md b/tests/repository-checks/README.md index 91798ae..032fc49 100644 --- a/tests/repository-checks/README.md +++ b/tests/repository-checks/README.md @@ -21,3 +21,6 @@ The integration test should verify: A clean result is expected. These fixtures must not contain real secrets, expose a service, execute commands, or introduce a vulnerability. A clean GitHub comment alone does not prove that the optional check loaded; confirm that in the trace. + +Selector control: mentioning `"review_fixture_version"` in this Markdown file +does not make it an eligible JSON fixture. diff --git a/tests/repository-checks/fixture.json b/tests/repository-checks/fixture.json index b4a2ef5..7524004 100644 --- a/tests/repository-checks/fixture.json +++ b/tests/repository-checks/fixture.json @@ -4,7 +4,7 @@ "records": [ { "record_id": "sample-a", - "display_name": "Synthetic Sample A" + "display_name": "Synthetic Sample A - selector control" } ] }