@mnemonik/cli 7.138.0 → 7.139.0

package/dist/launcher.js

@@ -2661,11 +2661,13 @@ import { basename as basename2, isAbsolute, join as join5, resolve as resolve2 }
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/preflight.js

@@ -879,11 +879,13 @@ import { join as join4 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/project/eligibility.js

@@ -2660,11 +2660,13 @@ import { join as join5, posix as posix2, win32 as win323 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/project/records.js

@@ -2660,11 +2660,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/project.js

@@ -3100,11 +3100,13 @@ import { randomUUID as randomUUID2 } from "node:crypto";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/router.js

@@ -2987,11 +2987,13 @@ import {
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/runtime/releaseSource.js

@@ -2691,11 +2691,13 @@ import { readFileSync } from "node:fs";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/runtime/selfUpdate.js

@@ -2660,11 +2660,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/runtime/updateCheck.js

@@ -2659,11 +2659,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/sbom.json

@@ -17,13 +17,13 @@
       }
     ],
     "component": {
-      "bom-ref": "@mnemonik/cli@0.1.137",
+      "bom-ref": "@mnemonik/cli@0.1.139",
       "type": "library",
       "name": "@mnemonik/cli",
-      "version": "0.1.137",
+      "version": "0.1.139",
       "scope": "required",
       "description": "Mnemonik installer and local project helper",
-      "purl": "pkg:npm/%40mnemonik/cli@0.1.137",
+      "purl": "pkg:npm/%40mnemonik/cli@0.1.139",
       "properties": [],
       "externalReferences": [
         {
@@ -35,12 +35,12 @@
   },
   "components": [
     {
-      "bom-ref": "@mnemonik/credentials@0.1.137",
+      "bom-ref": "@mnemonik/credentials@0.1.139",
       "type": "library",
       "name": "@mnemonik/credentials",
-      "version": "0.1.137",
+      "version": "0.1.139",
       "scope": "required",
-      "purl": "pkg:npm/%40mnemonik/credentials@0.1.137",
+      "purl": "pkg:npm/%40mnemonik/credentials@0.1.139",
       "properties": [],
       "externalReferences": [
         {
@@ -50,12 +50,12 @@
       ]
     },
     {
-      "bom-ref": "@mnemonik/local-setup@0.1.137",
+      "bom-ref": "@mnemonik/local-setup@0.1.139",
       "type": "library",
       "name": "@mnemonik/local-setup",
-      "version": "0.1.137",
+      "version": "0.1.139",
       "scope": "required",
-      "purl": "pkg:npm/%40mnemonik/local-setup@0.1.137",
+      "purl": "pkg:npm/%40mnemonik/local-setup@0.1.139",
       "properties": [],
       "externalReferences": [
         {
@@ -65,14 +65,14 @@
       ]
     },
     {
-      "bom-ref": "@mnemonik/shared@7.138.0",
+      "bom-ref": "@mnemonik/shared@7.139.0",
       "type": "library",
       "name": "@mnemonik/shared",
-      "version": "7.138.0",
+      "version": "7.139.0",
       "scope": "required",
       "author": "Anthony",
       "description": "Shared constants and utilities for Mnemonik packages",
-      "purl": "pkg:npm/%40mnemonik/shared@7.138.0",
+      "purl": "pkg:npm/%40mnemonik/shared@7.139.0",
       "properties": [],
       "externalReferences": [
         {
@@ -271,29 +271,29 @@
   ],
   "dependencies": [
     {
-      "ref": "@mnemonik/cli@0.1.137",
+      "ref": "@mnemonik/cli@0.1.139",
       "dependsOn": [
-        "@mnemonik/credentials@0.1.137",
-        "@mnemonik/local-setup@0.1.137",
-        "@mnemonik/shared@7.138.0",
+        "@mnemonik/credentials@0.1.139",
+        "@mnemonik/local-setup@0.1.139",
+        "@mnemonik/shared@7.139.0",
         "smol-toml@1.9.0"
       ]
     },
     {
-      "ref": "@mnemonik/credentials@0.1.137",
+      "ref": "@mnemonik/credentials@0.1.139",
       "dependsOn": [
-        "@mnemonik/local-setup@0.1.137"
+        "@mnemonik/local-setup@0.1.139"
       ]
     },
     {
-      "ref": "@mnemonik/local-setup@0.1.137",
+      "ref": "@mnemonik/local-setup@0.1.139",
       "dependsOn": [
-        "@mnemonik/shared@7.138.0",
+        "@mnemonik/shared@7.139.0",
         "proper-lockfile@4.1.2"
       ]
     },
     {
-      "ref": "@mnemonik/shared@7.138.0",
+      "ref": "@mnemonik/shared@7.139.0",
       "dependsOn": [
         "ignore@7.0.12",
         "web-tree-sitter@0.27.0"

package/dist/scanner/control.js

@@ -2655,11 +2655,13 @@ var require_proper_lockfile = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/data.js

@@ -874,11 +874,13 @@ var require_ignore = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/discover.js

@@ -879,11 +879,13 @@ import { basename, isAbsolute, join as join4, parse, relative, resolve as resolv
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/enable.js

@@ -2661,11 +2661,13 @@ import { isDeepStrictEqual } from "node:util";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/picker.js

@@ -879,11 +879,13 @@ import { parse, posix as posix2, resolve } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/service.js

@@ -2655,11 +2655,13 @@ var require_proper_lockfile = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner/update.js

@@ -2655,11 +2655,13 @@ var require_proper_lockfile = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.

package/dist/scanner-release.json

@@ -1,15 +1,15 @@
 {
-  "version": "7.138.0",
-  "digestsSha256": "db77175fb1f9325f7e87cc30ad4c396ad98444ed33593853a76cc365c870672f",
+  "version": "7.139.0",
+  "digestsSha256": "2cd4b2c38790846af3123b34bccd5f76947f2be527d1eadd5e97146483ddc5d7",
   "platforms": {
     "darwin-arm64": {
       "schemaVersion": 1,
       "artifact": "scanner",
-      "version": "7.138.0",
+      "version": "7.139.0",
       "entry": "scanner-darwin-arm64",
       "files": {
         "scanner-darwin-arm64": {
-          "sha256": "2757f93e959ba76a244d7397f5e8f82462e7be3335ab95a040cc87008b0f5741",
+          "sha256": "12b3d88cc9cb571ad966141084bf52bd48772867cd557edc821262db45073712",
           "size": 154586464,
           "executable": true
         }
@@ -17,7 +17,7 @@
       "totalSize": 154586464,
       "source": {
         "kind": "release",
-        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.138.0/"
+        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.139.0/"
       },
       "signer": {
         "platform": "darwin",
@@ -29,16 +29,16 @@
     "linux-arm64": {
       "schemaVersion": 1,
       "artifact": "scanner",
-      "version": "7.138.0",
+      "version": "7.139.0",
       "entry": "scanner-linux-arm64",
       "files": {
         "scanner-linux-arm64": {
-          "sha256": "6fdc0dcb383c3c0a15bdfc78b5b9d37c7d44a25ce9783371f4358dc443103a85",
+          "sha256": "39661445acc263ec88f9b8f6077bbb6ffca2c5984c4434afc589409b0a36fb44",
           "size": 156961920,
           "executable": true
         },
         "scanner-linux-arm64.minisig": {
-          "sha256": "f7c04e1567e4fe437c902212d16fb6a3b71d1c4a29764679424f24526dedf5f3",
+          "sha256": "1442fb389d1d36cbcc5d95b94eafb532a80bec011ad0457c4d61e705c660ec7f",
           "size": 314,
           "executable": false
         }
@@ -46,7 +46,7 @@
       "totalSize": 156962234,
       "source": {
         "kind": "release",
-        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.138.0/"
+        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.139.0/"
       },
       "signer": {
         "platform": "linux",
@@ -59,16 +59,16 @@
     "linux-x64": {
       "schemaVersion": 1,
       "artifact": "scanner",
-      "version": "7.138.0",
+      "version": "7.139.0",
       "entry": "scanner-linux-x64",
       "files": {
         "scanner-linux-x64": {
-          "sha256": "764bb451afcf2c3ed8fd385367736d4a7cc603f7cf61341c08e3668bc9513a35",
+          "sha256": "eee3270ebdfbca7bcba5494ae08b47029cd35ae5461ced9fafc9574a7e28fff8",
           "size": 155192512,
           "executable": true
         },
         "scanner-linux-x64.minisig": {
-          "sha256": "3d4e32be3f34a4ede995c6bb75a9a751857f8b22131fc365fc0498829aee34df",
+          "sha256": "ccf455a2419dd05903ab2c6717c98727ba3fe26f4d1c0abd5315b11158f211da",
           "size": 312,
           "executable": false
         }
@@ -76,7 +76,7 @@
       "totalSize": 155192824,
       "source": {
         "kind": "release",
-        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.138.0/"
+        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.139.0/"
       },
       "signer": {
         "platform": "linux",
@@ -89,19 +89,19 @@
     "win-x64": {
       "schemaVersion": 1,
       "artifact": "scanner",
-      "version": "7.138.0",
+      "version": "7.139.0",
       "entry": "scanner-win-x64.exe",
       "files": {
         "scanner-win-x64.exe": {
-          "sha256": "713f0d85bb5d45ff2ba31871d9d0baa5e011597150afe96abec7cc4d71bc730d",
-          "size": 127685632,
+          "sha256": "94934100edd61e0d1378b3e4e16f99f647f4d2bd3f02ed94bbc1240ab2525d76",
+          "size": 127686656,
           "executable": true
         }
       },
-      "totalSize": 127685632,
+      "totalSize": 127686656,
       "source": {
         "kind": "release",
-        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.138.0/"
+        "url": "https://github.com/JayDeeCo-Limited/mnemonik-cli/releases/download/scanner-v7.139.0/"
       },
       "signingStatus": "unsigned",
       "disclosureVersion": "2026.09.1"

package/dist/status.js

@@ -2733,11 +2733,13 @@ import {
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik provides persistent project memory: decisions, rationale, tasks, and policies across sessions. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({ cwd }) loads project context when cwd is the real absolute path of the project root; a placeholder or relative path fails. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-memory_discover supplies exact schemas and examples for unfamiliar or action-based methods; memory_tools runs their async JavaScript.
+What I learn about you belongs in Companion; what I learn about this project belongs here.
 
-Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Relevant IDs can be selected before exact originals are hydrated; a refined query or cursor reveals more without paging full bodies merely to discover what exists.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-Project work items live in tasks. A pending list requires action:"list" and status:"pending". Each page is { hydrated, index, extent, cursor }; a complete listing combines hydrated and index and follows cursor until null.
+Retrieval pages use hydrated for complete records, index for pointer rows, extent for totals, and cursor for continuation. Select relevant IDs before hydrating originals; a refined query or cursor reveals more without paging full bodies to discover what exists.
+
+Project work items live in tasks. A pending list requires action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: hydrates exact originals by id.