azclaude-copilot 0.5.7 → 0.5.9

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "azclaude",
       "description": "AZCLAUDE is a complete AI coding environment for Claude Code. It installs 39 commands, 10 auto-invoked skills, 15 specialized agents, 4 hooks, 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.5.7",
+      "version": "0.5.9",
       "source": {
         "source": "github",
         "repo": "haytamAroui/AZ-CLAUDE-COPILOT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "azclaude",
-  "version": "0.5.7",
+  "version": "0.5.9",
   "description": "AZCLAUDE is a complete AI coding environment for Claude Code. It installs 39 commands, 10 auto-invoked skills, 15 specialized agents, 4 hooks, 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

@@ -94,7 +94,6 @@ AZCLAUDE sits as a mandatory middleware firewall between your input and Claude.
 ┌──────────────────────────────────────────────────────────────┐
 │ 5. OUTBOUND SECURITY & MEMORY TRACKING                       │
 │  ├─► pre-tool-use.js: blocks curl|bash, secrets, traversal   │
-│  ├─► Native execution: Claude runs the approved command      │
 │  └─► post-tool-use.js: writes breadcrumb to goals.md         │
 └──────────────────────────────────────────────────────────────┘
 ```
@@ -118,6 +117,7 @@ One command, no flags. Auto-detects whether this is a fresh install or an upgrad
 ```bash
 npx azclaude-copilot@latest doctor   # 32 checks — verify everything is wired correctly
 ```
+│  ├─► Native execution: Claude runs the approved command      │
 
 ---
 
@@ -624,11 +624,11 @@ AZCLAUDE is a lazy-loaded environment of 48 capability modules. It only loads wh
 
 ## Verified
 
-1794 tests. Every template, command, capability, agent, hook, and CLI feature verified.
+1810 tests. Every template, command, capability, agent, hook, and CLI feature verified.
 
 ```bash
 bash tests/test-features.sh
-# Results: 1794 passed, 0 failed, 1794 total
+# Results: 1810 passed, 0 failed, 1810 total
 ```
 
 ---

package/package.json

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

package/templates/agents/orchestrator.md

@@ -36,6 +36,25 @@ If CLAUDE.md unfilled → run `/setup` with intent from copilot-intent.md first.
 
 ---
 
+### Step 1b: Resume Interrupted Parallel Wave
+
+```bash
+cat .claude/parallel-wave-state.md 2>/dev/null
+```
+
+If the file exists with `status: in-flight` → a previous session was interrupted mid-parallel-dispatch.
+
+**Do NOT skip this. Do NOT start a new wave until the interrupted wave is resolved.**
+
+Follow the Resume Protocol from `capabilities/shared/parallel-coordination.md`:
+1. Read the wave state file — it lists every milestone, branch, and last-known status
+2. For each `running` milestone: check if `parallel/{slug}` branch exists and has commits
+3. Branches with commits → mark `done`, proceed to merge
+4. Branches without commits or missing → re-dispatch those milestones
+5. After all milestones resolved → merge → delete `.claude/parallel-wave-state.md` → continue
+
+---
+
 ### Step 2: Select Next Milestone Wave
 
 **If plan.md has `Wave:` fields** (blueprint wrote them — read directly):

package/templates/capabilities/shared/parallel-coordination.md

@@ -166,6 +166,144 @@ These rules are injected by orchestrator into every parallel milestone-builder p
 
 ---
 
+## Proven Patterns — 3-Layer Conflict Prevention
+
+These patterns come from a real production run: 16 agents, 360 tests, zero merge conflicts.
+
+### Layer 1: Wave 0 — Bottleneck Files First (Sequential)
+
+Identify files that multiple milestones need to modify (shared models, core config, base schemas).
+**Do NOT parallelize these.** Instead, create a Wave 0 that runs sequentially before any parallel agents:
+
+```
+Wave 0 (sequential, orchestrator or single agent):
+  models.py      → ALL new fields added at once
+  versioning.py  → version bump
+  shared_config  → all schema changes
+
+Result: every subsequent agent finds shared dependencies already in place.
+```
+
+**Rule: SHARED DEPENDENCY → Wave 0 (sequential, do it first)**
+
+### Layer 2: Directory-Level File Isolation
+
+Design each parallel wave so agents own completely disjoint files:
+
+```
+Wave 1 (3 agents, zero file overlap):
+  Agent A: annex_1_rules.py, rules.py, conformity_path.py, test_annex_1.py
+  Agent B: gpai_rules.py, test_gpai_copyright.py
+  Agent C: test_fria_trigger.py, test_national_law_router.py (NEW files only)
+```
+
+**Test-only agents are always safe in parallel** — they create new test files and read (never write) engine code.
+
+**Rule: TEST-ONLY agents → always safe in any wave**
+
+### Layer 3: Same File, Different Sections
+
+When two agents must touch the same file, allow it **only if edits are 100+ lines apart**:
+
+```
+┌───────┬────────────────────────────────┬────────────┐
+│ Agent │ Section in rules.py            │ Line range │
+├───────┼────────────────────────────────┼────────────┤
+│ M2A   │ After result construction      │ ~line 392  │
+│ M2C   │ STEP 13 deadline unpacking     │ ~line 273  │
+└───────┴────────────────────────────────┴────────────┘
+```
+
+Git merges these cleanly because they don't touch overlapping context (3-line hunk window).
+
+**Rule: SAME FILE, DIFFERENT SECTIONS (100+ lines apart) → allowed in parallel**
+**Rule: SAME FILE, SAME SECTION → serialize into different waves**
+
+### Decision Table
+
+| Conflict type | Resolution |
+|---------------|-----------|
+| Multiple milestones need same model/schema file | Wave 0: one agent fixes it sequentially before all others |
+| Agents write different files entirely | Safe for parallel — standard worktree isolation |
+| Agents write same file, edits 100+ lines apart | Allowed in parallel — git auto-merges cleanly |
+| Agents write same file, edits < 100 lines apart | Serialize into different waves |
+| Agent only creates new test files | Always safe in any wave — no write conflicts possible |
+| Agent changes a function's return type | Must also fix all callers in the same agent's scope |
+
+---
+
+## Wave State File — Context Loss Protection
+
+During parallel execution, the orchestrator writes `.claude/parallel-wave-state.md` **before dispatching any agents**. This file survives context compaction and enables session resume.
+
+### Format
+
+```markdown
+---
+wave: {N}
+started: {ISO timestamp}
+status: in-flight
+milestones: [M3, M4, M5]
+---
+
+| Milestone | Branch | Status | Commit | Notes |
+|-----------|--------|--------|--------|-------|
+| M3 — Auth endpoints | parallel/m3-auth | running | — | P1 slot |
+| M4 — User profile | parallel/m4-profile | done | a1b2c3d | merged to worktree |
+| M5 — Email service | parallel/m5-email | failed | — | timeout on test suite |
+```
+
+### Lifecycle
+
+1. **Created** — by `/parallel` Step 4 or orchestrator Step 4, before agent dispatch
+2. **Updated** — as each agent reports completion (status → `done`/`failed`, commit hash filled)
+3. **Deleted** — by orchestrator Step 8 or `/parallel` Step 8, after all branches merged and cleanup done
+
+### Rules
+
+- The file MUST exist whenever parallel agents are in-flight
+- If this file exists at session start → a previous wave was interrupted → trigger Resume Protocol
+- Only the orchestrator or `/parallel` command writes this file — builders never touch it
+
+---
+
+## Resume Protocol — Recovering Interrupted Waves
+
+When the orchestrator or `/parallel` finds `.claude/parallel-wave-state.md` at session start:
+
+### Step 1: Read Wave State
+```bash
+cat .claude/parallel-wave-state.md
+```
+
+### Step 2: Check Each Branch
+For every milestone with `status: running` (was in-flight when session died):
+```bash
+# Does the branch exist?
+git branch --list "parallel/{slug}"
+
+# Does it have commits beyond the fork point?
+git log main..parallel/{slug} --oneline 2>/dev/null | head -5
+```
+
+### Step 3: Classify Each Milestone
+
+| Branch exists? | Has commits? | Action |
+|---------------|-------------|--------|
+| Yes | Yes | Mark `done` in wave state — ready to merge |
+| Yes | No | Agent never started — re-dispatch |
+| No | — | Branch was cleaned up or never created — re-dispatch |
+
+### Step 4: Resume
+- Milestones marked `done` or with commits → proceed to Merge Protocol
+- Milestones needing re-dispatch → spawn new agents (same parameters as original dispatch)
+- Update `.claude/parallel-wave-state.md` with new statuses before re-dispatching
+
+### Step 5: Continue Normal Flow
+After resume completes, continue with Merge Protocol → Plan Update → Cleanup as usual.
+
+---
+
 ## Ownership Map Cleanup
 
 After wave merge is complete:
@@ -173,4 +311,7 @@ After wave merge is complete:
 # Remove ownership.md entries for the completed wave
 # (or replace the table with a merge record)
 echo "## Wave {N} merged — {timestamp}" >> .claude/ownership.md
+
+# CRITICAL: Delete wave state file — prevents false resume on next session
+rm -f .claude/parallel-wave-state.md
 ```

package/templates/commands/parallel.md

@@ -21,6 +21,18 @@ Load: `capabilities/shared/parallel-coordination.md`
 
 ---
 
+## Step 0: Check for Interrupted Wave
+
+```bash
+cat .claude/parallel-wave-state.md 2>/dev/null
+```
+
+If the file exists with `status: in-flight` → a previous parallel session was interrupted.
+Follow the **Resume Protocol** from `parallel-coordination.md` before starting a new wave.
+Only proceed to Step 1 after the interrupted wave is fully resolved (merged or re-dispatched).
+
+---
+
 ## Step 1: Parse Targets
 
 ```bash
@@ -68,9 +80,9 @@ If any milestone returns `Parallel Safe: NO` → exclude from parallel wave, run
 
 ---
 
-## Step 4: Write Ownership Map
+## Step 4: Write Ownership Map + Wave State
 
-Create or update `.claude/ownership.md`:
+**4a. Ownership map** — create or update `.claude/ownership.md`:
 
 ```
 ## Active Parallel Session — {ISO timestamp}
@@ -83,6 +95,24 @@ Initiated by: /parallel command
 | P2 | M{N} — {title} | parallel/m{n}-{slug} | {dirs from spec} | pending |
 ```
 
+**4b. Wave state file** — write `.claude/parallel-wave-state.md` BEFORE dispatching agents:
+
+```markdown
+---
+wave: {N}
+started: {ISO timestamp}
+status: in-flight
+milestones: [{list}]
+---
+
+| Milestone | Branch | Status | Commit | Notes |
+|-----------|--------|--------|--------|-------|
+| M{N} — {title} | parallel/m{n}-{slug} | running | — | P1 slot |
+| M{N} — {title} | parallel/m{n}-{slug} | running | — | P2 slot |
+```
+
+This file survives context compaction. If the session dies mid-wave, the next session reads this file to resume.
+
 ---
 
 ## Step 5: Dispatch All Agents Simultaneously
@@ -116,6 +146,7 @@ Worktree rules (MANDATORY):
 After all agents complete:
 - Collect all completion reports
 - Mark each as COMPLETE or FAILED in ownership.md
+- **Update `.claude/parallel-wave-state.md`** — set each milestone's Status to `done`/`failed`, fill Commit hash
 
 ---
 
@@ -150,6 +181,7 @@ git branch -d parallel/{slug-1} parallel/{slug-2}
 
 Update `.claude/plan.md` — set merged milestones to `status: done`.
 Update `.claude/ownership.md` — replace active table with merge record.
+**Delete `.claude/parallel-wave-state.md`** — wave is complete, prevent false resume on next session.
 
 Show final report:
 ```

package/templates/commands/snapshot.md

@@ -17,6 +17,14 @@ This is different from `/persist` (end-of-session). Checkpoint = mid-flight snap
 
 Read `.claude/memory/goals.md` — scan the "In progress" entries and "Current threads."
 
+**Step 1b: Detect Active Parallel Wave**
+
+```bash
+cat .claude/parallel-wave-state.md 2>/dev/null
+```
+
+If the file exists → a parallel wave is active. Read it and include wave status in the checkpoint (Step 2).
+
 ---
 
 ## Step 2: Write Checkpoint File
@@ -48,6 +56,9 @@ files_in_progress: [{list from goals.md ## In progress}]
 
 ## Risk / open question
 {Anything uncertain that needs resolution — or "None"}
+
+## Active parallel wave (if any)
+{Copy the full contents of .claude/parallel-wave-state.md here, or "No active wave"}
 ```
 
 Create the directory if needed: `.claude/memory/checkpoints/`

package/templates/hooks/user-prompt.js

@@ -233,13 +233,25 @@ try {
         if (fs.existsSync(goalsPath)) {
           const goalsContent = fs.readFileSync(goalsPath, 'utf8');
           const header = `---\ndate: ${new Date().toISOString()}\nlabel: auto-compaction-guard-${pct}pct\nfiles_in_progress: []\n---\n\n`;
-          fs.writeFileSync(cpPath, header + '## Auto-saved before compaction\n\n' + goalsContent);
+          let cpContent = '## Auto-saved before compaction\n\n' + goalsContent;
+
+          // Include parallel wave state if an active wave exists
+          const waveStatePath = path.join(cfg, 'parallel-wave-state.md');
+          if (fs.existsSync(waveStatePath)) {
+            const waveContent = fs.readFileSync(waveStatePath, 'utf8');
+            cpContent += '\n\n## Active Parallel Wave (saved by compaction guard)\n\n' + waveContent;
+          }
+
+          fs.writeFileSync(cpPath, header + cpContent);
           fs.writeFileSync(autoSaveMarker, '');
         }
 
         console.log('');
         console.log(`--- COMPACTION GUARD (${pct}%) ---`);
         console.log(`Context at ${pct}% — AUTO-SAVED checkpoint to ${path.basename(cpPath)}`);
+        if (fs.existsSync(waveStatePath)) {
+          console.log('PARALLEL WAVE STATE INCLUDED — interrupted wave will auto-resume on next session.');
+        }
         console.log('Run /snapshot NOW to save your reasoning and decisions (goals.md alone is not enough).');
         console.log('--- END GUARD ---');
       }