@infinitedusky/indusk-mcp 1.2.9 → 1.4.0

package/dist/bin/commands/extensions.d.ts

@@ -6,3 +6,4 @@ export declare function extensionsAdd(projectRoot: string, name: string, from: s
 export declare function extensionsRemove(projectRoot: string, names: string[]): Promise<void>;
 export declare function extensionsUpdate(projectRoot: string, names?: string[]): Promise<void>;
 export declare function extensionsSuggest(projectRoot: string): Promise<void>;
+export declare function autoEnableExtensions(projectRoot: string): Promise<void>;

package/dist/bin/commands/extensions.js

@@ -323,6 +323,7 @@ export async function extensionsUpdate(projectRoot, names) {
     }
     else {
         console.info(`\n${updated} extension(s) updated.`);
+        console.info("\n⚠  Restart Claude Code to load the updated extensions.");
     }
 }
 export async function extensionsSuggest(projectRoot) {
@@ -361,6 +362,20 @@ export async function extensionsSuggest(projectRoot) {
                 }
             }
         }
+        if (ext.detect.mcp_server) {
+            try {
+                const mcpPath = join(projectRoot, ".mcp.json");
+                if (existsSync(mcpPath)) {
+                    const mcp = JSON.parse(readFileSync(mcpPath, "utf-8"));
+                    if (mcp.mcpServers?.[ext.detect.mcp_server]) {
+                        suggestions.push({ name: ext.name, reason: `${ext.detect.mcp_server} in .mcp.json` });
+                    }
+                }
+            }
+            catch {
+                // ignore
+            }
+        }
     }
     if (suggestions.length === 0) {
         console.info("No extension suggestions — all detected extensions are already enabled.");
@@ -372,6 +387,68 @@ export async function extensionsSuggest(projectRoot) {
     }
     console.info(`\nEnable with: extensions enable ${suggestions.map((s) => s.name).join(" ")}`);
 }
+export async function autoEnableExtensions(projectRoot) {
+    const builtins = getBuiltinExtensions();
+    let enabled = 0;
+    for (const ext of builtins) {
+        if (isEnabled(projectRoot, ext.name))
+            continue;
+        if (!ext.detect)
+            continue;
+        let detected = false;
+        let reason = "";
+        if (ext.detect.file && existsSync(join(projectRoot, ext.detect.file))) {
+            detected = true;
+            reason = `${ext.detect.file} found`;
+        }
+        if (!detected && ext.detect.file_pattern) {
+            const matches = globSync(ext.detect.file_pattern, { cwd: projectRoot, maxDepth: 3 });
+            if (matches.length > 0) {
+                detected = true;
+                reason = `${ext.detect.file_pattern} found`;
+            }
+        }
+        if (!detected && (ext.detect.dependency || ext.detect.devDependency)) {
+            const pkgPath = join(projectRoot, "package.json");
+            if (existsSync(pkgPath)) {
+                const pkg = JSON.parse(readFileSync(pkgPath, "utf-8"));
+                const deps = pkg.dependencies ?? {};
+                const devDeps = pkg.devDependencies ?? {};
+                if (ext.detect.dependency && deps[ext.detect.dependency]) {
+                    detected = true;
+                    reason = `${ext.detect.dependency} in dependencies`;
+                }
+                else if (ext.detect.devDependency && devDeps[ext.detect.devDependency]) {
+                    detected = true;
+                    reason = `${ext.detect.devDependency} in devDependencies`;
+                }
+            }
+        }
+        if (!detected && ext.detect.mcp_server) {
+            try {
+                const mcpPath = join(projectRoot, ".mcp.json");
+                if (existsSync(mcpPath)) {
+                    const mcp = JSON.parse(readFileSync(mcpPath, "utf-8"));
+                    if (mcp.mcpServers?.[ext.detect.mcp_server]) {
+                        detected = true;
+                        reason = `${ext.detect.mcp_server} in .mcp.json`;
+                    }
+                }
+            }
+            catch {
+                // ignore parse errors
+            }
+        }
+        if (detected) {
+            await extensionsEnable(projectRoot, [ext.name]);
+            console.info(`    (detected: ${reason})`);
+            enabled++;
+        }
+    }
+    if (enabled === 0) {
+        console.info("  No new extensions detected.");
+    }
+}
 // --- Helpers ---
 function runHook(projectRoot, name, hook) {
     const extPath = join(extensionsDir(projectRoot), `${name}.json`);

package/dist/bin/commands/init-docs.js

@@ -231,6 +231,12 @@ Architecture decision records for ${projectName}. Each decision documents what w
     writeFileSync(join(docsDir, "src/lessons/index.md"), `# Lessons Learned
 
 Insights from building ${projectName}. Each lesson captures what we learned, what surprised us, and what we'd do differently.
+`);
+    writeFileSync(join(docsDir, "src/changelog.md"), `# Changelog
+
+All notable changes to ${projectName} are documented here. Follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+
+## [Unreleased]
 `);
     // Dockerfile for local dev
     const dockerDir = join(projectRoot, "docker");

package/dist/bin/commands/init.js

@@ -294,15 +294,15 @@ export async function init(projectRoot, options = {}) {
             console.info("  skipped (CGC not available)");
         }
     }
-    // 11. Suggest extensions
+    // 11. Auto-enable detected extensions
     console.info("\n[Extensions]");
-    const { extensionsSuggest } = await import("./extensions.js");
-    await extensionsSuggest(projectRoot);
+    const { autoEnableExtensions } = await import("./extensions.js");
+    await autoEnableExtensions(projectRoot);
     // Summary
     console.info("\nDone!");
+    console.info("\n⚠  Restart Claude Code to load the updated MCP server and skills.");
     console.info("\nNext steps:");
-    console.info("  1. Edit CLAUDE.md with your project details");
-    console.info("  2. Enable extensions: extensions enable falkordb cgc typescript");
-    console.info("  3. Start a Claude Code session — MCP tools will be available");
-    console.info("  4. Start planning: /plan your-first-feature");
+    console.info("  1. Restart Claude Code");
+    console.info("  2. Edit CLAUDE.md with your project details");
+    console.info("  3. Start planning: /plan your-first-feature");
 }

package/dist/lib/extension-loader.d.ts

@@ -3,6 +3,7 @@ export interface DetectRule {
     file_pattern?: string;
     dependency?: string;
     devDependency?: string;
+    mcp_server?: string;
 }
 export interface HealthCheck {
     name: string;

package/extensions/dash0/manifest.json

@@ -0,0 +1,19 @@
+{
+	"name": "dash0",
+	"description": "Dash0 observability — query logs, traces, and metrics from your OpenTelemetry data via MCP",
+	"provides": {
+		"skill": true,
+		"health_checks": [
+			{
+				"name": "dash0-mcp-configured",
+				"command": "node -e \"const m=JSON.parse(require('fs').readFileSync('.mcp.json','utf-8'));process.exit(m.mcpServers?.dash0 ? 0 : 1)\""
+			}
+		]
+	},
+	"hooks": {
+		"on_init": "echo 'Dash0 extension enabled. Configure the Dash0 MCP server in .mcp.json if not already present.'"
+	},
+	"detect": {
+		"mcp_server": "dash0"
+	}
+}

package/extensions/dash0/skill.md

@@ -0,0 +1,70 @@
+# Dash0 Observability
+
+Dash0 provides access to your OpenTelemetry data — logs, traces, and metrics — directly from Claude Code via its MCP server.
+
+## When to Use Dash0
+
+- **Test failures**: query recent traces to see what happened in the service during the test
+- **Debugging production issues**: search logs for errors, find related traces by trace ID
+- **Performance investigation**: query metrics (PromQL) to check latency, throughput, error rates
+- **Deployment verification**: check traces and error rates after deploying a change
+- **During /work verification**: if a verification step involves checking service health, query Dash0
+
+## Available Tools (from Dash0 MCP server)
+
+Dash0's MCP server provides 23 tools. The most useful for development:
+
+| Tool | When |
+|------|------|
+| Search logs | Find errors, warnings, or specific log messages |
+| Search traces | Find request traces by service, endpoint, status, or trace ID |
+| Query metrics (PromQL) | Check latency percentiles, error rates, throughput |
+| List services | See what services are sending telemetry |
+| Get trace details | Deep-dive into a specific trace's spans |
+
+## Setup
+
+1. Sign up at [dash0.com](https://www.dash0.com)
+2. Get your API token from the Dash0 dashboard
+3. Add the Dash0 MCP server to your `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "dash0": {
+      "command": "npx",
+      "args": ["@dash0hq/mcp-server"],
+      "env": {
+        "DASH0_API_TOKEN": "your-token-here",
+        "DASH0_DATASET": "default"
+      }
+    }
+  }
+}
+```
+
+4. Enable the extension: `extensions enable dash0`
+
+## Workflow Integration
+
+### During verification
+When a verification step involves checking that a service is working correctly, don't just check the HTTP status — query Dash0 for:
+- Recent error traces for the service
+- Error rate metrics before and after your change
+- Log entries matching the feature you modified
+
+### During debugging
+When something fails:
+1. Check logs first — search for errors in the relevant service
+2. Find the trace — use the trace ID from logs to get the full request flow
+3. Check metrics — is this a new problem or an existing one? Compare error rates over time.
+
+### During retrospective
+Query Dash0 for metrics that show the impact of the plan:
+- Error rate before vs after
+- Latency changes
+- New services or endpoints that appeared
+
+## Connecting to OpenTelemetry
+
+Dash0 ingests standard OpenTelemetry data. If your services already export OTLP telemetry, point the OTLP exporter at Dash0's endpoint. See [Dash0 docs](https://www.dash0.com/documentation/dash0) for setup per language.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@infinitedusky/indusk-mcp",
-	"version": "1.2.9",
+	"version": "1.4.0",
 	"description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
 	"type": "module",
 	"files": [

package/skills/document.md

@@ -60,7 +60,8 @@ apps/indusk-docs/src/
 │   ├── skills/      # One page per skill
 │   └── tools/       # One page per tool (Biome, CGC, composable.env)
 ├── decisions/       # Distilled from ADRs during retrospective/archival
-└── lessons/         # Distilled from retrospective insights during archival
+├── lessons/         # Distilled from retrospective insights during archival
+└── changelog.md     # Version history — Added, Changed, Fixed, etc.
 ```
 
 **CRITICAL: Every new page must be added to the sidebar.** The sidebar is configured in a single file: `apps/indusk-docs/src/.vitepress/config.ts` under `themeConfig.sidebar`. If you create a page but don't add it to the sidebar, it is invisible — users cannot navigate to it. This is the most common documentation mistake.
@@ -79,11 +80,29 @@ Never consider a documentation item complete until the sidebar entry exists.
 
 | What changed | Where to document | Doc type |
 |---|---|---|
-| New feature or tool | `reference/` | Reference page |
-| New workflow or process | `guide/` | How-to guide |
-| Configuration change | `reference/` (update existing page) | Reference update |
-| Architecture change | `reference/` + diagram | Reference + diagram |
-| Nothing user-facing | Skip | — |
+| New feature or tool | `reference/` + changelog | Reference page + Added |
+| New workflow or process | `guide/` + changelog | How-to guide + Added |
+| Configuration change | `reference/` (update existing) + changelog | Reference update + Changed |
+| Bug fix | Existing page (if relevant) + changelog | Fixed |
+| Architecture change | `reference/` + diagram + changelog | Reference + diagram + Changed |
+| Nothing user-facing | Skip changelog | — |
+
+### Changelog
+
+The changelog lives at `changelog.md` in the docs site. It uses [Keep a Changelog](https://keepachangelog.com) categories:
+
+- **Added** — new features (from `feature` workflow plans)
+- **Changed** — changes to existing functionality (from `refactor` workflows)
+- **Fixed** — bug fixes (from `bugfix` workflows)
+- **Deprecated** — soon to be removed
+- **Removed** — removed features
+- **Security** — vulnerability fixes
+
+**When to write:** During the Document gate of each phase that changes user-facing behavior. Add the entry under `## [Unreleased]`. At publish time, move Unreleased entries into a versioned section.
+
+**What to write:** One line per change. Human-readable — what users gain, not what code changed. The workflow type from the impl frontmatter tells you the category (feature → Added, bugfix → Fixed, refactor → Changed).
+
+**During planning:** The ADR's Documentation Plan section should include planned changelog entries. This forces you to think about user impact during planning, not after.
 
 ### Decisions and Lessons