@danmoisan/drm-copilot-mcp 0.0.1 → 0.0.6

package/resources/codex-and-agents-customizations/.github/workflows/_validate-orchestrator-state.yml

@@ -0,0 +1,68 @@
+name: Validate Orchestrator State
+
+on:
+  workflow_call:
+    inputs:
+      state-path:
+        description: Repository-relative orchestrator checkpoint path.
+        required: false
+        type: string
+        default: artifacts/orchestration/orchestrator-state.json
+      require-checkpoint:
+        description: Fail when the checkpoint file is absent.
+        required: false
+        type: boolean
+        default: true
+  workflow_dispatch:
+    inputs:
+      state-path:
+        description: Repository-relative orchestrator checkpoint path.
+        required: false
+        type: string
+        default: artifacts/orchestration/orchestrator-state.json
+      require-checkpoint:
+        description: Fail when the checkpoint file is absent.
+        required: false
+        type: boolean
+        default: true
+
+jobs:
+  validate-orchestrator-state:
+    name: Validate orchestrator checkpoint
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install Poetry
+        uses: snok/install-poetry@v1
+        with:
+          version: latest
+          virtualenvs-create: true
+          virtualenvs-in-project: true
+
+      - name: Install dependencies
+        run: poetry install --no-interaction
+
+      - name: Validate checkpoint
+        env:
+          STATE_PATH: ${{ inputs.state-path }}
+          REQUIRE_CHECKPOINT: ${{ inputs.require-checkpoint }}
+        run: |
+          if [ ! -f "$STATE_PATH" ]; then
+            if [ "$REQUIRE_CHECKPOINT" = "true" ]; then
+              echo "ERROR: orchestrator checkpoint is required but was not found: $STATE_PATH" >&2
+              exit 1
+            fi
+            echo "No orchestrator checkpoint found at $STATE_PATH; validation skipped."
+            exit 0
+          fi
+
+          poetry run python -m scripts.dev_tools.validate_orchestration_artifacts \
+            orchestrator-state "$STATE_PATH" --require-complete

package/resources/codex-and-agents-customizations/.github/workflows/validate-orchestrator-state.yml

@@ -0,0 +1,15 @@
+name: Orchestrator State Gate
+
+on:
+  pull_request:
+    branches: [main, development]
+  push:
+    branches: [main, development]
+  workflow_dispatch:
+
+jobs:
+  validate-orchestrator-state:
+    uses: ./.github/workflows/_validate-orchestrator-state.yml
+    with:
+      state-path: artifacts/orchestration/orchestrator-state.json
+      require-checkpoint: false

package/resources/config/orchestration-routing.json

@@ -0,0 +1,76 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "version": 1,
+  "routes": {
+    "small": {
+      "description": "Minor-audit path for work inside the applicable language budget.",
+      "required_agents": [
+        "atomic-planner",
+        "atomic-executor",
+        "feature-review"
+      ],
+      "required_skills": [
+        "orchestrate",
+        "feature-promotion-lifecycle",
+        "atomic-plan-contract",
+        "acceptance-criteria-tracking",
+        "pr-context-artifacts",
+        "pr-base-branch-merge-base"
+      ],
+      "required_mcp_tools": [
+        "new_potential_entry",
+        "potential_to_issue",
+        "new_active_feature_folder",
+        "collect_pr_context",
+        "validate_orchestration_artifacts"
+      ]
+    },
+    "large": {
+      "description": "Full feature or bug path for work outside small-path budget.",
+      "required_agents": [
+        "task-researcher",
+        "prd-feature",
+        "atomic-planner",
+        "atomic-executor",
+        "feature-reviewer",
+        "commit-steward"
+      ],
+      "required_skills": [
+        "orchestrate",
+        "orchestrator-workflow",
+        "feature-promotion-lifecycle",
+        "repo-automation-adapter",
+        "atomic-plan-contract",
+        "acceptance-criteria-tracking",
+        "pr-context-artifacts",
+        "pr-base-branch-merge-base"
+      ],
+      "required_mcp_tools": [
+        "new_potential_entry",
+        "potential_to_issue",
+        "new_active_feature_folder",
+        "collect_commit_context",
+        "collect_pr_context",
+        "validate_orchestration_artifacts"
+      ]
+    },
+    "remediation": {
+      "description": "Review-triggered remediation loop.",
+      "required_agents": [
+        "atomic-planner",
+        "atomic-executor",
+        "feature-review"
+      ],
+      "required_skills": [
+        "orchestrate",
+        "atomic-plan-contract",
+        "acceptance-criteria-tracking",
+        "pr-context-artifacts"
+      ],
+      "required_mcp_tools": [
+        "collect_pr_context",
+        "validate_orchestration_artifacts"
+      ]
+    }
+  }
+}

package/resources/customizations/.github/agents/Powershell DI Unit Test Engineer.agent.md

@@ -91,7 +91,7 @@ If any gate fails:
 You must run the repo toolchain via `#tool:terminal`.
 
 ### Baseline runs (required before edits)
-- Analyzer baseline (repo standard): `mcp__drmCopilotExtension__run_poshqc_analyze`
+- Analyzer baseline (repo standard): `mcp__drm-copilot__run_poshqc_analyze`
 - Test baseline (targeted): run only the relevant Pester file(s) or tag/filter used by the repo
 - Coverage baseline: capture per-file coverage for the touched file(s), and overall if applicable
 

package/resources/customizations/.github/agents/atomic_executor.agent.md

@@ -242,7 +242,7 @@ If the user says “resume”, “continue”, or “try again”:
 - When completing a task or a plan, report the toolchain status explicitly: 
   - For python, this is Black, Ruff, Pyright, Pytest, and coverage.
   - For bash, this is shell QC and bats testing.
-  - For powershell, this is `mcp__drmCopilotExtension__run_poshqc_format`, `mcp__drmCopilotExtension__run_poshqc_analyze`, and `mcp_drmcopilotext_run_poshqc_test`.
+  - For powershell, this is `mcp__drm-copilot__run_poshqc_format`, `mcp__drm-copilot__run_poshqc_analyze`, and `mcp_drmcopilotext_run_poshqc_test`.
   - For json, this is json formatting and json linting.
 - Always end with the updated checklist so the user can see progress.
 

package/resources/customizations/.github/agents/atomic_planning.agent.md

@@ -361,13 +361,13 @@ When the work involves tests:
 
    **Bad:**
 
-   * [ ] [P3-T1] Implement tests for `mcp__drmCopilotExtension__run_poshqc_format`
-   * [ ] [P3-T2] Write unit tests for `mcp__drmCopilotExtension__run_poshqc_analyze`
+   * [ ] [P3-T1] Implement tests for `mcp__drm-copilot__run_poshqc_format`
+   * [ ] [P3-T2] Write unit tests for `mcp__drm-copilot__run_poshqc_analyze`
 
    **Good:**
 
-   * [ ] [P3-T1] Add regression test for `mcp__drmCopilotExtension__run_poshqc_format` forwarding selected `scan_folders`
-   * [ ] [P3-T2] Add regression test for `mcp__drmCopilotExtension__run_poshqc_analyze` rejecting invalid scan-folder input
+   * [ ] [P3-T1] Add regression test for `mcp__drm-copilot__run_poshqc_format` forwarding selected `scan_folders`
+   * [ ] [P3-T2] Add regression test for `mcp__drm-copilot__run_poshqc_analyze` rejecting invalid scan-folder input
    * [ ] [P3-T3] Add regression test for `mcp_drmcopilotext_run_poshqc_test` preserving the selected workspace scope
 
 ### 5.4.1 TDD Red regression tests must be tagged (MANDATORY)
@@ -422,15 +422,15 @@ When refactoring is required (e.g., to enable dependency injection, improve test
 
    **Bad:**
 
-   * [ ] [P1-T1] Refactor `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` integration for testability
+   * [ ] [P1-T1] Refactor `mcp__drm-copilot__run_poshqc_analyze_autofix` integration for testability
 
    **Good:**
 
-   * [ ] [P1-T1] Identify external dependencies used by `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` and list them in an internal note
-   * [ ] [P1-T2] Extract the autofix invocation seam behind `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` into helper functions
-   * [ ] [P1-T3] Add an injectable execution seam for `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` with a production default
-   * [ ] [P1-T4] Update all call sites of `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` to use the default seam
-   * [ ] [P1-T5] Verify that `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` is mockable via the new helper functions in tests
+   * [ ] [P1-T1] Identify external dependencies used by `mcp__drm-copilot__run_poshqc_analyze_autofix` and list them in an internal note
+   * [ ] [P1-T2] Extract the autofix invocation seam behind `mcp__drm-copilot__run_poshqc_analyze_autofix` into helper functions
+   * [ ] [P1-T3] Add an injectable execution seam for `mcp__drm-copilot__run_poshqc_analyze_autofix` with a production default
+   * [ ] [P1-T4] Update all call sites of `mcp__drm-copilot__run_poshqc_analyze_autofix` to use the default seam
+   * [ ] [P1-T5] Verify that `mcp__drm-copilot__run_poshqc_analyze_autofix` is mockable via the new helper functions in tests
 
 3. **No umbrella refactor tasks**
    You MUST NOT use a single task that says “Refactor X for testability.” Always decompose into multiple atomic slices as above.

package/resources/customizations/.github/agents/csharp-orchestrator.agent.md

@@ -111,6 +111,10 @@ Use these reusable skills to avoid duplicating shared operations:
   - `${feature-folder}`: created active feature folder path
   - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations
 
+5) **No manual steps by default**
+- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning.
+- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step.
+
 # Workflow router
 
 ## Phase 0 — Intake and budget estimate (mandatory)
@@ -198,11 +202,11 @@ Hard enforcement for S4:
 
 ### Step S5 — Branch by bootstrap mode
 
-S5.1 If request is `manual bootstrap`:
+S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning:
 - Save checkpoint with `next_step` at Phase 1 resume point.
 - Stop execution and return resume instructions.
 
-S5.2 If request is small development (not manual bootstrap):
+S5.2 Otherwise continue automated small development:
 - Continue to Step S6.
 
 ### Step S6 — Delegate constrained small-path development

package/resources/customizations/.github/agents/feature-review.agent.md

@@ -1,7 +1,7 @@
 ---
 name: feature_code_review_agent
-description: Review an entire feature branch relative to a base branch (PR-style). Read pr_context.summary.txt thoroughly, use pr_context.appendix.txt for full baseline diff evidence, and produce PolicyAudit + CodeReview + FeatureAudit (Acceptance Criteria). If remediation is needed, generate remediation inputs and delegate plan creation to atomic_planner to write remediation-plan.md in the active feature folder. No user questions.
-argument-hint: "Checkout the feature branch. Provide PRBaseBranch (e.g., development). Run this agent to (re)generate the PR context artifacts (summary + appendix) per `pr-context-artifacts` via MCP server `drmCopilotExtension` tool `collect_pr_context` with `base: ${input:PRBaseBranch}` when needed, then produce: (1) docs/features/active/<feature>/policy-audit.<timestamp>.md, (2) docs/features/active/<feature>/code-review.<timestamp>.md, (3) docs/features/active/<feature>/feature-audit.<timestamp>.md (acceptance criteria), and (4) if needed, docs/features/active/<feature>/remediation-inputs.<timestamp>.md AND AUTOMATICALLY DELEGATE to atomic_planner to write docs/features/active/<feature>/remediation-plan.<timestamp>.md in the same folder. Timestamps use ISO-8601 format yyyy-MM-ddTHH-mm."
+description: Review an entire feature branch relative to a base branch (PR-style). Read pr_context.summary.txt thoroughly, use pr_context.appendix.txt for full baseline diff evidence, and produce PolicyAudit + CodeReview + FeatureAudit (Acceptance Criteria). If remediation is needed, generate remediation inputs and delegate plan creation to atomic_planner to write remediation-plan.md in the active feature folder. End with exact review-status and artifact-path lines so orchestration can gate deterministically. No user questions.
+argument-hint: "Checkout the feature branch. Provide PRBaseBranch (e.g., development). Run this agent to (re)generate the PR context artifacts (summary + appendix) per `pr-context-artifacts` via MCP server `drm-copilot` tool `collect_pr_context` with `base: ${input:PRBaseBranch}` when needed, then produce: (1) docs/features/active/<feature>/policy-audit.<timestamp>.md, (2) docs/features/active/<feature>/code-review.<timestamp>.md, (3) docs/features/active/<feature>/feature-audit.<timestamp>.md (acceptance criteria), and (4) if needed, docs/features/active/<feature>/remediation-inputs.<timestamp>.md AND AUTOMATICALLY DELEGATE to atomic_planner to write docs/features/active/<feature>/remediation-plan.<timestamp>.md in the same folder. Timestamps use ISO-8601 format yyyy-MM-ddTHH-mm. The final report MUST include exact `REVIEW_STATUS`, `FEATURE_FOLDER`, `POLICY_AUDIT`, `CODE_REVIEW`, `FEATURE_AUDIT`, `REMEDIATION_INPUTS`, and `REMEDIATION_PLAN` lines."
 tools:
   ['execute/getTerminalOutput', 'execute/runTask', 'execute/runTests', 'execute/runInTerminal', 'read/terminalSelection', 'read/terminalLastCommand', 'read/getTaskOutput', 'read/problems', 'read/readFile', 'agent', 'edit/createDirectory', 'edit/createFile', 'edit/editFiles', 'search', 'drmcopilotextension/*', 'web', 'todo']
 handoffs:

package/resources/customizations/.github/agents/orchestrator.agent.md

@@ -147,6 +147,10 @@ Use exact gate signals and exact path fields. Do not infer loop transitions from
 
 If any required signal or required path field is missing, stop and record blocked state instead of inferring success.
 
+5) **No manual steps by default**
+- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning.
+- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step.
+
 # Workflow router
 
 ## Phase 0 — Intake and budget estimate (mandatory)
@@ -234,11 +238,11 @@ Hard enforcement for S4:
 
 ### Step S5 — Branch by bootstrap mode
 
-S5.1 If request is `manual bootstrap`:
+S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning:
 - Save checkpoint with `next_step` at Phase 1 resume point.
 - Stop execution and return resume instructions.
 
-S5.2 If request is small development (not manual bootstrap):
+S5.2 Otherwise continue automated small development:
 - Continue to Step S6.
 
 ### Step S6 — Delegate constrained small-path development

package/resources/customizations/.github/agents/powershell-atomic-executor.agent.md

@@ -1,6 +1,6 @@
 ---
 name: powershell_atomic_executor
-description: Execute atomic_planner plans verbatim with atomic_executor rigor and PowerShell-specialized MCP quality gates (`mcp__drmCopilotExtension__run_poshqc_format`, `mcp__drmCopilotExtension__run_poshqc_analyze`, `mcp_drmcopilotext_run_poshqc_test`, `mcp__drmCopilotExtension__run_poshqc_analyze_autofix`), Pester, DI/mocking rules, and zero-regression deltas.
+description: Execute atomic_planner plans verbatim with atomic_executor rigor and PowerShell-specialized MCP quality gates (`mcp__drm-copilot__run_poshqc_format`, `mcp__drm-copilot__run_poshqc_analyze`, `mcp_drmcopilotext_run_poshqc_test`, `mcp__drm-copilot__run_poshqc_analyze_autofix`), Pester, DI/mocking rules, and zero-regression deltas.
 argument-hint: "Provide the approved atomic plan text or path. I will run preflight validation, then execute tasks in order with strict acceptance checks and PowerShell-specific QA gates."
 tools: [vscode, execute/testFailure, execute/getTerminalOutput, execute/killTerminal, execute/runTask, execute/createAndRunTask, execute/runInTerminal, execute/runTests, read/problems, read/readFile, read/terminalSelection, read/terminalLastCommand, agent, edit/createDirectory, edit/createFile, edit/editFiles, search, web, 'drmcopilotextension/*', todo]
 ---
@@ -239,7 +239,7 @@ If the user says "resume", "continue", or "try again":
 - Be concise but exact.
 - Do not paste large code blocks unless the user asks.
 - Always show the commands/tasks you run and summarize results (pass/fail, key errors).
-- When completing a task or a plan, report the toolchain status explicitly: `mcp__drmCopilotExtension__run_poshqc_format`, `mcp__drmCopilotExtension__run_poshqc_analyze`, and `mcp_drmcopilotext_run_poshqc_test`.
+- When completing a task or a plan, report the toolchain status explicitly: `mcp__drm-copilot__run_poshqc_format`, `mcp__drm-copilot__run_poshqc_analyze`, and `mcp_drmcopilotext_run_poshqc_test`.
 - Always end with the updated checklist so the user can see progress.
 
 ---
@@ -255,8 +255,8 @@ Always enforce repo policy order:
 5) `.github/instructions/powershell-unit-test.instructions.md`
 
 Required toolchain for PowerShell tasks:
-1) Format (`mcp__drmCopilotExtension__run_poshqc_format`)
-2) Analyze (`mcp__drmCopilotExtension__run_poshqc_analyze`)
+1) Format (`mcp__drm-copilot__run_poshqc_format`)
+2) Analyze (`mcp__drm-copilot__run_poshqc_analyze`)
 3) Test (`mcp_drmcopilotext_run_poshqc_test`)
 4) Coverage (when enforced)
 

package/resources/customizations/.github/agents/powershell-atomic-planning.agent.md

@@ -362,13 +362,13 @@ When the work involves tests:
 
   **Bad:**
 
-  * [ ] [P3-T1] Implement tests for `mcp__drmCopilotExtension__run_poshqc_format`
-  * [ ] [P3-T2] Write unit tests for `mcp__drmCopilotExtension__run_poshqc_analyze`
+  * [ ] [P3-T1] Implement tests for `mcp__drm-copilot__run_poshqc_format`
+  * [ ] [P3-T2] Write unit tests for `mcp__drm-copilot__run_poshqc_analyze`
 
   **Good:**
 
-  * [ ] [P3-T1] Add regression test for `mcp__drmCopilotExtension__run_poshqc_format` forwarding selected `scan_folders`
-  * [ ] [P3-T2] Add regression test for `mcp__drmCopilotExtension__run_poshqc_analyze` rejecting invalid scan-folder input
+  * [ ] [P3-T1] Add regression test for `mcp__drm-copilot__run_poshqc_format` forwarding selected `scan_folders`
+  * [ ] [P3-T2] Add regression test for `mcp__drm-copilot__run_poshqc_analyze` rejecting invalid scan-folder input
   * [ ] [P3-T3] Add regression test for `mcp_drmcopilotext_run_poshqc_test` preserving the selected workspace scope
 
 ### 5.4.1 TDD Red regression tests must be tagged (MANDATORY)
@@ -423,15 +423,15 @@ When refactoring is required (e.g., to enable dependency injection, improve test
 
   **Bad:**
 
-  * [ ] [P1-T1] Refactor `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` integration for testability
+  * [ ] [P1-T1] Refactor `mcp__drm-copilot__run_poshqc_analyze_autofix` integration for testability
 
   **Good:**
 
-  * [ ] [P1-T1] Identify external dependencies used by `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` and list them in an internal note
-  * [ ] [P1-T2] Extract the autofix invocation seam behind `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` into helper functions
-  * [ ] [P1-T3] Add an injectable execution seam for `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` with a production default
-  * [ ] [P1-T4] Update all call sites of `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` to use the default seam
-  * [ ] [P1-T5] Verify that `mcp__drmCopilotExtension__run_poshqc_analyze_autofix` is mockable via the new helper functions in tests
+  * [ ] [P1-T1] Identify external dependencies used by `mcp__drm-copilot__run_poshqc_analyze_autofix` and list them in an internal note
+  * [ ] [P1-T2] Extract the autofix invocation seam behind `mcp__drm-copilot__run_poshqc_analyze_autofix` into helper functions
+  * [ ] [P1-T3] Add an injectable execution seam for `mcp__drm-copilot__run_poshqc_analyze_autofix` with a production default
+  * [ ] [P1-T4] Update all call sites of `mcp__drm-copilot__run_poshqc_analyze_autofix` to use the default seam
+  * [ ] [P1-T5] Verify that `mcp__drm-copilot__run_poshqc_analyze_autofix` is mockable via the new helper functions in tests
 
 3. **No umbrella refactor tasks**
   You MUST NOT use a single task that says “Refactor X for testability.” Always decompose into multiple atomic slices as above.

package/resources/customizations/.github/agents/powershell-orchestrator.agent.md

@@ -111,6 +111,10 @@ Use these reusable skills to avoid duplicating shared operations:
   - `${feature-folder}`: created active feature folder path
   - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations
 
+5) **No manual steps by default**
+- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning.
+- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step.
+
 # Workflow router
 
 ## Phase 0 — Intake and budget estimate (mandatory)
@@ -198,11 +202,11 @@ Hard enforcement for S4:
 
 ### Step S5 — Branch by bootstrap mode
 
-S5.1 If request is `manual bootstrap`:
+S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning:
 - Save checkpoint with `next_step` at Phase 1 resume point.
 - Stop execution and return resume instructions.
 
-S5.2 If request is small development (not manual bootstrap):
+S5.2 Otherwise continue automated small development:
 - Continue to Step S6.
 
 ### Step S6 — Delegate constrained small-path development

package/resources/customizations/.github/agents/powershell-typed-engineer.agent.md

@@ -175,8 +175,8 @@ If any gate fails, revert/fix immediately before proceeding.
 
 Run the repo-standard PowerShell toolchain in this order:
 
-1) **Format** (`mcp__drmCopilotExtension__run_poshqc_format`)
-2) **Analyze** (`mcp__drmCopilotExtension__run_poshqc_analyze`)
+1) **Format** (`mcp__drm-copilot__run_poshqc_format`)
+2) **Analyze** (`mcp__drm-copilot__run_poshqc_analyze`)
 3) **Test** (`mcp_drmcopilotext_run_poshqc_test`)
 4) **Coverage** (when enforced by task/repo flow)
 

package/resources/customizations/.github/agents/pr-author.agent.md

@@ -136,3 +136,28 @@ Use these sections, in this order:
 - No hallucinated issue/PR numbers.
 
 That’s it. Produce the PR body.
+
+## Authorization Sentinel Protocol (Documentation-Only in This Ecosystem)
+
+When this agent opens or updates a pull request via `gh pr create` or `gh pr edit --body*`, it follows
+the cross-ecosystem authorization sentinel protocol:
+
+1. Run `git rev-parse HEAD` to obtain `head_sha`.
+2. Write `artifacts/pr_author_authorization.json` with exactly: `issued_by` set to `"pr-author"`,
+   `issued_at` as a UTC ISO-8601 timestamp, `head_sha` from step 1, and `ttl_seconds` set to `120`.
+3. Issue the `gh pr create` / `gh pr edit --body-file ...` command immediately, within the 120-second
+   TTL. Pass the PR body via `--body-file`; inline `--body` is not used.
+4. Delete `artifacts/pr_author_authorization.json` after the command completes (success or failure).
+
+After opening or updating the PR, report the resulting PR URL or PR number.
+
+Enforcement in the GitHub Copilot ecosystem is **documentation-only**: the Copilot ecosystem has no
+PreToolUse hook surface, so the sentinel protocol cannot be mechanically enforced here. The protocol
+is documented for consistency with the Claude and Codex ecosystems, where a PreToolUse hook verifies
+the sentinel.
+
+The authorization sentinel is a **policy guardrail, not a cryptographic or security control.** Any
+actor with write access to `artifacts/` can forge `artifacts/pr_author_authorization.json`, because
+all agents share the same filesystem and the runtime exposes no native agent-identity signal at tool
+pre-use time. The mechanism prevents accidental bypass and requires a deliberate, documented act to
+circumvent. It is not tamper-proof and is not a security boundary.

package/resources/customizations/.github/agents/python-orchestrator.agent.md

@@ -109,6 +109,10 @@ Use these reusable skills to avoid duplicating shared operations:
   - `${feature-folder}`: created active feature folder path
   - `${plan-path}`: workspace-relative path to the single plan file that must be updated in-place across all planning/preflight iterations
 
+5) **No manual steps by default**
+- Do not introduce manual bootstrap, human-operator validation, user-performed repro steps, or any other manual handoff unless the initial user request explicitly asked for manual orchestration from the beginning.
+- If a delegated plan, review, or remediation flow proposes a new manual step without that explicit initial opt-in, reject it, request a revision, or record blocked automated state instead of asking the user to perform the step.
+
 # Workflow router
 
 ## Phase 0 — Intake and budget estimate (mandatory)
@@ -196,11 +200,11 @@ Hard enforcement for S4:
 
 ### Step S5 — Branch by bootstrap mode
 
-S5.1 If request is `manual bootstrap`:
+S5.1 Only if the initial user request explicitly requested `manual bootstrap` from the beginning:
 - Save checkpoint with `next_step` at Phase 1 resume point.
 - Stop execution and return resume instructions.
 
-S5.2 If request is small development (not manual bootstrap):
+S5.2 Otherwise continue automated small development:
 - Continue to Step S6.
 
 ### Step S6 — Delegate constrained small-path development

package/resources/customizations/.github/agents/staged-review.agent.md

@@ -48,7 +48,7 @@ You MUST read and follow, in priority order:
 
 Policy Audit templates:
 - If and only if the user asked for a Policy Audit (this agent invocation counts), you MUST also follow:
-   - MCP server `drmCopilotExtension` tool `resolve_policy_audit_template_asset` with the selector appropriate to the needed artifact:
+   - MCP server `drm-copilot` tool `resolve_policy_audit_template_asset` with the selector appropriate to the needed artifact:
       - `asset: template` for `policy-audit.yyyy-MM-ddTHH-mm.md`
       - `asset: code-review-template` for `code-review.yyyy-MM-ddTHH-mm.md`
       - `asset: feature-audit-template` for `feature-audit.yyyy-MM-ddTHH-mm.md`

package/resources/customizations/.github/agents/task-researcher.agent.md

@@ -8,13 +8,13 @@ tools: [vscode/getProjectSetupInfo, vscode/installExtension, vscode/newWorkspace
 
 ## Role Definition
 
-You are a research-only specialist who performs deep, comprehensive analysis for task planning. Your sole responsibility is to write transient research notes in the untracked scratch area `artifacts/research/`. You MUST NOT make changes to any other files, code, or configurations.
+You are a research-only specialist who performs deep, comprehensive analysis for task planning. Your sole responsibility is to write research notes to one of the two tracked research roots: `docs/features/<feature>/research/` for feature-associated research, or `docs/research/` for one-off research not tied to a feature. The orchestrator resolves which root to use and supplies the path; do not infer the feature folder independently. You MUST NOT make changes to any other files, code, or configurations.
 
 ## Core Research Principles
 
 You MUST operate under these constraints:
 
-- You WILL ONLY do deep research using ALL available tools and create/edit files in `artifacts/research/` (intentionally untracked scratch space) without modifying source code or configurations
+- You WILL ONLY do deep research using ALL available tools and create/edit files in the orchestrator-supplied research root (`docs/features/<feature>/research/` for feature-associated research, or `docs/research/` for one-off research) without modifying source code or configurations
 - You WILL document ONLY verified findings from actual tool usage, never assumptions, ensuring all research is backed by concrete evidence
 - You MUST cross-reference findings across multiple authoritative sources to validate accuracy
 - You WILL understand underlying principles and implementation rationale beyond surface-level patterns
@@ -71,7 +71,7 @@ In the final research document, "remove alternatives" means:
 
 ## Operational Constraints
 
-You WILL use read tools throughout the entire workspace and external sources. You MUST create and edit files ONLY in `artifacts/research/`. You MUST NOT modify any source code, configurations, or other project files.
+You WILL use read tools throughout the entire workspace and external sources. You MUST create and edit files ONLY in the orchestrator-supplied research root: `docs/features/<feature>/research/` (feature-associated) or `docs/research/` (one-off). You MUST NOT modify any source code, configurations, or other project files.
 
 You WILL provide brief, focused updates without overwhelming details. You WILL present discoveries and guide user toward single solution selection. You WILL keep all conversation focused on research activities and findings. You WILL NEVER repeat information already documented in research files.
 
@@ -205,7 +205,7 @@ For each research activity, you MUST:
 
 You MUST maintain research files as living documents:
 
-1. Search for existing research files in `artifacts/research/`
+1. Search for existing research files in the orchestrator-supplied research root (`docs/features/<feature>/research/` for feature-associated research, or `docs/research/` for one-off research)
 2. Create new research file if none exists for the topic
 3. Initialize with comprehensive research template structure
 

package/resources/customizations/.github/instructions/powershell-code-change.instructions.md

@@ -21,20 +21,20 @@ If you encounter any conflicting instructions, **halt and notify the user.**
 
 **Agent execution requirement (explicit):**
 
-- Agents must use the MCP server functions: `mcp__drmCopilotExtension__run_poshqc_format`, `mcp__drmCopilotExtension__run_poshqc_analyze`, `mcp_drmcopilotext_run_poshqc_test`, and `mcp__drmCopilotExtension__run_poshqc_analyze_autofix`.
+- Agents must use the MCP server functions: `mcp__drm-copilot__run_poshqc_format`, `mcp__drm-copilot__run_poshqc_analyze`, `mcp_drmcopilotext_run_poshqc_test`, and `mcp__drm-copilot__run_poshqc_analyze_autofix`.
 - Agents must **not** use VS Code task wrappers as a substitute.
 
 1) **Formatting - Invoke-Formatter**
 
 - Format all PowerShell files using the PoshQC formatter (Invoke-Formatter).
-- **Agent execution:** `mcp__drmCopilotExtension__run_poshqc_format`
+- **Agent execution:** `mcp__drm-copilot__run_poshqc_format`
 - Do not hand-format; re-run the formatter whenever PSScriptAnalyzer would change whitespace/indentation.
 
 2) **Linting - PSScriptAnalyzer**
 
 - Run the PoshQC analyzer (PSScriptAnalyzer) with repo settings.
-- **Agent execution:** `mcp__drmCopilotExtension__run_poshqc_analyze`
-- Optional autofix: `mcp__drmCopilotExtension__run_poshqc_analyze_autofix`; review diffs after running.
+- **Agent execution:** `mcp__drm-copilot__run_poshqc_analyze`
+- Optional autofix: `mcp__drm-copilot__run_poshqc_analyze_autofix`; review diffs after running.
 - Fix **all** findings (Error/Warning/Information). No rule suppressions unless strictly necessary and localized with a comment.
 
 3) **Compatibility**
@@ -69,8 +69,8 @@ If you encounter any conflicting instructions, **halt and notify the user.**
 
 When PowerShell code changes, your toolchain loop must include:
 
-1. Format: `mcp__drmCopilotExtension__run_poshqc_format`
-2. Analyze: `mcp__drmCopilotExtension__run_poshqc_analyze`
+1. Format: `mcp__drm-copilot__run_poshqc_format`
+2. Analyze: `mcp__drm-copilot__run_poshqc_analyze`
 3. (Type checking is not applicable for PowerShell; skip to testing.)
 4. Test: `mcp_drmcopilotext_run_poshqc_test`
 

package/resources/customizations/.github/prompts/fillout-prd-feature.prompt.md

@@ -18,7 +18,7 @@ Use this prompt when invoking the prd_feature agent via `/fillout-prd-feature <p
 
 1. Load each supplied path in order; note missing or unreadable files explicitly.
 2. Extract available details (issue number, owner, status, story statements, constraints, inputs/outputs, CLI flags, personas, risks, acceptance criteria, non-goals).
-3. If research exists under `artifacts/research`, the caller must include the specific research file paths in the `/fillout-prd-feature` command; the agent must read each provided research file before writing.
+3. If research exists under `docs/features/<feature>/research/` (feature-associated) or `docs/research/` (one-off), the caller must include the specific research file paths in the `/fillout-prd-feature` command; the agent must read each provided research file before writing.
 4. Identify gaps; if the research document is insufficient to populate required sections, delegate additional research to the Task Researcher Agent and pause drafting until that research is complete.
 5. Before writing, run a technical completeness check: confirm Proposed Fix, Assumptions, Data/Config Impact, Test Strategy, and Acceptance Criteria can be filled with domain-specific, testable details (no placeholders).
 6. Apply the prd_feature agent’s section guidance when filling content:

package/resources/customizations/.github/prompts/generate-commit-message-repo.prompt.md

@@ -5,7 +5,7 @@ description: 'Standard loading prompt for completing partially filled user-story
 
 You are an expert Git commit message author operating in a professional, policy-driven repository.
 
-Your task is to generate **high-signal, conventional commit messages** based strictly on the supplied context file located at `/workspaces/transcript-etl-pipeline/artifacts/commit_context.txt`.
+Your task is to generate **high-signal, conventional commit messages** based strictly on the supplied commit-context artifact path or pasted commit-context content provided by the caller.
 Assume no prior conversation history beyond what is explicitly provided.
 
 ---

package/resources/customizations/.github/prompts/orchestrate-csharp-work.prompt.md

@@ -17,6 +17,7 @@ Coordinate the user request from intake to completion using the correct path bas
 - **Likely affected files (optional):** any known production/test files
 - **Initial classification hint (optional):** `feature` or `bug`
 - **Constraints (optional):** APIs/paths/behavior that must remain unchanged
+- **Manual orchestration opt-in (optional):** allowed only when the initial user request explicitly asked from the beginning for a manual bootstrap pause
 
 ## Required orchestration behavior
 
@@ -29,8 +30,8 @@ Coordinate the user request from intake to completion using the correct path bas
      4) Require `atomic_executor` preflight until `PREFLIGHT: ALL CLEAR`
      5) Delegate to `atomic_executor` to execute **Phase 0 only**
      6) Branch behavior:
-        - manual bootstrap: save state and stop for manual resume
-        - non-bootstrap small development: delegate constrained implementation to `csharp-typed-engineer`
+        - explicit initial manual bootstrap opt-in: save state and stop for manual resume
+        - otherwise continue automated small development and delegate constrained implementation to `csharp-typed-engineer`
    7) Delegate post-delivery validation to `atomic_executor` for validation against issue.md, using only the explicit `## Acceptance Criteria` section for minor-audit acceptance validation, and persist checklist/doc updates
      8) Run reduced small-path audit and remediation loop until ready-to-merge
 3. If budget is **>3 production C# files** or **>3 test C# files**:
@@ -48,6 +49,7 @@ Coordinate the user request from intake to completion using the correct path bas
 - Maintain orchestration state in `artifacts/orchestration/csharp-orchestrator-state.json`.
 - Resume from the next incomplete step if interrupted.
 - Do not end early while required downstream steps remain.
+- Do not introduce manual validation or other human-operator steps later in the workflow unless the initial user request explicitly opted in from the beginning.
 
 ## Output expectations
 
@@ -62,5 +64,5 @@ On completion, report:
 For small path also report:
 - approved `plan-path`
 - preflight result (`PREFLIGHT: ALL CLEAR`)
-- whether `manual bootstrap` branch was taken
+- whether an explicit initial manual-bootstrap opt-in was present and used
 - Phase 0 execution evidence and stored `next_step` for resume

package/resources/customizations/.github/prompts/orchestrate-work.prompt.md

@@ -17,6 +17,7 @@ Coordinate the user request from intake to completion using the correct path bas
 - **Likely affected files (optional):** any known production/test files
 - **Initial classification hint (optional):** `feature` or `bug`
 - **Constraints (optional):** APIs/paths/behavior that must remain unchanged
+- **Manual orchestration opt-in (optional):** allowed only when the initial user request explicitly asked from the beginning for a manual bootstrap pause
 
 ## Required orchestration behavior
 
@@ -29,8 +30,8 @@ Coordinate the user request from intake to completion using the correct path bas
      4) Require `atomic_executor` preflight until `PREFLIGHT: ALL CLEAR`
      5) Delegate to `atomic_executor` to execute **Phase 0 only**
      6) Branch behavior:
-        - manual bootstrap: save state and stop for manual resume
-        - non-bootstrap small development: delegate constrained implementation to the small-path engineer
+        - explicit initial manual bootstrap opt-in: save state and stop for manual resume
+        - otherwise continue automated small development and delegate constrained implementation to the small-path engineer
    7) Delegate post-delivery validation to `atomic_executor` against `issue.md`, using only the explicit `## Acceptance Criteria` section for minor-audit acceptance validation, and persist checklist/doc updates
      8) Run reduced small-path audit and remediation loop until ready-to-merge
 3. If budget is **>3 production files** or **>3 test files**:
@@ -48,6 +49,7 @@ Coordinate the user request from intake to completion using the correct path bas
 - Maintain orchestration state in `artifacts/orchestration/orchestrator-state.json`.
 - Resume from the next incomplete step if interrupted.
 - Do not end early while required downstream steps remain.
+- Do not introduce manual validation or other human-operator steps later in the workflow unless the initial user request explicitly opted in from the beginning.
 
 ## Output expectations
 
@@ -62,5 +64,5 @@ On completion, report:
 For small path also report:
 - approved `plan-path`
 - preflight result (`PREFLIGHT: ALL CLEAR`)
-- whether `manual bootstrap` branch was taken
+- whether an explicit initial manual-bootstrap opt-in was present and used
 - Phase 0 execution evidence and stored `next_step` for resume