Retire lentago/coderabbit (ADR-0013 step 3)

brand/fleet.json

@@ -511,20 +511,5 @@
         "label": "Demo"
       }
     ]
-  },
-  "coderabbit": {
-    "mark": "lentago",
-    "kind": "FLEET",
-    "tagline": "Review defaults · one .coderabbit.yaml for the fleet",
-    "prompt": "central config  ·  repos inherit  ·  override per repo",
-    "badges": [
-      {
-        "label": "YAML",
-        "logo": "yaml"
-      },
-      {
-        "label": "Config"
-      }
-    ]
   }
 }

docs/adr/0013-haiku-reviews-every-pr-coderabbit-retires.md

@@ -1,6 +1,6 @@
 # ADR-0013: Haiku reviews every PR in the operating repos; CodeRabbit retires
 
-**Status:** Accepted (2026-10-29)
+**Status:** Accepted (2026-10-29; amended 2026-10-29: Decision 5's `.coderabbit.yaml` step was superseded, see there)
 
 ## Context
 
@@ -115,9 +115,14 @@ reach, and against one CodeRabbit had reviewed:
    - **every finding is triaged on the PR,** either fixed with the commit named
      or declined with a reason.
 5. **CodeRabbit retires once the callers are live:**
-   - auto-review goes off in the central `.coderabbit.yaml`;
+   - ~~auto-review goes off in the central `.coderabbit.yaml`~~ (*superseded
+     2026-10-29*: uninstalling the app stops all CodeRabbit activity at once,
+     and the repo is archived read-only, so a config edit first would only add
+     a PR to a closing repo; see #284);
    - the app is uninstalled from the org;
-   - `lentago/coderabbit` is archived through this repo's terraform.
+   - `lentago/coderabbit` is archived and removed from this repo's fleet
+     config and terraform state (`terraform/README.md` "Retiring a repo";
+     #284).
 
 ## Alternatives
 

fleet-ops/repos.json

@@ -646,29 +646,6 @@
         "ai-governance"
       ],
       "model_labels": []
-    },
-    "coderabbit": {
-      "description": "CodeRabbit central configuration for the Lentago Labs fleet \u2014 the org-wide .coderabbit.yaml that every repo without its own file inherits: review profile, path filters for generated trees, path instructions carrying the fleet's conventions, and the voice guide as a code guideline.",
-      "homepage": "https://docs.coderabbit.ai/configuration/central-configuration",
-      "visibility": "public",
-      "template": false,
-      "template_source": {
-        "owner": "lentago",
-        "repository": "repo-template"
-      },
-      "features": {
-        "issues": true,
-        "projects": false,
-        "wiki": false,
-        "discussions": false
-      },
-      "suggest_branch_update": false,
-      "topics": [
-        "code-review",
-        "configuration",
-        "governance"
-      ],
-      "model_labels": []
     }
   }
 }

fleet-ops/required-checks.json

@@ -175,10 +175,6 @@
     ],
     "uvularia-demo-ask-rules": [
       "evals"
-    ],
-    "coderabbit": [
-      "docs-check / docs-check",
-      "validate"
     ]
   }
 }

terraform/README.md

@@ -196,8 +196,8 @@ The state removal is the deliberate step that says "this is intentional."
 > **Transfers, not retirements** (`reference-checker` 2026-08-17, `music-curator`
 > 2026-10-13): a repo leaving for another owner follows the same path without the
 > archive step. Remove its rows in a PR; run `terraform state rm` for its
-> resources (twelve per repo: the repository, the merge gate, the ruleset, nine
-> labels) right before that PR merges, so no plan runs in between, since a plan
+> resources (fourteen per repo since ADR-0013's two review labels: the
+> repository, the merge gate, the ruleset, eleven labels) right before that PR merges, so no plan runs in between, since a plan
 > that sees a configured repo missing from state proposes creating it again;
 > transfer only after the merge. Transferring first leaves config declaring a
 > repo the org no longer has, with the same result (#146).