@arvoretech/hub 0.20.0 → 0.22.0

package/dist/{chunk-FMBCFOVH.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-J6FNJF7F.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.`));
@@ -1761,6 +1761,71 @@ Additional context sources:
 - Use monitoring MCPs for production debugging and log analysis when available`);
   return parts.join("\n");
 }
+function buildFetchCheckerSection() {
+  return `
+## Fact Checker \u2014 Mandatory Verification
+
+**NEVER state the status of any external resource without verifying it first.**
+
+Before making ANY claim about:
+- PR status (merged, open, closed, approved, changes requested)
+- Branch state (ahead, behind, conflicts, existence)
+- Deploy status (deployed, failed, in progress)
+- CI/CD pipeline results (passed, failed, running)
+- Issue/task status (open, closed, in progress)
+- Service health (up, down, degraded)
+- Any other external state that can change over time
+
+You MUST:
+1. Use the appropriate tool to check the actual current state (GitHub CLI, MCP tools, git commands, etc.)
+2. Only THEN report the result to the user
+3. If you cannot verify, explicitly say "I was unable to verify this \u2014 please check manually"
+
+**NEVER assume, guess, or rely on cached/stale information.** Every claim about external state must be backed by a fresh check.
+This applies to ALL agents in the pipeline, not just the orchestrator.`;
+}
+function buildMemorySection(config) {
+  const enforce = config.memory?.enforce ?? false;
+  if (enforce) {
+    return `
+## 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.
+
+**Use the index first.** You already know what memories exist \u2014 check the steering file before calling any MCP tool.
+
+### 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
+- Be specific: include context, rationale, and affected areas
+- Use appropriate categories: decisions, conventions, incidents, domain, gotchas
+
+### Why this matters:
+- Memories contain institutional knowledge that prevents repeated mistakes
+- Past decisions explain WHY things are the way they are
+- Conventions ensure consistency across the team
+- Gotchas save hours of debugging
+
+Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_memories\`, \`archive_memory\`, \`remove_memory\`.`;
+  }
+  return `
+## 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.
+
+**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.
+
+Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_memories\`, \`archive_memory\`, \`remove_memory\`.`;
+}
 function buildCoreBehaviorSections() {
   const sections = [];
   sections.push(`
@@ -1909,16 +1974,10 @@ ${prompt.sections.after_delivery.trim()}`);
     sections.push(mcpToolsSectionOpenCode);
   }
   if (config.memory) {
-    sections.push(`
-## Team Memory
-
-This workspace has a team memory knowledge base available via the \`team-memory\` MCP.
-
-**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.
-
-**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.
-
-Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_memories\`, \`archive_memory\`, \`remove_memory\`.`);
+    sections.push(buildMemorySection(config));
+  }
+  if (config.workflow?.fact_checker) {
+    sections.push(buildFetchCheckerSection());
   }
   const designSectionOpenCode = buildDesignSection(config);
   if (designSectionOpenCode) sections.push(designSectionOpenCode);
@@ -2234,16 +2293,10 @@ ${prompt.sections.after_delivery.trim()}`);
     sections.push(mcpToolsSectionKiro);
   }
   if (config.memory) {
-    sections.push(`
-## Team Memory
-
-This workspace has a team memory knowledge base available via the \`team-memory\` MCP.
-
-**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.
-
-**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.
-
-Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_memories\`, \`archive_memory\`, \`remove_memory\`.`);
+    sections.push(buildMemorySection(config));
+  }
+  if (config.workflow?.fact_checker) {
+    sections.push(buildFetchCheckerSection());
   }
   const designSectionKiro = buildDesignSection(config);
   if (designSectionKiro) sections.push(designSectionKiro);
@@ -2429,16 +2482,10 @@ ${prompt.sections.after_delivery.trim()}`);
     sections.push(mcpToolsSectionCursor);
   }
   if (config.memory) {
-    sections.push(`
-## Team Memory
-
-This workspace has a team memory knowledge base available via the \`team-memory\` MCP.
-
-**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.
-
-**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.
-
-Available tools: \`search_memories\`, \`get_memory\`, \`add_memory\`, \`list_memories\`, \`archive_memory\`, \`remove_memory\`.`);
+    sections.push(buildMemorySection(config));
+  }
+  if (config.workflow?.fact_checker) {
+    sections.push(buildFetchCheckerSection());
   }
   const designSectionCursor = buildDesignSection(config);
   if (designSectionCursor) sections.push(designSectionCursor);

package/dist/config/index.d.ts

@@ -115,6 +115,7 @@ interface MemoryConfig {
     categories?: string[];
     auto_capture?: boolean;
     embedding_model?: string;
+    enforce?: boolean;
 }
 interface RemoteSource {
     name: string;
@@ -163,6 +164,7 @@ interface HubConfig {
         pipeline?: WorkflowStep[];
         prompt?: PromptCustomization;
         enforce_workflow?: boolean;
+        fact_checker?: boolean;
     };
 }
 

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

@@ -1,7 +1,7 @@
 import {
   generateCommand,
   generators
-} from "./chunk-FMBCFOVH.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-FMBCFOVH.js";
+} from "./chunk-QLFFIFIE.js";
 import {
   loadHubConfig,
   resolveConfigPath

package/package.json

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