archtracker-mcp 0.5.0 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "archtracker-mcp",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "Architecture & Dependency Tracker — MCP server + CLI + interactive web viewer for AI-driven development",
   "type": "module",
   "main": "dist/index.js",
@@ -23,8 +23,10 @@
     "skills"
   ],
   "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
+    "build:client": "esbuild src/web/client/viewer.ts --bundle --format=iife --outfile=dist/web/viewer.js --target=es2020",
+    "build:server": "tsup",
+    "build": "npm run build:server && npm run build:client",
+    "dev": "npm run build:client && tsup --watch",
     "test": "vitest run",
     "test:watch": "vitest",
     "typecheck": "tsc --noEmit",

package/skills/arch-analyze/SKILL.md

@@ -14,6 +14,8 @@ Perform a comprehensive architecture analysis of the project.
 1. Run `analyze_existing_architecture` on the target directory
    - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists, and leave `targetDir` as default `"src"` to trigger auto-detection
    - For single-directory projects: set `targetDir` to the source directory
+   - Optional `topN` parameter to control number of items per section (default: 10, max: 50)
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
 2. Present the full report covering:
    - Overview (file count, edge count, circular deps)
    - Critical components (most depended-on files)

package/skills/arch-check/SKILL.md

@@ -13,6 +13,7 @@ Run an architecture diff check for the current project.
 1. Run `check_architecture_diff`
    - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists
    - Leave `targetDir` as default `"src"` to trigger multi-layer auto-detection
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
 2. Compare current code against the saved snapshot
 3. Report any files that have changed and their affected dependents
 

package/skills/arch-search/SKILL.md

@@ -18,6 +18,10 @@ Available search modes:
 
 Choose the most appropriate mode based on the user's question and execute the search.
 
+Optional parameters:
+- `limit`: Max number of results to return (default: 10, max: 50)
+- `language`: Target language if auto-detection is insufficient (e.g. `python`, `rust`, `java`)
+
 Present results in the user's language with clear formatting:
 - File paths and dependency counts
 - Match reason

package/skills/arch-snapshot/SKILL.md

@@ -13,6 +13,7 @@ Save the current project architecture as the baseline snapshot.
 1. Run `save_architecture_snapshot`
    - For multi-layer projects: set `projectRoot` to the project root where `.archtracker/layers.json` exists
    - Leave `targetDir` as default `"src"` to trigger multi-layer auto-detection
+   - Optional `language` parameter to specify target language (e.g. `python`, `rust`) if auto-detection fails
 2. Save it as `.archtracker/snapshot.json`
 3. Confirm the save with a summary