Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs: preserve canonical commit attribution
AkitaOnRails502ea7c55287
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.mdindex fc0818f8..8066c95e 100644--- a/.github/pull_request_template.md+++ b/.github/pull_request_template.md@@ -13,6 +13,12 @@- [ ] `cargo test --workspace` passes- [ ] Manual test: <!-- describe what you ran and what you observed -->+## Commit attribution++- [ ] I verified the name and email on every commit in this PR and corrected+ any unintended identity before requesting merge. See+ [commit attribution guidance](https://github.com/akitaonrails/ai-memory/blob/main/CONTRIBUTING.md#commit-attribution).+## CHANGELOG (merge gate)- [ ] I added a `CHANGELOG.md` `[Unreleased]` entry — **required** for anydiff --git a/.mailmap b/.mailmapnew file mode 100644index 00000000..51355ea4--- /dev/null+++ b/.mailmap@@ -0,0 +1,2 @@+# Keep contributor identities canonical without rewriting published history.+Lucas Oliveira <[email protected]> <[email protected]>diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 86b0fb6c..eaa78b4c 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -14,6 +14,31 @@ self-contained: SQLite is bundled via `rusqlite`'s `bundled` feature, and`libgit2` is vendored via `git2`'s `vendored-libgit2` feature. No systemlibraries need installing beyond a standard C toolchain.+## Commit attribution++GitHub associates commits with accounts through the author email stored in+each commit. Before pushing a branch, inspect every commit that the pull request+will add:++```bash+git log --format='%h %an <%ae>' "$(git merge-base HEAD origin/main)"..HEAD+```++Use an email verified by your GitHub account, or its GitHub-provided `noreply`+address. Set it for this checkout when your global Git identity belongs to a+different project or employer:++```bash+git config --local user.name "Your Name"+git config --local user.email "[email protected]"+```++Correct attribution mistakes on the pull-request branch before it is merged.+The project does not rewrite shared `main` history or published release tags+solely to change attribution because doing so invalidates commit hashes and+breaks existing clones and forks. Maintainers use [`.mailmap`](.mailmap) to+canonicalize accidental aliases without changing published commits.+## Required gates before every PRAll four must pass — the CI workflow enforces them and so does the `bin/release`