docguard-cli 0.23.0__tar.gz → 0.25.0__tar.gz

{docguard_cli-0.23.0/extensions/spec-kit-docguard → docguard_cli-0.25.0/.agent}/skills/docguard-fix/SKILL.md

@@ -6,10 +6,10 @@ description: AI-driven documentation repair with structured research workflow, t
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.23.0
+  version: 0.25.0
   source: extensions/spec-kit-docguard/skills/docguard-fix
 ---
-<!-- docguard:version: 0.23.0 -->
+<!-- docguard:version: 0.25.0 -->
 
 # DocGuard Fix Skill
 

{docguard_cli-0.23.0/extensions/spec-kit-docguard → docguard_cli-0.25.0/.agent}/skills/docguard-guard/SKILL.md

@@ -7,10 +7,10 @@ description: Run DocGuard guard validation against Canonical-Driven Development
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.23.0
+  version: 0.25.0
   source: extensions/spec-kit-docguard/skills/docguard-guard
 ---
-<!-- docguard:version: 0.23.0 -->
+<!-- docguard:version: 0.25.0 -->
 
 # DocGuard Guard Skill
 

{docguard_cli-0.23.0/extensions/spec-kit-docguard → docguard_cli-0.25.0/.agent}/skills/docguard-review/SKILL.md

@@ -6,10 +6,10 @@ description: Cross-document consistency analysis and quality assessment. Perform
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.23.0
+  version: 0.25.0
   source: extensions/spec-kit-docguard/skills/docguard-review
 ---
-<!-- docguard:version: 0.23.0 -->
+<!-- docguard:version: 0.25.0 -->
 
 # DocGuard Review Skill
 

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.agent/skills/docguard-score/SKILL.md

@@ -6,10 +6,10 @@ description: CDD maturity assessment with category-aware improvement roadmap. Ru
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.23.0
+  version: 0.25.0
   source: extensions/spec-kit-docguard/skills/docguard-score
 ---
-<!-- docguard:version: 0.23.0 -->
+<!-- docguard:version: 0.25.0 -->
 
 # DocGuard Score Skill
 

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.agent/skills/docguard-sync/SKILL.md

@@ -4,9 +4,10 @@ description: Keep canonical documentation ALWAYS UP TO DATE. Refreshes code-trut
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.23.0
+  version: 0.25.0
   source: extensions/spec-kit-docguard/skills/docguard-sync
 ---
+<!-- docguard:version: 0.25.0 -->
 
 # DocGuard Sync Skill
 

docguard_cli-0.25.0/.claude/rules/openwolf.md

@@ -0,0 +1,15 @@
+---
+description: OpenWolf protocol enforcement — active on all files
+globs: **/*
+---
+
+- Check .wolf/anatomy.md before reading any project file
+- Check .wolf/cerebrum.md Do-Not-Repeat list before generating code
+- After writing or editing files, update .wolf/anatomy.md and append to .wolf/memory.md
+- After receiving a user correction, update .wolf/cerebrum.md immediately (Preferences, Learnings, or Do-Not-Repeat)
+- LEARN from every interaction: if you discover a convention, user preference, or project pattern, add it to .wolf/cerebrum.md. Low threshold — when in doubt, log it.
+- BEFORE fixing any bug or error: read .wolf/buglog.json for known fixes
+- AFTER fixing any bug, error, failed test, failed build, or user-reported problem: ALWAYS log to .wolf/buglog.json with error_message, root_cause, fix, and tags
+- If you edit a file more than twice in a session, that likely indicates a bug — log it to .wolf/buglog.json
+- When the user asks to check/evaluate UI design: run `openwolf designqc` to capture screenshots, then read them from .wolf/designqc-captures/
+- When the user asks to change/pick/migrate UI framework: read .wolf/reframe-frameworks.md, ask decision questions, recommend a framework, then execute with the framework's prompt

docguard_cli-0.25.0/.claude/settings.json

@@ -0,0 +1,72 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/session-start.js\"",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Read",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/pre-read.js\"",
+            "timeout": 5
+          }
+        ]
+      },
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/pre-write.js\"",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Read",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/post-read.js\"",
+            "timeout": 5
+          }
+        ]
+      },
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/post-write.js\"",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.wolf/hooks/stop.js\"",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }
+}

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.docguardignore

@@ -5,9 +5,6 @@
 Research/
 Research/**
 
-# VS Code extension build artifacts
-vscode-extension/out/
-
 # Python distribution artifacts
 dist/
 build/

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.github/scripts/patch-catalog.py

@@ -37,11 +37,11 @@ old_entry_updated = dg["updated_at"]
 old_desc = dg["description"]
 top_updated = data["updated_at"]
 
-# Correct description (matches our constitution: "Zero NPM runtime dependencies")
+# Correct description (matches our constitution: minimal, vetted dependencies)
 new_desc = (
     "Canonical-Driven Development enforcement. "
     "Validates, scores, and traces project documentation with automated checks, "
-    "AI-driven workflows, and spec-kit hooks. Zero NPM runtime dependencies."
+    "AI-driven workflows, and spec-kit hooks. One pinned runtime dependency; pure Node.js otherwise."
 )
 
 # Surgical string replacements — only touch specific values

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.github/workflows/ci.yml

@@ -23,6 +23,22 @@ jobs:
         with:
           node-version: ${{ matrix.node-version }}
 
+      # ── Install the one runtime dependency (@babel/parser) from the lockfile.
+      #    Required: without it the AST-tier tests run with Babel absent. ──
+      - name: Install dependencies
+        run: npm ci
+
+      # ── Syntax-check EVERY CLI source, not just the files the entry point
+      #    eagerly imports (a lazily/dynamically loaded module's syntax error
+      #    would otherwise slip through). This is the lint gate that would have
+      #    caught the VS Code extension shipping with a parse error. ──
+      - name: Syntax-check all CLI sources
+        run: find cli -name '*.mjs' -print0 | xargs -0 -n1 node --check
+
+      # ── Python wrapper import smoke (PyPI distribution surface) ──
+      - name: Python wrapper imports
+        run: python3 -c "import docguard_cli.wrapper; print('docguard_cli.wrapper OK')"
+
       # ── Automated Test Suite ──
       - name: Run Tests
         run: npm test

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.github/workflows/release.yml

@@ -21,23 +21,28 @@ jobs:
     steps:
       - uses: actions/checkout@v6
         with:
-          fetch-depth: 2 # Need previous commit to compare
+          fetch-depth: 1 # only need HEAD's package.json; the tag check hits the remote
 
-      - name: Check if version changed
+      - name: Check if this version needs releasing
         id: check
         run: |
           CURRENT=$(node -p "require('./package.json').version")
-          # Get version from previous commit
-          PREVIOUS=$(git show HEAD~1:package.json 2>/dev/null | node -p "JSON.parse(require('fs').readFileSync('/dev/stdin','utf-8')).version" 2>/dev/null || echo "0.0.0")
+          TAG="v${CURRENT}"
           echo "current=$CURRENT"
-          echo "previous=$PREVIOUS"
-          if [ "$CURRENT" != "$PREVIOUS" ]; then
+          # TAG-DRIVEN gate (not HEAD~1): a version needs releasing iff no tag
+          # v$CURRENT exists yet. The old HEAD~1 comparison skipped the release
+          # whenever a push carried commits AFTER the version-bump commit (the
+          # bump wasn't the tip) — e.g. a batched push of several commits. It saw
+          # HEAD and HEAD~1 both already carrying the new version and wrongly
+          # concluded "unchanged", silently skipping npm/PyPI/GitHub-Release.
+          # Checking the tag is also idempotent: a re-run won't double-publish.
+          if git ls-remote --tags origin "refs/tags/$TAG" | grep -q "refs/tags/$TAG$"; then
+            echo "changed=false" >> "$GITHUB_OUTPUT"
+            echo "⏭️ $TAG already released — nothing to do"
+          else
             echo "version=$CURRENT" >> "$GITHUB_OUTPUT"
             echo "changed=true" >> "$GITHUB_OUTPUT"
-            echo "✅ Version changed: $PREVIOUS → $CURRENT"
-          else
-            echo "changed=false" >> "$GITHUB_OUTPUT"
-            echo "⏭️ Version unchanged ($CURRENT), skipping release"
+            echo "✅ $TAG is not yet released — releasing"
           fi
 
   # ── Step 2: Run full test suite ────────────────────────────────────────
@@ -55,6 +60,8 @@ jobs:
       - uses: actions/setup-node@v6
         with:
           node-version: ${{ matrix.node-version }}
+      - name: Install dependencies
+        run: npm ci
       - name: Run Tests
         run: npm test
       - name: Guard (self-check)

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.github/workflows/sync-speckit-catalog.yml

@@ -43,7 +43,7 @@ jobs:
           echo "updated_at=$(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$GITHUB_OUTPUT"
 
           # Extract short description (avoid multiline output issues)
-          DESC="Canonical-Driven Development enforcement with automated checks, AI skills, and spec-kit hooks. Zero NPM runtime dependencies."
+          DESC="Canonical-Driven Development enforcement with automated checks, AI skills, and spec-kit hooks. One pinned runtime dependency; pure Node.js otherwise."
           echo "description=$DESC" >> "$GITHUB_OUTPUT"
 
           # Count commands

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.gitignore

@@ -29,7 +29,7 @@ dist/
 build/
 coverage/
 
-# SpecGuard generated docs (for THIS project testing)
+# DocGuard generated docs (for THIS project testing)
 # Note: In real projects, docs-canonical/ SHOULD be committed.
 # These are excluded here because they're template-generated test files.
 docguard_cli/__pycache__/

docguard_cli-0.25.0/.jules-setup.sh

@@ -0,0 +1,41 @@
+#!/bin/bash
+# ==========================================
+# Google Jules Environment Startup Script
+# ==========================================
+# Use this configuration in the Jules Dashboard:
+# Repo -> Configuration -> Initial Setup
+
+set -e
+
+# ------------------------------------------
+# 1. Inject Headless Dummy Credentials
+# ------------------------------------------
+# Mocking AI provider keys in case tests or agent integrations require them
+export GEMINI_API_KEY="dummy-jules-key"
+export ANTHROPIC_API_KEY="dummy-anthropic-key"
+export OPENAI_API_KEY="dummy-openai-key"
+
+# ------------------------------------------
+# 2. Ecosystem-Specific Dependency Installation
+# ------------------------------------------
+echo "📦 === Installing Dependencies ==="
+# Note: DocGuard has zero production dependencies, but we run npm install
+# in case devDependencies are added in the future.
+npm install
+
+# ------------------------------------------
+# 3. Ecosystem-Specific Tests & Build Checks
+# ------------------------------------------
+echo "🧪 === Running Initial Test & Validation ==="
+# Execute the native Node.js tests
+npm test || echo "⚠️ Tests failed, but continuing..."
+
+echo "🏗️ === Verifying Build Integrity ==="
+# Test the primary CLI entrypoint to ensure it is executable
+node cli/docguard.mjs --version
+
+echo "🧹 === Enforcing Git Tree Integrity ==="
+# Jules requires the working directory to be clean after this script runs
+git clean -fd || true
+
+echo "✅ Jules VM Local Environment is Ready!"

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.npmignore

@@ -1,7 +1,6 @@
 # Development
 .git/
 .github/
-.specguard.json
 Research/
 docs-canonical/
 docs-implementation/

{docguard_cli-0.23.0 → docguard_cli-0.25.0}/.specify/memory/constitution.md

@@ -15,9 +15,11 @@
 
 DocGuard is built for AI coding agents. Every feature MUST be designed for LLM consumption first, with CLI as a secondary interface. Skills (behavior protocols) take priority over CLI commands (step-lists). When DocGuard detects an AI agent environment, it MUST surface skill-based instructions. CLI output MUST be machine-parseable (JSON mode) alongside human-readable text.
 
-### II. Zero NPM Runtime Dependencies (NON-NEGOTIABLE)
+### II. Minimal, Vetted Dependencies (NON-NEGOTIABLE)
 
-DocGuard has zero `node_modules` at runtime. All Node.js functionality uses built-in modules only (`node:fs`, `node:path`, `node:child_process`, `node:test`, `node:url`, `node:readline`, `node:os`, `node:assert`). This maximizes portability, eliminates supply chain risk, and ensures instant `npx` usage. Dev dependencies are also zero — tests use `node:test`. DocGuard depends on spec-kit as a **framework convention** (`.specify/` directory structure, skill architecture, constitution pattern). This is an integration, not a code dependency. When the `specify` CLI is available, DocGuard MUST leverage it for initialization and skill management.
+DocGuard ships with exactly **one** runtime dependency: `@babel/parser` (exact-pinned), which powers AST-accurate JavaScript/TypeScript parsing for the full-support language tier. Regex-only extraction silently truncated any nested structure (`z.object({ ... })` inside another, a Mongoose field object), and a scanner that returns too little makes the doc validators falsely pass — so a real parser earns its place. Everything else uses Node.js built-ins only (`node:fs`, `node:path`, `node:child_process`, `node:test`, `node:url`, `node:readline`, `node:os`, `node:assert`, `node:module`). The parser loads **optionally**: if it's ever absent the CLI degrades to the regex (beta) tier rather than crashing, so `npx` stays robust.
+
+Any NEW dependency is governed (NON-NEGOTIABLE): it MUST be justified against built-ins, exact-pinned (no `^`/`~`/`>=`), pass supply-chain vetting (>10k weekly downloads, >1 maintainer, first-published >30 days ago), and degrade gracefully if missing. Dev dependencies remain zero — tests use `node:test`. DocGuard also depends on spec-kit as a **framework convention** (`.specify/` structure, skills, constitution pattern); that is an integration, not a code dependency. When the `specify` CLI is available, DocGuard MUST leverage it for initialization and skill management.
 
 ### III. Documentation as Source of Truth
 

docguard_cli-0.25.0/.wolf/OPENWOLF.md

@@ -0,0 +1,135 @@
+# OpenWolf Operating Protocol
+
+You are working in an OpenWolf-managed project. These rules apply every turn.
+
+## File Navigation
+
+1. Check `.wolf/anatomy.md` BEFORE reading any file. It has a 2-3 line description and token estimate for every file in the project.
+2. If the description in anatomy.md is sufficient for your task, do NOT read the full file.
+3. If a file is not in anatomy.md, search with Grep/Glob, then update anatomy.md with the new entry.
+
+## Code Generation
+
+1. Before generating code, read `.wolf/cerebrum.md` and respect every entry.
+2. Check the `## Do-Not-Repeat` section — these are past mistakes that must not recur.
+3. Follow all conventions in `## Key Learnings` and `## User Preferences`.
+
+## After Actions
+
+1. After every significant action, append a one-line entry to `.wolf/memory.md`:
+   `| HH:MM | description | file(s) | outcome | ~tokens |`
+2. After creating, deleting, or renaming files: update `.wolf/anatomy.md`.
+
+## Cerebrum Learning (MANDATORY — every session)
+
+OpenWolf's value comes from learning across sessions. You MUST update `.wolf/cerebrum.md` whenever you learn something useful. This is not optional.
+
+**Update `## User Preferences` when the user:**
+- Corrects your approach ("no, do it this way instead")
+- Expresses a style preference (naming, structure, formatting)
+- Shows a preferred workflow or tool choice
+- Rejects a suggestion — record what they preferred instead
+- Asks for more/less detail, verbosity, explanation
+
+**Update `## Key Learnings` when you discover:**
+- A project convention not obvious from the code (e.g., "tests go in __tests__/ not test/")
+- A framework-specific pattern this project uses
+- An API behavior that surprised you
+- A dependency quirk or version constraint
+- How modules connect or data flows through the system
+
+**Update `## Do-Not-Repeat` (with date) when:**
+- The user corrects a mistake you made
+- You try something that fails and find the right approach
+- You discover a gotcha that would trip up a fresh session
+
+**Update `## Decision Log` when:**
+- A significant architectural or technical choice is made
+- The user explains why they chose approach A over B
+- A trade-off is explicitly discussed
+
+**The bar is LOW.** If in doubt, add it. A cerebrum entry that's slightly redundant costs nothing. A missing entry means the next session repeats the same discovery process.
+
+## Bug Logging (MANDATORY)
+
+**Log a bug to `.wolf/buglog.json` whenever ANY of these happen:**
+- The user reports an error, bug, or problem
+- A test fails or a command produces an error
+- You fix something that was broken
+- You edit a file more than twice to get it right
+- An import, module, or dependency is missing or wrong
+- A runtime error, type error, or syntax error occurs
+- A build or lint command fails
+- A feature doesn't work as expected
+- You change error handling, try/catch blocks, or validation logic
+- The user says something "doesn't work", "is broken", or "shows wrong X"
+
+**Before fixing:** Read `.wolf/buglog.json` first — the fix may already be known.
+
+**After fixing:** ALWAYS append to `.wolf/buglog.json` with this structure:
+```json
+{
+  "id": "bug-NNN",
+  "timestamp": "ISO date",
+  "error_message": "exact error or user complaint",
+  "file": "file that was fixed",
+  "root_cause": "why it broke",
+  "fix": "what you changed to fix it",
+  "tags": ["relevant", "keywords"],
+  "related_bugs": [],
+  "occurrences": 1,
+  "last_seen": "ISO date"
+}
+```
+
+**The threshold is LOW.** When in doubt, log it. A false positive in the bug log costs nothing. A missed bug means repeating the same mistake later.
+
+## Token Discipline
+
+- Never re-read a file already read this session unless it was modified since.
+- Prefer anatomy.md descriptions over full file reads when possible.
+- Prefer targeted Grep over full file reads when searching for specific code.
+- If appending to a file, do not read the entire file first.
+
+## Design QC
+
+When the user asks you to check, evaluate, or improve the design/UI of their app:
+
+1. Run `openwolf designqc` via Bash to capture screenshots.
+   - The command auto-detects a running dev server, or starts one from package.json if needed
+   - Use `--url <url>` only if auto-detection fails
+   - The command saves compressed JPEG screenshots to `.wolf/designqc-captures/`
+   - Full pages are captured as sectioned viewport-height images (top, section2, ..., bottom)
+2. Read the captured screenshot images from `.wolf/designqc-captures/` using the Read tool.
+3. Evaluate the design against modern standards (Shadcn UI, Tailwind, clean React patterns):
+   - Spacing and whitespace consistency
+   - Typography hierarchy and readability
+   - Color contrast and accessibility (WCAG)
+   - Visual hierarchy and focal points
+   - Component consistency
+   - Whether the design looks "dull" or "white-coded" (generic, no personality)
+4. Provide specific, actionable feedback with fix suggestions.
+5. If the user approves, implement the fixes directly in their code.
+6. After fixes, re-run `openwolf designqc` to capture new screenshots and verify improvement.
+
+**Token awareness:** Each screenshot costs ~2500 tokens. The command compresses images (JPEG quality 70, max width 1200px) to minimize cost. For large apps, use `--routes / /specific-page` to limit captures.
+
+## Reframe — UI Framework Selection
+
+When the user asks to change, pick, migrate, or "reframe" their project's UI framework:
+
+1. Read `.wolf/reframe-frameworks.md` for the full framework knowledge base.
+2. Ask the user the decision questions from the file (current stack, priority, Tailwind usage, theme preference, app type). Stop early once the choice narrows to 1-2 options.
+3. Present a recommendation with reasoning based on the comparison matrix.
+4. Once the user confirms, use the selected framework's prompt from the file — **adapted to the actual project** using `.wolf/anatomy.md` for real file paths, routes, and components.
+5. Execute the migration: install dependencies, update config, refactor components.
+6. After migration, run `openwolf designqc` to verify the new look.
+
+**Do NOT read the entire reframe-frameworks.md into context upfront.** Read the decision questions and comparison matrix first (~50 lines). Only read the specific framework's prompt section after the user chooses.
+
+## Session End
+
+Before ending or when asked to wrap up:
+
+1. Write a session summary to `.wolf/memory.md`.
+2. Review the session: did you learn anything? Did the user correct you? Did you fix a bug? If yes, update `.wolf/cerebrum.md` and/or `.wolf/buglog.json`.