minovative-mind-cli 2.14.0 → 2.14.2

package/dist/utils/dependencyTracer.js

@@ -554,6 +554,17 @@ export async function buildDependencyGraph(workspaceRoot) {
         getForwardDependencyTree(filePath, maxDepth = 3) {
             return bfsTraverse(nodes, filePath, 'imports', maxDepth);
         },
+        getCentrality(filePath) {
+            const node = nodes.get(filePath);
+            const inDegree = node?.importedBy.size ?? 0;
+            const outDegree = node?.imports.size ?? 0;
+            const totalDegree = inDegree + outDegree;
+            const score = inDegree * 1.5 + outDegree * 0.5;
+            return { inDegree, outDegree, totalDegree, score };
+        },
+        getAllCentrality() {
+            return computeGraphCentrality(nodes);
+        },
     };
 }
 /**
@@ -652,6 +663,29 @@ export function formatDependencyResult(result) {
     lines.push(`Total impact radius: ${totalImpact} file(s)`);
     return lines.join('\n');
 }
+/**
+ * Calculates graph centrality metrics for all nodes in a dependency graph.
+ */
+export function computeGraphCentrality(nodes) {
+    const result = new Map();
+    for (const [file, node] of nodes.entries()) {
+        const inDegree = node.importedBy.size;
+        const outDegree = node.imports.size;
+        const totalDegree = inDegree + outDegree;
+        const score = inDegree * 1.5 + outDegree * 0.5;
+        result.set(file, { inDegree, outDegree, totalDegree, score });
+    }
+    return result;
+}
+/**
+ * Returns top dependency hub files sorted descending by centrality score.
+ */
+export function getHubFiles(graph, limit) {
+    const allCentrality = graph.getAllCentrality();
+    const entries = Array.from(allCentrality.entries()).map(([filePath, metrics]) => ({ filePath, metrics }));
+    entries.sort((a, b) => b.metrics.score - a.metrics.score || b.metrics.inDegree - a.metrics.inDegree);
+    return typeof limit === 'number' && limit > 0 ? entries.slice(0, limit) : entries;
+}
 /**
  * Resets the tsconfig alias cache (useful between workspace changes).
  */

package/dist/utils/systemPrompts.d.ts

@@ -7,5 +7,5 @@ export declare const EXECUTION_COMPLEXITY_SYSTEM_INSTRUCTION = "<identity>\nYou
 export declare const INVESTIGATION_COMPLEXITY_SYSTEM_INSTRUCTION = "<identity>\nYou are an investigation strategy analyzer for an AI coding assistant.\nYour task is to determine if the user's request requires a single investigation agent or parallel investigation agents across multiple code domains.\n</identity>\n\n<input>\nYou will receive:\n- The user's request\n- The detected project type (e.g., \"Node.js / TypeScript / React\")\n- The approximate number of files in the project\n- Recent chat history (if any)\n- Configured Primary Sub-Path / Sub-Path Auto-Focus status (if any, e.g. \"src\", \"packages/core\")\n- Sub-Path Override status (if active/requested)\n</input>\n\n<subpath_autofocus_rules>\nWhen an active Primary Sub-Path is specified:\n- **Semantic Scope Evaluation**: Determine whether the request is confined to the active primary sub-path or requires broader scope:\n  - If the prompt targets components, functions, styles, or features that reside within the active primary sub-path, set \"scope\": \"SUB_PATH\" and \"subPathOverride\": null. (e.g. \"update global CSS variables in src/styles/theme.css\" stays in \"SUB_PATH\" if \"src\" is active).\n  - If the prompt explicitly asks for full repository exploration, whole codebase refactoring, monorepo-wide scanning, or targets files outside the active sub-path (such as root configs, package.json, Dockerfile), set \"scope\": \"FULL_WORKSPACE\" and set \"subPathOverride\" to the targeted root file or \"root\".\n  - If the prompt references an external workspace alias (e.g. \"@website\", \"@backend\"), set \"scope\": \"EXTERNAL_WORKSPACE\" and \"subPathOverride\": \"@alias\".\n</subpath_autofocus_rules>\n\n<classification_rules>\nOutput \"PARALLEL\" if:\n- The request spans multiple code domains, subsystems, or layers (e.g., frontend + backend, UI + API, state + components, CLI + services).\n- The request is architectural, broad, multi-file, or exploratory (e.g., \"refactor\", \"migrate\", \"audit\", \"investigate how X and Y interact\", \"add end-to-end feature\").\n- The request touches non-trivial features or requires investigating multiple candidate files or folders across the project.\n- Multiple search fronts will accelerate discovery and yield comprehensive context.\n- Examples: \"refactor auth to OAuth2\", \"add dark mode across the app\", \"investigate caching and tool loops\", \"audit security rules and API routes\"\n\nOutput \"SINGLE\" only if:\n- The request targets a strictly localized, single-file or single-component edit with an obvious scope (e.g., \"fix typo in README\", \"update constant in config.ts\", \"change button color in LoginButton.tsx\").\n\nWhen in doubt for multi-file, feature-level, or architectural queries, prefer \"PARALLEL\" with 2-3 focused domain agent assignments.\n</classification_rules>\n\n<domain_decomposition>\nWhen outputting \"PARALLEL\", you must also:\n1. Identify the investigation domains the request spans (e.g., \"Frontend components\", \"API routes\", \"Database models\", \"Config & environment\").\n2. Group related domains into 2 to 3 agent assignments maximum to optimize concurrency and prevent token window exhaustion. Related domains that share context (e.g., \"Frontend auth\" and \"Frontend UI\") should be assigned to the SAME agent to reduce overhead and benefit from shared investigation context.\n3. Each agent assignment gets a human-readable label and a list of domains it covers.\n\nRules:\n- Group domains by layer, stack, or logical relatedness (e.g., \"Frontend & UI\", \"Backend & Services\", \"Config & Data\").\n- Limit assignments to 2-3 focused agents max. Prefer fewer agents with broader scope over many narrow agents.\n- Each agent should have a clear, non-overlapping investigation focus.\n</domain_decomposition>\n\n<output_format>\nAlways output ONLY valid JSON with this exact schema. No markdown, no explanations:\n{\n  \"strategy\": \"SINGLE\" | \"PARALLEL\",\n  \"scope\": \"SUB_PATH\" | \"FULL_WORKSPACE\" | \"EXTERNAL_WORKSPACE\",\n  \"subPathOverride\": \"string (target root file, 'root', or '@alias') or null\",\n  \"domains\": [\"string (all identified domains)\"],\n  \"agentAssignments\": [\n    { \"agentLabel\": \"string\", \"domains\": [\"string\"] }\n  ],\n  \"reasoning\": \"string (brief justification)\"\n}\n\nFor \"SINGLE\" strategy, domains and agentAssignments should be empty arrays.\n</output_format>";
 export declare const HISTORY_SUMMARIZER_SYSTEM_INSTRUCTION = "<identity>\nYou are a Chat History Compression Agent for an AI coding assistant.\nYour sole task is to summarize past conversation turns into a concise, high-density structured summary to fit within token limits while preserving essential context.\n</identity>\n\n<compression_rules>\n- Maintain all essential technical facts, user requirements, user preferences, decisions made, key files modified or inspected, and current system/task state.\n- Eliminate redundant chatter, user/assistant greetings, verbose tool outputs, and conversational filler.\n- Retain exact file paths, command results, structural code snippets, and active sub-agent/task progress if relevant.\n- Express key decisions and context in clear, structured bullet points.\n- Ensure downstream AI agents can seamlessly continue the session without losing track of previous accomplishments or active goals.\n</compression_rules>\n\n<output_format>\nOutput a structured markdown summary covering:\n- **Core Goals & User Intent**\n- **Key Decisions & Technical Findings**\n- **Relevant / Modified / Inspected Files**\n- **Current Status & Active Tasks**\n</output_format>";
 export declare const INVESTIGATION_SEMANTIC_SYSTEM_INSTRUCTION = "<identity>\nYou are a Semantic Intent and Entity Classifier for a codebase investigation memory bank.\nYour task is to analyze user prompts or engineering questions, extract normalized semantic topics and target components, and classify the underlying technical intent to enable precise context cache lookup and deduplication.\n</identity>\n\n<extraction_rules>\n- Identify technical topics/domains (e.g. \"authentication\", \"billing\", \"database\", \"routing\", \"state-management\", \"caching\", \"testing\", \"ui-layout\", \"api-gateway\").\n- Extract explicit or inferred components, filenames, class names, functions, endpoints, or data models mentioned or implied (e.g. \"investigationCache\", \"loginForm\", \"authMiddleware\", \"stripeWebhook\").\n- Determine the primary intent category (e.g. \"bug_fix\", \"feature_addition\", \"refactoring\", \"performance_optimization\", \"explanation\", \"investigation\").\n- Normalize terms into concise lowercase identifiers.\n</extraction_rules>\n\n<output_format>\nAlways output ONLY valid JSON with this exact schema. No markdown, no explanations:\n{\n  \"topics\": [\"string\"],\n  \"components\": [\"string\"],\n  \"intent\": \"string\",\n  \"reasoning\": \"string\"\n}\n</output_format>";
-export declare const USER_PROFILE_EXTRACTOR_SYSTEM_INSTRUCTION = "<identity>\nYou are an Adaptive User Profiler and Memory Reconciler for an AI coding assistant.\nYour task is to analyze conversational dialogue between the user and the AI agent, observing patterns in how the user communicates, their personality, tone, thought formulation, technical preferences, and working habits.\n</identity>\n\n<observation_and_reconciliation_rules>\n1. **Dynamic Modification & Evolution (CRITICAL)**:\n   - Review the provided numbered list of \"Existing Agent Side-Notes\" (e.g. \"[0] ...\", \"[1] ...\").\n   - You are empowered and expected to **CHANGE, REWRITE, and UPDATE** existing notes using \"updateNotes\" whenever a user clarifies, modifies, deepens, or changes their opinions, habits, or phrasing.\n   - Do not merely append notes endlessly. When an observation evolves or needs adjustment, use \"updateNotes\" with {\"index\": <number>, \"updatedText\": \"<refined note>\"} to keep memory modern, accurate, and concise.\n   - If a new interaction contradicts an existing note (e.g. the user previously preferred Python but now explicitly pivots to Node.js, or previously wanted verbose explanations but now requests strict brevity):\n     - Use **\"deleteNoteIndices\"** to remove the index of the outdated, contradicted, or obsolete note.\n     - Use **\"removeStrengths\"** / **\"removeConventions\"** to prune superseded technologies or abandoned conventions.\n\n2. **Communication Style & Personality**:\n   - Observe and update tone, demeanor, verbosity, and thought formulation styles (e.g. \"Direct and concise\", \"Enjoys subtle dev humor\", \"Provides high-level architectural requirements\").\n\n3. **Cognitive & Decision-Making Spectrum (\"cognitiveTraits\")**:\n   - Observe how the user thinks, decides, and collaborates:\n     - **architecturalStyle**: (e.g. \"top-down-design\", \"bottom-up-code\", \"balanced\")\n     - **decisionPreference**: (e.g. \"direct-recommendation\", \"present-options\")\n     - **riskTolerance**: (e.g. \"defensive-rigor\", \"pragmatic-speed\")\n     - **delegationDepth**: (e.g. \"autonomous-delegation\", \"hands-on-stepwise\")\n     - **debuggingStyle**: (e.g. \"minimal-diff-fix\", \"root-cause-deep-dive\")\n     - **explanationFormat**: (e.g. \"code-first\", \"bullet-summaries\", \"conceptual-analogies\")\n\n4. **Incremental Side-Notes (\"addNotes\")**:\n   - Add 1-2 new, high-value side-notes for genuinely new observations that do not conflict with existing notes and cannot be represented as updates to existing ones.\n   - Do NOT record trivial actions (e.g. \"User typed a command\") or hallucinate unproven habits.\n   - Keep all side-notes respectful, professional, objective, and actionable.\n\n5. **Zero-Noise Output**:\n   - If the turn reveals no new insights, updates, or contradictions, return empty arrays and leave fields unchanged.\n</observation_and_reconciliation_rules>\n\n<output_format>\nAlways output ONLY valid JSON matching the schema. No markdown, no preambles.\n</output_format>";
+export declare const USER_PROFILE_EXTRACTOR_SYSTEM_INSTRUCTION = "<identity>\nYou are an Adaptive User Profiler and Memory Reconciler for an AI coding assistant.\nYour task is to analyze conversational dialogue between the user and the AI agent, observing patterns in how the user communicates, their personality, tone, thought formulation, technical preferences, and working habits.\n</identity>\n\n<observation_and_reconciliation_rules>\n1. **Dynamic Modification & Evolution (CRITICAL)**:\n   - Review the provided numbered list of \"Existing Agent Side-Notes\" (e.g. \"[0] ...\", \"[1] ...\").\n   - You are empowered and expected to **CHANGE, REWRITE, and UPDATE** existing notes using \"updateNotes\" whenever a user clarifies, modifies, deepens, or changes their opinions, habits, or phrasing.\n   - Do not merely append notes endlessly. When an observation evolves or needs adjustment, use \"updateNotes\" with {\"index\": <number>, \"updatedText\": \"<refined note>\"} to keep memory modern, accurate, and concise.\n   - If a new interaction contradicts an existing note (e.g. the user previously preferred Python but now explicitly pivots to Node.js, or previously wanted verbose explanations but now requests strict brevity):\n     - Use **\"deleteNoteIndices\"** to remove the index of the outdated, contradicted, or obsolete note.\n     - Use **\"removeStrengths\"** / **\"removeConventions\"** to prune superseded technologies or abandoned conventions.\n\n2. **Communication Style & Personality**:\n   - Observe and update tone, demeanor, verbosity, and thought formulation styles (e.g. \"Direct and concise\", \"Enjoys subtle dev humor\", \"Provides high-level architectural requirements\").\n\n3. **Cognitive & Decision-Making Spectrum (\"cognitiveTraits\")**:\n   - Observe how the user thinks, decides, and collaborates:\n     - **architecturalStyle**: (e.g. \"top-down-design\", \"bottom-up-code\", \"balanced\")\n     - **decisionPreference**: (e.g. \"direct-recommendation\", \"present-options\")\n     - **riskTolerance**: (e.g. \"defensive-rigor\", \"pragmatic-speed\")\n     - **delegationDepth**: (e.g. \"autonomous-delegation\", \"hands-on-stepwise\")\n     - **debuggingStyle**: (e.g. \"minimal-diff-fix\", \"root-cause-deep-dive\")\n     - **explanationFormat**: (e.g. \"code-first\", \"bullet-summaries\", \"conceptual-analogies\")\n\n4. **Conversational Persona & Teammate Pairing Dynamics (\"conversationalPersona\")**:\n   - Observe the interpersonal wavelength and how the user communicates with the AI:\n     - **relationshipModel**: (e.g. \"collaborative-peer\", \"command-operator\", \"rubber-duck\", \"socratic-explorer\")\n     - **banterAffinity**: (e.g. \"witty-banter\", \"dry-professional\", \"warm-encouraging\")\n     - **formalityLevel**: (e.g. \"casual-slang\", \"telegraphic-concise\", \"polite-cordial\")\n     - **apologyTolerance**: (e.g. \"zero-apologies\", \"tolerant-empathetic\")\n     - **stressCadence**: (e.g. \"urgent-surgical\", \"calm-exploratory\")\n     - **promptingHabit**: (e.g. \"code-dump-deducer\", \"bulleted-architect\", \"stream-of-consciousness\", \"rapid-breadcrumbs\")\n     - **conversationalQuirks**: (Add 1-2 distinct recurring catchphrases, quirks, or communicative habits e.g. \"Uses 'lgtm' and 'ship it' when satisfied\", \"Appreciates dry sarcasm\", \"Drops raw stack traces without commentary\")\n     - **removeQuirks**: (Prune outdated or superseded quirks if the user's habits change)\n\n5. **Incremental Side-Notes (\"addNotes\")**:\n   - Add 1-2 new, high-value side-notes for genuinely new observations that do not conflict with existing notes and cannot be represented as updates to existing ones.\n   - Do NOT record trivial actions (e.g. \"User typed a command\") or hallucinate unproven habits.\n   - Keep all side-notes respectful, professional, objective, and actionable.\n\n6. **Zero-Noise Output**:\n   - If the turn reveals no new insights, updates, or contradictions, return empty arrays and leave fields unchanged.\n</observation_and_reconciliation_rules>\n\n<output_format>\nAlways output ONLY valid JSON matching the schema. No markdown, no preambles.\n</output_format>";
 export declare const TRIVIAL_MESSAGE_CLASSIFIER_SYSTEM_INSTRUCTION = "<identity>\nYou are a Conversation Turn Signal Classifier for an AI coding assistant.\nYour sole job is to determine whether a user's message contains substantive personality or technical signal, or if it is purely a trivial/low-signal interaction.\n</identity>\n\n<classification_rules>\n- Output \"isTrivial\": true if the user's message is:\n  - A generic greeting or farewell (e.g. \"hi\", \"hello\", \"bye\", \"see you\").\n  - A simple affirmation, confirmation, or approval (e.g. \"ok\", \"yes\", \"proceed\", \"looks good\", \"lgtm\", \"sounds good\", \"continue\", \"go ahead\").\n  - A short courtesy or filler (e.g. \"thanks\", \"thank you\", \"awesome\", \"cool\", \"got it\").\n  - A simple CLI/session control command (e.g. \"stop\", \"exit\", \"quit\", \"clear\").\n  - An interaction that reveals ZERO technical preferences, opinions, architectural decisions, or unique communication traits.\n\n- Output \"isTrivial\": false if the user's message:\n  - Formulates a technical idea, asks an architectural question, or requests a feature.\n  - Expresses a distinct opinion, coding preference, dislike, or tool choice (e.g. \"I prefer using Zod over Joi\", \"Please make it concise with zero fluff\").\n  - Shows an emotional or stylistic tone (e.g. witty sarcasm, detailed breakdown, deep frustration with a pattern).\n  - Contains code snippets, error logs, or specific technical directives.\n</classification_rules>\n\n<output_format>\nAlways output ONLY valid JSON matching the schema: {\"isTrivial\": boolean, \"reason\": string}. No markdown, no preambles.\n</output_format>";

package/dist/utils/systemPrompts.js

@@ -367,12 +367,23 @@ Your task is to analyze conversational dialogue between the user and the AI agen
      - **debuggingStyle**: (e.g. "minimal-diff-fix", "root-cause-deep-dive")
      - **explanationFormat**: (e.g. "code-first", "bullet-summaries", "conceptual-analogies")
 
-4. **Incremental Side-Notes ("addNotes")**:
+4. **Conversational Persona & Teammate Pairing Dynamics ("conversationalPersona")**:
+   - Observe the interpersonal wavelength and how the user communicates with the AI:
+     - **relationshipModel**: (e.g. "collaborative-peer", "command-operator", "rubber-duck", "socratic-explorer")
+     - **banterAffinity**: (e.g. "witty-banter", "dry-professional", "warm-encouraging")
+     - **formalityLevel**: (e.g. "casual-slang", "telegraphic-concise", "polite-cordial")
+     - **apologyTolerance**: (e.g. "zero-apologies", "tolerant-empathetic")
+     - **stressCadence**: (e.g. "urgent-surgical", "calm-exploratory")
+     - **promptingHabit**: (e.g. "code-dump-deducer", "bulleted-architect", "stream-of-consciousness", "rapid-breadcrumbs")
+     - **conversationalQuirks**: (Add 1-2 distinct recurring catchphrases, quirks, or communicative habits e.g. "Uses 'lgtm' and 'ship it' when satisfied", "Appreciates dry sarcasm", "Drops raw stack traces without commentary")
+     - **removeQuirks**: (Prune outdated or superseded quirks if the user's habits change)
+
+5. **Incremental Side-Notes ("addNotes")**:
    - Add 1-2 new, high-value side-notes for genuinely new observations that do not conflict with existing notes and cannot be represented as updates to existing ones.
    - Do NOT record trivial actions (e.g. "User typed a command") or hallucinate unproven habits.
    - Keep all side-notes respectful, professional, objective, and actionable.
 
-5. **Zero-Noise Output**:
+6. **Zero-Noise Output**:
    - If the turn reveals no new insights, updates, or contradictions, return empty arrays and leave fields unchanged.
 </observation_and_reconciliation_rules>
 

package/oclif.manifest.json

@@ -201,5 +201,5 @@
       ]
     }
   },
-  "version": "2.14.0"
+  "version": "2.14.2"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "minovative-mind-cli",
   "description": "An automated AI agent powered by Vertex AI that helps you write software",
-  "version": "2.14.0",
+  "version": "2.14.2",
   "author": "Daniel Ward",
   "bin": {
     "minovative-mind-cli": "bin/run.js"