@danmoisan/drm-copilot-mcp 1.0.15 → 1.0.17

package/package.json

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

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

@@ -77,10 +77,19 @@ chain; the PreToolUse hook `.claude/hooks/enforce-epic-invocation-origin.ps1` de
 
 ## Prepared-Epic Execution (epic-planner Handoff)
 
-When the epic was prepared by `epic-planner` (the integration branch already exists and
-`docs/features/epics/<epic-slug>/epic-kickoff.md` is present), each child feature folder already
-contains its issue, research, `spec.md`, `user-story.md`, an approved atomic plan, and a
-recorded preflight clearance. In that case:
+When the epic was prepared by `epic-planner`, the integration branch
+`epic/<epic-slug>-integration` already exists and carries the committed kickoff artifact and
+every prepared child feature folder. Because `epic-plan` commits those outputs to the integration
+branch (worked in a separate integration worktree), do not assume they are present in the invoking
+worktree: establish their presence by fetching and reading from the integration branch rather than
+gating on a local checkout. Run `git fetch origin epic/<epic-slug>-integration`, then read
+`docs/features/epics/<epic-slug>/epic-kickoff.md` from that ref — for example
+`git show origin/epic/<epic-slug>-integration:docs/features/epics/<epic-slug>/epic-kickoff.md`, or
+test existence with
+`git cat-file -e epic/<epic-slug>-integration:docs/features/epics/<epic-slug>/epic-kickoff.md` —
+without checking the integration branch out into the invoking worktree. Once the integration branch
+is fetched, each child feature folder on it already contains its issue, research, `spec.md`,
+`user-story.md`, an approved atomic plan, and a recorded preflight clearance. In that case:
 
 1. Do not recreate the integration branch; fetch and reuse it.
 2. Each child `Agent(orchestrator)` delegation prompt cites the child's committed `plan-path`

package/resources/claude-customizations/.claude/hooks/validate-planner-output.ps1

@@ -1,4 +1,4 @@
-<#
+<#
 .SYNOPSIS
     SubagentStop hook for the atomic-planner subagent.
 
@@ -14,7 +14,7 @@
       - output contains `PREFLIGHT: ALL CLEAR` or
         `PREFLIGHT: REVISIONS REQUIRED`,
       - the advertised plan exists on disk,
-      - the plan contains canonical `### Phase N - <Title>` headings,
+      - the plan contains canonical `### Phase N — <Title>` headings,
       - Phase 0 exists and includes policy-read and baseline tasks,
       - each task uses `- [ ] [P#-T#]` (or checked equivalent),
       - task numbering is sequential within each phase,
@@ -118,7 +118,7 @@ function Get-PlanStructureValidationReport {
         [string[]] $Lines
     )
 
-    $phasePattern = '^### Phase (?<Phase>\d+)\s+-\s+(?<Title>.+)$'
+    $phasePattern = '^### Phase (?<Phase>\d+)\s+—\s+(?<Title>.+)$'
     $taskPattern = '^- \[(?<State>[ xX])\] \[P(?<Phase>\d+)-T(?<Task>\d+)\] (?<Text>.+)$'
     $errors = [System.Collections.Generic.List[string]]::new()
     $tasksByPhase = @{}
@@ -134,7 +134,7 @@ function Get-PlanStructureValidationReport {
         if ($line -match '^### Phase ') {
             $phaseMatch = [regex]::Match($line, $phasePattern)
             if (-not $phaseMatch.Success) {
-                $errors.Add("Line ${lineNumber}: phase heading must match `### Phase N - <Title>`.")
+                $errors.Add("Line ${lineNumber}: phase heading must match `### Phase N — <Title>`.")
                 $currentPhase = $null
                 continue
             }
@@ -245,7 +245,7 @@ function Invoke-PlannerOutputValidation {
     }
 
     $agentOutput = $null
-    if ($payload.PSObject.Properties.Name -contains 'output') {
+    if ($null -ne $payload.PSObject.Properties['output']) {
         $agentOutput = $payload.output
     }
     if ([string]::IsNullOrWhiteSpace($agentOutput)) {

package/resources/claude-customizations/.claude/skills/epic-run/SKILL.md

@@ -18,10 +18,28 @@ $ARGUMENTS
 
 1. Resolve the epic home. A bare slug resolves to `docs/features/epics/<epic-slug>/`; a path
    argument resolves to its containing epic folder.
-2. Read the committed kickoff artifact at `docs/features/epics/<epic-slug>/epic-kickoff.md`.
-   - If the file does not exist, STOP without delegating anything and report that the epic has
-     no committed kickoff artifact: the user must run `/epic-plan` first (or, for an epic that
-     was authored manually, invoke `/epic-orchestrate <epic-manifest-path>` directly).
+2. Resolve the committed kickoff artifact `docs/features/epics/<epic-slug>/epic-kickoff.md`. It
+   may exist only on the epic integration branch: `epic-plan` commits it to
+   `epic/<epic-slug>-integration` (worked in a separate integration worktree), so the worktree
+   that invokes `/epic-run` is not guaranteed to have it checked out. Discover it across both
+   locations before concluding it is missing:
+   - Attempt `git fetch origin epic/<epic-slug>-integration`. A failure because the remote
+     branch does not exist is the genuine "epic not planned" case; tolerate it and continue to
+     the local check rather than treating the fetch failure as fatal.
+   - Treat the artifact as present when EITHER the plain local path exists in the invoking
+     worktree, OR it exists on the fetched integration ref, tested with
+     `git cat-file -e epic/<epic-slug>-integration:docs/features/epics/<epic-slug>/epic-kickoff.md`
+     (equivalently `origin/epic/<epic-slug>-integration:<path>`).
+   - When the artifact is present only on the integration ref, read its content with
+     `git show <ref>:<path>`. That is sufficient to extract the `## Invocation Prompt` text
+     needed to proceed; do NOT check the integration branch out into the invoking worktree — the
+     session worktree must never be checked out onto the integration branch (worktree-isolation
+     convention).
+   - STOP without delegating anything only when the artifact is absent BOTH locally and on the
+     fetched integration branch (the branch does not exist, or exists but lacks the file). In
+     that case report that the epic has no committed kickoff artifact: the user must run
+     `/epic-plan` first (or, for an epic that was authored manually, invoke
+     `/epic-orchestrate <epic-manifest-path>` directly).
 3. Execute the kickoff artifact's `## Invocation Prompt` section as the epic objective, applying
    the `epic-orchestrate` skill procedure and the `## Prepared-Epic Execution (epic-planner
    Handoff)` section of `.claude/agents/epic-orchestrator.md`: reuse the existing integration

package/resources/codex-and-agents-customizations/.codex/config.toml

@@ -2,7 +2,7 @@ default_permissions = ":danger-full-access"
 
 [mcp_servers.drm-copilot]
 command = "npx"
-args = ["-y", "@danmoisan/drm-copilot-mcp@1.0.15"]
+args = ["-y", "@danmoisan/drm-copilot-mcp@1.0.17"]
 required = true
 enabled_tools = [
     "collect_commit_context",

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

@@ -82,6 +82,9 @@
             # to AST-based scriptblocks (Parser::ParseFile(...).GetScriptBlock()) so Pester
             # coverage breakpoints bind to the on-disk source file.
             'scripts/powershell/PoshQC/PoshQC.ScanConfig.psm1'
+            # Issue #357 remediation cycle 1 (fix #1): measure the atomic-planner SubagentStop
+            # hook so its Pester coverage is captured in the canonical artifact.
+            '.claude/hooks/validate-planner-output.ps1'
         )
         # Optional: don't fail the run on coverage percentage
         CoveragePercentTarget = 0