Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(process): two testing rules and a base-branch check for contributors

AkitaOnRailsa3609630673a
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index ccd7f869..a7ac1de4 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -31,6 +31,11 @@
- [ ] **Major (breaking)**: on-disk format, removed/renamed surface, or
breaking MCP schema change, called out in "What changed" above
+- [ ] The base branch matches: `main` for a patch, the standing feature
+ branch (currently `release/3.1`) for minor or major work.
+- [ ] I checked that this does not redo something already on `main` or the
+ feature branch, or fixed by a closed issue.
+
## CHANGELOG (merge gate)
- [ ] I added a `CHANGELOG.md` `[Unreleased]` entry. It is **required** for any
diff --git a/AGENTS.md b/AGENTS.md
index a5cf0765..11097582 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -549,6 +549,19 @@ Additional boundary rules:
precedence, and cross-workspace isolation; PRs touching permissions still need
root, DB-user, and anonymous cases — now recorded against the inventory.
- New disk+SQL mutations need recovery/rollback tests.
+- **A changed default reaches every consumer.** When a change alters a default
+ or where a setting or credential lives (auth on for new installs, a token
+ read from a file, a new required header or path), list every component that
+ reads it (thin CLI clients, hook capture and the spool drain, `run` and its
+ jail re-exec, `/web`, backfill, the generated TS adapters) and test each one
+ under the new default. 3.0.0's token-file default broke three of them that
+ no test exercised with it (#1283, #1284, #1288).
+- **Third-party behavior is modeled from its docs.** When code reproduces how
+ another tool behaves (a harness's hook payloads or missing fields, Claude
+ Code's instruction-file and `@import` rules), link the vendor doc next to the
+ code and test each case the doc describes, not only the case at hand. A
+ one-case model of the import rules shipped in #1297 and had to be redone in
+ #1298.
- The recall-eval framework lives at
`crates/ai-memory-consolidate/tests/suite/recall_eval.rs`.
- Tests run with `cargo t` locally,
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a619897e..29c35702 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -192,3 +192,12 @@ than the following major release.
are not held for feature releases. Small additive features (a new
agent harness, LLM provider, install client) ship in the next
**minor**.
+- **Pick the base branch from that impact.** A fix targets `main`. A new
+ capability (flag, subcommand, MCP tool, config key, agent harness,
+ provider, companion) targets the standing feature branch, currently
+ `release/3.1`. A fix to code that exists only on the feature branch
+ targets that branch too.
+- **Check what already landed first.** Before opening a PR, look for the
+ issue's closing commit and search `git log origin/main origin/release/3.1`
+ for the feature or fix. A closed issue usually means the work shipped;
+ a PR that redoes it gets closed, however good it is.