claude-autopm 3.23.1 → 3.23.2

package/.github/workflows/deploy-docs.yml

@@ -35,7 +35,7 @@ jobs:
           cache-dependency-path: docs-site/package-lock.json
 
       - name: Setup Pages
-        uses: actions/configure-pages@v4
+        uses: actions/configure-pages@v6
 
       - name: Install dependencies
         run: npm ci
@@ -59,4 +59,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v5

package/.github/workflows/npm-publish.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v6
         with:
           node-version: '20'
       - run: npm ci --legacy-peer-deps
@@ -24,7 +24,7 @@ jobs:
       contents: read
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v6
         with:
           node-version: '20'
           registry-url: 'https://registry.npmjs.org'

package/.github/workflows/plugin-publish.yml

@@ -34,7 +34,7 @@ jobs:
           - plugin-testing
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v6
         with:
           node-version: '20'
           registry-url: 'https://registry.npmjs.org'
@@ -52,7 +52,7 @@ jobs:
       id-token: write
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v6
         with:
           node-version: '20'
           registry-url: 'https://registry.npmjs.org'

package/README.md

@@ -27,6 +27,7 @@ Choose your scenario during installation:
 | **GitHub** | 12 | Core + languages for GitHub projects |
 | **Azure** | 14 | Core + languages + Azure DevOps |
 | **Docker** | 16 | Core + DevOps + containers |
+| **Obsidian** | 12 | PM + Obsidian vault integration |
 | **Full** | 44+ | All plugins, all agents |
 | **Performance** | 44+ | Full + max parallelization |
 
@@ -134,10 +135,11 @@ All commands run inside Claude Code (not terminal):
 
 ## Features
 
-### 13 Official Plugins
+### 14 Official Plugins
 
 - **Core** — Context management, testing, configuration, MCP
 - **PM System** — PRD, epics, issues, decomposition, git workflow
+- **Obsidian** — Read-only vault sync, Dataview frontmatter, diagnostics
 - **Azure DevOps** — Work items, boards, pipelines, sprints
 - **GitHub** — Workflows, issues, PRs, automation
 - **Languages** — Python, JavaScript, Node.js, Bash

package/autopm/.claude/docs/xml-prompts/README.md

@@ -435,7 +435,7 @@ Create templates tailored to your project:
   --stage 2
 
 # Edit template
-vim autopm/.claude/templates/xml-prompts/dev/microservice.xml
+vim .claude/templates/xml-prompts/dev/microservice.xml
 
 # Use custom template
 /prompt:xml microservice \
@@ -522,5 +522,5 @@ Solution: Provide missing flag
   - `.claude/commands/xml/prompt-xml.md`
   - `.claude/commands/xml/template.md`
 - **Utilities:**
-  - `autopm/.claude/lib/xml-prompt-builder.js`
-  - `autopm/.claude/lib/xml-validator.js`
+  - `.claude/lib/xml-prompt-builder.js`
+  - `.claude/lib/xml-validator.js`

package/autopm/.claude/docs/xml-prompts/creating-templates.md

@@ -111,7 +111,7 @@ This will prompt you for:
 
 ```bash
 # Create file in appropriate category
-vim autopm/.claude/templates/xml-prompts/dev/my-template.xml
+vim .claude/templates/xml-prompts/dev/my-template.xml
 ```
 
 ### Step 3: Define Template Content
@@ -558,7 +558,7 @@ cat test.xml | grep -q "<thinking>" && echo "✅ Has thinking" || echo "❌ Miss
 Track template changes:
 
 ```bash
-git add autopm/.claude/templates/xml-prompts/dev/my-template.xml
+git add .claude/templates/xml-prompts/dev/my-template.xml
 git commit -m "Update microservice template with health check requirements"
 ```
 

package/autopm/.claude/docs/xml-prompts/templates-guide.md

@@ -462,7 +462,7 @@ done
 /xml:template create microservice --category dev --stage 2
 
 # Edit to add project-specific constraints
-vim autopm/.claude/templates/xml-prompts/dev/microservice.xml
+vim .claude/templates/xml-prompts/dev/microservice.xml
 
 # Add your patterns:
 # - Service structure requirements

package/install/install.js

@@ -556,6 +556,14 @@ ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
    • Advanced users only
 `);
 
+    // Option 7: Obsidian (always available)
+    console.log(`${this.colors.CYAN}7. Obsidian${this.colors.NC} - PM + Obsidian vault integration (rsync, Dataview, templates)
+   • Core + PM + Obsidian vault sync
+   • Unidirectional project → vault mirroring
+   • Best for: Knowledge management, documentation-heavy projects
+   ${this.colors.DIM}• Plugins: core, pm, obsidian (3 plugins)${this.colors.NC}
+`);
+
     if (process.env.AUTOPM_TEST_MODE === '1') {
       this.printMsg('CYAN', 'Auto-selecting option 0 (lite) for test mode');
       return 'lite';
@@ -571,7 +579,7 @@ ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
 
     return new Promise((resolve) => {
       const askQuestion = () => {
-        rl.question(`${this.colors.CYAN}Enter your choice (0-6) [${defaultChoice}]: ${this.colors.NC}`, (answer) => {
+        rl.question(`${this.colors.CYAN}Enter your choice (0-7) [${defaultChoice}]: ${this.colors.NC}`, (answer) => {
           const choice = answer.trim() || defaultChoice;
           const scenarios = {
             '0': 'lite',
@@ -580,7 +588,8 @@ ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
             '3': 'docker',
             '4': 'full',
             '5': 'performance',
-            '6': 'custom'
+            '6': 'custom',
+            '7': 'obsidian'
           };
 
           const selectedScenario = scenarios[choice];
@@ -608,7 +617,7 @@ ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
           }
 
           if (!selectedScenario) {
-            console.log(`${this.colors.RED}✗ Invalid choice. Please select 0-6.${this.colors.NC}`);
+            console.log(`${this.colors.RED}✗ Invalid choice. Please select 0-7.${this.colors.NC}`);
             askQuestion();
             return;
           }
@@ -703,6 +712,16 @@ ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
           kubernetes: { enabled: true }
         },
         plugins: ['plugin-core', 'plugin-languages', 'plugin-frameworks', 'plugin-testing', 'plugin-devops', 'plugin-cloud', 'plugin-databases', 'plugin-data', 'plugin-pm', 'plugin-pm-github', 'plugin-ai', 'plugin-ml']
+      },
+      obsidian: {
+        version: version,
+        installed: new Date().toISOString(),
+        execution_strategy: 'sequential',
+        tools: {
+          docker: { enabled: false },
+          kubernetes: { enabled: false }
+        },
+        plugins: ['plugin-core', 'plugin-pm', 'plugin-obsidian']
       }
     };
 

package/install/post-install-check.js

@@ -37,6 +37,7 @@ class PostInstallChecker {
     this.checkMCPConfiguration();
     this.checkGitHooks();
     this.checkNodeVersion();
+    this.checkObsidianVault();
 
     // Display results
     this.displayResults();
@@ -336,6 +337,34 @@ class PostInstallChecker {
     }
   }
 
+  /**
+   * Check Obsidian vault configuration
+   */
+  checkObsidianVault() {
+    const configPath = path.join(this.projectRoot, '.claude', 'config.json');
+    let configured = false;
+    let message = 'Not configured — run: obsidian:setup';
+
+    if (fs.existsSync(configPath)) {
+      try {
+        const config = JSON.parse(fs.readFileSync(configPath, 'utf8'));
+        const vaultPath = config.obsidian?.vault_path;
+        if (vaultPath) {
+          configured = true;
+          message = `Vault: ${vaultPath}`;
+        }
+      } catch (error) {
+        // config unreadable, leave as not configured
+      }
+    }
+
+    this.results.optional.push({
+      name: 'Obsidian vault',
+      status: configured,
+      message: message
+    });
+  }
+
   /**
    * Display check results
    */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-autopm",
-  "version": "3.23.1",
+  "version": "3.23.2",
   "description": "Autonomous Project Management Framework for Claude Code - Advanced AI-powered development automation",
   "main": "bin/autopm.js",
   "workspaces": [
@@ -125,7 +125,7 @@
     "README.md"
   ],
   "dependencies": {
-    "@anthropic-ai/sdk": "^0.67.0",
+    "@anthropic-ai/sdk": "^0.82.0",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@octokit/rest": "^22.0.0",
     "azure-devops-node-api": "^15.1.1",
@@ -135,10 +135,10 @@
     "fast-glob": "^3.3.2",
     "fs-extra": "^11.3.2",
     "glob": "^11.0.3",
-    "inquirer": "^12.9.6",
+    "inquirer": "^13.3.2",
     "js-yaml": "^4.1.0",
     "markdown-it": "^14.1.0",
-    "marked": "^16.4.0",
+    "marked": "^17.0.6",
     "moment": "^2.29.4",
     "ora": "~5.4.1",
     "simple-git": "^3.20.0",
@@ -151,7 +151,7 @@
     "@jest/globals": "^30.1.2",
     "@types/jest": "^30.0.0",
     "axios": "^1.12.2",
-    "c8": "^10.1.3",
+    "c8": "^11.0.0",
     "chai": "^6.0.1",
     "jest": "^30.1.3",
     "jest-diff": "^30.1.2",
@@ -166,7 +166,7 @@
     "sinon": "^21.0.0"
   },
   "optionalDependencies": {
-    "@playwright/mcp": "^0.0.68",
+    "@playwright/mcp": "^0.0.70",
     "@upstash/context7-mcp": "^2.1.6"
   },
   "publishConfig": {

package/packages/plugin-obsidian/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Rafal Lagowski
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/packages/plugin-obsidian/README.md

@@ -0,0 +1,129 @@
+# @claudeautopm/plugin-obsidian
+
+> **Obsidian Vault Integration Plugin for ClaudeAutoPM Framework**
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+## Overview
+
+`@claudeautopm/plugin-obsidian` creates a read-only Obsidian vault mirror of your ClaudeAutoPM project. It syncs project markdown (agents, commands, rules, epics, PRDs, issues) to an Obsidian vault where Dataview, Mermaid, Excalidraw, and canonical frontmatter work out of the box.
+
+Sync is **unidirectional**: project to vault. Never edit files in the Obsidian vault directly.
+
+### Package Information
+
+- **Package Name:** `@claudeautopm/plugin-obsidian`
+- **Category:** Integration
+- **Schema Version:** 2.0
+
+---
+
+## Features
+
+- **Vault Sync** -- Unidirectional project-to-vault sync via rsync (one-shot, watch, dry-run, safe-mode)
+- **Setup Wizard** -- Interactive configuration for vault path, prefix, watch mode, and environment detection (WSL2, macOS, Linux)
+- **Doctor** -- Five-check diagnostic for common integration issues (missing tools, unreachable vault, dotfolder visibility, Dataview prefix, broken symlinks)
+- **Templates** -- MOC, Dashboard, Dataview queries, Mermaid diagrams, and Excalidraw canvas
+- **Canonical Frontmatter** -- Schema for Dataview + Breadcrumbs compatibility across all synced files
+- **Cross-Platform** -- Supports WSL2, macOS, and Linux-native environments
+
+---
+
+## Installation
+
+```bash
+# Install via scenario
+autopm install --scenario=obsidian
+
+# Or add to existing installation (scenario 7)
+autopm install
+```
+
+### Prerequisites
+
+- `rsync` (required)
+- `inotify-tools` (Linux/WSL, optional for `--watch` mode)
+- `fswatch` (macOS, optional for `--watch` mode)
+- Obsidian desktop app
+
+---
+
+## Commands
+
+### `obsidian:setup`
+
+Interactive vault configuration wizard. Run once after install.
+
+```bash
+/obsidian:setup --vault-path /path/to/vault --prefix my-project
+```
+
+### `obsidian:sync`
+
+Sync project files to the Obsidian vault.
+
+```bash
+/obsidian:sync              # One-shot sync
+/obsidian:sync --watch      # Continuous sync on file changes
+/obsidian:sync --check      # Dry-run (show what would sync)
+/obsidian:sync --safe-mode  # Don't delete vault files
+```
+
+### `obsidian:doctor`
+
+Diagnose common integration problems:
+
+1. Missing rsync / inotify-tools / fswatch
+2. Unreachable or non-writable vault path
+3. Issues under `.claude/issues/` (invisible to Dataview)
+4. Wrong Dataview FROM prefix
+5. Broken symlink between `.claude/issues` and `issues/`
+
+---
+
+## Configuration
+
+Settings are stored in `.claude/config.json`:
+
+```json
+{
+  "obsidian": {
+    "vault_path": "/path/to/vault",
+    "vault_prefix": "my-project",
+    "watch": false,
+    "environment": "wsl"
+  }
+}
+```
+
+---
+
+## Sync Mapping
+
+| Project Path | Vault Path |
+|--------------|------------|
+| `.claude/agents/` | `{vault}/{prefix}/agents/` |
+| `.claude/commands/` | `{vault}/{prefix}/commands/` |
+| `.claude/rules/` | `{vault}/{prefix}/rules/` |
+| `.claude/epics/` | `{vault}/{prefix}/epics/` |
+| `.claude/prds/` | `{vault}/{prefix}/prds/` |
+| `issues/` | `{vault}/{prefix}/issues/` |
+| `*.md` (root) | `{vault}/{prefix}/` |
+
+---
+
+## Documentation
+
+Full user guide: [docs/plugins/obsidian.md](../../docs/plugins/obsidian.md)
+
+---
+
+## Peer Dependencies
+
+- **@claudeautopm/plugin-core** (^2.0.0) -- Core framework plugin (REQUIRED)
+
+---
+
+## License
+
+MIT

package/packages/plugin-obsidian/claude-md/obsidian-section.md

@@ -0,0 +1,30 @@
+## Obsidian Vault Integration
+
+This project uses Obsidian as a visual layer for project documentation.
+
+### Vault Sync
+
+- **Sync is unidirectional**: Project → Vault (never edit in Obsidian)
+- Run `/obsidian:sync` for one-shot sync
+- Run `/obsidian:sync --watch` for continuous sync
+- Run `/obsidian:doctor` to diagnose issues
+
+### Frontmatter Convention
+
+All markdown files should include canonical frontmatter for Dataview:
+
+```yaml
+---
+type: issue|prd|epic|agent|rule
+status: open|in-progress|closed
+created: "YYYY-MM-DDTHH:mm:ssZ"
+updated: "YYYY-MM-DDTHH:mm:ssZ"
+tags: [relevant, tags]
+---
+```
+
+### Important Rules
+
+- **Never edit files in the Obsidian vault directly** — changes will be overwritten on next sync
+- Dotfolders (`.claude/`) are invisible to Dataview — the sync script maps them to visible paths
+- If using shared vaults, set `obsidian.vault_prefix` in `.claude/config.json`

package/packages/plugin-obsidian/commands/obsidian:doctor.md

@@ -0,0 +1,63 @@
+---
+allowed-tools: Bash, Read
+---
+
+# Obsidian Doctor
+
+Run diagnostics on the Obsidian integration and suggest fixes for common problems.
+
+## Usage
+
+```
+/obsidian:doctor
+```
+
+## Instructions
+
+### 1. Locate Script
+
+```bash
+SCRIPT_JS="packages/plugin-obsidian/scripts/obsidian/doctor.js"
+
+if [ ! -f "$SCRIPT_JS" ]; then
+  SCRIPT_JS=".claude/scripts/doctor.js"
+fi
+
+if [ ! -f "$SCRIPT_JS" ]; then
+  echo "❌ Doctor script not found. Reinstall plugin-obsidian or run: /obsidian:setup"
+  exit 1
+fi
+```
+
+### 2. Run Diagnostics
+
+```bash
+node "$SCRIPT_JS"
+```
+
+### 3. Output
+
+On success (all checks pass or only warnings):
+
+```
+Obsidian Doctor
+════════════════════════════════════════════════════════════
+
+✅  rsync                    installed    /usr/bin/rsync
+⚠️  inotify-tools            missing      Install: sudo apt install inotify-tools
+✅  Vault path               ok           /path/to/vault
+✅  Issues location          ok           issues/
+✅  Dataview prefix          correct      my-project
+✅  Symlink                  ok           .claude/issues -> issues
+
+════════════════════════════════════════════════════════════
+Result: 5 passed, 1 warning
+```
+
+On failure (any check has an error):
+
+```
+Result: 3 passed, 1 warning, 2 errors
+```
+
+Exit code 0 means all checks passed (warnings are OK). Exit code 1 means at least one check failed.

package/packages/plugin-obsidian/commands/obsidian:setup.md

@@ -0,0 +1,69 @@
+---
+allowed-tools: Bash, Read, Write
+---
+
+# Obsidian Setup Wizard
+
+Configure an Obsidian vault for use with ClaudeAutoPM. Run this once after `autopm install --scenario=obsidian`.
+
+## Usage
+
+```
+/obsidian:setup --vault-path /path/to/vault [--prefix my-project] [--watch] [--no-watch]
+```
+
+Options:
+- `--vault-path PATH` — Absolute path to your Obsidian vault (required)
+- `--prefix NAME` — Subfolder name inside the vault (default: project directory name)
+- `--watch` — Enable continuous sync in config
+- `--no-watch` — Disable continuous sync in config (default)
+
+## Instructions
+
+### 1. Gather Arguments
+
+Ask the user for `--vault-path` if not provided. The vault must already exist as a directory.
+
+On WSL, vault paths typically look like: `/mnt/c/Users/<name>/Documents/Obsidian/Vault`
+
+### 2. Run Setup Script
+
+Execute the backend script with the user's arguments:
+
+```bash
+node packages/plugin-obsidian/scripts/obsidian/setup.js \
+  --vault-path "$VAULT_PATH" \
+  --prefix "$PREFIX" \
+  --project-root "$(pwd)"
+```
+
+Add `--watch` or `--no-watch` if the user specified either.
+
+### 3. What the Script Does
+
+The setup script performs these steps in order:
+
+1. **Detects environment** — WSL, macOS, or Linux
+2. **Validates vault path** — Checks existence and write permissions
+3. **Merges config** — Adds `obsidian` section to `.claude/config.json` (preserves all existing keys)
+4. **Generates templates** — Writes MOC, Dashboard, Obsidian templates, and diagram stubs into the vault
+5. **Applies canonical frontmatter** — Adds missing fields (`type`, `status`, `created`, `updated`, `tags`) to existing issues and PRDs without overwriting existing values
+6. **Migrates issues** — If `issues/` doesn't exist but `.claude/issues/` does, moves it and creates a symlink
+7. **Copies sync script** — Places `sync-to-obsidian.sh` into `.claude/scripts/`
+8. **Runs first sync** — Executes the sync script once to populate the vault
+
+### 4. Output
+
+On success, the script prints a summary showing the vault path, prefix, environment, generated files, and recommended next steps (plugin installation links).
+
+### 5. Troubleshooting
+
+If the script fails:
+
+- **Vault path does not exist** — Create the directory first or check the path
+- **Vault path is not writable** — Fix permissions: `chmod u+w /path/to/vault`
+- **Sync script not found** — Re-run `autopm install --scenario=obsidian`
+
+## Related Commands
+
+- `/obsidian:sync` — Run a one-off or continuous sync after setup