@danmoisan/drm-copilot-mcp 1.1.15 → 1.1.16

package/resources/customizations/.github/agents/powershell-orchestrator.agent.md

@@ -14,7 +14,7 @@ handoffs:
     send: true
   - label: Small-scope implementation path
     agent: powershell-typed-engineer
-    prompt: "Estimate and confirm scope (1-2 production PowerShell files + corresponding tests). If confirmed, execute the constrained short-path implementation phase from the approved minimal-audit plan and return analyzer/test/coverage deltas."
+    prompt: "Estimate and confirm scope (1-3 production PowerShell files + corresponding tests). If confirmed, execute the constrained short-path implementation phase from the approved minimal-audit plan and return analyzer/test/coverage deltas."
     send: true
   - label: Validate small-path delivery and post-QC docs
     agent: atomic_executor
@@ -98,8 +98,8 @@ Use these reusable skills to avoid duplicating shared operations:
 
 3) **Single source of routing truth = change budget**
 - First action is always to estimate rough change budget by identifying likely affected production PowerShell files.
-- If estimate is `1-2` production PowerShell files (+ corresponding tests), use **small path**.
-- If estimate is `>2` production PowerShell files, use **large path**.
+- If estimate is `1-3` production PowerShell files (+ corresponding tests), use **small path**.
+- If estimate is more than 3 (`>3`) production PowerShell files, use **large path**. The large path has no production-file cap.
 
 4) **Deterministic variable handling**
 - Persist and reuse these variables exactly as names:
@@ -123,12 +123,12 @@ Use these reusable skills to avoid duplicating shared operations:
 2. Estimate rough change budget.
 3. Write/update orchestration checkpoint.
 4. Route to one of two paths:
-   - **Small path**: budget `1-2`
-   - **Large path**: budget `>2`
+   - **Small path**: budget `1-3`
+   - **Large path**: budget `>3`
 
 ---
 
-## Small path (budget 1-2 production PowerShell files)
+## Small path (budget 1-3 production PowerShell files)
 
 Follow this exact sequence.
 
@@ -245,7 +245,7 @@ Hard enforcement for S8:
 
 ---
 
-## Large path (budget >2 production PowerShell files)
+## Large path (budget >3 production PowerShell files)
 
 Follow this exact sequence.
 

package/resources/customizations/.github/agents/powershell-typed-engineer.agent.md

@@ -49,8 +49,8 @@ Use these reusable skills to avoid duplicating shared operations:
 
 - **Direct mode (default)**
   - Trigger: no directive line present.
-  - Intended scope: up to 2 production PowerShell files (+ corresponding tests).
-  - If estimated scope is >2 production files: stop and instruct caller to use `powershell-orchestrator` (or `.github/prompts/orchestrate-powershell-work.prompt.md`).
+  - Intended scope: 1-3 production PowerShell files (+ corresponding tests).
+  - If estimated scope is more than 3 production files: stop and instruct caller to use `powershell-orchestrator` (or `.github/prompts/orchestrate-powershell-work.prompt.md`).
 
 - **Orchestrator handoff mode**
   - Trigger: request includes exact line `DIRECTIVE: ORCHESTRATOR HANDOFF MODE`.
@@ -115,9 +115,9 @@ Blocking rules in orchestrator mode:
 
 ## 1) Scope control (NO scope creep)
 
-- **Direct mode** default scope is one small feature/bug slice (typically **1–2 production PowerShell files**) plus corresponding test file(s).
-- In **Direct mode**, if estimated scope exceeds **2 production PowerShell files**, do not continue implementation; instruct the user to invoke `powershell-orchestrator` (or `.github/prompts/orchestrate-powershell-work.prompt.md`) and stop.
-- In **Orchestrator handoff mode**, overall scope may exceed 2 production files when supported by provided context package and approved plan artifacts.
+- **Direct mode** default scope is one small feature/bug slice (typically **1-3 production PowerShell files**) plus corresponding test file(s).
+- In **Direct mode**, if estimated scope exceeds **3 production PowerShell files**, do not continue implementation; instruct the user to invoke `powershell-orchestrator` (or `.github/prompts/orchestrate-powershell-work.prompt.md`) and stop.
+- In **Orchestrator handoff mode**, overall scope may exceed 3 production files when supported by provided context package and approved plan artifacts.
 - In all modes, avoid unrelated files and preserve minimal, targeted changes.
 - If scope expansion is required, STOP and provide:
   - a one-paragraph justification,
@@ -127,11 +127,9 @@ Blocking rules in orchestrator mode:
 
 ## 2) Change budget (hard gate)
 
-- **Direct mode** overall budget: up to **2 production PowerShell files** (+ corresponding tests).
+- **Direct mode** overall budget: **1-3 production PowerShell files** (+ corresponding tests).
 - **Orchestrator handoff mode**: no strict overall production-file budget, provided required documentation package is present.
-- In all modes, per-batch budget remains: at most **3 production files** and **3 test files** unless explicit override is approved.
-- If no override is provided, the 3/3 per-batch limit applies.
-- If a batch would exceed budget, split it into smaller batches.
+- Test files are not counted toward the routing threshold in any mode, and the large path has no production-file cap.
 
 ## 3) Deterministic unit tests only (no external dependency coupling)
 
@@ -195,7 +193,7 @@ If tools cannot run in the environment, STOP implementation and provide plan + p
   - if `DIRECTIVE: ORCHESTRATOR HANDOFF MODE` is present, use orchestrator handoff mode and validate full context package.
   - otherwise use direct mode.
 4) Enforce budget routing:
-  - in direct mode, if estimated scope is >2 production PowerShell files, STOP and instruct user to invoke `powershell-orchestrator` for orchestration.
+  - in direct mode, if estimated scope is more than 3 production PowerShell files, STOP and instruct user to invoke `powershell-orchestrator` for orchestration.
 5) Summarize root cause/design constraint in one paragraph.
 
 ## Phase B — Design + plan (no edits)

package/resources/customizations/.github/prompts/orchestrate-powershell-work.prompt.md

@@ -21,9 +21,9 @@ Coordinate the user request from intake to completion using the correct path bas
 ## Required orchestration behavior
 
 1. Estimate rough change budget first (production PowerShell files).
-2. If budget is **1–2 production PowerShell files** (+ corresponding tests):
+2. If budget is **1-3 production PowerShell files** (+ corresponding tests):
    - Delegate directly to `powershell-typed-engineer` for plan + implementation + QA closure.
-3. If budget is **>2 production PowerShell files**:
+3. If budget is **more than 3 production PowerShell files**:
    - Execute full large-path lifecycle:
      1) Scope and create potential entry (`feature` vs `bug`, short-name creation)
      2) Promote to GitHub issue and capture issue metadata

package/resources/customizations/.github/skills/powershell-change-budget-router/SKILL.md

@@ -18,8 +18,8 @@ Use this skill when:
 
 1) Estimate rough change budget first based on likely **production PowerShell files** touched.
 2) Route:
-- `1-2` production files (+ corresponding tests) → **small path** (`powershell-typed-engineer` direct mode).
-- `>2` production files → **large path** (`powershell-orchestrator`).
+- `1-3` production files (+ corresponding tests) → **small path** (`powershell-typed-engineer` direct mode).
+- More than 3 production files → **large path** (`powershell-orchestrator`). The large path has no production-file cap.
 
 ## Orchestrated Small-Path Requirements
 
@@ -36,7 +36,7 @@ Direct invocation of `powershell-typed-engineer` remains implementation-focused
 
 ## Direct-Mode Rejection Rule
 
-If `powershell-typed-engineer` is invoked directly and estimated scope is `>2` production files:
+If `powershell-typed-engineer` is invoked directly and estimated scope is more than 3 production files:
 - Stop before implementation.
 - Return explicit routing instruction to invoke `powershell-orchestrator` (or `.github/prompts/orchestrate-powershell-work.prompt.md`).
 

package/resources/powershell/PoshQC/settings/pester.runsettings.psd1

@@ -29,6 +29,7 @@
             '.claude/hooks/check-powershell-test-purity.ps1'
             '.claude/hooks/enforce-python-batch-budget.ps1'
             '.claude/hooks/enforce-powershell-batch-budget.ps1'
+            '.claude/hooks/enforce-powershell-batch-budget-route.ps1'
             # Issue #272 hardened this PreToolUse hook with a new orchestrator-state preflight
             # check; measured here so the change produces real per-file coverage evidence.
             '.claude/hooks/enforce-pr-author-skill.ps1'