memorix 1.8.3 → 1.8.5

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "memorix",
   "mcpName": "io.github.AVIDS2/memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Local-first shared memory layer for AI coding agents across MCP clients, Git history, reasoning context, and project sessions.",
   "type": "module",
   "sideEffects": false,
@@ -57,12 +57,19 @@
   ],
   "scripts": {
     "build:workspaces": "npm --workspaces --if-present run build",
-    "build": "npm run build:workspaces && node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsup",
+    "build:runtime": "tsup --config tsup.runtime.config.ts",
+    "build:cli": "tsup --config tsup.cli.config.ts",
+    "build:memcode": "tsup --config tsup.memcode.config.ts",
+    "build": "npm run build:workspaces && node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && npm run build:runtime && npm run build:cli && npm run build:memcode",
     "dev": "tsup --watch",
     "update-models": "npm --workspace @memorix/ai run update-models",
     "start": "node dist/index.js",
     "test": "vitest run --no-file-parallelism --maxWorkers=1 --minWorkers=1",
     "test:mcp-stdio-smoke": "node scripts/mcp-stdio-smoke.mjs",
+    "test:mcp-modern-stdio-smoke": "node scripts/mcp-modern-stdio-smoke.mjs",
+    "test:mcp-conformance-smoke": "node scripts/mcp-conformance-smoke.mjs",
+    "test:mcp-modern-smoke": "node scripts/mcp-modern-smoke.mjs",
+    "test:background-start-smoke": "node scripts/background-start-smoke.mjs",
     "test:watch": "vitest",
     "test:llm-live": "MEMORIX_RUN_LIVE_LLM_TESTS=1 vitest run tests/integration/formation-llm-quality.test.ts",
     "test:e2e": "vitest run tests/e2e/",
@@ -127,14 +134,11 @@
   },
   "dependencies": {
     "@clack/prompts": "^0.9.1",
+    "@modelcontextprotocol/node": "^2.0.0",
+    "@modelcontextprotocol/server": "^2.0.0",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "@orama/orama": "^3.1.0",
-    "@orama/plugin-data-persistence": "^3.1.0",
     "citty": "^0.1.6",
-    "cytoscape": "^3.33.1",
-    "cytoscape-dagre": "^2.5.0",
-    "dagre": "^0.8.5",
-    "diff": "^9.0.0",
     "dotenv": "^17.3.1",
     "gpt-tokenizer": "^2.8.0",
     "ink": "^6.8.0",
@@ -143,9 +147,6 @@
     "ink-scroll-view": "^0.3.6",
     "ink-spinner": "^5.0.0",
     "react": "19.2.7",
-    "remark": "^15.0.1",
-    "remark-stringify": "^11.0.0",
-    "undici": "8.10.0",
     "unpdf": "^1.8.0",
     "yaml": "2.9.0",
     "zod": "^3.24.0"
@@ -174,7 +175,6 @@
   },
   "devDependencies": {
     "@types/better-sqlite3": "^7.6.0",
-    "@types/diff": "^7.0.0",
     "@types/node": "^22.0.0",
     "@types/react": "19.2.7",
     "ink-testing-library": "^4.0.0",

package/plugins/antigravity/memorix/plugin.json

@@ -1,4 +1,4 @@
 {
   "name": "memorix",
-  "version": "1.8.3"
+  "version": "1.8.5"
 }

package/plugins/antigravity/memorix/rules/memorix.md

@@ -9,9 +9,14 @@ Use Memorix when prior workspace context, decisions, fixes, or handoff state wou
 - Use `memorix_search` for focused lookup.
 - Use `memorix_detail` before relying on a specific memory.
 - Use `memorix_store` for durable workspace knowledge.
+- Use `memorix_evidence` when you need to check a memory's source, freshness, or verification state.
+- Use `memorix_feedback` when a memory helped, conflicted with current evidence, or was corrected.
+- Use `memorix_media` for controlled local media import, inspection, and derivation; provider-backed generation remains explicitly gated.
 - Use `longTerm` on `memorix_store` only for a stable fact, reusable procedure, or completed episode that merits explicit review. It creates a candidate, not live context; keep the default project scope and do not use it for routine updates.
 - A `user` + `portable` durable memory in a task brief is intentionally reusable across projects. When it matches the task, use it as background even if it originated elsewhere; it is not a current-project fact. Expand it only when needed with `memorix_detail` and `typedRefs: ["durable:<id>"]`, stating the missing fact as `purpose`.
 - Use `memorix_store_reasoning` for the reason behind a technical decision.
 - Use `memorix_resolve` when completed or outdated memories should stop surfacing.
 
+The standard plugin uses the `lite` MCP profile (20 tools). Coordination and advanced tools are opt-in through `--mode team` or `--mode full`; use the CLI fallback instead of repeatedly probing unavailable tools.
+
 Do not store secrets, credentials, raw private transcripts, or trivial one-off actions.

package/plugins/claude/memorix/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Shared workspace memory for Claude Code and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/claude/memorix/skills/memorix-memory/SKILL.md

@@ -16,6 +16,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/claude/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/claude/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/codebuddy/memorix/.codebuddy-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Local-first project memory for CodeBuddy Code and other coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/codebuddy/memorix/skills/memorix-memory/SKILL.md

@@ -16,6 +16,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/codebuddy/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/codebuddy/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/codex/memorix/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Shared workspace memory for Codex and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/codex/memorix/skills/memorix-memory/SKILL.md

@@ -17,6 +17,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/codex/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/codex/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/copilot/memorix/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Shared local workspace memory for GitHub Copilot CLI and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/copilot/memorix/skills/memorix-memory/SKILL.md

@@ -17,6 +17,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/copilot/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/copilot/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/cursor/memorix/skills/memorix-memory/SKILL.md

@@ -17,6 +17,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/cursor/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/cursor/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/gemini/memorix/GEMINI.md

@@ -11,9 +11,14 @@ Use Memorix when prior workspace context, decisions, fixes, or handoff state wou
 - Use `memorix_search` for focused lookup.
 - Use `memorix_detail` before relying on a specific memory.
 - Use `memorix_store` for durable workspace knowledge.
+- Use `memorix_evidence` when you need to check a memory's source, freshness, or verification state.
+- Use `memorix_feedback` when a memory helped, conflicted with current evidence, or was corrected.
+- Use `memorix_media` for controlled local media import, inspection, and derivation; provider-backed generation remains explicitly gated.
 - Use `longTerm` on `memorix_store` only for a stable fact, reusable procedure, or completed episode that merits explicit review. It creates a candidate, not live context; keep the default project scope and do not use it for routine updates.
 - A `user` + `portable` durable memory in a task brief is intentionally reusable across projects. When it matches the task, use it as background even if it originated elsewhere; it is not a current-project fact. Expand it only when needed with `memorix_detail` and `typedRefs: ["durable:<id>"]`, stating the missing fact as `purpose`.
 - Use `memorix_store_reasoning` for the reason behind a technical decision.
 - Use `memorix_resolve` when completed or outdated memories should stop surfacing.
 
+The standard extension uses the `lite` MCP profile (20 tools). Coordination and advanced tools are opt-in through `--mode team` or `--mode full`; use the CLI fallback instead of repeatedly probing unavailable tools.
+
 Do not store secrets, credentials, raw private transcripts, or trivial one-off actions.

package/plugins/gemini/memorix/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "mcpServers": {
     "memorix": {
       "command": "memorix",

package/plugins/hermes/memorix/plugin.yaml

@@ -1,5 +1,5 @@
 name: memorix
-version: "1.8.3"
+version: "1.8.5"
 description: Shared workspace memory bridge for Hermes Agent.
 author: AVIDS2
 license: Apache-2.0
@@ -15,3 +15,9 @@ provides_cli_commands:
   - memorix
 provides_skills:
   - memorix-memory
+  - memorix-reasoning
+  - memorix-sessions
+  - memorix-git-memory
+  - memorix-mini-skills
+  - memorix-orchestrate
+  - memorix-troubleshooting

package/plugins/omp/memorix/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix-omp-package",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Memorix shared workspace memory package for Oh-my-Pi.",
   "license": "Apache-2.0",
   "keywords": [

package/plugins/openclaw/memorix/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Shared workspace memory for OpenClaw and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/pi/memorix/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix-pi-package",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "description": "Memorix shared workspace memory package for Pi coding agent.",
   "license": "Apache-2.0",
   "keywords": [

package/plugins/pi/memorix/skills/memorix-memory/SKILL.md

@@ -17,6 +17,9 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
 | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |
+| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |
+| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |
+| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |
 | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |
 | Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |
 | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |

package/plugins/pi/memorix/skills/memorix-mini-skills/SKILL.md

@@ -7,6 +7,8 @@ description: Use when durable project knowledge, gotchas, workflows, or repeated
 
 Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
 
+The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/plugins/pi/memorix/skills/memorix-orchestrate/SKILL.md

@@ -7,6 +7,8 @@ description: Use when a main agent needs Memorix to coordinate explicit subagent
 
 Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
 
+The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
+
 ## Tool Router
 
 | Situation | Prefer | CLI fallback |

package/server.json

@@ -7,7 +7,7 @@
     "url": "https://github.com/AVIDS2/memorix",
     "source": "github"
   },
-  "version": "1.8.3",
+  "version": "1.8.5",
   "websiteUrl": "https://github.com/AVIDS2/memorix#readme",
   "icons": [
     {
@@ -22,7 +22,7 @@
     {
       "registryType": "npm",
       "identifier": "memorix",
-      "version": "1.8.3",
+      "version": "1.8.5",
       "runtimeHint": "npx",
       "packageArguments": [
         {

package/src/cli/command-guide.ts

@@ -61,6 +61,10 @@ const GUIDES: Record<string, CliCommandGuide> = {
     usage: [
       'memorix codegraph status',
       'memorix codegraph refresh',
+      'memorix codegraph init',
+      'memorix codegraph sync',
+      'memorix codegraph diff [--from <snapshot>] [--to <snapshot>]',
+      'memorix codegraph impact --path <relative-source-path>',
       'memorix codegraph context-pack --task "trace the auth flow" [--limit 20]',
     ],
   },
@@ -79,10 +83,57 @@ const GUIDES: Record<string, CliCommandGuide> = {
     usage: [
       'memorix knowledge init [--mode local|versioned]',
       'memorix knowledge status',
+      'memorix knowledge claims',
+      'memorix knowledge review --id <claim-id> --review approved|rejected --detail "..."',
       'memorix knowledge compile',
       'memorix knowledge lint',
-      'memorix knowledge workflow list',
+      'memorix knowledge apply --proposal <id> [--force]',
+      'memorix knowledge workflow import|list',
+      'memorix knowledge workflow select --task "prepare a release"',
+      'memorix knowledge workflow preview|apply --id <workflow-id> --agent codex',
+      'memorix knowledge workflow run --id <workflow-id> --task "..." --outcome passed',
     ],
+    notes: ['Claims need source review before they can become maintained Knowledge Workspace pages.'],
+  },
+  evidence: {
+    summary: 'Inspect the source, freshness, and verification state behind project memories.',
+    usage: [
+      'memorix evidence list [--query "auth"] [--limit 20]',
+      'memorix evidence get --id 42',
+      'memorix evidence sync',
+      'memorix evidence stale --paths src/server.ts,tests/server.test.ts --reason "source changed"',
+      'memorix evidence events --id 42',
+    ],
+    notes: ['Evidence cards point back to observations and source files; they are not a second memory store.'],
+  },
+  feedback: {
+    summary: 'Record and inspect whether a memory helped, conflicted, or was corrected.',
+    usage: [
+      'memorix feedback record --id 42 --signal verification-success --source test:run-1',
+      'memorix feedback show --id 42',
+      'memorix feedback audit --id 42 [--limit 100]',
+    ],
+    notes: ['Feedback changes the candidate score through an auditable event; it does not rewrite the original memory.'],
+  },
+  formation: {
+    summary: 'Inspect Memory Formation quality metrics collected by the runtime.',
+    usage: ['memorix formation metrics'],
+    notes: ['Metrics are empty until the formation pipeline has processed observations.'],
+  },
+  media: {
+    summary: 'Import, inspect, derive, embed, and clean controlled local media assets.',
+    usage: [
+      'memorix media import --path ./diagram.png',
+      'memorix media attach --asset <asset-id> --title "Architecture diagram"',
+      'memorix media list --kind image',
+      'memorix media show --asset <asset-id>',
+      'memorix media derive-pdf|derive-audio --asset <asset-id> [--attach]',
+      'memorix media embed|similar --asset <asset-id>',
+      'memorix media generate image|video --prompt "..."',
+      'memorix media status|cancel --job <media-job-id>',
+      'memorix media cleanup [--max-bytes <limit>]',
+    ],
+    notes: ['Media generation is explicit and provider-gated; importing a file does not automatically send it to a model.'],
   },
   reasoning: {
     summary: 'Capture and retrieve engineering decision rationale.',