npm - @danmoisan/drm-copilot-mcp - Versions diffs - 1.0.26 → 1.1.0 - Mend

@danmoisan/drm-copilot-mcp 1.0.26 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (63) hide show

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/class.md ADDED Viewed

@@ -0,0 +1,63 @@
+# Class Diagram Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/classDiagram.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword forms
+`classDiagram`, or the legacy-accepted `classDiagram-v2`.
+## Relation tokens
+A relation is composed as `<tail><line><head>`:
+| Token | Meaning |
+| --- | --- |
+| `<|--` / `--|>` | inheritance |
+| `*--` / `--*` | composition |
+| `o--` / `--o` | aggregation |
+| `-->` / `<--` | association |
+| `--` | link, solid |
+| `..>` / `<..` | dependency |
+| `..|>` / `<|..` | realization |
+| `..` | link, dashed |
+Cardinalities are quoted and sit outside the token: `Customer "1" --> "0..*" Order`.
+Generics use tilde runs: `List~T~`, and a tilde run is never an edge defect.
+## Structural conventions
+- A member block is `class <Name> { ... }` with `+`, `-`, `#`, `~` visibility prefixes; methods
+  carry `()`. Brackets and braces are structural in a class diagram, so every opener needs a closer.
+- A member may also be declared inline: `Animal : +String name`.
+- `namespace <Name> { ... }` groups classes.
+- Annotations use `<<interface>>` / `<<abstract>>` on their own line inside the block or after the
+  class name.
+- `classDef`, `cssClass`, `click`, `style`, `note`, `note for <Class>` are statement lines exempt
+  from the edge rules.
+- Text after the first `:` on a relation line is the relation label and is free text.
+## Example
+```mermaid
+classDiagram
+    direction LR
+    class Repository~T~ {
+        <<interface>>
+        +findById(id) T
+        +save(entity) void
+    }
+    class OrderRepository {
+        -connection
+        +findById(id) Order
+        +save(order) void
+    }
+    class Order {
+        +String id
+        +decimal total
+        +addLine(line)
+    }
+    Repository~T~ <|.. OrderRepository
+    OrderRepository ..> Order : returns
+    Order "1" --* "0..*" OrderLine : contains
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/er.md ADDED Viewed

@@ -0,0 +1,56 @@
+# Entity Relationship Diagram Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/entityRelationshipDiagram.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword form
+`erDiagram`.
+## Cardinality tokens
+A relationship token is `<left><line><right>`.
+| Position | Options |
+| --- | --- |
+| left | `\|o` (zero or one), `\|\|` (exactly one), `}o` (zero or more), `}\|` (one or more) |
+| line | `--` (identifying), `..` (non-identifying) |
+| right | `o\|` (zero or one), `\|\|` (exactly one), `o{` (zero or more), `\|{` (one or more) |
+Common complete forms: `||--||`, `||--o{`, `}o--o{`, `}|--|{`, `|o..o|`, `}|..|{`.
+Word aliases are also accepted in place of the token: `one or zero`, `zero or more`, `only one`,
+`1+`, `0+`, `many(0)`, `many(1)`, joined by `to` or `optionally to`.
+The relationship label follows the first `:` and is free text.
+## Structural conventions
+- An attribute block is `ENTITY { <type> <name> <key> "<comment>" }`. Braces are structural.
+- Key markers are `PK`, `FK`, `UK`; several may be comma-separated.
+- An entity name may be quoted when it is not identifier-shaped.
+- `%%` comments and the statement keywords behave as in every other type.
+## Example
+```mermaid
+erDiagram
+    CUSTOMER ||--o{ ORDER : places
+    ORDER ||--|{ ORDER_LINE : contains
+    PRODUCT }o--o{ ORDER_LINE : "appears in"
+    CUSTOMER {
+        string id PK
+        string email UK "lowercased on write"
+        string display_name
+    }
+    ORDER {
+        string id PK
+        string customer_id FK
+        decimal total
+    }
+    ORDER_LINE {
+        string order_id FK
+        string product_id FK
+        int quantity
+    }
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/flowchart.md ADDED Viewed

@@ -0,0 +1,68 @@
+# Flowchart Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/flowchart.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword forms
+- `flowchart` followed optionally by a direction: `TB`, `TD`, `BT`, `LR`, `RL`. The direction is
+  optional and defaults to `TB`.
+- `graph` with the same optional direction. Accepted and equivalent for the validator's purposes.
+- `flowchart-elk` selects the ELK layout variant.
+- A trailing `;` on the keyword line is accepted (`graph LR;`).
+## Edge tokens
+| Token | Meaning |
+| --- | --- |
+| `-->` | arrow |
+| `---` | open link |
+| `-.->` | dotted arrow |
+| `-.-` | dotted open link |
+| `==>` | thick arrow |
+| `===` | thick open link |
+| `~~~` | invisible link |
+| `--o` | circle edge |
+| `--x` | cross edge |
+| `o--o`, `x--x`, `<-->` | bidirectional forms |
+Length variants extend the dash, dot, or equals run (`---->`, `====>`, `-...->`) and rank the edge
+lower in layout. Text forms: `A -- text --> B`, `A -->|text| B`, `A -. text .-> B`,
+`A == text ==> B`.
+## Node shapes
+`A[rect]`, `A(round)`, `A([stadium])`, `A[[subroutine]]`, `A[(cylinder)]`, `A((circle))`,
+`A>asymmetric]`, `A{rhombus}`, `A{{hexagon}}`, `A[/parallelogram/]`, `A[\parallelogram alt\]`,
+`A[/trapezoid\]`, `A(((double circle)))`.
+Brackets are structural in a flowchart, so every opener needs its closer. A bracket inside a quoted
+label is content, not structure: `A["foo[bar](baz)"]` is valid.
+## Structural conventions
+- `subgraph <id> [<free-text title>]` opens a block; `end` closes it. A `direction` statement inside
+  a subgraph sets that subgraph's direction.
+- Statement lines are exempt from edge and bracket rules: `click`, `style`, `classDef`, `linkStyle`,
+  `class`, `accTitle`, `accDescr`, `title`.
+- `%%` starts a comment outside a quoted span. `%%{init: {...}}%%` is a directive, not a comment.
+- Labels may carry HTML (`<br/>`, `<b>`) and Markdown strings in backticks. Angle brackets are never
+  structural.
+- Mermaid has no backslash escape; use the `#quot;` entity for a double quote inside a label.
+## Example
+```mermaid
+flowchart LR
+    A[Client] --> B{Authenticated}
+    B -->|yes| C[Handler]
+    B -->|no| D((Reject))
+    subgraph backend [Backend services]
+        direction TB
+        C --> E[(Database)]
+        C -.-> F[Queue]
+    end
+    click C "https://example.com/handler" "Open the handler"
+    classDef hot fill:#f96,stroke:#333
+    class E hot
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/gantt.md ADDED Viewed

@@ -0,0 +1,51 @@
+# Gantt Chart Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/gantt.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword form
+`gantt`.
+## Body form
+A gantt body is free text to the validator: it carries no edge tokens, and brackets and parentheses
+are not structural. A task named `Deploy (phase 1` is accepted by the gate even though it is
+untidy, because rejecting it would be a false positive. The date and duration grammar is not
+structurally checkable either, so a malformed date passes the gate and fails to render — check
+dates by reading them.
+Statement lines:
+- `title <free text>`
+- `dateFormat <format>` — the input format of the task dates, for example `YYYY-MM-DD`.
+- `axisFormat <format>` — the output format of the axis, for example `%Y-%m-%d`.
+- `tickInterval <n><unit>` — for example `1week`, `2day`.
+- `excludes <weekends|YYYY-MM-DD|monday..sunday>`
+- `todayMarker <off|stroke:...>`
+- `section <free text>` opens a section; sections need no closing statement.
+## Task form
+`<task label> :<tags>, <id>, <start or dependency>, <duration or end>`
+- Tags: `done`, `active`, `crit`, `milestone`.
+- The start may be a literal date, `after <id>`, or omitted to continue from the previous task.
+- The duration is a number with a unit (`3d`, `2w`, `12h`) or an explicit end date.
+## Example
+```mermaid
+gantt
+    title Order service rollout
+    dateFormat YYYY-MM-DD
+    axisFormat %m-%d
+    excludes weekends
+    section Preparation
+    Schema migration          :done,   mig,  2026-01-05, 3d
+    Contract tests            :active, ct,   after mig, 4d
+    section Rollout
+    Deploy to staging         :crit,   stg,  after ct, 2d
+    Soak (24 hours minimum)   :        soak, after stg, 1d
+    Production cutover        :milestone, prod, after soak, 0d
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/other-types.md ADDED Viewed

@@ -0,0 +1,82 @@
+# Remaining Diagram Types
+Pinned to Mermaid **11.17.0**. Entry point: `https://mermaid.js.org/intro/syntax-reference.html`;
+per-type pages at `https://mermaid.js.org/syntax/<type>.html`. When a construct is absent here,
+`WebFetch` the type's page and confirm the form before generating.
+Every type on this page is **keyword-checked only** by the structural gate: the validator confirms
+the first-line keyword and declines to judge the body, because these grammars are free text,
+indentation-structured, CSV-like, or supplied by an external plugin. A body defect in one of these
+types therefore passes the gate and fails to render. Read the body.
+## Verified keyword forms
+| Keyword | Type | Body shape |
+| --- | --- | --- |
+| `journey` | User journey | `section <name>` then `Task: <score>: <Actor>, <Actor>` rows |
+| `quadrantChart` | Quadrant chart | `x-axis`, `y-axis`, `quadrant-1`..`quadrant-4`, then `"<label>": [x, y]` points |
+| `requirementDiagram` | Requirement diagram | `requirement`/`element` blocks in braces; relationships as `<a> - <verb> -> <b>` |
+| `gitGraph` | Git graph | `commit`, `branch`, `checkout`, `merge`, `cherry-pick`. Accepts a direction and trailing colon: `gitGraph LR:`, `gitGraph TB:`, `gitGraph BT:` |
+| `mindmap` | Mind map | indentation-structured; node shapes `((circle))`, `))cloud((`, `)bang(`, `{{hexagon}}` |
+| `timeline` | Timeline | `title`, optional `section`, then `<period> : <event> : <event>` rows |
+| `zenuml` | ZenUML sequence | requires the external `@mermaid-js/mermaid-zenuml` plugin even in browser Mermaid; the gate keyword-accepts and never judges the body |
+| `sankey-beta` | Sankey diagram | CSV-like `source,target,value` rows |
+| `xychart-beta` | XY chart | `title`, `x-axis`, `y-axis`, `bar [..]`, `line [..]`. Accepts the `horizontal` modifier: `xychart-beta horizontal` |
+| `block-beta` | Block diagram | `columns <n>`, block ids, `space`, flowchart-style arrows between blocks |
+| `packet` | Packet diagram | `<start>-<end>: "<name>"` rows. `packet-beta` was the earlier keyword and remains accepted |
+| `kanban` | Kanban board | indentation-structured columns and cards |
+| `architecture-beta` | Architecture diagram | `group`, `service`, `junction`; edges carry port syntax `L`/`R`/`T`/`B`, as in `db:L -- R:server` |
+| `radar-beta` | Radar chart | axis list then per-series value rows |
+| `treemap-beta` | Treemap | indentation plus `"<label>": <value>` rows |
+| `info` | Version info | no body; renders the Mermaid version |
+## Keyword-accept rows: documented types, unverified keyword form
+These types appear in the 11.x documentation sidebar, but their exact first-line keyword form was
+not individually verified against the pinned pages. The validator resolves them and records a drift
+warning rather than judging the body, so neither spelling costs a false rejection. Confirm the form
+by `WebFetch` before relying on one.
+`swimlanes`, `eventmodeling`, `venn`, `ishikawa`, `wardley`, `cynefin`, `treeView`, `railroad`
+(`railroad-beta`).
+## Version drift
+The allowlist in `.claude/lib/mermaid/MermaidGrammar.psm1` is a snapshot of 11.17.0, and Mermaid adds
+diagram types several times a year. An unknown but keyword-shaped first-line token produces a drift
+warning and is allowed. That warning is the signal to confirm the keyword against the documentation
+and add it to the table; it is never a reason to abandon the diagram.
+One exception: a token within a single character of a known keyword and at least five characters
+long is reported as a misspelling and denied, because a typo is a defect the gate is required to
+name. `flowchar TD` is a misspelling of `flowchart`, not a new diagram type.
+## Examples
+```mermaid
+gitGraph LR:
+    commit id: "init"
+    branch feature
+    checkout feature
+    commit id: "work"
+    checkout main
+    merge feature
+```
+```mermaid
+timeline
+    title Release history
+    2026-01 : 1.0 shipped : docs published
+    2026-02 : 1.1 shipped
+```
+```mermaid
+journey
+    title Order placement
+    section Browse
+      Search catalogue: 4: Customer
+      Read reviews: 3: Customer
+    section Checkout
+      Enter payment: 2: Customer
+      Confirm order: 5: Customer, System
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/pie.md ADDED Viewed

@@ -0,0 +1,32 @@
+# Pie Chart Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/pie.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword forms
+- `pie`
+- `pie showData` — the modifier appends each slice's numeric value to its legend label.
+## Body form
+- `title <free text>` is optional and appears above the chart.
+- Each data row is `"<label>" : <number>`. The label is double-quoted; the value may be an integer
+  or a decimal. Mermaid computes the percentages, so values need not sum to 100.
+- Up to twelve slices render with distinct default colours; beyond that the palette repeats, so
+  aggregate the tail into one slice rather than emitting twenty.
+The body carries no edge tokens and no structural brackets, so the validator keyword-checks a pie
+chart and does not judge the body. An unquoted label or a non-numeric value passes the gate and
+fails to render; read the rows.
+## Example
+```mermaid
+pie showData
+    title Test suite composition
+    "Unit" : 271
+    "Hook" : 28
+    "Contract" : 15
+    "Distribution" : 3
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/sequence.md ADDED Viewed

@@ -0,0 +1,63 @@
+# Sequence Diagram Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/sequenceDiagram.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword form
+`sequenceDiagram`. No direction modifier.
+## Message tokens
+| Token | Meaning |
+| --- | --- |
+| `->` | solid line, no arrowhead |
+| `-->` | dotted line, no arrowhead |
+| `->>` | solid line with arrowhead |
+| `-->>` | dotted line with arrowhead |
+| `<<->>` | solid bidirectional |
+| `<<-->>` | dotted bidirectional |
+| `-x` | solid line with a cross (async, lost) |
+| `--x` | dotted line with a cross |
+| `-)` | solid line with an open arrow (async) |
+| `--)` | dotted line with an open arrow |
+Half-arrow variants (`-\`, `-/` families) were added in 11.12.3 and later.
+Everything after the first `:` on a message line is free text: it may contain dashes, angle
+brackets, and brackets, and it is never edge-checked. Only the pre-colon segment carries the
+message token.
+## Structural conventions
+- `participant <id> as <label>` and `actor <id>` declare lifelines; declaration order fixes the
+  left-to-right order.
+- `activate <id>` / `deactivate <id>`, or a `+`/`-` suffix on the message token, mark activation.
+- Block keywords: `loop`, `alt`, `else`, `opt`, `par`, `and`, `critical`, `break`, `rect`, `box`.
+  Each block is closed by `end`.
+- `Note left of <id>`, `Note right of <id>`, `Note over <id>,<id>` place notes.
+- `autonumber` numbers messages. `create participant <id>` and `destroy <id>` manage lifeline
+  lifetime.
+- Brackets are NOT structural in a sequence diagram, because message text routinely contains them.
+## Example
+```mermaid
+sequenceDiagram
+    autonumber
+    participant C as Client
+    participant A as API
+    participant D as Database
+    C->>A: POST /orders [payload 2 - 3 items]
+    activate A
+    A->>D: INSERT order
+    D-->>A: order id
+    A-->>C: 201 Created
+    deactivate A
+    alt payment declined
+        A-->>C: 402 Payment Required
+    else accepted
+        A-)C: webhook: order.confirmed
+    end
+    Note over C,A: Retry policy is 3 attempts
+```

package/resources/claude-customizations/.claude/skills/mermaid-diagram/references/state.md ADDED Viewed

@@ -0,0 +1,49 @@
+# State Diagram Syntax Reference
+Pinned to Mermaid **11.17.0**. Source: `https://mermaid.js.org/syntax/stateDiagram.html`.
+When a construct is absent here, `WebFetch` that page and confirm the form before generating.
+## First-line keyword forms
+`stateDiagram-v2` (preferred) or `stateDiagram` (legacy). Both accept a following `direction`
+statement rather than a direction suffix on the keyword line.
+## Transition token
+`-->` is the only transition token. A single-dash `->` is a defect, and a sequence or class token in
+a state diagram is a defect. Length variants (`--->`) are accepted.
+The transition label follows the first `:` and is free text: `Idle --> Running: start button`.
+## Structural conventions
+- `[*]` is the start pseudo-state when it is the transition source and the end pseudo-state when it
+  is the target.
+- `state <Name> { ... }` declares a composite state; braces are structural, so every opener needs a
+  closer. `direction` inside a composite sets that composite's direction.
+- `state "free text description" as <id>` names a state whose label is not identifier-shaped.
+- Fork and join use `<<fork>>` and `<<join>>` annotations; a choice point uses `<<choice>>`.
+- `note left of <id>` / `note right of <id>` place notes; a `note` block is closed by `end note`.
+- `--` inside a composite state separates concurrent regions.
+## Example
+```mermaid
+stateDiagram-v2
+    direction LR
+    [*] --> Idle
+    Idle --> Validating: submit
+    state Validating {
+        direction TB
+        [*] --> Schema
+        Schema --> Business: schema ok
+        Business --> [*]
+    }
+    Validating --> Accepted: all checks pass
+    Validating --> Rejected: any check fails
+    Accepted --> [*]
+    Rejected --> Idle: correct and resubmit
+    note right of Rejected
+        The reason names the failing check.
+    end note
+```

package/resources/claude-customizations/.claude/skills/parallel-orchestrate/SKILL.md CHANGED Viewed

@@ -324,13 +324,14 @@ Procedure, per item:
    `docs/features/parallel/<slug>/parallel-status.md`.
 5. On a merge failure caused by a conflict, follow `## Per-Item Merge-Conflict Handling`.
-**F7 dependency.** `.claude/hooks/enforce-epic-merge-gate.ps1` is a project-wide `PreToolUse`
-Bash-matcher hook that denies any `gh pr merge --merge` unless an epic-shaped checkpoint satisfies
-its allow conditions; its block reason is `EPIC_MERGE_GATE_BLOCKED`. A parallel run has no
-epic-shaped checkpoint, so step 3 above is denied until F7 scopes or extends that gate's allow
-conditions for the parallel case. This feature modifies no file under `.claude/hooks/` and does not
-change `.claude/settings.json`, so the parallel surface is not executable end-to-end before F7
-lands. That limitation is documented, not worked around.
+**Merge-gate authorization.** `.claude/hooks/enforce-epic-merge-gate.ps1` is a project-wide
+`PreToolUse` Bash-matcher hook that denies any `gh pr merge --merge` unless a checkpoint satisfies
+one of its allow conditions; its block reason is `EPIC_MERGE_GATE_BLOCKED`. The gate now authorizes
+a parallel per-item merge when the parallel-orchestrator checkpoint has `route_id == "parallel"`,
+the target item's `merge_status == "ci_green"`, and, when a PR number is named, it matches the
+item's `pr_number`. Step 3 above is therefore permitted for a legitimate parallel merge; a missing,
+unreadable, or invalid parallel checkpoint, a target item whose `merge_status` is not `ci_green`, or
+a PR number that matches no item still fails closed with `EPIC_MERGE_GATE_BLOCKED`.
 Branch protection on `main` affects only the pacing of step 3, not its ownership: if `main`
 requires branches to be up to date, an automated `gh pr update-branch` plus re-green cycle is

package/resources/claude-customizations/.claude/skills/parallel-plan/SKILL.md CHANGED Viewed

@@ -221,14 +221,34 @@ separator-free repository-root shared surfaces from plan and spec text, admittin
 as an exact ordinal member of the configured `shared_surfaces` list in `config/blast-radius.json`;
 and the contention path comparison now honours listed-directory prefixes on both sides, aligning
 with `is_path_subsumed`. Both corrections move results in the fail-closed direction — they report
-more contention, not less. Do not work around either correction, and do not narrow a radius in
-order to suppress a conflict edge they produce.
+more contention, not less. Do not work around either correction.
+**The exclusions are configured, not improvised (issue #489).** `config/blast-radius.json` carries
+an optional `mandate_reads` list naming the paths every agent is instructed to read before doing
+any work: the policy rules, the tier map, and the process artifacts. A citation of one of those
+paths is evidence that the author obeyed the reading order, not evidence that the change will write
+the file, so `derive_blast_radius` drops it from the harvest and `validate_blast_radius` drops it
+from its plan-side extraction, which keeps V1 and V2 self-consistent. The extractor likewise rejects
+three token shapes that were never write claims: a wildcard-free token naming a directory rather
+than a file, a `docs/features/` glob whose wildcard spans every feature folder, and a contract token
+carrying no ASCII letter. These exclusions are part of the landed contract, so the prohibition now
+reads: do not narrow a radius beyond the configured exclusions in order to suppress a conflict edge.
+**Appending an excluded path is the planner's obligation, not an exception.** An exclusion describes
+the default reading relationship, not a permanent ban. When an item's plan will genuinely WRITE a
+path that the exclusions remove — amending a rule file under `.claude/rules/`, editing
+`quality-tiers.yml`, or changing an instruction document under `.github/instructions/` — the planner
+MUST append that exact path to the item's declared radius explicitly after normalization. Omitting
+it under-reports contention and lets two items that both rewrite the same policy file run
+concurrently.
 ### Planner procedure
 1. After an item's plan is approved and preflight-clear, read the approved plan text and the
-   feature `spec.md` text, derive the radius with `source: "declared"`, and record it on the item.
-   The `declared` radius is the authoritative input to scheduling.
+   feature `spec.md` text, derive the radius with `source: "declared"`, then call
+   `normalize_declared_radius(radius, config)` to re-apply the current extraction rules and the
+   configured exclusions, append any excluded path the plan's diff will genuinely write, and record
+   the result on the item. The `declared` radius is the authoritative input to scheduling.
 2. Validate the radius and record the findings under the item's `radius_validation` entry.
 3. **V1 (coverage) or V2 (shared-surface enumeration) Blocking failure.** The item does NOT
    transition to `prepared`. Record the findings in the checkpoint and issue a follow-up

package/resources/claude-customizations/config/blast-radius.json CHANGED Viewed

@@ -2,12 +2,26 @@
   "version": 1,
   "shared_surfaces": [
     ".claude/settings.json",
+    "config/blast-radius.json",
     "config/orchestration-routing.json",
-    "config/blast-radius.json"
+    "package-lock.json",
+    "poetry.lock",
+    "quality-tiers.yml"
   ],
   "shared_surface_globs": [],
+  "mandate_reads": [
+    ".claude/rules/**",
+    ".claude/skills/atomic-plan-contract/SKILL.md",
+    ".claude/skills/evidence-and-timestamp-conventions/SKILL.md",
+    ".github/instructions/**",
+    "artifacts/**",
+    "quality-tiers.yml",
+    ".claude/skills/acceptance-criteria-tracking/SKILL.md",
+    ".claude/skills/policy-compliance-order/SKILL.md",
+    ".claude/agent-memory/**",
+    ".agents/skills/**"
+  ],
   "modules": {
-    "claude-runtime": [".claude/**"],
     "config": ["config/**"]
   },
   "over_breadth_fraction": 0.25

package/resources/claude-customizations/pack-manifests/core.json CHANGED Viewed

@@ -35,11 +35,13 @@
     ".claude/hooks/enforce-orchestration-preimplementation-gate.ps1",
     ".claude/hooks/enforce-parallel-abandon-gate.ps1",
     ".claude/hooks/enforce-parallel-cohort-barrier.ps1",
+    ".claude/hooks/enforce-parallel-cohort-barrier-helpers.ps1",
     ".claude/hooks/enforce-parallel-drift-gate.ps1",
     ".claude/hooks/enforce-parallel-drift-gate-helpers.ps1",
     ".claude/hooks/enforce-parallel-worktree-removal-gate.ps1",
     ".claude/hooks/enforce-pr-author-skill.epic-base-branch.ps1",
     ".claude/hooks/enforce-pr-author-skill.ps1",
+    ".claude/hooks/enforce-pr-author-skill-helpers.ps1",
     ".claude/hooks/enforce-prd-feature-before-planner.ps1",
     ".claude/hooks/enforce-promotion-mcp-only.ps1",
     ".claude/hooks/persist-session-id.ps1",
@@ -57,6 +59,7 @@
     ".claude/rules/general-code-change.md",
     ".claude/rules/general-unit-test.md",
     ".claude/rules/orchestrator-state.md",
+    ".claude/rules/plan-acceptance-gates.md",
     ".claude/rules/quality-tiers.md",
     ".claude/rules/self-explanatory-code-commenting.md",
     ".claude/rules/tonality.md",
@@ -104,6 +107,7 @@
     ".claude/skills/skill-canonical-location-audit/SKILL.md",
     ".claude/skills/translate-copilot-to-claude/SKILL.md",
     ".claude/skills/update-status/SKILL.md",
+    ".claude/lib/hook-payload/HookPayload.psm1",
     ".claude/lib/model-routing/ModelRouting.psm1",
     ".claude/lib/orchestrator-state/OrchestratorState.psm1",
     ".claude/lib/orchestrator-state/OrchestratorStateCompletion.psm1",
@@ -124,6 +128,7 @@
     ".claude/lib/blast-radius/BlastRadiusConfig.psm1",
     ".claude/lib/blast-radius/BlastRadiusValidation.psm1",
     ".claude/lib/blast-radius/BlastRadius.psm1",
+    ".claude/lib/blast-radius/BlastRadiusNormalization.psm1",
     ".claude/rules/parallel-orchestration.md",
     ".claude/rules/shell.md",
     ".claude/lib/bash/compute-cohorts.sh",
@@ -136,6 +141,22 @@
     ".claude/lib/bash/parallel-yaml-scan.sh",
     ".claude/lib/bash/validate-parallel-manifest.sh",
     "config/orchestration-routing.json",
-    "config/blast-radius.json"
+    "config/blast-radius.json",
+    ".claude/hooks/enforce-mermaid-validation.ps1",
+    ".claude/rules/mermaid.md",
+    ".claude/skills/mermaid-diagram/SKILL.md",
+    ".claude/lib/mermaid/MermaidGrammar.psm1",
+    ".claude/lib/mermaid/MermaidLineScanner.psm1",
+    ".claude/lib/mermaid/MermaidMarkdownFences.psm1",
+    ".claude/lib/mermaid/MermaidValidation.psm1",
+    ".claude/skills/mermaid-diagram/references/flowchart.md",
+    ".claude/skills/mermaid-diagram/references/sequence.md",
+    ".claude/skills/mermaid-diagram/references/class.md",
+    ".claude/skills/mermaid-diagram/references/state.md",
+    ".claude/skills/mermaid-diagram/references/er.md",
+    ".claude/skills/mermaid-diagram/references/c4.md",
+    ".claude/skills/mermaid-diagram/references/gantt.md",
+    ".claude/skills/mermaid-diagram/references/pie.md",
+    ".claude/skills/mermaid-diagram/references/other-types.md"
   ]
 }

package/resources/codex-and-agents-customizations/.agents/skills/evidence-and-timestamp-conventions/SKILL.md CHANGED Viewed

@@ -111,6 +111,19 @@ When evidence artifacts are used for automated checking or plan reconciliation,
 - `Command: <exact command>`
 - `EXIT_CODE: <int>`
+One optional field may also be declared:
+- `ExpectedExitCode: <int>` — the exit code the gate is expected to produce.
+Rules for the optional expectation field:
+- The spelling is exact and case-sensitive: `ExpectedExitCode`. `expectedexitcode` and `Expected Exit Code` do not match the accept-list and are discarded as unrecognized rows.
+- The value is a single integer. A leading sign is accepted and no range check is applied; the value is used for an equality comparison only.
+- When the field is absent the expectation defaults to `0`, so every artifact that omits it keeps its existing result. Writing `ExpectedExitCode: 0` explicitly renders identically to omitting the field.
+- A present but non-integer value (including an empty value) makes the WHOLE artifact `unparseable`. An unparseable artifact is dropped by the collector filter, so a typo in the expectation removes the row from the PR body rather than degrading it to `fail`.
+- When the field is duplicated, the FIRST occurrence wins in both the Python and the TypeScript parser; later occurrences are ignored.
+- The field is per-FILE, not per-gate: one artifact carries exactly one expectation, so an artifact recording several gates cannot express a different expectation for each. Record a gate that needs a non-zero expectation in its own artifact file.
+A gate whose observed `EXIT_CODE` equals its declared expectation is normalized to `pass`. The observed exit code is still displayed, and the rendered row additionally carries `  - Expected EXIT_CODE: <int>` between the `EXIT_CODE` and `Normalized result` lines when the expectation is non-zero.
 ### Baseline Evidence Output Summary (Required)
 For baseline evidence artifacts stored under `evidence/baseline/`, include an output summary in addition to the schema fields above:

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

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