@danmoisan/drm-copilot-mcp 1.0.24 → 1.0.27

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danmoisan/drm-copilot-mcp",
-  "version": "1.0.24",
+  "version": "1.0.27",
   "description": "Stdio MCP server exposing drm-copilot repo-automation tools.",
   "license": "MIT",
   "type": "commonjs",

package/resources/claude-customizations/.claude/agents/feature-review.md

@@ -109,12 +109,14 @@ Coverage metrics are mandatory for every language that has changed files in the
 
 Coverage thresholds follow the uniform tier rule (Authoritative Decision #2) defined in `.claude/rules/quality-tiers.md`:
 
-- **New code files** (files added in this feature, not previously existing): line coverage >= 85%, branch coverage >= 75%.
-- **Modified files** (files that existed before and were changed): line coverage >= 85%, branch coverage >= 75%, and no regression on changed lines relative to baseline.
-- **Repo-wide per language**: line coverage >= 85%, branch coverage >= 75%.
+- **New code files** (files added in this feature, not previously existing): line coverage >= 85%, branch coverage >= 75% for branch-capable languages.
+- **Modified files** (files that existed before and were changed): line coverage >= 85%, branch coverage >= 75% for branch-capable languages, and no regression on changed lines relative to baseline.
+- **Repo-wide per language**: line coverage >= 85%, branch coverage >= 75% for branch-capable languages.
 
 Tier-specific lower thresholds are not used.
 
+The branch threshold applies only to branch-capable languages — TypeScript, Python, and C#. PowerShell is a coverage language and is fully subject to the line threshold and the no-regression requirement, but Pester measures command (instruction) coverage and line coverage only, so no branch percentage exists to evaluate and no branch threshold applies to it (see `.claude/rules/powershell.md`). Do not record FAIL for an absent PowerShell branch figure.
+
 ### Verification Procedure
 
 For each language that has changed files in the feature branch:

package/resources/claude-customizations/.claude/agents/parallel-orchestrator.md

@@ -187,10 +187,17 @@ Read `cohorts[] { index, generation, item_keys[] }` and schedule from it exactly
 
 Two scheduling rules govern every launch:
 
-1. **Cohort barrier.** Cohort `N+1` branches from `main` only after every cohort-`N` item is
-   `merged` or `worktree_removed`. `current_cohort` increments only on durable confirmation via
-   `git` and `gh` commands, never from in-memory notifications. A blocked item is neither `merged`
-   nor `worktree_removed`, so a blocked item holds the barrier.
+1. **Cohort barrier (per-edge).** An item may start only when every conflicting neighbour
+   (`conflict_edges[]`) that sits in a strictly prior current-generation cohort has `merge_status`
+   of `merged` or `worktree_removed`. `ci_green` does not satisfy the barrier. Same-cohort and
+   later-cohort neighbours do not hold an item back, and an item with no conflicting prior-cohort
+   neighbour may start regardless of other cohorts' progress. Evaluate the predicate only against
+   durable state confirmed by `git` and `gh` commands, never from in-memory notifications. A
+   blocked item is neither `merged` nor `worktree_removed`, so it holds only its own conflicting
+   later-cohort neighbours and, transitively, the tail of its own conflict component; unrelated
+   lanes keep advancing. `current_cohort` is a PROGRESS INDICATOR — the lowest current-generation
+   cohort index still holding a non-terminal, non-withdrawn item, updated only on the same durable
+   confirmation — and gates nothing.
 2. **`max_concurrency` slot filling.** `max_concurrency` caps the number of simultaneously in-flight
    items independently of cohort size. Fill slots in ascending item-key (`issue_num`) order, and
    refill each freed slot with the next unstarted item of the current cohort in the same ascending

package/resources/claude-customizations/.claude/agents/parallel-planner.md

@@ -1,7 +1,7 @@
 ---
 name: parallel-planner
 model: opus
-description: Planning half of the parallel orchestration surface. It performs item intake over issue numbers and potential-entry paths, drives per-item preparation (promotion, research, spec/user-story, atomic plan, preflight clearance) through concurrent preparation-mode Agent(orchestrator) delegations, computes and validates each item's blast radius, seeds the generation-0 cohort table, writes the parallel run manifest and the planner checkpoint, and emits the parallel-orchestrator kickoff prompt artifact. Performs no atomic execution, PR authoring, or CI monitoring.
+description: Planning half of the parallel orchestration surface. It performs item intake over issue numbers and potential-entry paths, drives per-item preparation (promotion, research, spec/user-story, atomic plan, preflight clearance) through preparation-mode Agent(orchestrator) delegations launched in bounded waves of at most max_concurrency, computes and validates each item's blast radius, seeds the generation-0 cohort table, writes the parallel run manifest and the planner checkpoint, and emits the parallel-orchestrator kickoff prompt artifact. Performs no atomic execution, PR authoring, or CI monitoring.
 tools:
   - "Agent(orchestrator)"
   - Read
@@ -90,7 +90,10 @@ On every invocation:
 ## Delegation Model
 
 You delegate exclusively through `Agent(orchestrator)`, one delegation per item, each carrying the
-preparation-mode kickoff line defined in the `parallel-plan` skill. Each child `orchestrator` runs
+preparation-mode kickoff line defined in the `parallel-plan` skill. Delegations are launched in
+BOUNDED WAVES of at most `max_concurrency`, computed with
+`bash .claude/lib/bash/compute-concurrency-batches.sh`, with wave *k+1* launched only after every
+child of wave *k* has terminated. Never launch every item's preparation at once. Each child `orchestrator` runs
 promotion, research, feature documents, atomic planning, and preflight clearance under
 `route_id: preparation`, commits and pushes its own branch, then stops before any execution. You do
 not delegate directly to `atomic-planner`, `atomic-executor`, `task-researcher`, or `prd-feature`;

package/resources/claude-customizations/.claude/hooks/enforce-discovery-artifact-gate.ps1

@@ -25,8 +25,10 @@
     interprets the CLI's exit code and captured output.
 
 .NOTES
-    Compatible with PowerShell 7+. Read-only validation gate; the validator
-    subprocess is the only external process invoked.
+    Requires PowerShell 7.4+ (the shared validation module uses
+    `Test-Json -SchemaFile` Draft 2020-12 support). Read-only validation gate that
+    invokes NO external process: validation runs in-process through
+    `.claude/lib/discovery-validation/DiscoveryValidation.psm1` (issue #475).
 #>
 [CmdletBinding()]
 param()
@@ -34,11 +36,23 @@ param()
 function Invoke-DiscoveryValidatorExe {
     <#
     .SYNOPSIS
-        Wrapper around the discovery-artifact validator CLI. Mockable seam.
+        Wrapper around the discovery-artifact validator. Mockable seam.
     .DESCRIPTION
-        Invokes `python -m scripts.dev_tools.validate_discovery_artifacts` with
-        the supplied arguments and captures both stdout and stderr. Tests mock
-        this function directly; production code must never mock `python`.
+        Delegates to the portable PowerShell implementation in
+        `.claude/lib/discovery-validation/DiscoveryValidation.psm1`, keeping this
+        function's name, its `-ValidatorArgs <string[]>` parameter, and its
+        `@{ ExitCode; Output }` return shape unchanged so existing mocks and
+        `Should -Invoke` assertions continue to bind.
+
+        This no longer invokes a Python interpreter (issue #475). The `.claude/**`
+        payload ships to destinations with no guaranteed Python, Poetry, or
+        `scripts/dev_tools`, where the previous `python -m ...` call failed
+        obscurely or blocked every operation.
+
+        Success is SILENT by contract: a passing validation returns `ExitCode = 0`
+        with an EMPTY `Output`. The caller denies on a non-zero exit code OR on
+        non-empty output, so any success chatter here would deny a passing
+        validation (defect D-2).
     #>
     [CmdletBinding()]
     [OutputType([hashtable])]
@@ -47,8 +61,14 @@ function Invoke-DiscoveryValidatorExe {
         [string[]] $ValidatorArgs
     )
 
-    $output = & python -m scripts.dev_tools.validate_discovery_artifacts @ValidatorArgs 2>&1
-    return @{ ExitCode = $LASTEXITCODE; Output = ($output | Out-String).Trim() }
+    $modulePath = Join-Path -Path $PSScriptRoot `
+        -ChildPath '../lib/discovery-validation/DiscoveryValidation.psm1'
+    if (-not (Test-Path -LiteralPath $modulePath -PathType Leaf)) {
+        return @{ ExitCode = 1; Output = "Discovery-validation module not found: $modulePath" }
+    }
+
+    Import-Module -Name $modulePath -Force -ErrorAction Stop
+    return Invoke-DiscoveryArtifactValidation -ValidatorArgs $ValidatorArgs
 }
 
 function Get-DiscoveryArtifactType {

package/resources/claude-customizations/.claude/hooks/enforce-epic-merge-gate.ps1

@@ -5,7 +5,7 @@
 .DESCRIPTION
     Invoked by the Claude Code PreToolUse hook on the "Bash" matcher before any Bash
     command runs. Regex-matches gh pr merge with a --merge flag against
-    CLAUDE_TOOL_INPUT.command and, when matched, allows the merge only when one of two
+    CLAUDE_TOOL_INPUT.command and, when matched, allows the merge only when one of three
     checkpoint-only conditions holds:
 
       1. Child-feature path: artifacts/orchestration/orchestrator-state.json exists,
@@ -14,11 +14,17 @@
       2. Epic-integration path: artifacts/orchestration/epic-orchestrator-state.json exists,
          epic_merge_pr.ci_gate.conclusion == "success", and, when the command names an
          explicit PR number, that number matches epic_merge_pr.pr_number.
+      3. Parallel path: artifacts/orchestration/parallel-orchestrator-state.json exists,
+         route_id == "parallel", and the command's explicit PR number matches an items[]
+         entry whose merge_status == "ci_green". A parallel run always names an explicit PR
+         number (each item merges from its own isolated worktree), so a bare command with no
+         PR number cannot satisfy this branch.
 
     Otherwise the command is denied with reason EPIC_MERGE_GATE_BLOCKED. A missing or
-    unreadable checkpoint in either branch fails closed (denies); standalone (non-epic)
-    orchestration never sets epic_mode or populates epic_merge_pr, so it is structurally
-    prevented from invoking gh pr merge --merge at all.
+    unreadable checkpoint in any branch fails closed (denies); standalone (non-epic,
+    non-parallel) orchestration never sets epic_mode, populates epic_merge_pr, or writes a
+    parallel checkpoint with route_id == "parallel", so it is structurally prevented from
+    invoking gh pr merge --merge at all.
 
     Design decision: this gate trusts the on-disk checkpoint rather than shelling out live
     to gh pr view for a real-time head-SHA check, matching the same non-adversarial,
@@ -35,6 +41,7 @@ param()
 
 $script:ChildCheckpointPath = 'artifacts/orchestration/orchestrator-state.json'
 $script:EpicCheckpointPath = 'artifacts/orchestration/epic-orchestrator-state.json'
+$script:ParallelCheckpointPath = 'artifacts/orchestration/parallel-orchestrator-state.json'
 
 function Get-ChildOrchestratorCheckpointContent {
     <#
@@ -72,6 +79,24 @@ function Get-EpicOrchestratorCheckpointContent {
     return (Get-Content -LiteralPath $script:EpicCheckpointPath -Raw)
 }
 
+function Get-ParallelOrchestratorCheckpointContent {
+    <#
+    .SYNOPSIS
+        Read the raw JSON text of the parallel-orchestrator checkpoint. Tests mock
+        this function (read seam).
+    .OUTPUTS
+        System.String or $null
+    #>
+    [CmdletBinding()]
+    [OutputType([string])]
+    param()
+
+    if (-not (Test-Path -LiteralPath $script:ParallelCheckpointPath -PathType Leaf)) {
+        return $null
+    }
+    return (Get-Content -LiteralPath $script:ParallelCheckpointPath -Raw)
+}
+
 function ConvertFrom-EpicMergeGateJson {
     <#
     .SYNOPSIS
@@ -113,9 +138,20 @@ function Get-EpicMergeGateCommandPrNumber {
         [string] $CommandText
     )
 
+    # Original form: the PR number appears immediately after "merge"
+    # (e.g. "gh pr merge 410 --merge"). Preserved verbatim so epic-path outcomes
+    # for the forms the epic path uses are unchanged.
     if ($CommandText -match '(?i)\bgh\s+pr\s+merge\s+(\d+)\b') {
         return [int]$Matches[1]
     }
+    # Broadened, additive form: the parallel command places the flag before the
+    # number (e.g. "gh pr merge --merge 410"). Once "gh pr merge" is confirmed,
+    # capture the first standalone run of digits that is not preceded by "-" or a
+    # word character, so a flag token such as "--merge" is not treated as a number
+    # and a bare "gh pr merge --merge" still yields $null.
+    if ($CommandText -match '(?i)\bgh\s+pr\s+merge\b' -and $CommandText -match '(?<![-\w])(\d+)\b') {
+        return [int]$Matches[1]
+    }
     return $null
 }
 
@@ -206,6 +242,69 @@ function Test-EpicCheckpointAllowsMerge {
     return $true
 }
 
+function Test-ParallelCheckpointAllowsMerge {
+    <#
+    .SYNOPSIS
+        Decision logic for the parallel-orchestrator checkpoint path (branch 3).
+    .PARAMETER Checkpoint
+        Parsed parallel-orchestrator checkpoint, or $null when absent/unreadable.
+    .PARAMETER CommandPrNumber
+        The explicit PR number parsed from the command, or $null when the command
+        does not name one. A parallel run always names an explicit PR number because
+        each item merges from its own isolated worktree, so a $null value denies.
+    .OUTPUTS
+        System.Boolean
+    #>
+    [CmdletBinding()]
+    [OutputType([bool])]
+    param(
+        [AllowNull()]
+        $Checkpoint,
+
+        [AllowNull()]
+        [Nullable[int]] $CommandPrNumber
+    )
+
+    if ($null -eq $Checkpoint) {
+        return $false
+    }
+    $props = @($Checkpoint.PSObject.Properties.Name)
+    if ($props -notcontains 'route_id' -or ([string]$Checkpoint.route_id) -ne 'parallel') {
+        return $false
+    }
+    # A parallel merge always names an explicit PR number; without one the target
+    # item cannot be identified, so fail closed.
+    if ($null -eq $CommandPrNumber) {
+        return $false
+    }
+    if ($props -notcontains 'items' -or $null -eq $Checkpoint.items) {
+        return $false
+    }
+
+    foreach ($item in @($Checkpoint.items)) {
+        if ($null -eq $item) {
+            continue
+        }
+        $itemProps = @($item.PSObject.Properties.Name)
+        if ($itemProps -notcontains 'pr_number') {
+            continue
+        }
+        $itemPrNumber = 0
+        if (-not [int]::TryParse([string]$item.pr_number, [ref] $itemPrNumber)) {
+            continue
+        }
+        if ($itemPrNumber -ne $CommandPrNumber) {
+            continue
+        }
+        if ($itemProps -notcontains 'merge_status') {
+            return $false
+        }
+        return ([string]$item.merge_status) -eq 'ci_green'
+    }
+
+    return $false
+}
+
 function Get-EpicMergeGateAllowDecision {
     [CmdletBinding()]
     [OutputType([System.Collections.Specialized.OrderedDictionary])]
@@ -284,7 +383,12 @@ function Invoke-EpicMergeGateDecision {
         return Get-EpicMergeGateAllowDecision
     }
 
-    return Get-EpicMergeGateBlockDecision -Reason 'EPIC_MERGE_GATE_BLOCKED: gh pr merge --merge requires either a per-feature checkpoint with epic_mode == true and step9_status == "passed", or an epic checkpoint with epic_merge_pr.ci_gate.conclusion == "success" and a matching pr_number. Neither checkpoint satisfied this gate.'
+    $parallelCheckpoint = ConvertFrom-EpicMergeGateJson -Raw (Get-ParallelOrchestratorCheckpointContent)
+    if (Test-ParallelCheckpointAllowsMerge -Checkpoint $parallelCheckpoint -CommandPrNumber $commandPrNumber) {
+        return Get-EpicMergeGateAllowDecision
+    }
+
+    return Get-EpicMergeGateBlockDecision -Reason 'EPIC_MERGE_GATE_BLOCKED: gh pr merge --merge requires either a per-feature checkpoint with epic_mode == true and step9_status == "passed", an epic checkpoint with epic_merge_pr.ci_gate.conclusion == "success" and a matching pr_number, or a parallel-orchestrator checkpoint with route_id == "parallel" whose target item (matched by pr_number) has merge_status == "ci_green". No checkpoint satisfied this gate.'
 }
 
 # Guard allows dot-sourcing in tests without executing the entrypoint.