From dd6b2ad75a8b79b67abb79cee0201ce6e341b3eb Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Sat, 19 Sep 2026 14:55:01 +0000 Subject: [PATCH 1/2] fix(docs): list the contributing guide where it actually lives The repository-structure block listed `CONTRIBUTING.md` at the repository root, but the guide lives at `.github/CONTRIBUTING.md` - the entry pointed at a location it had already moved away from. The entry is moved under the tree's existing `.github/` branch, at the block's own comment column; the layout of the rest of the tree is untouched. --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 45a4882..16604e5 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -39,11 +39,11 @@ cafescripto/ │ └── contractiles/ # Policy contracts (k9, dust, intend, must, trust) ├── .well-known/ # Protocol files (Perimeter 1-3) ├── .github/ # GitHub config (Perimeter 1) +│ ├── CONTRIBUTING.md # This file │ ├── ISSUE_TEMPLATE/ │ └── workflows/ ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md -├── CONTRIBUTING.md # This file ├── GOVERNANCE.md ├── LICENSE ├── MAINTAINERS.md From 15b280aa93481555f4014dfa5b7c6ad59adbea46 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Sat, 19 Sep 2026 15:05:48 +0000 Subject: [PATCH 2/2] fix(docs): resolve the {{MAIN_BRANCH}} template token in the contributing guide The guide is instantiated from the estate template, whose own copy legitimately holds `{{MAIN_BRANCH}}`. Here it was never substituted, so the reader is told to check whether a bug "is already fixed in `{{MAIN_BRANCH}}`". Resolved to this repository's default branch. One token, no other change. --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 16604e5..354c918 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -62,7 +62,7 @@ cafescripto/ **Before reporting**: 1. Search existing issues -2. Check if it's already fixed in `{{MAIN_BRANCH}}` +2. Check if it's already fixed in `main` 3. Determine which perimeter the bug affects **When reporting**: