@mnemonik/cli 7.165.0 → 7.166.0

package/dist/install/ui.js

@@ -2705,13 +2705,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2721,7 +2721,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/installSession.js

@@ -878,13 +878,13 @@ import { devReadiness } from "./runtime/releaseSource.js";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -894,7 +894,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/installation.js

@@ -2705,13 +2705,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2721,7 +2721,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/launcher.js

@@ -2707,13 +2707,13 @@ import { basename as basename2, isAbsolute, join as join5, resolve as resolve2 }
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2723,7 +2723,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/preflight.js

@@ -879,13 +879,13 @@ import { join as join4 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -895,7 +895,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/project/eligibility.js

@@ -2706,13 +2706,13 @@ import { join as join5, posix as posix2, win32 as win323 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2722,7 +2722,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/project/records.js

@@ -2706,13 +2706,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2722,7 +2722,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/project.js

@@ -3183,13 +3183,13 @@ import { randomUUID as randomUUID2 } from "node:crypto";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -3199,7 +3199,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/router.js

@@ -3076,13 +3076,13 @@ import {
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -3092,7 +3092,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/runtime/releaseSource.js

@@ -2737,13 +2737,13 @@ import { readFileSync } from "node:fs";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2753,7 +2753,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/runtime/selfUpdate.js

@@ -2706,13 +2706,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2722,7 +2722,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/runtime/updateCheck.js

@@ -2705,13 +2705,13 @@ import { join as join5 } from "node:path";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2721,7 +2721,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/sbom.json

@@ -17,13 +17,13 @@
       }
     ],
     "component": {
-      "bom-ref": "@mnemonik/cli@0.1.219",
+      "bom-ref": "@mnemonik/cli@0.1.221",
       "type": "library",
       "name": "@mnemonik/cli",
-      "version": "0.1.219",
+      "version": "0.1.221",
       "scope": "required",
       "description": "Mnemonik installer and local project helper",
-      "purl": "pkg:npm/%40mnemonik/cli@0.1.219",
+      "purl": "pkg:npm/%40mnemonik/cli@0.1.221",
       "properties": [],
       "externalReferences": [
         {
@@ -274,12 +274,12 @@
       ]
     },
     {
-      "bom-ref": "@mnemonik/credentials@0.1.219",
+      "bom-ref": "@mnemonik/credentials@0.1.221",
       "type": "library",
       "name": "@mnemonik/credentials",
-      "version": "0.1.219",
+      "version": "0.1.221",
       "scope": "required",
-      "purl": "pkg:npm/%40mnemonik/credentials@0.1.219",
+      "purl": "pkg:npm/%40mnemonik/credentials@0.1.221",
       "properties": [],
       "externalReferences": [
         {
@@ -289,12 +289,12 @@
       ]
     },
     {
-      "bom-ref": "@mnemonik/local-setup@0.1.219",
+      "bom-ref": "@mnemonik/local-setup@0.1.221",
       "type": "library",
       "name": "@mnemonik/local-setup",
-      "version": "0.1.219",
+      "version": "0.1.221",
       "scope": "required",
-      "purl": "pkg:npm/%40mnemonik/local-setup@0.1.219",
+      "purl": "pkg:npm/%40mnemonik/local-setup@0.1.221",
       "properties": [],
       "externalReferences": [
         {
@@ -304,14 +304,14 @@
       ]
     },
     {
-      "bom-ref": "@mnemonik/shared@7.165.0",
+      "bom-ref": "@mnemonik/shared@7.166.0",
       "type": "library",
       "name": "@mnemonik/shared",
-      "version": "7.165.0",
+      "version": "7.166.0",
       "scope": "required",
       "author": "Anthony",
       "description": "Shared constants and utilities for Mnemonik packages",
-      "purl": "pkg:npm/%40mnemonik/shared@7.165.0",
+      "purl": "pkg:npm/%40mnemonik/shared@7.166.0",
       "properties": [],
       "externalReferences": [
         {
@@ -1187,11 +1187,11 @@
   ],
   "dependencies": [
     {
-      "ref": "@mnemonik/cli@0.1.219",
+      "ref": "@mnemonik/cli@0.1.221",
       "dependsOn": [
-        "@mnemonik/credentials@0.1.219",
-        "@mnemonik/local-setup@0.1.219",
-        "@mnemonik/shared@7.165.0",
+        "@mnemonik/credentials@0.1.221",
+        "@mnemonik/local-setup@0.1.221",
+        "@mnemonik/shared@7.166.0",
         "smol-toml@1.9.0"
       ]
     },
@@ -1246,20 +1246,20 @@
       ]
     },
     {
-      "ref": "@mnemonik/credentials@0.1.219",
+      "ref": "@mnemonik/credentials@0.1.221",
       "dependsOn": [
-        "@mnemonik/local-setup@0.1.219"
+        "@mnemonik/local-setup@0.1.221"
       ]
     },
     {
-      "ref": "@mnemonik/local-setup@0.1.219",
+      "ref": "@mnemonik/local-setup@0.1.221",
       "dependsOn": [
-        "@mnemonik/shared@7.165.0",
+        "@mnemonik/shared@7.166.0",
         "proper-lockfile@4.1.2"
       ]
     },
     {
-      "ref": "@mnemonik/shared@7.165.0",
+      "ref": "@mnemonik/shared@7.166.0",
       "dependsOn": [
         "@vue/compiler-core@3.5.44",
         "@vue/compiler-sfc@3.5.44",

package/dist/scanner/control.js

@@ -2701,13 +2701,13 @@ var require_proper_lockfile = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -2717,7 +2717,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/scanner/data.js

@@ -874,13 +874,13 @@ var require_ignore = __commonJS({
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -890,7 +890,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/scanner/discover.js

@@ -879,13 +879,13 @@ import { basename, isAbsolute, join as join4, parse, relative, resolve as resolv
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -895,7 +895,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.

package/dist/scanner/enable.js

@@ -3038,13 +3038,13 @@ import { isDeepStrictEqual } from "node:util";
 // packages/shared/dist/instructions.js
 var INSTRUCTIONS_CONTENT = `Mnemonik is your lasting memory of this project: what you decided and why, what you found, tasks and policies. If no block begins "PROJECT_CONTEXT schemaVersion=", session_bootstrap({}) loads project context; installed hooks supply the project. With that block, context is loaded and no session_bootstrap call is needed. Code and docs show current artifacts, git shows changes, and you remember why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
 
-What I learn about you belongs in Companion; what I learn about this project belongs here.
+What you learn about the user goes in Companion, your memory of the person; what you learn about this project goes here.
 
-memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
+memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs async JavaScript that calls them.
 
-Recall pages put the memories you recall in full in hydrated, pointers to more in index, how many match in extent, and the next page in cursor. Pick the ids you need before recalling whole memories; to see what else exists, ask a sharper question or follow the cursor instead of paging through whole memories.
+In a recall page, hydrated holds the memories you recall in full, index pointers to more, extent how many match, and cursor the next page. Choose ids from index before you recall memories whole; to find more, ask a sharper question or follow the cursor.
 
-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.
+Project work items live in tasks. A pending tasks list needs action:"list" and status:"pending". A complete listing combines hydrated and index and follows cursor until null.
 
 Which tool for what:
 - memory_get: recalls exact memories whole by id.
@@ -3054,7 +3054,7 @@ Which tool for what:
 - memory_links: connects related decisions so you recall them together.
 - assist: measures coverage when a recall comes back thin or empty.
 - search_summaries: finds past work by topic or date across sessions.
-- policy: stores durable enforced rules or preferences, not memories.
+- policy: stores enforced rules for this project, not memories.
 - tasks: creates follow-up work and closes completed work.
 - code_search: finds conceptual code when source wording differs.
 - memory_search: finds rationale, intent, decisions, and prior work.