azclaude-copilot 0.7.5 → 0.7.6

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "azclaude",
       "description": "AZCLAUDE is a complete AI coding environment for Claude Code. It installs 40 commands, 10 auto-invoked skills, 15 specialized agents, 5 hooks, a real-time pipeline visualizer, and a persistent memory system — in one command.\n\nKey features:\n• Memory across sessions — goals.md + checkpoints injected automatically before every session\n• Self-improving loop — /reflect fixes stale CLAUDE.md rules, /reflexes learns from tool-use patterns, /evolve creates agents from git evidence\n• Autonomous copilot mode — /copilot runs a three-tier team (orchestrator → problem-architect → milestone-builder) across sessions until the product ships\n• Spec-driven workflow — /constitute writes project rules, /spec writes structured ACs, /analyze detects plan drift and ghost milestones, /blueprint traces every milestone to a spec\n• Security layer — 111-rule environment scan (/sentinel), pre-write secret blocking, pre-ship credential audit\n• Progressive levels 0–10 — start with CLAUDE.md, grow into multi-agent pipelines and self-evolving environments\n• Zero dependencies — no npm packages, no external APIs, no vector databases. Plain markdown files and Claude Code's native architecture.\n• Smart install — npx azclaude-copilot@latest auto-detects first install vs upgrade vs verify. Context-aware onboarding shows the right next command for your project state.\n\nExample use cases:\n• /setup — scan an existing project, detect stack + domain + scale, fill CLAUDE.md, generate project-specific skills and agents automatically\n• /copilot \"Build a compliance SaaS with trilingual support\" — walk away, come back to working code across multiple sessions\n• /sentinel — run a scored security audit (0–100, grade A–F) across hooks, permissions, MCP servers, agent configs, and secrets\n• /evolve — detect gaps in the environment, generate new skills and agents from git co-change evidence, report score delta (e.g. 42/100 → 68/100)\n• /constitute — write your project's constitution (non-negotiables, architectural commitments, definition of done) — gates all future AI actions\n• /analyze — cross-artifact consistency check: ghost milestones, spec vs. code drift, unplanned commits\n• /reflect — find stale, missing, or contradicting rules in CLAUDE.md and propose exact fixes\n• /debate \"REST vs GraphQL for this project\" — adversarial evidence-based decision with order-independent scoring, logged to decisions.md",
-      "version": "0.7.5",
+      "version": "0.7.6",
       "source": {
         "source": "github",
         "repo": "haytamAroui/AZ-CLAUDE-COPILOT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "azclaude",
-  "version": "0.7.5",
+  "version": "0.7.6",
   "description": "AZCLAUDE is a complete AI coding environment for Claude Code. It installs 40 commands, 10 auto-invoked skills, 15 specialized agents, 5 hooks, a real-time pipeline visualizer, and a persistent memory system — in one command.\n\nKey features:\n• Memory across sessions — goals.md + checkpoints injected automatically before every session\n• Self-improving loop — /reflect fixes stale CLAUDE.md rules, /reflexes learns from tool-use patterns, /evolve creates agents from git evidence\n• Autonomous copilot mode — /copilot runs a three-tier team (orchestrator → problem-architect → milestone-builder) across sessions until the product ships\n• Spec-driven workflow — /constitute writes project rules, /spec writes structured ACs, /analyze detects plan drift and ghost milestones, /blueprint traces every milestone to a spec\n• Security layer — 111-rule environment scan (/sentinel), pre-write secret blocking, pre-ship credential audit\n• Progressive levels 0–10 — start with CLAUDE.md, grow into multi-agent pipelines and self-evolving environments\n• Zero dependencies — no npm packages, no external APIs, no vector databases. Plain markdown files and Claude Code's native architecture.\n• Smart install — npx azclaude-copilot@latest auto-detects first install vs upgrade vs verify. Context-aware onboarding shows the right next command for your project state.\n\nExample use cases:\n• /setup — scan an existing project, detect stack + domain + scale, fill CLAUDE.md, generate project-specific skills and agents automatically\n• /copilot \"Build a compliance SaaS with trilingual support\" — walk away, come back to working code across multiple sessions\n• /sentinel — run a scored security audit (0–100, grade A–F) across hooks, permissions, MCP servers, agent configs, and secrets\n• /evolve — detect gaps in the environment, generate new skills and agents from git co-change evidence, report score delta (e.g. 42/100 → 68/100)\n• /constitute — write your project's constitution (non-negotiables, architectural commitments, definition of done) — gates all future AI actions\n• /analyze — cross-artifact consistency check: ghost milestones, spec vs. code drift, unplanned commits\n• /reflect — find stale, missing, or contradicting rules in CLAUDE.md and propose exact fixes\n• /debate \"REST vs GraphQL for this project\" — adversarial evidence-based decision with order-independent scoring, logged to decisions.md",
   "author": {
     "name": "haytamAroui",

package/README.md

@@ -637,11 +637,11 @@ AZCLAUDE is a lazy-loaded environment of 48 capability modules. It only loads wh
 
 ## Verified
 
-1958 tests. Every template, command, capability, agent, hook, and CLI feature verified.
+1967 tests. Every template, command, capability, agent, hook, and CLI feature verified.
 
 ```bash
 bash tests/test-features.sh
-# Results: 1958 passed, 0 failed, 1958 total
+# Results: 1967 passed, 0 failed, 1967 total
 ```
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "azclaude-copilot",
-  "version": "0.7.5",
+  "version": "0.7.6",
   "description": "AI coding environment — 40 commands, 10 skills, 15 agents, real-time visualizer, memory, reflexes, evolution. Install: npx azclaude-copilot@latest, then open Claude Code.",
   "bin": {
     "azclaude": "bin/cli.js",

package/templates/agents/milestone-builder.md

@@ -60,6 +60,23 @@ Do NOT skip pre-reads. Context-blind implementation is the most common failure m
 
 ---
 
+### Step 1b: Web Research (if Team Spec says REQUIRED)
+
+Check your prompt for `## Web Research`. If it says `REQUIRED`:
+1. Run the search queries listed (WebSearch for best practices, common pitfalls)
+2. Fetch official docs if a URL is provided (WebFetch)
+3. Note findings that affect your implementation:
+   - Deprecated methods → use the replacement
+   - Breaking changes → adapt code to current API
+   - Common pitfalls → add to your anti-patterns for this milestone
+4. If a search reveals the Team Spec's approach is outdated → report to orchestrator before proceeding
+
+If `SKIP` or no Web Research section → proceed directly to Step 2.
+
+**Why:** Claude's training data is frozen. A 30-second web search prevents hours of debugging deprecated code.
+
+---
+
 ### Step 2: Implement
 
 If TDD active:

package/templates/agents/orchestrator.md

@@ -239,6 +239,14 @@ Pre-conditions verified:
 Complexity: {SIMPLE|MEDIUM|COMPLEX}
 Fix attempts: {2 for SIMPLE/MEDIUM, 3 for COMPLEX}
 
+## Web Research (from Team Spec)
+{REQUIRED or SKIP}
+{If REQUIRED, include the search queries from the Team Spec:}
+- Search: "{technology} {version} best practices {year}"
+- Search: "{technology} common pitfalls {year}"
+- Fetch: {docs URL}
+Run these searches BEFORE writing any code. Include findings in your implementation decisions.
+
 Only read files NOT listed in Pre-loaded Context.
 When done, report: files changed + test status + new patterns/anti-patterns.
 ```

package/templates/agents/problem-architect.md

@@ -87,6 +87,19 @@ If milestone crosses 2+ agent boundaries → recommend sequential: agent-A first
   (e.g., GraphQL, Stripe, i18n, accessibility, ML pipeline), mark it as MISSING in the Team Spec.
   The orchestrator will use skill-creator to generate it before dispatch.
 
+**Web Research — classify this milestone:**
+Scan the milestone for external dependencies (imports, API calls, library usage):
+```bash
+# Check what the milestone's files import
+grep -r "import\|require\|from " src/ --include="*.ts" --include="*.py" --include="*.js" -l 2>/dev/null | head -10
+# Check package.json / requirements.txt for external deps
+cat package.json 2>/dev/null | grep -E '"dependencies"' -A 50 | head -30
+```
+- If milestone touches ANY external API, library, or framework → `Web Research: REQUIRED`
+- If milestone is pure internal code (no imports from node_modules, no API calls) → `Web Research: SKIP`
+- If milestone creates a new skill or agent for external technology → `Web Research: REQUIRED`
+- Include specific search queries the builder should run (technology + version + year)
+
 **Pre-Read Files:**
 - Schema files (if touching DB)
 - API specs (if touching endpoints)
@@ -136,6 +149,16 @@ Output this EXACT format — the orchestrator parses it:
 - {domain/technology}: needed because {reason} — use skill-creator to generate
   (omit this section if all needed skills are installed)
 
+### Web Research
+REQUIRED | SKIP
+If REQUIRED:
+- Search: "{technology} {version} best practices {year}"
+- Search: "{technology} common pitfalls {year}"
+- Fetch: {official docs URL if known}
+- Reason: {why this milestone needs current info — e.g. "uses Stripe webhook v2025 signatures"}
+If SKIP: reason = {pure internal code, no external dependencies}
+The milestone-builder runs these searches BEFORE writing code. Orchestrator includes this in the prompt.
+
 ### Pre-Read Files
 - {file-path}: for {specific context reason}