carson 2.13.1 → 2.13.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d7fde15079ed380bb8c6e4d476fb8157dd7980ea6a250e06706188a645c1d160
-  data.tar.gz: 85a76cdb10a52573ba463a884079178e2b69befe21b8b377bb425f620057bd65
+  metadata.gz: 17b8bd4f2f9f3b9d1cc1d637accc607cfb3f7a49e98cc4a998cb8b797a82bc50
+  data.tar.gz: 3247d5bac41cbd0da539a45210521c66436b2ee3d2da8b6e28ee8f6a6c694955
 SHA512:
-  metadata.gz: 910cfd8d4ee3095b3ea559ba66bcd372d764043d02131f38d2d75071542aa04e1ea7cf5bdf10ab1aabd792f8ff21762ea31063720c23c719cc361d4313ea38fd
-  data.tar.gz: 236417f25de6aba2640a3ec992c5f756851b931f961f213408f57533533403f20d011cf4169cb8384ed980d58100456e49ea9209ed08fc2bb87a2d9729fcd9e4
+  metadata.gz: e018a857a0af89a3828355f0af131b4bf3fee40412d6c1e719c20493f9c6daf91f2da595d9b0b611f0df787a25e6d65997456668160615ca4b9c6419ffb89ee7
+  data.tar.gz: f7db01059c1dfb0b8be6be61c34859c157ac7283df40f010120f57bcdc1ad95b3bbdaf2a6596329be260be1dfcb818d2b177ded70e92d637294441fe70bc0f69

data/.github/copilot-instructions.md

@@ -1 +1 @@
-Read `.github/carson-instructions.md` for repository governance rules enforced by Carson.
+Read `.github/AGENTS.md` for repository governance rules enforced by Carson.

data/API.md

@@ -73,7 +73,7 @@ Blocked Carson artefacts in host repositories:
 - `.tools/carson/*`
 
 Allowed Carson-managed persistence in host repositories:
-- `.github/carson-instructions.md` — governance baseline (source of truth)
+- `.github/carson.md` — governance baseline (source of truth)
 - `.github/copilot-instructions.md` — agent discovery pointer for Copilot
 - `.github/CLAUDE.md` — agent discovery pointer for Claude Code
 - `.github/AGENTS.md` — agent discovery pointer for Codex
@@ -99,6 +99,39 @@ Environment overrides:
 - `CARSON_WORKFLOW_STYLE`
 - `CARSON_RUBY_INDENTATION`
 - `CARSON_LINT_POLICY_SOURCE`
+- `CARSON_GOVERN_REPOS`
+- `CARSON_GOVERN_MERGE_AUTHORITY`
+- `CARSON_GOVERN_MERGE_METHOD`
+- `CARSON_GOVERN_AGENT_PROVIDER`
+- `CARSON_GOVERN_CHECK_WAIT`
+
+`govern` schema:
+
+```json
+{
+  "govern": {
+    "repos": ["~/Dev/project-a", "~/Dev/project-b"],
+    "agent": {
+      "provider": "auto",
+      "codex": {},
+      "claude": {}
+    },
+    "check_wait": 30,
+    "merge": {
+      "authority": false,
+      "method": "squash"
+    }
+  }
+}
+```
+
+`govern` semantics:
+- `repos`: list of local repo paths to govern (empty = current repo only).
+- `agent.provider`: `"auto"`, `"codex"`, or `"claude"`.
+- `agent.codex` / `agent.claude`: provider-specific options (reserved).
+- `check_wait`: seconds to wait for CI checks before classifying (default: `30`).
+- `merge.authority`: `false` (default) — Carson does not merge until explicitly enabled.
+- `merge.method`: `"squash"` (default), `"merge"`, or `"rebase"`.
 
 `lint` schema:
 

data/MANUAL.md

@@ -8,7 +8,7 @@ For the mental model and command overview, see `README.md`. For formal interface
 Prerequisites: Ruby `>= 3.4`, `gem` and `git` in `PATH`. `gh` (GitHub CLI) recommended for full review governance.
 
 ```bash
-gem install --user-install carson
+gem install carson
 ```
 
 If `carson` is not found after installation:
@@ -202,7 +202,7 @@ These define what Carson *is*. They are not configurable.
 - **Outsider boundary** — Carson never places its own artefacts inside a governed repository.
 - **Centralised lint** — one policy source distributed into each repo's `.github/linters/`, zero per-repo drift. MegaLinter enforces it in CI.
 - **Active review** — undisposed reviewer findings block merge; feedback must be acknowledged.
-- **Self-diagnosing output** — every message names the cause and the fix.
+- **Self-diagnosing output** — every warning and error names what went wrong, why, and what to do next.
 - **Transparent governance** — Carson prepares everything for merge but never makes decisions without telling you.
 
 ### Configurable defaults
@@ -299,10 +299,9 @@ Carson writes managed files that help interactive agents (Claude Code, Codex, Co
 
 **How it works:**
 
-- `.github/carson-instructions.md` — the single source of truth containing the full governance baseline. This file tells agents what Carson is, what commands to run, and what rules to follow.
-- `.github/CLAUDE.md` — read by Claude Code at session start. Points to `carson-instructions.md`.
-- `.github/AGENTS.md` — read by Codex at session start. Points to `carson-instructions.md`.
-- `.github/copilot-instructions.md` — read by GitHub Copilot. Points to `carson-instructions.md`.
+- `.github/AGENTS.md` — full governance baseline; read by Codex and other agents. Points to `carson.md`.
+- `.github/CLAUDE.md` — read by Claude Code at session start. Points to `AGENTS.md`.
+- `.github/copilot-instructions.md` — read by GitHub Copilot. Points to `AGENTS.md`.
 
 Each agent reads its own expected filename and follows the reference to the shared baseline. One file to maintain, zero drift across agents.
 

data/README.md

@@ -2,11 +2,15 @@
 
 # ⧓ Carson
 
+*Carson at your service.*
+
 Named after the head of household in Downton Abbey, Carson is your repositories' autonomous governance runtime — you write the code, Carson manages everything else. From commit-time checks through PR triage, agent dispatch, merge, and cleanup, Carson runs the household with discipline and professional standards. Carson itself has no intelligence — it follows a deterministic decision tree. The intelligence comes from the coding agents it dispatches (Codex, Claude) to fix problems.
 
-## The Problem
+## The Problem to Solve
+
+Managing a growing portfolio of repositories is rewarding work — but the operational overhead scales faster than the code itself. Lint configs drift between repos, PR templates go stale, reviewer feedback gets quietly buried, and what passes on a developer's laptop fails in CI. When coding agents start producing PRs across multiple projects, the coordination load multiplies: checking results, dispatching fixes, clicking merge, cleaning up branches.
 
-If you govern more than a handful of repositories, you know the pattern: lint configs drift between repos, PR templates go stale, reviewer feedback gets quietly ignored, and what passes on a developer's laptop fails in CI. Across a portfolio of projects with coding agents producing many PRs, you become the bottleneck — manually checking results, dispatching fixes, clicking merge, and cleaning up.
+Carson exists so you can focus on what matters — building — while governance runs itself.
 
 ## How Carson Works
 
@@ -14,27 +18,14 @@ Carson is an autonomous governance runtime that lives on your workstation and in
 
 **Per-commit governance** — Carson gates merges on unresolved review comments, synchronises templates, and keeps your local branches clean. Every commit triggers `carson audit` through managed hooks; the same checks run in GitHub Actions. Lint execution is handled entirely by MegaLinter in CI and by the developer's own local tooling — Carson distributes the shared lint configuration but does not run linters itself.
 
-**Portfolio-level autonomy** — `carson govern` is a scheduled triage loop that scans all your repositories, classifies every open PR, and acts: merge what's ready, dispatch coding agents (Codex or Claude) to fix what's failing, and escalate what needs human judgement. One command, all your projects, unmanned.
+**Portfolio-level autonomy** — `carson govern` is a triage loop that scans your registered repositories, classifies every open PR, and acts: merge what's ready, dispatch coding agents (Codex or Claude) to fix what's failing, and escalate what needs human judgement. One command, all your projects, unmanned.
 
 ```
-┌──────────────────────────────────────────────┐
-│  Your workstation                             │
-│                                               │
-│  ~/.carson/            Carson config          │
-│  ~/.carson/hooks/      Git hooks              │
-│  ~/.carson/cache/      Reports                │
-│  ~/.carson/govern/     Dispatch state         │
-│                                               │
-│  carson govern ──► for each repo:             │
-│    1. List open PRs (gh)                      │
-│    2. Classify: CI / review / audit status    │
-│    3. Act: merge | dispatch agent | escalate  │
-│    4. Housekeep: sync + prune                 │
-│                                               │
-│  Governed repos:  repo-A/  repo-B/  repo-C/   │
-│    .github/* templates (committed)            │
-│    core.hooksPath → ~/.carson/hooks           │
-└──────────────────────────────────────────────┘
+  ~/.carson/                     ← Carson lives here, never inside your repos
+       │
+       ├─ hooks ──────────────►  commit gates      (every governed repo)
+       ├─ lint configs ───────►  .github/linters/  (MegaLinter auto-discovers)
+       └─ govern ─────────────►  PR triage → merge | dispatch agent | escalate
 ```
 
 This separation is Carson's defining trait — the **outsider boundary**: no Carson scripts, config files, or governance payloads are ever placed inside a governed repository.
@@ -56,80 +47,17 @@ Carson is opinionated about governance. These are non-negotiable principles, not
 - **Outsider boundary** — Carson lives outside your repo, never inside. No Carson-owned artefacts in your repository. Offboarding leaves no trace.
 - **Centralised lint** — lint policy distributed from a central source into each repo's `.github/linters/`. One source of truth, zero drift. MegaLinter enforces it in CI.
 - **Active review** — undisposed reviewer findings block merge. Feedback must be acknowledged, not buried.
-- **Self-diagnosing output** — every message names the cause and the fix. If you need to debug Carson's output, the output failed.
+- **Self-diagnosing output** — every warning and error names what went wrong, why, and what to do next. If you have to read source code to understand a message, that message is a bug.
 - **Transparent governance** — Carson prepares everything for merge but never oversteps. It does not make decisions for you without telling you.
 
-Everything else — workflow style, merge method, remote name, main branch — is a configurable default chosen during `carson setup`. See `MANUAL.md` for the full list of defaults and why each was chosen.
-
-The data flow:
-
-1. You maintain a **policy source** — a directory or git repository containing your lint config files (e.g. `.rubocop.yml`, `biome.json`, `ruff.toml`). `carson lint policy --source <repo>` copies these into each governed repo's `.github/linters/`, where MegaLinter auto-discovers them.
-2. `carson onboard` installs git hooks, synchronises `.github/*` templates (including a MegaLinter CI workflow), and runs a first governance audit on a host repository.
-3. From that point, every commit triggers `carson audit` through the managed `pre-commit` hook. The same `carson audit` runs in GitHub Actions. If it passes locally, it passes in CI.
-4. `carson review gate` enforces review accountability: it blocks merge until every actionable reviewer comment has been formally acknowledged by the PR author through a **disposition comment**.
-5. `carson govern` triages all open PRs across your portfolio. Ready PRs are merged and housekept. Failing PRs get a coding agent dispatched to fix them. Stuck PRs are escalated for your attention.
-
-## Commands at a Glance
-
-**Govern** — autonomous portfolio management:
-
-| Command | What it does |
-|---|---|
-| `carson govern` | Triage all open PRs: merge ready ones, dispatch agents for failures, escalate the rest. |
-| `carson govern --dry-run` | Show what Carson would do without taking action. |
-| `carson govern --loop SECONDS` | Run the govern cycle continuously, sleeping SECONDS between cycles. |
-| `carson housekeep` | Sync main + prune stale branches (also runs automatically after govern merges). |
-
-**Setup** — run once per machine or per repository:
-
-| Command | What it does |
-|---|---|
-| `carson lint policy --source <repo>` | Distribute lint configs from policy source into `.github/linters/`. |
-| `carson onboard` | One-command baseline: hooks + templates + first audit. |
-| `carson prepare` | Install or refresh Carson-managed global hooks. |
-| `carson refresh` | Re-apply hooks, templates, and audit after upgrading Carson. |
-| `carson refresh --all` | Refresh all governed repositories at once. |
-| `carson offboard` | Remove Carson from a repository. |
-
-**Daily** — regular development workflow:
-
-| Command | What it does |
-|---|---|
-| `carson audit` | Full governance check (also runs automatically on every commit). |
-| `carson sync` | Fast-forward local `main` from remote. |
-| `carson prune` | Remove stale local branches whose upstream is gone. |
-| `carson template check` | Detect drift between managed and host `.github/*` files. |
-| `carson template apply` | Repair drifted `.github/*` files. |
-
-**Review** — PR merge readiness:
-
-| Command | What it does |
-|---|---|
-| `carson review gate` | Block or approve merge based on unresolved review comments. |
-| `carson review sweep` | Scan recent PRs and update a tracking issue for late feedback. |
-
-**Info**:
-
-| Command | What it does |
-|---|---|
-| `carson version` | Print installed version. |
-| `carson inspect` | Verify Carson-managed hook installation and repository setup. |
+Everything else bends to your preference. Which branch is main, how PRs are merged, which repositories to govern, which coding agent to dispatch, where your lint policy lives — Carson asks during setup and remembers. Sensible defaults are provided; you only change what matters to you. See `MANUAL.md` for the full list.
 
 ## Quickstart
 
-Prerequisites: Ruby `>= 3.4`, `git`, and `gem` in your PATH.
-`gh` (GitHub CLI) is recommended for full review governance features.
-
-```bash
-# Install
-gem install --user-install carson
-carson version
-```
-
-**Prepare your lint policy.** A policy source is any directory (or git URL) containing your lint configuration files (`.rubocop.yml`, `biome.json`, `ruff.toml`, etc.). Carson copies these into the governed repo's `.github/linters/` where MegaLinter auto-discovers them:
+Prerequisites: Ruby `>= 3.4`, `git`, and `gem` in your PATH. `gh` (GitHub CLI) is recommended for full review governance features.
 
 ```bash
-carson lint policy --source /path/to/your-policy-repo
+gem install carson
 ```
 
 **Onboard a repository:**
@@ -138,6 +66,8 @@ carson lint policy --source /path/to/your-policy-repo
 carson onboard /path/to/your-repo
 ```
 
+On first run, Carson walks you through setup — remote, main branch, workflow style, merge method — then installs hooks, syncs templates, and runs an initial audit.
+
 After `carson onboard`, your repository has:
 - Git hooks that run `carson audit` on every commit.
 - Managed `.github/*` templates synchronised from Carson.
@@ -145,31 +75,28 @@ After `carson onboard`, your repository has:
 
 Commit the generated `.github/*` changes, and the repository is governed.
 
-**Daily workflow:**
+**Set up lint policy** (optional). If you have a central directory or repository of lint configs, point Carson at it — configs are copied into `.github/linters/` where MegaLinter auto-discovers them:
 
 ```bash
-carson govern --dry-run     # see what Carson would do across all repos
-carson govern               # triage PRs, merge ready ones, dispatch agents, housekeep
-carson govern --loop 300    # run continuously, cycling every 5 minutes
+# local directory
+carson lint policy --source /path/to/your-policy-dir
+
+# remote repository
+carson lint policy --source https://github.com/you/lint-policy.git
 ```
 
-Or the individual commands if you prefer manual control:
+**Govern your portfolio.** Once repositories are onboarded, `carson govern` is your recurring command. Run it whenever you want Carson to triage open PRs, enforce review policy, dispatch coding agents, and housekeep across all governed repos:
 
 ```bash
-carson audit                # full governance check
-carson review gate          # block or approve merge based on review status
-carson sync                 # fast-forward local main
-carson prune                # clean up stale local branches
+carson govern --dry-run     # preview what Carson would do, change nothing
+carson govern               # triage PRs, merge ready ones, dispatch agents, housekeep
+carson govern --loop 300    # run continuously, cycling every 5 minutes
 ```
 
 ## Where to Read Next
 
-- **MANUAL.md** — installation, first-time setup, CI configuration, daily operations, troubleshooting.
+- **MANUAL.md** — installation, first-time setup, CI configuration, daily operations, full command reference, troubleshooting.
 - **API.md** — formal interface contract: commands, exit codes, configuration schema.
-- **RELEASE.md** — version history and upgrade actions.
-- **docs/define.md** — product definition and scope.
-- **docs/design.md** — experience and brand design.
-- **docs/develop.md** — contributor guide: architecture, development workflow.
 
 ## Support
 

data/RELEASE.md

@@ -5,6 +5,33 @@ Release-note scope rule:
 - `RELEASE.md` records only version deltas, breaking changes, and migration actions.
 - Operational usage guides live in `MANUAL.md` and `API.md`.
 
+## 2.13.3 — Rename carson-instructions.md to carson.md
+
+### What changed
+
+- Renamed `.github/carson-instructions.md` → `.github/carson.md` in both the template set and the Carson repo itself. Shorter name, consistent with Carson's naming conventions.
+- Enriched `carson.md` content: added Commands section (before committing, before merge, housekeeping), exit codes table, and clearer headings. Governance rules are unchanged.
+- Updated agent pointer files: `CLAUDE.md` and `copilot-instructions.md` now point to `AGENTS.md`; `AGENTS.md` points to `carson.md`. One extra level of indirection, zero new files to maintain.
+
+### Migration
+
+In each governed repository, run:
+
+```bash
+git rm .github/carson-instructions.md
+carson template apply
+```
+
+`carson template apply` writes the new `carson.md` and updates the pointer files. The old `carson-instructions.md` must be removed manually — Carson will not delete it automatically.
+
+## 2.13.2 — Docs Refresh
+
+### What changed
+
+- Updated `docs/define.md`: added missing in-scope commands (`govern`, `housekeep`, `refresh --all`, `lint policy`); corrected out-of-scope merge authority statement.
+- Updated `docs/plan.md`: corrected test counts, added `prompt.rb` and `runtime_refresh_all_test.rb` to file structure, added `--loop SECONDS` and `refresh --all` to CLI section, updated delivery status.
+- Updated `API.md`: added `govern` config schema and environment overrides.
+
 ## 2.13.1 — Guided Governance Registration
 
 ### What changed

data/VERSION

@@ -1 +1 @@
-2.13.1
+2.13.3

data/carson.gemspec

@@ -7,8 +7,8 @@ Gem::Specification.new do |spec|
 	spec.version = Carson::VERSION
 	spec.authors = [ "Hailei Wang" ]
 	spec.email = [ "wanghailei@users.noreply.github.com" ]
-	spec.summary = "Autonomous governance runtime — lint, review gates, PR triage, and merge across repositories."
-	spec.description = "Carson lives outside the repositories it governs. On every commit it enforces centralised lint policy and scope checks. On PRs it gates merge on unresolved reviewer feedback, dispatches coding agents to fix CI failures, merges passing PRs, and housekeeps branches. Runs locally and in GitHub Actions."
+	spec.summary = "Autonomous repository governance — you write the code, Carson manages everything else."
+	spec.description = "Carson is a governance runtime that lives outside the repositories it governs — no Carson-owned artefacts in your repo. On every commit, managed hooks enforce centralised lint policy and review gates. At portfolio level, carson govern triages every open PR across your registered repositories: merge what's ready, dispatch coding agents to fix what's failing, escalate what needs human judgement. One command, all your projects, unmanned."
 	spec.homepage = "https://github.com/wanghailei/carson"
 	spec.license = "MIT"
 	spec.required_ruby_version = ">= 3.4"

data/lib/carson/config.rb

@@ -48,7 +48,7 @@ module Carson
 					}
 				},
 				"template" => {
-					"managed_files" => [ ".github/carson-instructions.md", ".github/copilot-instructions.md", ".github/CLAUDE.md", ".github/AGENTS.md", ".github/pull_request_template.md", ".github/workflows/carson-lint.yml" ]
+					"managed_files" => [ ".github/carson.md", ".github/copilot-instructions.md", ".github/CLAUDE.md", ".github/AGENTS.md", ".github/pull_request_template.md", ".github/workflows/carson-lint.yml" ]
 				},
 				"lint" => {
 					"policy_source" => "wanghailei/lint.git"

data/lib/carson/runtime/local.rb

@@ -188,7 +188,7 @@ module Carson
 				puts_line ""
 				puts_line "Onboarding #{repo_name}..."
 
-				unless global_config_exists?
+				if !global_config_exists? || !git_remote_exists?( remote_name: config.git_remote )
 					if self.in.respond_to?( :tty? ) && self.in.tty?
 						setup_status = setup!
 						return setup_status unless setup_status == EXIT_OK

data/lib/carson/runtime/setup.rb

@@ -356,9 +356,9 @@ module Carson
 				accepted = prompt_yes_no( default: true )
 				if accepted
 					append_govern_repo!( repo_path: expanded )
-					puts_line "Registered."
+					puts_line "Registered. Run carson refresh --all to keep all repos in sync."
 				else
-					puts_line "Skipped. Re-run carson onboard to register later."
+					puts_line "Skipped. Run carson onboard here again to register later."
 				end
 			end
 

data/templates/.github/AGENTS.md

@@ -1 +1 @@
-Read `.github/carson-instructions.md` for repository governance rules enforced by Carson.
+Read `.github/carson.md` for repository governance rules enforced by Carson.

data/templates/.github/CLAUDE.md

@@ -1 +1 @@
-Read `.github/carson-instructions.md` for repository governance rules enforced by Carson.
+Read `.github/AGENTS.md` for repository governance rules enforced by Carson.

data/templates/.github/carson.md

@@ -0,0 +1,45 @@
+# Carson Governance
+
+This repository is governed by [Carson](https://github.com/wanghailei/carson), an autonomous governance runtime. Carson lives on the maintainer's workstation, not inside this repository.
+
+## What Carson Does Not Do
+
+Carson has no `commit`, `push`, or `pr` commands. Use `git` and `gh` for those. Carson audits and governs; you execute.
+
+## Commands
+
+**Before committing:**
+```bash
+carson audit           # full governance check — run before every commit
+carson template check  # detect drift in .github/* managed files
+carson template apply  # fix drift if detected
+```
+
+**Before recommending merge:**
+```bash
+carson review gate     # block until actionable review findings are resolved
+```
+
+**Branch housekeeping:**
+```bash
+carson sync            # fast-forward local main from remote
+carson prune           # remove stale branches (safer than git branch -d on squash repos)
+carson housekeep       # sync + prune together
+```
+
+## Exit Codes
+
+- `0` — success
+- `1` — runtime or configuration error
+- `2` — policy blocked (hard stop; treat as expected failure in CI)
+
+## Governance Rules
+
+- Before commit and before push, run `carson audit`.
+- At session start and again immediately before merge recommendation, run `gh pr list --state open --limit 50` and re-confirm active PR priorities.
+- Before merge recommendation, run `carson review gate`; it enforces warm-up wait, unresolved-thread convergence, and `Disposition:` acknowledgements for actionable top-level findings.
+- Actionable findings are unresolved review threads, any non-author `CHANGES_REQUESTED` review, or non-author comments/reviews with risk keywords (`bug`, `security`, `incorrect`, `block`, `fail`, `regression`).
+- `Disposition:` responses must include one token (`accepted`, `rejected`, `deferred`) and the target review URL.
+- Scheduled governance runs `carson review sweep` every 8 hours to track late actionable review activity.
+- Do not treat green checks or `mergeStateStatus: CLEAN` as sufficient if unresolved review threads remain.
+- Never suggest destructive operations on protected refs (`main`/`master`, local or remote).

data/templates/.github/copilot-instructions.md

@@ -1 +1 @@
-Read `.github/carson-instructions.md` for repository governance rules enforced by Carson.
+Read `.github/AGENTS.md` for repository governance rules enforced by Carson.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: carson
 version: !ruby/object:Gem::Version
-  version: 2.13.1
+  version: 2.13.3
 platform: ruby
 authors:
 - Hailei Wang
@@ -9,10 +9,12 @@ bindir: exe
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies: []
-description: Carson lives outside the repositories it governs. On every commit it
-  enforces centralised lint policy and scope checks. On PRs it gates merge on unresolved
-  reviewer feedback, dispatches coding agents to fix CI failures, merges passing PRs,
-  and housekeeps branches. Runs locally and in GitHub Actions.
+description: 'Carson is a governance runtime that lives outside the repositories it
+  governs — no Carson-owned artefacts in your repo. On every commit, managed hooks
+  enforce centralised lint policy and review gates. At portfolio level, carson govern
+  triages every open PR across your registered repositories: merge what''s ready,
+  dispatch coding agents to fix what''s failing, escalate what needs human judgement.
+  One command, all your projects, unmanned.'
 email:
 - wanghailei@users.noreply.github.com
 executables:
@@ -61,7 +63,7 @@ files:
 - lib/carson/version.rb
 - templates/.github/AGENTS.md
 - templates/.github/CLAUDE.md
-- templates/.github/carson-instructions.md
+- templates/.github/carson.md
 - templates/.github/copilot-instructions.md
 - templates/.github/pull_request_template.md
 - templates/.github/workflows/carson-lint.yml
@@ -93,6 +95,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 4.0.3
 specification_version: 4
-summary: Autonomous governance runtime — lint, review gates, PR triage, and merge
-  across repositories.
+summary: Autonomous repository governance — you write the code, Carson manages everything
+  else.
 test_files: []

data/templates/.github/carson-instructions.md

@@ -1,12 +0,0 @@
-## Shared Governance Baseline
-
-- GitHub rulesets and required checks are merge authority.
-- Carson runs as an outsider runtime for hook health, main sync, scope integrity, and gh visibility.
-- Before commit and before push, run `carson audit`.
-- At session start and again immediately before merge recommendation, run `gh pr list --state open --limit 50` and re-confirm active PR priorities.
-- Before merge recommendation, run `carson review gate`; it enforces warm-up wait, unresolved-thread convergence, and `Disposition:` dispositions for actionable top-level findings.
-- Actionable findings are unresolved review threads, any non-author `CHANGES_REQUESTED` review, or non-author comments/reviews with risk keywords (`bug`, `security`, `incorrect`, `block`, `fail`, `regression`).
-- `Disposition:` dispositions must include one token (`accepted`, `rejected`, `deferred`) and the target review URL.
-- Scheduled governance runs `carson review sweep` every 8 hours to track late actionable review activity on recent open/closed PRs.
-- Do not treat green checks or `mergeStateStatus: CLEAN` as sufficient if unresolved review threads remain.
-- Never suggest destructive operations on protected refs (`main`/`master`, local or remote).