docs(devops): fix-forward-in-git; ban escalating reconcilable changes as manual/board actions (GRO-2536)

The board flagged that agents repeatedly requested board approval and hand-run kubectl on a Flux-managed cluster — unfillable, wrong, and the root cause of a multi-day stall. The devops skill prohibited `kubectl apply` to prod but never stated the corollary: the resolution of any reconcilable breakage is a PR to groombook/infra, never a human-run command. This adds that contract explicitly. cc @cpfarhood
2026-06-25 11:50:00 +00:00
3 changed files with 3 additions and 3 deletions
@@ -4,7 +4,7 @@ description: >
  Engineering quality bar for GroomBook code: priority ordering of correctness
  vs. clarity vs. maintainability vs. performance vs. elegance, PR and test
  requirements, no-hardcoded-values rules, branch discipline, and the
-  PR self-merge rule. The uat→main merge-gate policy lives in the `sdlc`
+  no-self-merge contract. The uat→main merge-gate policy lives in the `sdlc`
  skill, not here.
 ---

@@ -35,7 +35,7 @@ Use the `GITEA_TOKEN` environment variable for all Gitea operations — it is al
 tea pr create --base main --title "..." --body "... cc @cpfarhood"
 ```

-Gitea branch protection requires CI checks to pass. See `coding-standards` for the PR self-merge rule and the `cc @cpfarhood` rule.
+Gitea branch protection requires CI checks to pass. See `coding-standards` for the no-self-merge contract and the `cc @cpfarhood` rule.

 ## Infrastructure topology

@@ -36,7 +36,7 @@ Three long-lived branches map to the three deployment environments:

 ## Pull requests

-All changes happen via pull request. Gitea branch protection requires CI checks to pass. See `coding-standards` for the PR self-merge rule and the `cc @cpfarhood` visibility rule.
+All changes happen via pull request. Gitea branch protection requires CI checks to pass. See `coding-standards` for the no-self-merge contract and the `cc @cpfarhood` visibility rule.

 ```bash
 tea pr create --base dev --title "..." --body "... cc @cpfarhood"