{"category_id":"repository","default_severity":"warning","description":"Tracked script test/spec artifacts in operational trees are review candidates. Top-level .github/scripts test/spec artifacts also require review, including nested paths and declared packages; this does not change verifier ownership. An exact declared nonoperational native package may own conventional tests when substantive tracked lockfile or source-entrypoint evidence supports it. This package exception excludes top-level operational roots, package-local operational directories, GitHub automation, and native Terraform modules. Repository Standards owns this path boundary; semantic workflow analysis belongs in Code Standards.","examples":[{"after":"Retained distinct coverage or an equivalent existing check","before":"iac/bell/preview-contract.test.ts","expected_severity":"warning","id":"sarj-artifact-no-operational-script-tests","language":"text","title":"Operational test requiring contract review"},{"after":"Retained distinct coverage or an equivalent existing check","before":".github/scripts/deployment-steps.test.mts","expected_severity":"warning","id":"sarj-artifact-github-script-tests","language":"text","title":"GitHub script test requiring contract review"}],"fix":"Name the wrong outcome and retained check that rejects it. Keep one-off rollout rehearsals and reports outside Git. Recurring tests need a distinct regression, an owned harness, and a bounded execution cost. Remove redundant tests and invocations only after proving equivalent coverage; retain distinct behavior and safety contracts. Moving or renaming is not remediation.","kind":"rule","references":[],"rule_id":"repository/artifacts/operational-script-tests","rule_version":6,"slug":"operational-script-tests","source":{"path":"src/repo_standards/policy_sarj/policy.py","symbol":"repository/artifacts/operational-script-tests"},"title":"Review operational script tests for duplicate contracts","topic_id":"artifacts","why":"Deployment tests can repeat contracts owned by Terraform, providers, shared policy, or runtime behavior. Filenames and placement do not establish redundancy or test value; workflow contents are outside this rule's evidence."}