@danmoisan/drm-copilot-mcp 0.0.1 → 0.0.5

package/resources/claude-customizations/.claude/skills/policy-audit-template-usage/SKILL.md

@@ -15,13 +15,13 @@ Use this skill when:
 
 ## Template Source
 
-- Required template source: the MCP server tool `mcp__drmCopilotExtension__resolve_policy_audit_template_asset` with asset selector `template`.
+- Required template source: the MCP server tool `mcp__drm-copilot__resolve_policy_audit_template_asset` with asset selector `template`.
 - The resolved MCP asset is authoritative even when a matching repo file also exists.
 - If MCP asset resolution fails, create a minimal policy audit artifact marked BLOCKED and document the missing template resolution.
 
 ## Required Steps
 
-1) Resolve the policy-audit template through the MCP server tool `mcp__drmCopilotExtension__resolve_policy_audit_template_asset` with asset `template`, then copy the resolved asset to the target location using an ISO-8601 timestamp.
+1) Resolve the policy-audit template through the MCP server tool `mcp__drm-copilot__resolve_policy_audit_template_asset` with asset `template`, then copy the resolved asset to the target location using an ISO-8601 timestamp.
 2) Replace placeholders with actual values (component, date, files under test, commits).
 3) Remove any template usage instructions per template guidance.
 4) Mark each section PASS/FAIL/N/A using the template’s expected conventions.
@@ -39,7 +39,7 @@ Use this skill when:
    - `## 10. Compliance Verdict`
    - `## Appendix A: Test Inventory`
    - `## Appendix B: Toolchain Commands Reference`
-6) Run the `mcp__drmCopilotExtension__validate_orchestration_artifacts` MCP tool with `artifact_type: "policy-audit"` and `artifact_path: <path>` and fail closed on any non-zero result.
+6) Run the `mcp__drm-copilot__validate_orchestration_artifacts` MCP tool with `artifact_type: "policy-audit"` and `artifact_path: <path>` and fail closed on any non-zero result.
 
 ## Invalid Outputs
 

package/resources/claude-customizations/.claude/skills/powershell-qa-gate/SKILL.md

@@ -27,9 +27,9 @@ Before invoking this gate, the agent must have:
 
 Run the full toolchain in this exact order. If any step fails or modifies files, fix the issue and restart from step 1. Do not stop the loop until all steps complete without errors in a single pass.
 
-1. `mcp__drmCopilotExtension__run_poshqc_format`
-2. `mcp__drmCopilotExtension__run_poshqc_analyze`
-3. `mcp__drmCopilotExtension__run_poshqc_test`
+1. `mcp__drm-copilot__run_poshqc_format`
+2. `mcp__drm-copilot__run_poshqc_analyze`
+3. `mcp__drm-copilot__run_poshqc_test`
 4. Coverage check (when enforced by task/repo flow) — use the Pester coverage output from step 3 or the repo coverage task.
 
 If the environment prevents running any tool, stop and report the change as **unverified**. Do not declare completion.
@@ -42,7 +42,7 @@ Compare the final results to the Phase A baseline. All of the following must hol
 - **Pester delta**: 0 new failing tests.
 - **Per-file coverage delta**: coverage for every touched file is greater than or equal to the baseline for that file.
 - **Overall coverage delta** (when the repo enforces it): overall coverage is greater than or equal to the baseline.
-- **New modules, classes, or methods**: coverage >= 90% for each new unit introduced in the batch.
+- **New modules, classes, or methods**: line coverage >= 85% and branch coverage >= 75% per the uniform tier rule (`.claude/rules/quality-tiers.md`). No tier-specific lower thresholds. No regression on changed lines.
 
 If any delta check fails, the agent must revert or fix immediately and rerun the full toolchain. Do not proceed to reporting until all deltas are clean.
 

package/resources/claude-customizations/.claude/skills/pr-base-branch-merge-base/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pr-base-branch-merge-base
-description: 'Resolve PRBaseBranch for mcp__drmCopilotExtension__collect_pr_context using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.'
+description: 'Resolve PRBaseBranch for mcp__drm-copilot__collect_pr_context using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.'
 ---
 
 # PR Base Branch (Merge-Base)
@@ -10,7 +10,7 @@ Deterministic branch-selection rules for PR context collection.
 ## When to Use This Skill
 
 Use this skill when:
-- running `mcp__drmCopilotExtension__collect_pr_context`,
+- running `mcp__drm-copilot__collect_pr_context`,
 - delegating post-implementation review that depends on `PRBaseBranch`,
 - constructing PR context artifacts where the base must not be hard-coded.
 
@@ -44,7 +44,7 @@ Definition of correct base:
 
 When invoking PR context collection, pass the resolved base explicitly:
 
-- `mcp__drmCopilotExtension__collect_pr_context` with `base=<resolved-PRBaseBranch>`
+- `mcp__drm-copilot__collect_pr_context` with `base=<resolved-PRBaseBranch>`
 
 ## Evidence Recommendation
 

package/resources/claude-customizations/.claude/skills/python-qa-gate/SKILL.md

@@ -43,7 +43,7 @@ Compare the final results to the Phase A baseline. All of the following must hol
 - **Pytest delta**: 0 new failing tests.
 - **Per-file coverage delta**: coverage for every touched file is greater than or equal to the baseline for that file.
 - **Overall coverage delta** (when the repo enforces it): overall coverage is greater than or equal to the baseline.
-- **New modules, classes, or methods**: coverage >= 90% for each new unit introduced in the batch.
+- **New modules, classes, or methods**: line coverage >= 85% and branch coverage >= 75% per the uniform tier rule (`.claude/rules/quality-tiers.md`). No tier-specific lower thresholds. No regression on changed lines.
 
 If any delta check fails, the agent must revert or fix immediately and rerun the full toolchain. Do not proceed to reporting until all deltas are clean.
 

package/resources/claude-customizations/.claude/skills/remediation-handoff-atomic-planner/SKILL.md

@@ -1,40 +1,113 @@
 ---
 name: remediation-handoff-atomic-planner
-description: 'Reusable remediation trigger and atomic_planner handoff steps. Use when audits require remediation inputs and a delegated remediation plan.'
+description: 'Remediation handoff chain from orchestrator through atomic-planner, atomic-executor, and feature-review. Use when an audit cycle requires a delegated remediation plan, preflight clearance, task-by-task execution, and reaudit.'
 ---
 
-# Remediation Handoff to atomic_planner
+# Remediation Handoff to atomic-planner
 
-Shared remediation workflow and handoff expectations for agents that delegate to `atomic_planner`.
+Strict handoff chain for orchestrator-initiated remediation cycles. The chain enforces that an `atomic-planner`-authored plan is preflighted by `atomic-executor`, revised through a preflight sub-loop if needed, executed by `atomic-executor` task-by-task, and reaudited by `feature-review`. Workers are never invoked directly by the orchestrator.
 
 ## When to Use This Skill
 
 Use this skill when:
-- Audit findings require remediation.
-- You must create remediation inputs and delegate plan creation to `atomic_planner`.
 
-## Trigger Conditions (Generic)
+- Audit findings require remediation (FAIL or material PARTIAL findings).
+- Toolchain checks fail.
+- Acceptance criteria are unmet.
+- A required CI check fails after the pull request is open.
+- Any new finding surfaces during execution of an active cycle (in which case begin a new cycle, do not extend the active one).
+
+## Full Handoff Chain
+
+```
+orchestrator
+  -> writes remediation-inputs.<entry-ts>.md
+  -> delegates to atomic-planner
+     -> atomic-planner authors remediation-plan.<entry-ts>.md
+        (plan shape per .claude/skills/atomic-plan-contract/SKILL.md)
+     -> orchestrator hands plan to atomic-executor for preflight
+        -> atomic-executor returns one of:
+             PREFLIGHT: ALL CLEAR        -> proceed to execution
+             PREFLIGHT: REVISIONS REQUIRED -> route back to atomic-planner
+                with a precise plan delta; planner revises in place and
+                orchestrator re-runs preflight (sub-loop until clear)
+     -> atomic-executor executes the cleared plan task-by-task
+        (workers are invoked by atomic-executor only)
+     -> orchestrator delegates to feature-review
+        -> feature-review writes code-review.<exit-ts>.md,
+           feature-audit.<exit-ts>.md, and policy-audit.<exit-ts>.md
+  -> orchestrator evaluates exit condition:
+     blocking_count == 0 -> mark exit_condition_met = true, end loop
+     blocking_count > 0  -> begin cycle N+1 with new remediation-inputs.<new-ts>.md
+```
+
+The orchestrator must not call typed-engineer workers directly during any phase of the cycle. The orchestrator must not act on a preflight delta itself; revisions are routed to `atomic-planner`.
+
+## Trigger Conditions
 
 Trigger remediation when any of these are true:
+
 - Audit artifacts contain FAIL or meaningful PARTIAL findings.
-- Toolchain checks fail.
+- Toolchain checks fail (format, lint, type-check, test, contract, or integration stages).
 - Acceptance criteria are not met.
+- A required CI check fails after the PR is open (workflow-file changes specifically must enter the loop and trigger the `modified-workflow-needs-green-run` rule defined in `.claude/skills/feature-review-workflow/SKILL.md`).
 
 ## Required Remediation Inputs
 
-Create `remediation-inputs.<timestamp>.md` with:
+The orchestrator authors `remediation-inputs.<entry-ts>.md` with:
+
 - Enumerated fix list with file paths, expected behavior, and verification commands.
-- A “do not do” list (no scope creep, no policy weakening, no silent skips).
+- A "do not do" list (no scope creep, no policy weakening, no silent skips).
+- A pointer to the audit artifacts that produced the findings.
 
-## Plan Creation and Handoff
+## Required Artifacts
 
-1) Create a remediation plan target file using the repo’s plan template.
-2) Delegate to `atomic_planner` with:
-   - `${spec}` pointing to remediation inputs (authoritative)
-   - `${file}` pointing to the remediation plan target file
-3) Require `atomic_planner` to output a deterministic, atomic plan with phases and `[P#-T#]` IDs.
+Each remediation cycle produces exactly five artifacts under the active feature folder:
 
-## Context Package (When Required)
+1. `docs/features/active/<slug>/remediation-inputs.<entry-ts>.md` — orchestrator authors at cycle entry.
+2. `docs/features/active/<slug>/remediation-plan.<entry-ts>.md` — `atomic-planner` authors at cycle entry.
+3. `docs/features/active/<slug>/code-review.<exit-ts>.md` — `feature-review` authors at cycle exit.
+4. `docs/features/active/<slug>/feature-audit.<exit-ts>.md` — `feature-review` authors at cycle exit.
+5. `docs/features/active/<slug>/policy-audit.<exit-ts>.md` — `feature-review` authors at cycle exit.
+
+Timestamp rule:
+
+- `<entry-ts>` is the ISO-8601 timestamp at cycle entry, in the `yyyy-MM-ddTHH-mm` format defined in `.claude/skills/evidence-and-timestamp-conventions/SKILL.md`. It applies to both `remediation-inputs.<entry-ts>.md` and `remediation-plan.<entry-ts>.md`.
+- `<exit-ts>` is the ISO-8601 timestamp at cycle exit (when `feature-review` runs), in the same `yyyy-MM-ddTHH-mm` format. It applies to all three reaudit artifacts: `code-review.<exit-ts>.md`, `feature-audit.<exit-ts>.md`, and `policy-audit.<exit-ts>.md`.
+
+A cycle with fewer than five artifacts is malformed. A cycle that uses a single timestamp for both entry and exit is malformed unless both phases ran within the same minute.
+
+## Plan Shape
 
-If the calling agent requires a context package, inline the specified audit artifacts, PR context artifacts, and any relevant plan files in the delegated prompt.
+`remediation-plan.<entry-ts>.md` MUST conform to `.claude/skills/atomic-plan-contract/SKILL.md`. In particular:
+
+- Phase headings: `### Phase N — <Title>`.
+- Tasks: `- [ ] [P#-T#]` with sequential per-phase IDs.
+- Phase 0 captures policy reads and baseline toolchain results per `policy-compliance-order` and `evidence-and-timestamp-conventions`.
+- Final phase runs the full toolchain QA loop in the order specified by `atomic-plan-contract` and records numeric coverage values where the repository policy requires coverage.
+- Evidence paths resolve to `<FEATURE>/evidence/<kind>/` per the non-overridable evidence path clause.
+
+The plan must pass the `mcp__drm-copilot__validate_orchestration_artifacts` MCP tool with `artifact_type: "plan"` and `artifact_path: <plan-path>` before `atomic-executor` runs preflight against it.
+
+## Preflight Sub-Loop
+
+After the plan is authored, `atomic-executor` runs preflight under the directive `DIRECTIVE: PREFLIGHT VALIDATION ONLY`. The exact signal returned is either:
+
+- `PREFLIGHT: ALL CLEAR` — the plan proceeds to execution.
+- `PREFLIGHT: REVISIONS REQUIRED` — `atomic-executor` returns a precise plan delta. The orchestrator routes the delta to `atomic-planner` for revision. `atomic-planner` updates the same plan file in place (per the plan-path continuity contract in `atomic-plan-contract`). The orchestrator then re-runs preflight. The sub-loop repeats until `PREFLIGHT: ALL CLEAR` is returned.
+
+The orchestrator records the preflight outcome in `remediation_loop.cycles[current_cycle].preflight` with `iterations` (counter) and `final_status` (`clear|changes_requested|pending`).
+
+## Execution and Reaudit
+
+When preflight is clear, `atomic-executor` executes the plan task-by-task. The executor invokes workers (`python-typed-engineer`, `typescript-engineer`, `csharp-typed-engineer`, `powershell-typed-engineer`) internally as needed. The orchestrator does not call workers.
+
+When execution is complete, the orchestrator delegates to `feature-review`. `feature-review` produces the three reaudit artifacts under the active feature folder using the exit timestamp.
+
+## Exit Gate
+
+The orchestrator reads the latest cycle's three reaudit artifacts and computes `blocking_count` as the total number of FAIL findings plus material PARTIAL findings flagged as blocking. Only when `blocking_count == 0` does the orchestrator set `exit_condition_met = true` on the current cycle and mark the remediation loop complete. Otherwise, the orchestrator opens cycle N+1 with a new `remediation-inputs.<new-ts>.md` and runs the full chain again.
+
+## Context Package (When Required)
 
+If the calling agent requires a context package, inline the relevant audit artifacts, PR context artifacts, and any active plan files in the delegated prompt to `atomic-planner` rather than referencing them by path alone.

package/resources/claude-dir-customizations/.mcp.json

@@ -1,8 +1,8 @@
 {
   "mcpServers": {
-    "drmCopilotExtension": {
-      "command": "node",
-      "args": ["extensions/drm-copilot/out/mcp-server.js"]
+    "drm-copilot": {
+      "command": "npx",
+      "args": ["-y", "@danmoisan/drm-copilot-mcp"]
     }
   }
 }

package/resources/codex-and-agents-customizations/.agents/README.md

@@ -66,7 +66,7 @@ When migrating a Copilot artifact:
 2. If it defines a reusable agent persona or bounded delegation role, migrate it to `.codex/agents/<name>.toml`.
 3. If it is mainly a launch prompt or an orchestration shortcut, migrate it to `.codex/prompts/<name>.md`.
 4. Preserve stable names where possible so downstream handoffs remain readable and consistent.
-5. If a Copilot workflow relied on `drmCopilotExtension.*` commands or another host-specific surface, move that translation logic into `repo-automation-adapter`, target semantic MCP tools on server `drmCopilotExtension` when available, and keep the business workflow skill host-agnostic.
+5. If a Copilot workflow relied on `drmCopilotExtension.*` commands or another host-specific surface, move that translation logic into `repo-automation-adapter`, target semantic MCP tools on server `drm-copilot` when available, and keep the business workflow skill host-agnostic.
 
 ## External Tool Bindings
 

package/resources/codex-and-agents-customizations/.agents/skills/acceptance-criteria-tracking/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: acceptance-criteria-tracking
 description: 'Track and check off acceptance criteria in requirement source files (issue.md, spec.md, user-story.md) as they are delivered. Use when executing plans, reviewing features, or validating delivery to keep AC checkboxes current.'

package/resources/codex-and-agents-customizations/.agents/skills/architecture-boundaries/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: architecture-boundaries
+description: Architecture boundary enforcement rules for the No-COM architecture.
+paths:
+  - "**/*.ts"
+  - "**/*.cs"
+description: Architecture boundary enforcement rules for the No-COM architecture.
+---
+
+# Converted rule
+
+Source: legacy Claude rule `architecture-boundaries`.
+
+# Architecture Boundaries
+
+Architecture boundary enforcement is a uniform gate across all tiers (T1–T4). Violations block PRs.
+
+## Enforcement Tools
+
+- **TypeScript:** `dependency-cruiser`. Configuration file pattern: `.dependency-cruiser.cjs`.
+- **.NET (when the backend exists):** `NetArchTest.Rules`. Test project naming pattern: `*.ArchitectureTests`.
+
+## No-COM Architecture Rules (enforceable assertions)
+
+Production code in this repository must satisfy each of the following assertions. Each assertion is enforced by `dependency-cruiser` (TypeScript) or `NetArchTest.Rules` (.NET) where applicable; legacy import utilities, when added, must satisfy the same assertions.
+
+1. New runtime code must not reference VSTO APIs (`Microsoft.Office.Tools.*`).
+2. New runtime code must not reference Outlook desktop automation APIs (`Microsoft.Office.Interop.Outlook`).
+3. New runtime code must not expose COM-visible interfaces (`[ComVisible(true)]` attribute is banned in production code).
+4. New runtime code must not use Ribbon extensibility callbacks tied to the desktop object model.
+5. New runtime code must not depend on local Outlook event streams.
+6. New runtime code must not depend on Outlook user-defined fields as the primary state store.
+7. Mailbox data must be accessed only through Office.js or Microsoft Graph.
+8. Business behavior must be implemented in the backend or in host-neutral domain or application modules.
+9. Client UI must be implemented as web UI.
+10. Legacy integration, when required, must be limited to offline data import from files or exported data.
+
+## Layer Boundary Assertions (TypeScript)
+
+- `src/taskpane/` and `src/commands/` must not import from backend internals.
+- Domain modules must not import from Office.js, Microsoft Graph SDK, or any infrastructure adapter.
+- Adapters may import from domain; domain must not import from adapters.
+
+## Layer Boundary Assertions (.NET, applies once the backend exists)
+
+- `TaskMaster.Domain` must have zero references to Outlook PIA, VSTO, or Office.js types.
+- `TaskMaster.Application` may depend on `TaskMaster.Domain` only.
+- Adapter projects may depend on `TaskMaster.Domain` and `TaskMaster.Application`; domain may not depend on adapters.
+
+## Enforcement Outcome
+
+Violations of any rule above are PR-blocking findings. CI runs the architecture-boundary stage on every PR; a non-zero violation count fails the stage and prevents merge.

package/resources/codex-and-agents-customizations/.agents/skills/atomic-plan-contract/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill paths to shared skill paths.
-
 ---
 name: atomic-plan-contract
 description: 'Atomic plan format and toolchain contract shared by planning and execution agents. Use when generating, validating, or executing atomic plans with Phase 0, baseline capture, and final QA loops.'
@@ -24,7 +19,7 @@ Use this skill when:
 - Phase headings must be: `### Phase N — <Title>`
 - Tasks must start with: `- [ ] [P#-T#]` (or `[x]` for completed)
 - Task IDs must match their phase and be sequential per phase.
-- Plans must pass the `mcp__drmCopilotExtension__validate_orchestration_artifacts` MCP tool with `artifact_type: "plan"` and `artifact_path: <plan-path>` before they can be reported as approved.
+- Plans must pass the `mcp__drm-copilot__validate_orchestration_artifacts` MCP tool with `artifact_type: "plan"` and `artifact_path: <plan-path>` before they can be reported as approved.
 
 ## Short-Path Minimal Plan Contract
 
@@ -78,9 +73,22 @@ After preflight all-clear on the minimal-audit plan:
 - orchestrator MUST checkpoint Phase 0 evidence before branching.
 
 Branching after Phase 0:
-- `manual bootstrap` → save state and stop for manual resume,
+- `manual bootstrap` → save state and stop for manual resume ONLY when the initial user request explicitly opted into manual orchestration from the beginning,
 - otherwise continue with constrained small-path development, then executor validation, then reduced audit/remediation loop.
 
+## No-Manual-Step Contract (Mandatory)
+
+Unless the user's initial request explicitly opts into manual orchestration from the beginning, approved plans and remediation plans MUST remain fully automated.
+
+This prohibition includes:
+
+- manual bootstrap pauses,
+- human-operator validation tasks,
+- user-performed repro or QA steps,
+- requests for screenshots, notes, or runtime evidence that the agent cannot collect itself.
+
+When a fully automated equivalent is unavailable, the plan MUST fail closed by recording blocked or remediation-required automated state. It MUST NOT introduce a new manual step later in the workflow.
+
 ## Phase 0 Requirements
 
 Phase 0 must include tasks to read policy files in the order defined in `policy-compliance-order`.
@@ -158,7 +166,7 @@ When validating or handing off plans for execution:
 
 Before a plan can be treated as approved:
 
-- run the `mcp__drmCopilotExtension__validate_orchestration_artifacts` MCP tool with `artifact_type: "plan"` and `artifact_path: <plan-path>`,
+- run the `mcp__drm-copilot__validate_orchestration_artifacts` MCP tool with `artifact_type: "plan"` and `artifact_path: <plan-path>`,
 - reject the plan if that validator exits non-zero,
 - do not treat human-readable summaries as a substitute for validator success.
 

package/resources/codex-and-agents-customizations/.agents/skills/benchmark-baselines/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: benchmark-baselines
+description: Benchmark baseline provenance rules for performance regression gates.
+---
+
+# Converted rule
+
+Source: legacy Claude rule `benchmark-baselines`.
+
+# Benchmark Baseline Provenance
+
+This rule governs performance baselines used by benchmark regression gates. It exists because a baseline captured on a developer workstation was compared against a `windows-latest` runner, producing deterministic latency regressions that the benchmark gate could not survive (issue #26, PR #30).
+
+## Runner-Environment Parity (Required)
+
+Performance baselines must be captured in the same runner environment class against which they are compared. A baseline captured on a developer workstation must not be committed for comparison against a CI runner.
+
+## Prohibited: Unknown Processor
+
+A baseline whose `HostEnvironmentInfo.ProcessorName` is the literal string `"Unknown processor"` is rejected. This value indicates the baseline was captured in an environment where the processor could not be identified (typically a virtualized or developer workstation), which violates runner-environment parity.
+
+- Tooling MUST reject any baseline JSON where `HostEnvironmentInfo.ProcessorName == "Unknown processor"`.
+- The rejection is a Blocking finding; the baseline must be recaptured on the target runner class.
+
+## Required: Sibling Provenance File
+
+Every committed baseline file MUST have a sibling `baseline.provenance.json` in the same directory. The provenance file records, at minimum:
+
+- `runner_class` — the runner environment class that produced the baseline (for example `windows-latest`).
+- `host_signature` — a stable signature of the host (for example a hashed or labeled description of the CPU/core configuration).
+- `workflow_run_url` — the URL of the workflow run that produced the baseline.
+
+- Tooling MUST reject a baseline that has no sibling `baseline.provenance.json`.
+- The rejection is a Blocking finding; the baseline must be recaptured with provenance recorded.
+
+## Enforcement
+
+- The validator `scripts/benchmarks/Test-BaselineProvenance.ps1` enforces both rejection conditions above and accepts a runner-captured baseline whose `ProcessorName` is a real processor and whose sibling `baseline.provenance.json` is present.
+- The feature-review policy rule `modified-workflow-needs-green-run` (see `.agents/skills/feature-review-workflow/SKILL.md`) provides a second line of defense: a diff under `scripts/benchmarks/**` is Blocking unless a green workflow run against the branch head is present in remediation inputs.
+
+## Scope
+
+- This rule applies to any baseline consumed by a benchmark regression gate.
+- It does not change which checks are required by branch protection; it constrains the provenance of the data those checks consume.

package/resources/codex-and-agents-customizations/.agents/skills/ci-workflows/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: ci-workflows
+description: GitHub Actions PowerShell workflow authoring rules.
+---
+
+# Converted rule
+
+Source: legacy Claude rule `ci-workflows`.
+
+# CI Workflow Authoring
+
+This rule governs GitHub Actions workflow steps that run PowerShell (`pwsh`). It exists because a `pwsh` step that intentionally invoked a failing nested command left `$LASTEXITCODE == 1` after its verification logic had already succeeded, leaking a failure to GitHub Actions even though the step's intent was satisfied (issue #26, PR #30).
+
+## Deliberately-Failing Nested Command Pattern (Required)
+
+A workflow step whose `run:` block intentionally invokes a command expected to fail — for example a negative-path self-validation that asserts a gate catches a synthetic regression — MUST not allow the residual non-zero exit code to propagate to GitHub Actions.
+
+For any such step, the `run:` block MUST do one of the following:
+
+1. Reset the exit code explicitly after the expected failure:
+   ```powershell
+   & ./some-tool --expect-failure
+   $LASTEXITCODE = 0
+   ```
+2. Or terminate the success path with an explicit zero exit:
+   ```powershell
+   if ($verificationSucceeded) { exit 0 } else { exit 1 }
+   ```
+
+A `pwsh` step terminates with the exit code of the last external command unless the script explicitly resets it or calls `exit`. Negative-path verification steps therefore require an explicit reset or explicit `exit 0`.
+
+## Rationale
+
+- GitHub Actions interprets a step's process exit code as the step result. A leaked `$LASTEXITCODE` from an intentionally-failing nested command causes a passing verification to report failure.
+- No local toolchain stage executes a workflow's `run:` block, so this defect is invisible to local feature-review. This textual rule is the artifact local review cites when reading workflow YAML.
+
+## Enforcement
+
+- Local feature-review cites this rule when reviewing diffs that add or modify `pwsh` steps with deliberately-failing nested commands.
+- The feature-review policy rule `modified-workflow-needs-green-run` (see `.agents/skills/feature-review-workflow/SKILL.md`) requires a green workflow run against the branch head before a workflow change can merge, which exercises the exit-code path on the runner.
+
+## Scope
+
+- This rule applies to any workflow step whose `run:` block uses `shell: pwsh` (or the repo default `pwsh`) and intentionally invokes a failing nested command.
+- It does not change required-check configuration or branch protection.

package/resources/codex-and-agents-customizations/.agents/skills/commit-message/SKILL.md

@@ -1,15 +1,6 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: commit-message
 description: Generate a conventional commit message from staged Git changes following the repository's commit message conventions.
-allowed-tools:
-  - Read
-  - "Bash(git log *)"
-  - "Bash(git diff *)"
 ---
 
 # Commit Message Skill
@@ -26,12 +17,13 @@ Generate a single conventional commit message from staged Git changes or a provi
 ## Context Gathering
 
 1. Use the supplied commit-context artifact first when present.
-2. Otherwise inspect the staged diff and commit history only:
+2. When the `drm-copilot` MCP commit-context tool is available for the workflow, collect commit context through that tool and stop if the MCP call fails.
+3. Otherwise inspect read-only staged Git state only:
    - `git diff --cached --stat`
    - `git diff --cached`
    - `git diff --cached --name-only`
    - `git log --oneline -n 20`
-3. Do not infer intent from unstaged files or unrelated commit history.
+4. Do not infer intent from unstaged files or unrelated commit history.
 
 ## Classification
 

package/resources/codex-and-agents-customizations/.agents/skills/csharp/SKILL.md

@@ -1,9 +1,5 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
+name: csharp
 paths:
   - "**/*.cs"
   - "**/*.csproj"

package/resources/codex-and-agents-customizations/.agents/skills/csharp-change-budget-router/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: csharp-change-budget-router
 description: Budget-first routing contract for C# work: estimate production-file scope, choose small vs large path, enforce orchestration-first routing for larger changes, and use the VS Code extension command surface for promotion lifecycle steps when available.
@@ -29,7 +24,7 @@ Use this skill when:
 ## Orchestrated Small-Path Requirements
 
 When routed through `csharp-orchestrator`, small path still requires lifecycle scaffolding before implementation:
-- invoke promotion/folder lifecycle steps through `vscode/runCommand` + extension access per `feature-promotion-lifecycle` when available; use script/CLI fallback only when direct extension command execution is unavailable,
+- invoke promotion/folder lifecycle steps through the `drm-copilot` MCP tools required by `repo-automation-adapter`. If the MCP server or required tool is unavailable, stop before promotion,
 - promote potential item to GitHub issue with `--work-mode minor-audit`,
 - create active feature folder with `--work-mode minor-audit`,
 - delegate minimal-audit plan creation to `atomic_planner` with `DIRECTIVE: MINIMAL-AUDIT PLAN REQUIRED`,

package/resources/codex-and-agents-customizations/.agents/skills/csharp-orchestration-state-machine/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: csharp-orchestration-state-machine
 description: Checkpoint schema and resume protocol for long-running C# orchestration workflows.

package/resources/codex-and-agents-customizations/.agents/skills/csharp-qa-gate/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill paths to shared skill paths.
-
 ---
 name: csharp-qa-gate
 description: Final QA gate for C# changes. Executes the full CSharpier -> .NET Analyzers -> Nullable Analysis -> MSTest toolchain, compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.

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

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: evidence-and-timestamp-conventions
 description: 'Evidence storage and timestamp naming conventions for audits and remediation. Use when storing baseline/regression/QA evidence or naming audit artifacts with ISO-8601 timestamps.'

package/resources/codex-and-agents-customizations/.agents/skills/execute-hard-lock/SKILL.md

@@ -1,20 +1,11 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude agent manifest paths to Codex agent paths.
-- Rewrite remaining VS Code command IDs to semantic MCP tool usage.
-
 ---
 name: execute-hard-lock
-description: Place the session in atomic execution mode bound to a specific plan-of-record. Resolves the hard-lock prompt via the drmCopilotExtension MCP tool, then delegates to the atomic-executor subagent with the resolved text. Use when a caller provides ${plan-path} and ${work-mode} and requires strict plan-following behavior.
-allowed-tools:
-  - mcp__drmCopilotExtension__resolve_execute_hard_lock_prompt
-  - Read
+description: Place the session in atomic execution mode bound to a specific plan-of-record. Resolves the hard-lock prompt via the drm-copilot MCP tool, then delegates to the atomic-executor subagent with the resolved text. Use when a caller provides ${plan-path} and ${work-mode} and requires strict plan-following behavior.
 ---
 
 # Execute Hard Lock
 
-Thin wrapper that resolves the hard-lock prompt via the drmCopilotExtension MCP tool and hands the resolved text to the `atomic-executor` subagent as kickoff directives. The resolved prompt is the authoritative instruction set for the session; this skill does not duplicate its contents.
+Thin wrapper that resolves the hard-lock prompt via the drm-copilot MCP tool and hands the resolved text to the `atomic-executor` subagent as kickoff directives. The resolved prompt is the authoritative instruction set for the session; this skill does not duplicate its contents.
 
 ## When to Use This Skill
 
@@ -22,7 +13,7 @@ Use this skill when:
 
 - The caller provides an explicit plan file path (`${plan-path}`) and a selected work mode (`${work-mode}`).
 - Strict plan-following behavior is required (no replanning, no reordering, no bucket tasks).
-- The drmCopilotExtension MCP server is registered and reachable.
+- The drm-copilot MCP server is registered and reachable.
 
 ## Inputs
 
@@ -37,7 +28,7 @@ Required:
 
 Call the extension's resolver as the first action:
 
-- Tool: `mcp__drmCopilotExtension__resolve_execute_hard_lock_prompt`
+- Tool: `mcp__drm-copilot__resolve_execute_hard_lock_prompt`
 - Parameters:
   - `target` (required): the plan-of-record path (`${plan-path}`).
   - `workspace_root` (optional): the workspace root. Omit to default to the current working directory.
@@ -50,7 +41,7 @@ Use the `Read` tool on the path returned in `artifacts[0]`. Treat the file conte
 
 ### 3. Delegate to atomic-executor
 
-Invoke the `atomic-executor` subagent via the Agent tool. Pass the resolved prompt text as the subagent's kickoff directive, followed by `${plan-path}` and `${work-mode}` as session context.
+Spawn the `atomic-executor` subagent from `.codex/agents/atomic-executor.toml`. Pass the resolved prompt text as the subagent's kickoff directive, followed by `${plan-path}` and `${work-mode}` as session context. If the `atomic-executor` agent is unavailable, stop with `BLOCKED: execute-hard-lock spawn_agent_unavailable`.
 
 The resolved prompt itself already instructs the subagent to perform the mandatory read-proof (`git rev-parse HEAD`, SHA-256 of the plan file, unchecked-task count), preflight validation, and `READY TO BEGIN FROM [P#-T#]` handshake before executing any task. This skill does not reissue those instructions locally — doing so would risk divergence from the canonical template.
 
@@ -67,8 +58,8 @@ Stop immediately and report `BLOCKED: execute-hard-lock <cause>` in any of these
 
 The three entry points below all produce the same resolved hard-lock prompt for a given plan path. This skill always uses the MCP form:
 
-- MCP (used by this skill): `mcp__drmCopilotExtension__resolve_execute_hard_lock_prompt` with `target=<plan-path>`. The extension passes `--output artifacts/hard_lock_prompt.txt` and `--quiet` to the bundled Python resolver.
-- VS Code command: `@command:mcp__drmCopilotExtension__resolve_execute_hard_lock_prompt` (interactive; writes to stdout + clipboard, no file artifact).
+- MCP (used by this skill): `mcp__drm-copilot__resolve_execute_hard_lock_prompt` with `target=<plan-path>`. The extension passes `--output artifacts/hard_lock_prompt.txt` and `--quiet` to the bundled Python resolver.
+- VS Code command: `@command:mcp__drm-copilot__resolve_execute_hard_lock_prompt` (interactive; writes to stdout + clipboard, no file artifact).
 
 ## Delegation Contract
 
@@ -84,5 +75,5 @@ The `atomic-executor` subagent at [.codex/agents/atomic-executor.toml](.codex/ag
 - Do not proceed without a successful MCP resolver response AND a successful `Read` of the artifact.
 - Do not reconstruct the hard-lock contract from any other source (not from this file nor from prior session memory).
 - Do not modify the resolved prompt text before passing it to `atomic-executor`.
-- Do not replan, reorder, or add tasks at this layer — the subagent owns that contract.
+- Do not replan, reorder, or add tasks at this layer. The subagent owns that contract.
 - Do not create or read secrets unless explicitly authorized.