memoryintel 1.0.1 → 1.0.2

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Persistent, cross-session project memory for AI coding agents.",
-    "version": "1.0.1"
+    "version": "1.0.2"
   },
   "plugins": [
     {
       "name": "memoryintel",
       "source": "./",
       "description": "Persistent project memory for AI coding agents — initialize once, then agents automatically load and update project understanding across sessions.",
-      "version": "1.0.1"
+      "version": "1.0.2"
     }
   ]
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "memoryintel",
   "description": "Persistent project memory for AI coding agents — initialize once, then agents automatically load and update project understanding across sessions.",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "author": {
     "name": "Adeesh Sharma",
     "url": "https://github.com/adeeshsharma"

package/dist/adapters/genericPointer.js

@@ -3,10 +3,19 @@ import { join } from 'node:path';
 const START_MARKER = '<!-- memoryintel:managed:start -->';
 const END_MARKER = '<!-- memoryintel:managed:end -->';
 const POINTER_BLOCK = `${START_MARKER}
-This project uses Memory Intel. At the start of a session, run \`memoryintel load\` and treat its
-output as project context. Before finishing a task with a meaningful change (new architecture,
-feature, decision, integration, or roadmap item — not formatting/typos), draft an update-plan per
-\`.memoryintel/instructions.md\` and run \`memoryintel update\`, without narrating this to the user.
+This project uses Memory Intel (\`.memoryintel/\`) for persistent, cross-session project memory.
+Read \`.memoryintel/instructions.md\` for the full mechanism. Two hard requirements, not optional
+background context:
+
+1. **Session start:** run \`memoryintel load\` before doing anything else and treat its output as
+   real project context, not a formality to skip past.
+2. **Before ending any task that changed project understanding** (new architecture, feature,
+   decision, integration, or roadmap item — not formatting/typos): draft an update-plan and run
+   \`memoryintel update <plan-file>\`. This applies even in a long session covering many sub-tasks —
+   that is exactly when it is easiest to reach the end and have forgotten this step was ever
+   pending. If nothing meaningful changed, skip it; do not skip it just because the task grew long.
+
+Tell the user when you do this — do not do it silently.
 ${END_MARKER}`;
 function upsertPointerBlock(filePath, existingContentIfNew) {
     if (!existsSync(filePath)) {

package/dist/commands/init.js

@@ -58,6 +58,24 @@ on a real project: a "known limitation, deliberately left unfixed" entry was sti
 \`currentMentalModel.md\`, but never reconciled against the older, now-wrong decisions entry right
 next to it.
 
+## Committing \`.memoryintel/\` itself
+\`.memoryintel/\` is a normal, git-committed part of the project — \`memoryintel update\` only writes
+files to disk, it never runs git for you. After a successful \`update\`, commit \`.memoryintel/\`'s
+changes yourself, ideally in the same commit as (or immediately after) whatever code change
+prompted the update, so it travels with the same commit/PR automatically instead of being left
+behind as an uncommitted diff.
+
+This matters most in a git worktree, a container, or any other isolated checkout: an uncommitted
+\`.memoryintel/\` change only exists in that one working directory. Merging a feature branch's PR and
+pulling the primary checkout up to date only brings memory updates along if they were actually
+committed first, the same as any other file — there is nothing worktree-specific about the
+mechanism itself, only that a worktree's own uncommitted state is easier to lose track of, since it
+is invisible everywhere else once the session ends and that directory stops being looked at. Found
+on a real project: a full feature built end-to-end in a worktree, with real, meaningful
+architecture changes throughout, reached a merged PR with \`.memoryintel/\` never once updated or
+committed — not because updating was hard, but because nothing in the session ever came back to it
+before the worktree's job was considered done.
+
 ## Compaction
 A file marked \`status: over\` in \`load\`'s manifest has grown past its configured line ceiling.
 This is a signal, not a command — compact it only when it's a sensible moment to (the same

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memoryintel",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Persistent, cross-session project memory for AI coding agents.",
   "type": "module",
   "bin": {