#2 feat(2-git-memory): git memory — write side, read side, bootstrap distribution

[ivan-hilckov]

Summary

Implements the git memory (#2, ADR-0012): commit messages become the project's long-term decision history, written for coding agents as the primary readers. The existing subject convention stays; commits that carry a decision get a prose body explaining why plus optional decision trailers from a fixed vocabulary of four (Constraint:, Rejected:, Directive:, Related:). Every code skill now reads the affected files' history before working, and bootstrap distributes the convention to target projects as a mandatory CLAUDE.md section plus a commit-msg hook.

Design decisions

• Body by content, not by type — the test is "will a reader six months out wonder why"; mechanical commits stay one-liners, so the hook warns (never blocks) on a bodyless feat/fix/refactor and blocks only a malformed subject.
• Four trailers, not nine — the Lore Protocol self-assessment keys (Confidence:, Scope-risk:, …) were dropped as ritual noise; see .yoke/adr/0012-commit-messages-as-git-memory.md for the full trade-off.
• Both guides live in skills/gca/reference/ — the owning-skill precedent (issues/reference/github-issues.md); the seven consuming skills cross-reference them.
• Trailer ban narrowed, not lifted — identity trailers (Co-Authored-By, Signed-off-by) stay banned; decision trailers are the point.
• The commits in this branch already follow the new convention — review them as the first live sample of the memory.

Test plan

• Hook validated against 9 message shapes (valid one-liner, body+trailers, bodyless feat → warning, colon-after-ticket → block, no type → block, merge commit → skip, YouTrack id with digit in project code, docs one-liner, no-slug fix)
• pnpm run format:check — clean
• YAML frontmatter intact in all 7 touched SKILL.md files; JSON manifests parse
• Reviewer: read git log of this branch — the bodies and trailers should read as useful memory, not ritual

Changes

File	Action	Description
skills/gca/reference/commit-convention.md	extend	"Body — the git memory" section: by-content rule, 4 trailers, example, anti-patterns; trailer ban narrowed to identity trailers
skills/gca/reference/history-reading.md	new	Read side: which git command answers which question, acting on Constraint:/Directive:/Rejected:
skills/{do,draft,review,grill,grill-docs,prd,issues}/SKILL.md	extend	Read-the-git-memory step before touching or judging code
skills/bootstrap/agents/claude-md-generator.md	extend	Mandatory "Git memory (commit convention)" CLAUDE.md section (create + enrich)
skills/bootstrap/reference/hooks-patterns.md	extend	§ Git memory commit-msg hook — the scaffolded script
skills/bootstrap/reference/bootstrap-pipeline.md	extend	Phase 3 orchestrator step scaffolds the hook; Phase 7 stages it when tracked
.husky/commit-msg, CLAUDE.md	new/extend	Dogfood: yoke runs the hook itself; Conventions documents the format

Commits

• 0739619 Git memory: commit messages as the long-term memory layer for agents #2 feat(2-git-memory): extend commit convention with git memory body and decision trailers
• 770ea40 Git memory: commit messages as the long-term memory layer for agents #2 feat(2-git-memory): add history reading guide
• 2ef07b2 Git memory: commit messages as the long-term memory layer for agents #2 feat(2-git-memory): add git memory read step to all code skills
• c045055 Git memory: commit messages as the long-term memory layer for agents #2 feat(2-git-memory): scaffold git memory section and commit-msg hook in bootstrap
• 68519b0 Git memory: commit messages as the long-term memory layer for agents #2 fix(2-git-memory): accept digits in ticket project codes
• 9d37dda Git memory: commit messages as the long-term memory layer for agents #2 chore(2-git-memory): adopt the git memory convention in the yoke repo

Validation

• pnpm run format:check — all files use Prettier code style
• Hook test matrix: 9/9 expected outcomes (2 blocks, 2 warnings, 5 clean passes)
• python3 JSON parse of plugin.json + marketplace.json — OK

---