{"category_id":"repository","default_severity":"error","description":"Prohibit script-language source under scripts/{test,tests,spec,specs,__tests__}, including nested roots and support files, case-insensitively. Documentation and data remain allowed. Exact-content fingerprints bind legacy baselines.","examples":[{"after":"python/release/tests/test_release.py","before":"python/scripts/tests/test_release.py","expected_severity":"error","id":"sarj-artifact-script-test-directories","language":"text","title":"Script test code belongs with its durable owner"}],"fix":"Reuse native lint, type, build, plan or smoke checks when they establish a one-off change's contract. Put distinct durable coverage in its owning package or shared policy suite. Retain legacy safety coverage through a reviewed exact-content baseline or exception. Delete tests only when their contracts are retired or retained coverage rejects the same wrong outcomes; renaming duplicates is not remediation.","kind":"rule","references":[],"rule_id":"repository/artifacts/script-test-directories","rule_version":1,"slug":"script-test-directories","source":{"path":"src/repo_standards/policy_sarj/policy.py","symbol":"repository/artifacts/script-test-directories"},"title":"Keep test code out of script test directories","topic_id":"artifacts","why":"An explicit directory policy prevents a growing parallel script-test suite. This is a placement gate, not evidence that an existing test lacks value or that a one-off change needs a new unit test."}