@latentforce/shift 1.0.13 → 1.0.15

package/build/cli/commands/add.js

@@ -27,84 +27,84 @@ function getMcpConfig(projectId) {
     };
 }
 const CLAUDE_MD_SECTION_MARKER = '<!-- shift-mcp-instructions -->';
-const CLAUDE_MD_CONTENT = `${CLAUDE_MD_SECTION_MARKER}
-## Shift MCP Tools — MANDATORY USAGE RULES
-
-This project has the **Shift MCP server** (\`shift\`) configured with a pre-built knowledge graph of the entire codebase. You MUST use its tools as the primary way to understand code. Do NOT rely solely on reading raw files.
-
-### Tools
-
-| Tool | Purpose |
-|------|---------|
-| \`file_summary\` | Get an summary of any file |
-| \`dependencies\` | List every file that a given file imports/depends on |
-| \`blast_radius\` | List every file that would be affected if a given file changed |
-
-### Supported file types
-
-The knowledge graph is built **only** from source files. The tools will return an error for any other file type.
-
-**Indexed (use MCP tools):**
-\`.js\` \`.jsx\` \`.ts\` \`.tsx\` \`.py\` \`.java\` \`.cpp\` \`.cs\` \`.go\` \`.c\` \`.h\` \`.css\` \`.scss\` \`.html\`
-
-**NOT indexed (read directly with normal file tools):**
-\`.json\` \`.yaml\` \`.yml\` \`.toml\` \`.env\` \`.md\` \`.txt\` \`.pdf\` \`.png\` \`.lock\` \`.xml\` \`.csv\` and any other non-source format.
-
-Do NOT call \`file_summary\`, \`dependencies\`, or \`blast_radius\` on non-indexed files — it will fail. Read those files directly instead.
-
----
-
-### RULE 1 — Codebase exploration (e.g. "explain the codebase", "how does this project work")
-
-You MUST call \`file_summary\` on **multiple key files** to build a complete picture. Do not stop after one call.
-
-Follow this protocol:
-1. Identify the likely entry points (e.g. \`main.ts\`, \`index.ts\`, \`app.py\`, \`server.ts\`, \`main.py\`, route files, CLI entry files).
-2. Call \`file_summary\` on each entry point (run calls in parallel where possible).
-3. Call \`dependencies\` on the most central files to discover the module graph.
-4. Call \`file_summary\` on the key modules discovered in step 3.
-5. Synthesise all results into a coherent explanation.
-
-Never answer a "explain the whole project" question from a single \`file_summary\` call.
-
----
-
-### RULE 2 — Before reading any file
-
-ALWAYS call \`file_summary\` first. Only open the raw file if you need implementation details that the summary does not cover.
-
----
-
-### RULE 3 — Before editing any file
-
-ALWAYS call \`blast_radius\` on that file first. List the affected files in your plan before making any changes.
-
----
-
-### RULE 4 — When tracing a bug or data flow
-
-Use \`dependencies\` to follow the chain rather than grepping manually. Start from the file where the symptom appears and walk the dependency graph.
-
----
-
-### Usage reference
-
-\`\`\`
-# Understand a file
-file_summary(file_path="src/server.ts")
-
-# Understand with folder context (level = number of parent dirs to include)
-file_summary(file_path="src/server.ts", level=1)
-
-# See what a file imports
-dependencies(file_path="src/server.ts")
-
-# See what breaks if this file changes
-blast_radius(file_path="src/server.ts")
-\`\`\`
-
-> Run \`shift-cli update-drg\` after significant code changes to keep the knowledge graph current.
-<!-- end-shift-mcp-instructions -->
+const CLAUDE_MD_CONTENT = `${CLAUDE_MD_SECTION_MARKER}
+## Shift MCP Tools — MANDATORY USAGE RULES
+
+This project has the **Shift MCP server** (\`shift\`) configured with a pre-built knowledge graph of the entire codebase. You MUST use its tools as the primary way to understand code. Do NOT rely solely on reading raw files.
+
+### Tools
+
+| Tool | Purpose |
+|------|---------|
+| \`file_summary\` | Get an summary of any file |
+| \`dependencies\` | List every file that a given file imports/depends on |
+| \`blast_radius\` | List every file that would be affected if a given file changed |
+
+### Supported file types
+
+The knowledge graph is built **only** from source files. The tools will return an error for any other file type.
+
+**Indexed (use MCP tools):**
+\`.js\` \`.jsx\` \`.ts\` \`.tsx\` \`.py\` \`.java\` \`.cpp\` \`.cs\` \`.go\` \`.c\` \`.h\` \`.css\` \`.scss\` \`.html\`
+
+**NOT indexed (read directly with normal file tools):**
+\`.json\` \`.yaml\` \`.yml\` \`.toml\` \`.env\` \`.md\` \`.txt\` \`.pdf\` \`.png\` \`.lock\` \`.xml\` \`.csv\` and any other non-source format.
+
+Do NOT call \`file_summary\`, \`dependencies\`, or \`blast_radius\` on non-indexed files — it will fail. Read those files directly instead.
+
+---
+
+### RULE 1 — Codebase exploration (e.g. "explain the codebase", "how does this project work")
+
+You MUST call \`file_summary\` on **multiple key files** to build a complete picture. Do not stop after one call.
+
+Follow this protocol:
+1. Identify the likely entry points (e.g. \`main.ts\`, \`index.ts\`, \`app.py\`, \`server.ts\`, \`main.py\`, route files, CLI entry files).
+2. Call \`file_summary\` on each entry point (run calls in parallel where possible).
+3. Call \`dependencies\` on the most central files to discover the module graph.
+4. Call \`file_summary\` on the key modules discovered in step 3.
+5. Synthesise all results into a coherent explanation.
+
+Never answer a "explain the whole project" question from a single \`file_summary\` call.
+
+---
+
+### RULE 2 — Before reading any file
+
+ALWAYS call \`file_summary\` first. Only open the raw file if you need implementation details that the summary does not cover.
+
+---
+
+### RULE 3 — Before editing any file
+
+ALWAYS call \`blast_radius\` on that file first. List the affected files in your plan before making any changes.
+
+---
+
+### RULE 4 — When tracing a bug or data flow
+
+Use \`dependencies\` to follow the chain rather than grepping manually. Start from the file where the symptom appears and walk the dependency graph.
+
+---
+
+### Usage reference
+
+\`\`\`
+# Understand a file
+file_summary(file_path="src/server.ts")
+
+# Understand with folder context (level = number of parent dirs to include)
+file_summary(file_path="src/server.ts", level=1)
+
+# See what a file imports
+dependencies(file_path="src/server.ts")
+
+# See what breaks if this file changes
+blast_radius(file_path="src/server.ts")
+\`\`\`
+
+> Run \`shift-cli update-drg\` after significant code changes to keep the knowledge graph current.
+<!-- end-shift-mcp-instructions -->
 `;
 const CLAUDE_MD_END_MARKER = '<!-- end-shift-mcp-instructions -->';
 function createClaudeMd(projectRoot) {

package/build/cli/commands/init.js

@@ -207,6 +207,28 @@ export async function initCommand(options = {}) {
     else {
         console.log('[Init] No .shift/scan_target.json found — server will auto-detect scan targets');
     }
+    // Read source file contents so orchestrator can run pipeline inline (e.g. LOCAL mode) and index via init-scan
+    const MAX_FILES_TO_SEND = 800;
+    const MAX_FILE_SIZE_CHARS = 150000;
+    const filesToRead = categorized.source_files.slice(0, MAX_FILES_TO_SEND);
+    const filesWithContent = [];
+    let filesSkipped = 0;
+    for (const filePath of filesToRead) {
+        try {
+            const absolutePath = path.join(projectRoot, filePath);
+            const content = readFileSync(absolutePath, 'utf-8');
+            const truncated = content.length > MAX_FILE_SIZE_CHARS
+                ? content.slice(0, MAX_FILE_SIZE_CHARS) + '\n/* ... truncated */'
+                : content;
+            filesWithContent.push({ file_path: filePath, content: truncated });
+        }
+        catch {
+            filesSkipped++;
+        }
+    }
+    if (filesWithContent.length > 0) {
+        console.log(`[Init] Read ${filesWithContent.length} source file(s) for inline indexing${filesSkipped > 0 ? ` (${filesSkipped} skipped)` : ''}`);
+    }
     const payload = {
         project_id: project.projectId,
         project_tree: treeData,
@@ -222,11 +244,12 @@ export async function initCommand(options = {}) {
         },
         scan_targets: scanTargets,
         total_loc: totalLOC,
+        files: filesWithContent.length > 0 ? filesWithContent : undefined,
     };
     try {
         const response = await sendInitScan(apiKey, project.projectId, payload);
         console.log('[Init] ✓ Backend initialization completed');
-        console.log(`[Init]   Source files queued: ${response.source_files_count ?? response.files_read}`);
+        console.log(`[Init]   Source files queued: ${response.source_files_count}`);
         // Update local config with agent info (matching extension)
         if (response.agents_created?.theme_planner) {
             const agentInfo = {
@@ -240,9 +263,6 @@ export async function initCommand(options = {}) {
             writeProjectConfig(projectConfig, projectRoot);
             console.log(`[Init] ✓ Agent info saved: ${agentInfo.agent_id}`);
         }
-        if (response.files_read === 0 && response.files_failed > 0) {
-            console.log(`\n[Init] ⚠️  No files were read (${response.files_failed} failed).`);
-        }
         console.log('\n╔═══════════════════════════════════════════════╗');
         console.log('║       ✓ Project Initialization Complete       ║');
         console.log('╚═══════════════════════════════════════════════╝');

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@latentforce/shift",
-    "version": "1.0.13",
+    "version": "1.0.15",
     "description": "Shift CLI - AI-powered code intelligence with MCP support",
     "type": "module",
     "main": "./build/index.js",