memgit 0.4.0__tar.gz → 0.6.0__tar.gz

{memgit-0.4.0 → memgit-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memgit
-Version: 0.4.0
+Version: 0.6.0
 Summary: Git for AI memory — version-controlled context persistence across Claude, GPT, Gemini, Cursor, Windsurf, and more
 License: MIT
 Project-URL: Homepage, https://memgit.dev
@@ -44,7 +44,7 @@ Version-controlled, cross-AI context that persists, diffs, rolls back, and syncs
 
 [![PyPI](https://img.shields.io/pypi/v/memgit)](https://pypi.org/project/memgit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-54%20passing-brightgreen)](tests/)
+[![Tests](https://img.shields.io/badge/tests-245%20passing-brightgreen)](tests/)
 
 ---
 
@@ -215,13 +215,14 @@ memgit resume --json     # for tooling
 Wire it into Claude Code so memory becomes **automatic** — no tool call, no judgment required:
 
 ```bash
-memgit setup hooks       # installs all four hooks (~/.claude/settings.json)
+memgit setup hooks       # installs all five hooks (~/.claude/settings.json)
 ```
 
 | Hook | What it enforces |
 |---|---|
-| `SessionStart` | every session opens with the resume digest in context |
-| `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `SessionStart` | every session opens with the resume digest in context — status board, checkpoints, critical rules, memory index |
+| `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected, ending with a "+N more on '<topic>'" depth hint when more exists (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `PostToolUse` | reading a file whose path matches a memory tag surfaces a one-line hint ("6 memories tagged 'x' relate to this path") — tagmap cache only, capped 3/session, `--no-ctx-recall` to skip |
 | `Stop` (guard) | a session that did real work but saved nothing gets ONE nudge to save durable facts before finishing — `--no-guard` to skip |
 | `Stop` (sync) | markdown memories are checkpointed asynchronously at session end |
 
@@ -284,13 +285,35 @@ The tool descriptions teach the AI **judgment** — "does this request depend on
 
 ---
 
+## Core operating guide (v0.5.0)
+
+A project's hardest onboarding problem isn't *what* it does — it's *how to work in it*: which skill to invoke, which command to run, which tool to reach for. That lives in a `CLAUDE.md` or a skills folder the AI host may or may not be configured to read. memgit carries it for you.
+
+`memgit core seed` distills a compact operating guide from the project's existing skills + rule files. `memgit core sync` writes it into **every AI host's own rules surface** as a dedicated, memgit-owned file — `.claude/rules/memgit.md`, `.cursor/rules/memgit.mdc`, `.windsurf/rules/memgit.md`, `.clinerules/`, `.roo/rules/`, `.continue/rules/`, `.gemini/`, and a marker-block in Codex's `AGENTS.md`. It's **additive only** — memgit never touches your own config or content — and injected at session start, so any tool knows how to work in the project even when its native setup is missing.
+
+And it **learns**: a sidecar usage ledger tracks which memories actually get recalled, and the most-used ones are auto-promoted as pointers into the guide over time (budget-capped, decaying, and always subordinate to the repo's own rules — it never restates or overrides them). Drifted? `memgit core heal` rebuilds it.
+
+---
+
+## Depth advertisement, trackers & supersession (v0.6.0)
+
+Measured across 289 real sessions: injected recall reached ~59% of them, but only **6.8%** ever ran an active search — the injected top-3 reads as "memory consulted", so the model never learns there's a queryable store behind it. 0.6.0 makes the passive layer advertise what the active layer knows:
+
+- **Memory index** — the resume digest ends with tag→count pairs (`8a8f4ec (6) · instagram (5)`) and the exact call to go deeper. Counts are truthful: superseded memories are excluded, and every advertised topic is guaranteed to return search results.
+- **"+N more" recall hints** — when the per-prompt recall block has more on-topic memories behind it, it says so, with the one call to get them.
+- **Context-triggered recall** — a `PostToolUse` hook: reading a file whose path matches a memory tag surfaces `memgit: 6 memories tagged 'x' relate to this path`. Reads only a commit-time tagmap cache (never the store), capped 3/session.
+- **Trackers (`tr`)** — one memory per in-flight entity (`<entity>-status`), updated by re-saving the same slug. They render as a **status board** at the top of every session: memgit is the authority for entity status; files may lag.
+- **Supersession** — a correction names what it replaces (`supersedes=[old-slug]`) instead of a "CORRECTED:" prefix. Superseded memories vanish from search/recall/resume (history preserved; `list` still shows them marked ⊘), so injected context is never stale.
+
+---
+
 ## Commands
 
 ```bash
 # Core (git-like)
 memgit init                       # initialize store (auto-detects best path)
 memgit onboard                    # bootstrap brief for an existing codebase
-memgit add <slug> <rule>          # stage a memory (--body for full detail, --project to scope)
+memgit add <slug> <rule>          # stage a memory (--body detail, --project scope, --supersedes old-slug)
 memgit commit -m "message"        # checkpoint current state
 memgit log                        # history
 memgit diff [sha1] [sha2]         # what changed
@@ -301,6 +324,13 @@ memgit search <query>             # BM25 relevance search
 memgit rollback <ref>             # restore state to a checkpoint (HEAD~N or SHA)
 memgit resume                     # where we left off — session-start digest
 memgit merge <thread>             # three-way merge a thread into the current one
+memgit remove <slug>              # (aliases: delete, rm, del) — mistypes get a "did you mean?"
+
+# Core operating guide — per-project, always-on, cross-host
+memgit core seed                  # draft a guide from this project's skills + rule files
+memgit core sync                  # deliver it into each AI host's own rules file (additive)
+memgit core show / edit           # view / curate the guide
+memgit core heal                  # self-repair a guide that has drifted
 
 # Scale & proof
 memgit squash                     # compress old history (archives what it collapses)
@@ -415,7 +445,7 @@ git clone https://github.com/code4161/memgit.git
 cd memgit
 python -m venv .venv && source .venv/bin/activate
 pip install -e ".[dev]"
-pytest    # 48 tests, all passing, < 1 second
+pytest    # 245 tests, all passing, < 5 seconds
 ```
 
 See [CONTRIBUTING.md](CONTRIBUTING.md).
@@ -435,6 +465,8 @@ See [CONTRIBUTING.md](CONTRIBUTING.md).
 - [x] Flat `memories/` directory — grep/diff/blame your memories
 - [x] D3.js graph visualization of memory relationships
 - [x] `memgit resume` + SessionStart hook — sessions start with "where we left off"
+- [x] Guardrail hooks — per-prompt auto-recall + end-of-session capture guard (v0.4.0)
+- [x] Core operating guide — per-project, always-on, cross-host, self-improving (v0.5.0)
 - [x] `memgit gc` — space reclamation (mark-and-sweep, lossless squash archive)
 - [x] Multi-agent write safety — store lock, auto-merge commits, `memgit merge`
 - [x] PyPI + Homebrew (tap) + npm published (v0.1.5)

{memgit-0.4.0 → memgit-0.6.0}/README.md

@@ -10,7 +10,7 @@ Version-controlled, cross-AI context that persists, diffs, rolls back, and syncs
 
 [![PyPI](https://img.shields.io/pypi/v/memgit)](https://pypi.org/project/memgit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-54%20passing-brightgreen)](tests/)
+[![Tests](https://img.shields.io/badge/tests-245%20passing-brightgreen)](tests/)
 
 ---
 
@@ -181,13 +181,14 @@ memgit resume --json     # for tooling
 Wire it into Claude Code so memory becomes **automatic** — no tool call, no judgment required:
 
 ```bash
-memgit setup hooks       # installs all four hooks (~/.claude/settings.json)
+memgit setup hooks       # installs all five hooks (~/.claude/settings.json)
 ```
 
 | Hook | What it enforces |
 |---|---|
-| `SessionStart` | every session opens with the resume digest in context |
-| `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `SessionStart` | every session opens with the resume digest in context — status board, checkpoints, critical rules, memory index |
+| `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected, ending with a "+N more on '<topic>'" depth hint when more exists (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `PostToolUse` | reading a file whose path matches a memory tag surfaces a one-line hint ("6 memories tagged 'x' relate to this path") — tagmap cache only, capped 3/session, `--no-ctx-recall` to skip |
 | `Stop` (guard) | a session that did real work but saved nothing gets ONE nudge to save durable facts before finishing — `--no-guard` to skip |
 | `Stop` (sync) | markdown memories are checkpointed asynchronously at session end |
 
@@ -250,13 +251,35 @@ The tool descriptions teach the AI **judgment** — "does this request depend on
 
 ---
 
+## Core operating guide (v0.5.0)
+
+A project's hardest onboarding problem isn't *what* it does — it's *how to work in it*: which skill to invoke, which command to run, which tool to reach for. That lives in a `CLAUDE.md` or a skills folder the AI host may or may not be configured to read. memgit carries it for you.
+
+`memgit core seed` distills a compact operating guide from the project's existing skills + rule files. `memgit core sync` writes it into **every AI host's own rules surface** as a dedicated, memgit-owned file — `.claude/rules/memgit.md`, `.cursor/rules/memgit.mdc`, `.windsurf/rules/memgit.md`, `.clinerules/`, `.roo/rules/`, `.continue/rules/`, `.gemini/`, and a marker-block in Codex's `AGENTS.md`. It's **additive only** — memgit never touches your own config or content — and injected at session start, so any tool knows how to work in the project even when its native setup is missing.
+
+And it **learns**: a sidecar usage ledger tracks which memories actually get recalled, and the most-used ones are auto-promoted as pointers into the guide over time (budget-capped, decaying, and always subordinate to the repo's own rules — it never restates or overrides them). Drifted? `memgit core heal` rebuilds it.
+
+---
+
+## Depth advertisement, trackers & supersession (v0.6.0)
+
+Measured across 289 real sessions: injected recall reached ~59% of them, but only **6.8%** ever ran an active search — the injected top-3 reads as "memory consulted", so the model never learns there's a queryable store behind it. 0.6.0 makes the passive layer advertise what the active layer knows:
+
+- **Memory index** — the resume digest ends with tag→count pairs (`8a8f4ec (6) · instagram (5)`) and the exact call to go deeper. Counts are truthful: superseded memories are excluded, and every advertised topic is guaranteed to return search results.
+- **"+N more" recall hints** — when the per-prompt recall block has more on-topic memories behind it, it says so, with the one call to get them.
+- **Context-triggered recall** — a `PostToolUse` hook: reading a file whose path matches a memory tag surfaces `memgit: 6 memories tagged 'x' relate to this path`. Reads only a commit-time tagmap cache (never the store), capped 3/session.
+- **Trackers (`tr`)** — one memory per in-flight entity (`<entity>-status`), updated by re-saving the same slug. They render as a **status board** at the top of every session: memgit is the authority for entity status; files may lag.
+- **Supersession** — a correction names what it replaces (`supersedes=[old-slug]`) instead of a "CORRECTED:" prefix. Superseded memories vanish from search/recall/resume (history preserved; `list` still shows them marked ⊘), so injected context is never stale.
+
+---
+
 ## Commands
 
 ```bash
 # Core (git-like)
 memgit init                       # initialize store (auto-detects best path)
 memgit onboard                    # bootstrap brief for an existing codebase
-memgit add <slug> <rule>          # stage a memory (--body for full detail, --project to scope)
+memgit add <slug> <rule>          # stage a memory (--body detail, --project scope, --supersedes old-slug)
 memgit commit -m "message"        # checkpoint current state
 memgit log                        # history
 memgit diff [sha1] [sha2]         # what changed
@@ -267,6 +290,13 @@ memgit search <query>             # BM25 relevance search
 memgit rollback <ref>             # restore state to a checkpoint (HEAD~N or SHA)
 memgit resume                     # where we left off — session-start digest
 memgit merge <thread>             # three-way merge a thread into the current one
+memgit remove <slug>              # (aliases: delete, rm, del) — mistypes get a "did you mean?"
+
+# Core operating guide — per-project, always-on, cross-host
+memgit core seed                  # draft a guide from this project's skills + rule files
+memgit core sync                  # deliver it into each AI host's own rules file (additive)
+memgit core show / edit           # view / curate the guide
+memgit core heal                  # self-repair a guide that has drifted
 
 # Scale & proof
 memgit squash                     # compress old history (archives what it collapses)
@@ -381,7 +411,7 @@ git clone https://github.com/code4161/memgit.git
 cd memgit
 python -m venv .venv && source .venv/bin/activate
 pip install -e ".[dev]"
-pytest    # 48 tests, all passing, < 1 second
+pytest    # 245 tests, all passing, < 5 seconds
 ```
 
 See [CONTRIBUTING.md](CONTRIBUTING.md).
@@ -401,6 +431,8 @@ See [CONTRIBUTING.md](CONTRIBUTING.md).
 - [x] Flat `memories/` directory — grep/diff/blame your memories
 - [x] D3.js graph visualization of memory relationships
 - [x] `memgit resume` + SessionStart hook — sessions start with "where we left off"
+- [x] Guardrail hooks — per-prompt auto-recall + end-of-session capture guard (v0.4.0)
+- [x] Core operating guide — per-project, always-on, cross-host, self-improving (v0.5.0)
 - [x] `memgit gc` — space reclamation (mark-and-sweep, lossless squash archive)
 - [x] Multi-agent write safety — store lock, auto-merge commits, `memgit merge`
 - [x] PyPI + Homebrew (tap) + npm published (v0.1.5)

{memgit-0.4.0 → memgit-0.6.0}/memgit/__init__.py

@@ -1,3 +1,3 @@
 """memgit — git for AI memory."""
 
-__version__ = "0.4.0"
+__version__ = "0.6.0"