Templates & rulesets
What each per-repo file is, where it lands, who installs it, and — for the two ruleset JSON files — whether anything actually applies it.
Not everything here is live automation. Three of these files are read and written directly by redline init; two are copied by a human once; two are reference shapes that nothing in this codebase applies. Each page below says which.
repo-context.md →
Per-repo context template — a human copies it above the generated block in AGENTS.md.
CODEOWNERS →
Reference shape of the CODEOWNERS pattern redline init seeds — the CLI generates the real content in code, it doesn't read this file.
redline.yml →
Thin caller installed verbatim as .github/workflows/redline.yml in every onboarded GitHub repo.
pull_request_template.md →
GitHub PR template — the gated Launch readiness checklist, written whole by redline init when the repo has none, merged into an existing one otherwise.
azure/pull_request_template.md →
The same checklist, worded for Azure DevOps, written whole by redline init when the repo has none, merged into an existing one otherwise.
azure/gate-template.yml →
The Azure Pipelines gate — materially weaker than GitHub's: no dependency review, no secret scan.
redline-ruleset.json →
Reference shape only — nothing reads this file; redline init builds the equivalent ruleset at runtime.
redline-org-ruleset.json →
Reference shape for a one-time manual org-level import — not applied by any code here.