From 219f1c9087deb7e00bfc02b62fe6ef588f964846 Mon Sep 17 00:00:00 2001
From: fullsend-code
 <278716306+fullsend-ai-coder[bot]@users.noreply.github.com>
Date: Wed, 15 Jul 2026 09:33:13 +0000
Subject: [PATCH] docs(#1776): add collection change pattern to AGENTS.md

Add a row to the Common Change Patterns table documenting
testing expectations for new collection definitions. The new
entry clarifies that collections are metadata-only definition
files that do not require new tests themselves, since the CLI
repo tests collection filtering and make conventions-check
validates dependency-collection superset constraints. Rules
introduced alongside a collection still need _test.rego
coverage.

Closes #1776
---
 AGENTS.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/AGENTS.md b/AGENTS.md
index 39a2c4081..0b7e52664 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -63,7 +63,7 @@ These files have `effective_on` dates — rules with future dates are warnings,
 - **Add a pipeline policy rule:** follow the pattern in `policy/pipeline/required_tasks.rego`
 - **Add a shared library function:** see `policy/lib/tekton/` for reference implementation (must have test coverage)
 - **Fetch and parse an OCI blob:** use `oci.parsed_blob(ref)` from `data.lib.oci`, not `json.unmarshal(ec.oci.blob(ref))` directly. A Regal lint rule (`prefer-parsed-blob`) enforces this
-- **Add a new collection:** follow the pattern in `policy/release/collection/` — import specific policy packages
+- **Add a new collection:** follow the pattern in `policy/release/collection/` — metadata-only definition file; no new tests needed for the collection itself since the CLI repo tests collection filtering and `make conventions-check` validates dependency-collection superset constraints. If new rules are added alongside the collection, those rules need `_test.rego` coverage as usual
 
 ## PR Conventions