@arvoretech/hub 0.21.0 → 0.22.0

package/dist/{chunk-KRYKCNRK.js → chunk-QLFFIFIE.js}

@@ -117,7 +117,7 @@ async function checkAndAutoRegenerate(hubDir) {
       return;
     }
     console.log(chalk.yellow("\n  Detected outdated configs, auto-regenerating..."));
-    const { generators: generators2 } = await import("./generate-ZH3P5EB4.js");
+    const { generators: generators2 } = await import("./generate-3KUUBRXF.js");
     const generator = generators2[result.editor];
     if (!generator) {
       console.log(chalk.red(`  Unknown editor '${result.editor}' in cache. Run 'hub generate' manually.`));
@@ -1791,21 +1791,15 @@ function buildMemorySection(config) {
 ## Team Memory \u2014 MANDATORY
 
 This workspace has a team memory knowledge base via the \`team-memory\` MCP.
+The MCP automatically generates a steering file (\`team-memories-index\`) with an index of all active memories. This file is always included in your context.
 
-**YOU MUST consult memory at the START of EVERY interaction.** This is not optional.
+**Use the index first.** You already know what memories exist \u2014 check the steering file before calling any MCP tool.
 
-### On every message from the user:
-1. Extract the key topics, entities, and domain terms from the user's request
-2. Run \`search_memories\` with relevant keywords BEFORE doing anything else
-3. If memories are found, factor them into your response \u2014 they may contain past decisions, conventions, known issues, or domain context that directly affects the current task
-4. If no relevant memories are found, proceed normally
-
-### Before calling tools:
-When you are about to use a tool that interacts with external systems (database queries, API calls, git operations, deployments, file modifications in specific domains), do a quick \`search_memories\` for the relevant entity or system first. There may be a memory about:
-- Schema changes, migrations, or known issues with that table/endpoint
-- Conventions for how that system should be used
-- Past incidents or gotchas that affect the operation you're about to perform
-This does NOT apply to simple read/search tools \u2014 use judgment on when a memory check adds value.
+### How to use memories:
+1. **Read the index** \u2014 the \`team-memories-index\` steering file lists all active memories with title, category, tags, and ID
+2. **Get full content** \u2014 use \`get_memory(id)\` when you need the complete context of a specific memory
+3. **Semantic search** \u2014 use \`search_memories\` only when you need fuzzy/semantic matching beyond what the index shows
+4. **Capture knowledge** \u2014 use \`add_memory\` when you discover decisions, conventions, gotchas, or domain insights during work
 
 ### When completing work:
 - If you discovered something valuable (a decision, a gotcha, a convention, a domain insight, a debugging finding), use \`add_memory\` to capture it
@@ -1824,8 +1818,9 @@ Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_mem
 ## Team Memory
 
 This workspace has a team memory knowledge base available via the \`team-memory\` MCP.
+The MCP automatically generates a steering file (\`team-memories-index\`) with an index of all active memories.
 
-**Before starting any task**, use \`search_memories\` to find relevant context \u2014 past decisions, conventions, known issues, and domain knowledge. This avoids repeating mistakes and ensures consistency with previous choices.
+**Check the index first** \u2014 use \`get_memory(id)\` for full content, and \`search_memories\` only for semantic search beyond the index.
 
 **After completing a task**, if you discovered something valuable (a decision, a gotcha, a convention, domain insight), use \`add_memory\` to capture it for the team.
 

package/dist/{generate-ZH3P5EB4.js → generate-3KUUBRXF.js}

@@ -1,7 +1,7 @@
 import {
   generateCommand,
   generators
-} from "./chunk-KRYKCNRK.js";
+} from "./chunk-QLFFIFIE.js";
 import "./chunk-VMN4KGAK.js";
 export {
   generateCommand,

package/dist/index.js

@@ -6,7 +6,7 @@ import {
   horizontalLine,
   personaCommand,
   symbols
-} from "./chunk-KRYKCNRK.js";
+} from "./chunk-QLFFIFIE.js";
 import {
   loadHubConfig,
   resolveConfigPath

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arvoretech/hub",
-  "version": "0.21.0",
+  "version": "0.22.0",
   "description": "CLI for managing AI-aware multi-repository workspaces",
   "main": "dist/index.js",
   "type": "module",