@mnemonik/cli 7.164.2 → 7.164.4

package/dist/install/ownership.js

@@ -2706,23 +2706,23 @@ import { readUpdateCheck } from "../runtime/updateCheck.js";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/install/transaction.js

@@ -2703,23 +2703,23 @@ import { createCliAuth } from "../auth/index.js";
 import { createCliCredentials } from "../auth/credentials.js";
 
 // 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/install/ui.js

@@ -2703,23 +2703,23 @@ import { humanReport } from "../humanReason.js";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/installSession.js

@@ -876,23 +876,23 @@ import { humanReason, humanReport } from "./humanReason.js";
 import { devReadiness } from "./runtime/releaseSource.js";
 
 // 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/installation.js

@@ -2703,23 +2703,23 @@ import { mkdir as mkdir2 } from "node:fs/promises";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/launcher.js

@@ -2705,23 +2705,23 @@ import { homedir as homedir3 } from "node:os";
 import { basename as basename2, isAbsolute, join as join5, resolve as resolve2 } 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/preflight.js

@@ -877,23 +877,23 @@ import { homedir as homedir2 } from "node:os";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/project/eligibility.js

@@ -2704,23 +2704,23 @@ import { homedir as homedir3, tmpdir } from "node:os";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/project/records.js

@@ -2704,23 +2704,23 @@ import { readFile as readFile2, readdir, unlink as unlink2 } from "node:fs/promi
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/project.js

@@ -3181,23 +3181,23 @@ import { basename as basename3, join as join8 } from "node:path";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/router.js

@@ -3074,23 +3074,23 @@ import {
 } from "./scanner/service.js";
 
 // 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/runtime/releaseSource.js

@@ -2735,23 +2735,23 @@ import { readFile as readFile2, realpath } from "node:fs/promises";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/runtime/selfUpdate.js

@@ -2704,23 +2704,23 @@ import { readFile as readFile2 } from "node:fs/promises";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/runtime/updateCheck.js

@@ -2703,23 +2703,23 @@ import { readFile as readFile2 } from "node:fs/promises";
 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({}) 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 memory carries the why; memory_search recalls rationale or intent, then Grep or Read verifies current source.
+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.
 
 memory_discover supplies exact schemas and examples for unfamiliar methods; memory_tools runs their async JavaScript.
 
-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.
+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.
 
 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.
-- memory_add: records an experience: a decision and why, what the user said, what you found.
+- memory_get: recalls exact memories whole by id.
+- memory_add: memorizes an experience: a decision and why, what the user said, what you found.
 - memory_state: corrects wrong, outdated, or conflicting memory.
 - memory_info: explains confidence or origin when memory looks suspect.
-- memory_links: connects related decisions so they surface together.
-- assist: measures coverage when search results are thin or empty.
+- 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.
 - tasks: creates follow-up work and closes completed work.

package/dist/sbom.json

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