Release: working-process 0.13.0, project-memory 0.4.0, standards 0.3.1

.claude-plugin/marketplace.json

@@ -22,7 +22,7 @@
     {
       "name": "project-memory",
       "source": "./plugins/project-memory",
-      "description": "In-repo project memory: committed Team memory and git-ignored per-user Private memory, with grooming (memory-review-session) and migration (migrate-memory) skills, shipped as a Rules payload"
+      "description": "In-repo project memory: committed Team memory and git-ignored per-user Private memory, with grooming (memory-review-session), migration (migrate-memory), and the Auto-memory redirect (redirect-memory) skills, shipped as a Rules payload"
     }
   ]
 }

.claude/rules/elements-of-style.md

@@ -0,0 +1,17 @@
+# Elements-of-style pass on prose
+
+Every committed Markdown file in this repo is prose for humans — `docs/`
+artifacts (specs, plans, ADRs, the glossary), plugin content (rules,
+skills, READMEs), and the repo's own README and rules — and gets an
+elements-of-style pass:
+
+- **Writing a new document**: when the
+  `elements-of-style:writing-clearly-and-concisely` skill is available,
+  invoke it BEFORE drafting — never write "from memory of the rules".
+- **Editing an existing document**: run an explicit editing pass with
+  that skill's full rules over the changed prose.
+- Without the plugin the rule stays silent: no substitute pass, and the
+  edit proceeds normally.
+
+The pass binds wording, never decisions — it changes how sentences carry
+a document's content, not what the document decides.

README.md

@@ -14,12 +14,12 @@ Marketplace of [Claude Code](https://code.claude.com) plugins by Missing Bits.
 
 ## Plugins
 
-| Plugin | Description |
-|--------|-------------|
-| `working-process` | Spec-driven working process: grilling-session, architect-session, system-designer-session and sync-rules skills, architect and plan-adversary review agents, two verdict-free consultation agents, distributed process rules |
-| `python-standards` | Python coding standards for uv + ruff + pytest + pyright: area skills, code-review stack, plan-review checklist, distributed toolchain rule |
-| `salesforce-standards` | Salesforce coding standards for the sf CLI toolchain: area skills (Apex, LWC, Flow, data/security model, legacy UI), code-review stack, plan-review checklist, distributed toolchain rule |
-| `project-memory` | In-repo project memory: committed Team memory (`docs/memory/`) and per-user Private memory (`.claude/memory/`), with `memory-review-session` and `migrate-memory` skills, distributed as a Rules payload |
+| Plugin | Docs | Description |
+|--------|------|-------------|
+| `working-process` | [README](plugins/working-process/README.md) | Spec-driven working process: grilling-session, architect-session, system-designer-session and sync-rules skills, architect and plan-adversary review agents, two verdict-free consultation agents, distributed process rules |
+| `python-standards` | [README](plugins/python-standards/README.md) | Python coding standards for uv + ruff + pytest + pyright: area skills, code-review stack, plan-review checklist, distributed toolchain rule |
+| `salesforce-standards` | [README](plugins/salesforce-standards/README.md) | Salesforce coding standards for the sf CLI toolchain: area skills (Apex, LWC, Flow, data/security model, legacy UI), code-review stack, plan-review checklist, distributed toolchain rule |
+| `project-memory` | [README](plugins/project-memory/README.md) | In-repo project memory: committed Team memory (`docs/memory/`) and per-user Private memory (`.claude/memory/`), with `memory-review-session`, `migrate-memory`, and `redirect-memory` skills, distributed as a Rules payload |
 
 ## License
 

docs/domain/adr/0002-own-entry-format.md

@@ -0,0 +1,25 @@
+---
+ticket: none
+---
+
+# Project memory defines its own entry format
+
+Auto-memory keeps entries in a shape — `name`, `description`,
+`metadata.type` with a four-value taxonomy — that the platform never
+documents; the published contract for entry bodies is "any markdown", and the
+surrounding surface moved four times inside one minor line. Project memory
+therefore converges on that shape without adopting it: the plugin's rules
+define every field on the plugin's own terms and adopt only fields that earn
+their place there, so a field like `description` is kept because it gives the
+index line a source, not because Auto-memory writes one. The asymmetry decides
+it — the store holds durable, versioned, team-shared data in git, while the
+format is a moving internal detail of a self-updating tool, and binding the
+first to the second would pay for interoperability with other people's
+repositories.
+
+The consequence is that compatibility is textual rather than contractual: a
+tolerance clause keeps unknown frontmatter keys intact so both writers can
+share a file, and nothing in the rules calls Auto-memory the source of the
+format. Making the store double as the Auto-memory directory would reverse
+this decision, so that later choice has to face it deliberately instead of
+sliding past it.

docs/domain/adr/0003-hybrid-store-adoption.md

@@ -0,0 +1,25 @@
+---
+ticket: none
+---
+
+# Private memory may double as the Auto-memory directory, opt-in
+
+ADR 0002 closed with: "Making the store double as the Auto-memory
+directory would reverse this decision, so that later choice has to face
+it deliberately instead of sliding past it." This record is that choice,
+faced. The hybrid adopts exactly two platform-owned identities — the
+directory (`autoMemoryDirectory` may point at `.claude/memory/`) and the
+index filename (`MEMORY.md`, the only name Auto-memory loads, adopted
+globally so the format has no mode variants) — because in a Hybrid store
+both pass ADR 0002's own test: they earn their place as the only way the
+harness reads the store at all.
+
+Everything else stands. The plugin defines its own entry format,
+converges on Auto-memory's without adopting it, and keeps the tolerance
+clause for keys the harness writes; an entry Auto-memory writes into a
+Hybrid store is an ordinary note whose missing H1 is format debt. The
+adoption is opt-in per developer and per Environment, carried by one key
+in `.claude/settings.local.json` written and removed by the
+redirect-memory skill; declining it leaves the store purely rule-driven.
+ADR 0002 remains in force for the format — this record narrows it only
+at the directory-and-name boundary.

docs/domain/glossary.md

@@ -45,6 +45,16 @@ wins, mirroring the Rules engine's project-over-user conflict rule. Part
 of the review-reports contract: the paths may not drift independently.
 _Avoid_: discovery, probe (unqualified)
 
+**Store probe**:
+The existence check a plugin other than project-memory runs to decide
+whether the reviewed project keeps a Project-memory part: one test per
+part, on the part's directory (`docs/memory/`, `.claude/memory/`) — never
+on a file inside it. Three surfaces run it (the review-reports
+Candidate-gap park offer and the two standards code-review restatements).
+Distinct from the Contract probe, which finds the installed report
+contract; the unqualified word stays banned there.
+_Avoid_: index check, store check
+
 **Review report**:
 The single persistent document one code-review run writes under
 `docs/code-review/` of the reviewed project — one run, one report,
@@ -286,12 +296,41 @@ asked, and NOT a Process directory — a per-user store under the `.claude/`
 config namespace, governed by the Project-memory rule.
 _Avoid_: local memory
 
+**Auto-memory**:
+The harness's own memory mechanism — the notes Claude Code writes for itself,
+their `MEMORY.md` index and its load budget, and the `autoMemoryDirectory` /
+`autoMemoryEnabled` settings that place and disable it. The mechanism, never a
+store: the store it manages by default is Home-dir memory. Project memory
+borrows none of its machinery — even a Hybrid store only points the harness
+at the plugin's directory.
+_Avoid_: native memory, auto memory (unhyphenated)
+
 **Home-dir memory**:
-The built-in Claude Code memory at `~/.claude/…/memory/`, auto-loaded by the
-harness. The store the Project-memory rule redirects project-scoped writes
-away from; it keeps cross-project and personal facts.
+The store Auto-memory manages when no redirect points it elsewhere — one
+per checkout path and per Environment, kept by default under
+`~/.claude/projects/<project>/memory/`; a default, not a definition, since
+`autoMemoryDirectory` may place it anywhere. The store the Project-memory
+rule redirects project-scoped writes away from; it keeps cross-project and
+personal facts.
 _Avoid_: native memory
 
+**Hybrid store**:
+The Private memory store that is the current session's Auto-memory
+directory — the opt-in redirect (`autoMemoryDirectory` pointing at
+`.claude/memory/`) honored in that session and landing on the store. A property of the
+session, never of the checkout: the same store may be hybrid in one
+environment and plain in another. Team memory is never one — Auto-memory's
+team mounts are server-backed, so a repo directory cannot join.
+_Avoid_: hybrid memory, hybrid mode
+
+**Environment**:
+One filesystem view a session runs in — its own path namespace, settings
+home (`~/.claude`), and trust record: the host, a dev container, a WSL
+distro. The unit the redirect activates per, and the unit each Home-dir
+memory store belongs to; one checkout may be visible from several
+environments through different absolute paths.
+_Avoid_: machine (where the path namespace is what matters)
+
 **Idea entry**:
 A Project-memory entry with the idea shape: an `idea-` filename prefix and
 lifecycle frontmatter (`status` parked → spec'd | dropped, a `spec:` pointer,
@@ -303,18 +342,18 @@ _Avoid_: backlog item
 **Archive**:
 The closed-entry record of a Project-memory part — `ARCHIVE.md`, holding one
 line per closed entry in a **Done** or **Dropped** section, read on demand and
-never at session start. Distinct from a live entry (listed in `INDEX.md`): a
+never at session start. Distinct from a live entry (listed in `MEMORY.md`): a
 closed entry keeps no body, only its archive line.
 _Avoid_: archive folder, backlog
 
 **Live entry**:
-A Project-memory entry currently listed in `INDEX.md` — an active note or a
+A Project-memory entry currently listed in `MEMORY.md` — an active note or a
 `parked` idea. The only entries reachable at session start (via the index).
 Opposite of an archived (closed) entry.
 _Avoid_: active entry, open entry
 
 **Close (an entry)**:
-Move an entry out of `INDEX.md` when it reaches a terminal state — Done (its
+Move an entry out of `MEMORY.md` when it reaches a terminal state — Done (its
 content now lives in a spec, ADR, glossary, or another artifact) or Dropped
 (abandoned) — leaving a one-line Archive record. Deleting an obsolete entry is
 NOT a close: it leaves no Archive line.