@danmoisan/drm-copilot-mcp 1.0.11 → 1.0.14

package/resources/feature-templates/epic/epic.md

@@ -0,0 +1,79 @@
+---
+# Epic manifest (source of truth).
+#
+# This YAML frontmatter is the machine-readable manifest for the epic: the
+# dependency DAG (parsed deterministically by the epic-orchestrator agent) and an
+# optional SAFe-style intent block. The Markdown body below the frontmatter is the
+# single human-authored narrative and is not machine-parsed.
+#
+# The DAG is keyed by stable `issue_num`. `feature_folder` is a resolvable hint
+# that may point into docs/features/active/<folder> OR docs/features/completed/<folder>;
+# it is not a stable identifier and changes when a child is promoted.
+epic: <epic-slug>
+integration_branch: epic/<epic-slug>-integration
+created_at: <iso8601>
+
+# Optional additive SAFe-style intent block. Omit the whole `intent` block when
+# not used; when present, `epic_type` and `business_outcome_hypothesis` are
+# required, and `leading_indicators` / `nfrs` are optional lists of strings.
+intent:
+  epic_type: <business | enabler>
+  business_outcome_hypothesis: <the measurable outcome this epic is expected to move>
+  leading_indicators:
+    - <early signal that the hypothesis is being validated>
+  nfrs:
+    - <non-functional requirement the epic must satisfy>
+
+# Manifest DAG. Primary key is `issue_num`. `depends_on` lists the `issue_num`
+# values of upstream siblings (each must be another entry in `features[]`).
+features:
+  - issue_num: <int>
+    feature_folder: <resolvable-hint-basename>
+    depends_on: []
+  - issue_num: <int>
+    feature_folder: <resolvable-hint-basename>
+    depends_on: [<upstream-issue_num>]
+---
+
+# <epic-name> - Epic
+
+- Issue: #<tracking-issue>
+- Owner: <name>
+- Last Updated: YYYY-MM-DD
+
+## Goal
+
+State the epic objective and the measurable outcomes. Keep it user/impact
+oriented, not implementation detail. This is the source from which the epic
+GitHub issue body is generated.
+
+## Scope
+
+Enumerate what is in scope for this epic. Reference the child features by their
+`issue_num` so the narrative and the manifest DAG stay aligned.
+
+## Non-Goals
+
+List what is explicitly out of scope so child features and reviewers do not
+scope-creep into adjacent work.
+
+## Shared Design
+
+Capture the cross-cutting design decisions every child feature must honor:
+
+- Shared behaviors/algorithms that must stay aligned across children.
+- Determinism/performance/compatibility guarantees.
+- Data/artifact locations, formats, or tooling expectations.
+- Quality gates (tests/lint/type-checks) required across all children.
+
+## Decomposition
+
+Describe the child features and their ordering. Each child keeps its own git
+branch/worktree and its own independent active/ -> completed/ lifecycle; this
+section is the human-readable projection of the `features[]` DAG above.
+
+- <Child feature A> (Issue #<id>) - wave 0
+- <Child feature B> (Issue #<id>) - depends on #<id>
+
+`epic-status.md` in this same directory is a generated projection of the epic
+checkpoint; it is never the source of the DAG and is never hand-authored.

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

@@ -44,6 +44,10 @@
             '.claude/hooks/enforce-pr-author-skill.ps1'
             '.claude/hooks/validate-orchestrator-output.ps1'
             '.claude/hooks/enforce-pr-author-skill.epic-base-branch.ps1'
+            # Issue #334 added this SessionStart hook that persists the current session id;
+            # measured here so the new production hook is not excluded from coverage. The
+            # test suite dot-sources the file (guarded body) so line attribution is valid.
+            '.claude/hooks/persist-session-id.ps1'
         )
         ExcludedPath          = @(
             '.claude/hooks/validate-feature-review-coverage.ps1' # Feature-review wrapper around repository evidence; not deterministic in normal unit-test execution.

package/resources/templates/new-claude-worktree-session.ps1

@@ -3,20 +3,25 @@
     Creates a git worktree and launches a Claude CLI session inside it as a background process.
 
 .DESCRIPTION
-    Creates a new git worktree at a timestamped path derived from the destination
-    repository's basename, branches it off the current HEAD, and starts the Claude CLI
-    non-blocking via Start-Process.
+    Creates a new git worktree under a per-repository grouping directory and branches it
+    off the current HEAD, then starts the Claude CLI non-blocking via Start-Process.
+    The worktree is created at the nested path
+    <WorktreeParentPath>/<repoName>-wt/<yyyy-MM-ddTHH-mm>, where <repoName>-wt is a single
+    grouping directory that holds every timestamped worktree for the repository. The
+    grouping directory is created (idempotently) before 'git worktree add' runs.
     Writes WorktreePath, ProcessId, and LogFile to stdout before returning to the caller.
 
 .PARAMETER Objective
     Prompt text passed to the Claude CLI as its primary argument.
 
 .PARAMETER WorktreeParentPath
-    Parent directory for the new worktree. Defaults to the parent of the repo root.
+    Parent directory for the new worktree. Defaults to the parent of the repo root. The
+    grouping directory <repoName>-wt is created beneath this path.
 
 .PARAMETER BranchName
-    Explicit branch name for the new worktree. When omitted, defaults to
-    <repoName>-wt-<timestamp>.
+    Explicit branch name for the new worktree. When omitted, defaults to the flat name
+    <repoName>-wt-<yyyy-MM-ddTHH-mm>. The branch name is never nested with a slash even
+    though the on-disk worktree path is nested.
 #>
 [CmdletBinding(SupportsShouldProcess)]
 param(
@@ -37,7 +42,21 @@ function Get-WorktreeTimestamp {
     )
 
     $now = & $GetDateTime
-    return $now.ToString('yyyy-MM-dd-HH-mm')
+    return $now.ToString('yyyy-MM-ddTHH-mm')
+}
+
+function Get-WorktreeGroupDirectory {
+    [CmdletBinding()]
+    [OutputType([string])]
+    param(
+        [Parameter(Mandatory = $true)]
+        [string] $WorktreeParentPath,
+
+        [Parameter(Mandatory = $true)]
+        [string] $RepoName
+    )
+
+    return "$WorktreeParentPath/$RepoName-wt"
 }
 
 function Build-WorktreePath {
@@ -54,7 +73,8 @@ function Build-WorktreePath {
         [string] $RepoName
     )
 
-    return "$WorktreeParentPath/$RepoName-wt-$Timestamp"
+    $groupDirectory = Get-WorktreeGroupDirectory -WorktreeParentPath $WorktreeParentPath -RepoName $RepoName
+    return "$groupDirectory/$Timestamp"
 }
 
 function Build-BranchName {
@@ -77,6 +97,23 @@ function Build-BranchName {
     return "$RepoName-wt-$Timestamp"
 }
 
+function New-WorktreeParentDirectory {
+    [CmdletBinding(SupportsShouldProcess = $true)]
+    param(
+        [Parameter(Mandatory = $true)]
+        [string] $GroupDirectory,
+
+        [scriptblock] $NewDirectory = { param([string] $Path) New-Item -ItemType Directory -Force -Path $Path | Out-Null }
+    )
+
+    # -Force makes creation idempotent (a no-op when the directory already exists) and
+    # creates any missing leading directories. The filesystem action is isolated behind
+    # the injectable $NewDirectory seam so it can be mocked without touching disk.
+    if ($PSCmdlet.ShouldProcess($GroupDirectory, 'Create worktree grouping directory')) {
+        & $NewDirectory $GroupDirectory
+    }
+}
+
 function Test-PreconditionsMet {
     [CmdletBinding()]
     param(
@@ -192,6 +229,14 @@ function Write-LaunchResult {
     Write-Output "StderrLog: $StderrLog"
 }
 
+# When dot-sourced (for example by the Pester test suite, to resolve the functions
+# above for coverage attribution), define the functions but do not execute the
+# top-level script body. Direct invocation leaves $MyInvocation.InvocationName as the
+# script name (not '.'), so the body runs unchanged and production behavior is preserved.
+if ($MyInvocation.InvocationName -eq '.') {
+    return
+}
+
 # ---------------------------------------------------------------------------
 # Script body
 # ---------------------------------------------------------------------------
@@ -215,6 +260,11 @@ catch {
     exit 1
 }
 
+# Ensure the <repoName>-wt grouping directory exists before 'git worktree add' runs.
+# Creation is idempotent, so re-running for an existing group directory is a no-op.
+$groupDirectory = Get-WorktreeGroupDirectory -WorktreeParentPath $WorktreeParentPath -RepoName $repoName
+New-WorktreeParentDirectory -GroupDirectory $groupDirectory
+
 if ($PSCmdlet.ShouldProcess($worktreePath, 'git worktree add')) {
     Invoke-GitWorktreeAdd -WorktreePath $worktreePath -BranchName $resolvedBranch
 }
@@ -229,4 +279,3 @@ $stdoutLog = "$worktreePath/claude-session.stdout.log"
 $stderrLog = "$worktreePath/claude-session.stderr.log"
 
 Write-LaunchResult -WorktreePath $worktreePath -ProcessId $processId -StdoutLog $stdoutLog -StderrLog $stderrLog
-

package/resources/feature-templates/epic/initiative.md

@@ -1,43 +0,0 @@
-# <epic-name> - Initiative Overview
-
-- Issue: #<tracking-issue>
-- Owner: <name>
-- Last Updated: YYYY-MM-DD
-
-## Goal & Outcomes
-
-State the objective and the measurable outcomes for this initiative. Keep it user/impact oriented, not implementation detail.
-
-## Decomposition (Child Features/Workstreams)
-
-- <Workstream A> (Issue #<id>) - `../<child-folder>/`
-- <Workstream B> (Issue #<id>) - `../<child-folder>/`
-- <Workstream C> (Issue #<id>) - `../<child-folder>/`
-
-Dependencies: Describe ordering or coupling between child items (e.g., A → B → C).
-
-## Cross-Cutting Constraints & Assumptions
-
-- Shared behaviors/algorithms that must stay aligned
-- Determinism/performance/compatibility guarantees
-- Data/artifact locations, formats, or tooling expectations
-- Compliance/legal/licensing boundaries
-- Quality gates (tests/lint/type-checks) required across all children
-
-## Milestones & Status
-
-- M1 <Name> - <Not started | In progress | Done> (criteria)
-- M2 <Name> - <Not started | In progress | Done>
-- M3 <Name> - <Not started | In progress | Done>
-- CLI/UX alignment or other cross-initiative milestones
-
-## Initiative-Level Validation
-
-- End-to-end: <Describe end-to-end validation that proves the initiative outcome>
-- Integration: <Cross-layer checks to ensure child workstreams fit together>
-- Determinism/Regression: <What needs to remain stable; how to detect drift>
-- Error handling/Resilience: <Key failure modes and expected handling>
-
-## Notes / Follow-Ups
-
-Capture decisions, risks, and future adjustments to decomposition/milestones.