@danmoisan/drm-copilot-mcp 1.1.16 → 1.1.17

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

@@ -277,6 +277,8 @@ Negative obligations on the prompt:
 Excluded from the prompt as parent-side concerns: the item's declared blast radius,
 `max_concurrency`, and `mode`. Keeping the prompt minimal preserves the child contract unchanged.
 
+The run gates `enforce-orchestration-preimplementation-gate.ps1`, `enforce-parallel-cohort-barrier.ps1`, and `enforce-parallel-drift-gate.ps1` locate the parallel checkpoint by the `parallel_slug:` value of the marker line. They select the single live worktree whose `artifacts/orchestration/parallel-orchestrator-state.json` records `route_id` `parallel` and that slug, and deny the delegation with `TARGET_WORKTREE_NOT_DERIVABLE` or `TARGET_WORKTREE_AMBIGUOUS` when none or more than one matches. The child run's own delegations to implementation agents carry the canonical issue-number line and `branch:` label defined in `.claude/skills/orchestrate/SKILL.md` `## Issue Number Consistency`.
+
 ## Model Selection
 
 When `parallel-orchestrator` delegates an item to `Agent(orchestrator)`, the prompt appends the
@@ -729,8 +731,8 @@ a detached item.
 ### Abandon confirmation-marker contract
 
 The `abandon` disposition is destructive: it closes the item's pull request and removes its
-worktree. Both side effects run through ONE deterministic CLI invocation of
-`scripts/dev_tools/parallel_mutation_abandon_cli.py`, documented in full in
+worktree. Both side effects run through ONE deterministic invocation of the bundled bash entry
+point `.claude/lib/bash/abandon-parallel-item.sh`, documented in full in
 `.claude/skills/parallel-remove/SKILL.md`. Executing the abandon disposition through ad hoc `gh` or
 `git` commands is prohibited, because an ad hoc command is not matchable and would bypass the
 confirmation contract.
@@ -875,25 +877,35 @@ carries no such marker, evaluates no drift, and is unaffected.
 
 #### CLI Invocation
 
-Detection logic is pure and lives in `scripts/dev_tools/parallel_drift_detection.py` (escape
-detection, `drift_events[]` construction, the derived quiesce predicate, and conflict recomputation)
-and `scripts/dev_tools/parallel_drift_halt.py` (halt selection and the requeue seam). All I/O is
-confined to the thin wrapper `scripts/dev_tools/parallel_drift_detection_cli.py`, invoked as:
+Detection logic is pure and lives in `.claude/lib/parallel-drift/ParallelDrift.psm1` (escape
+detection, `drift_events[]` construction, and conflict recomputation) and
+`.claude/lib/parallel-drift/ParallelDriftHalt.psm1` (halt selection). The first calls the bundled
+blast-radius library under `.claude/lib/blast-radius/` rather than re-deriving it. All I/O is confined
+to the destination-runtime entry point `.claude/lib/parallel-drift/Invoke-ParallelDriftDetection.ps1`,
+which needs PowerShell 7 and no Python interpreter, invoked as:
 
 ```
-poetry run python -m scripts.dev_tools.parallel_drift_detection_cli \
-  --item-key <issue_num> \
-  [--checkpoint artifacts/orchestration/parallel-orchestrator-state.json] \
-  [--config config/blast-radius.json] \
-  [--at <yyyy-MM-ddTHH-mm>] [--computed-at <yyyy-MM-ddTHH-mm>] \
+pwsh -NoProfile -NonInteractive -File .claude/lib/parallel-drift/Invoke-ParallelDriftDetection.ps1 \
+  -ItemKey <issue_num> \
+  [-CheckpointPath artifacts/orchestration/parallel-orchestrator-state.json] \
+  [-ConfigPath config/blast-radius.json] \
+  [-At <yyyy-MM-ddTHH-mm>] [-ComputedAt <yyyy-MM-ddTHH-mm>] \
   <CHANGED_PATH>...
 ```
 
-Argument surface: `--item-key` is the only required argument and is the item's `issue_num`;
-`--checkpoint` and `--config` default to the two paths shown; `--at` is the timestamp recorded on
-the `drift_events[]` entry and `--computed-at` the timestamp recorded on the observed radius, each
-defaulting at the I/O boundary so the pure functions never read a clock; and the changed paths are
-positional and variadic. An empty changed-path list is legal and yields `no_escape`.
+The Python modules `scripts/dev_tools/parallel_drift_detection.py` and
+`scripts/dev_tools/parallel_drift_halt.py`, with their thin wrapper
+`scripts/dev_tools/parallel_drift_detection_cli.py`, remain the repository authority and the parity
+reference; the shared corpus under `tests/fixtures/parallel_drift/` binds the two, and the Python
+modules are not invoked on the destination-runtime path.
+
+Argument surface: `-ItemKey` is the only required argument and is the item's `issue_num`;
+`-CheckpointPath` and `-ConfigPath` default to the two paths shown and resolve against the caller's
+working directory; `-At` is the timestamp recorded on the `drift_events[]` entry and `-ComputedAt` the
+timestamp recorded on the observed radius, each defaulting at the I/O boundary so the pure functions
+never read a clock; and the changed paths are positional and variadic. No parameter is mandatory, so
+a missing `-ItemKey` exits `2` instead of prompting. An empty changed-path list is legal and yields
+`no_escape`.
 
 The changed-path list is an argument, not something the module derives: the caller produces it with
 `git diff --name-only <merge-base(origin/main, HEAD)> HEAD` at the child's pre-review commit, and
@@ -930,7 +942,8 @@ escaped paths is not a drift event. `observed_radius` is the serialized observed
 parent writes back in step 7 of `#### Seven-Step Procedure`: it carries the six invariant-9 keys with
 `source: observed`, is built by F1's library rather than by hand, and is `null` exactly when `result`
 is `no_escape`, on the same precondition as `drift_event`. Exit status is `0` on success, `1` on
-missing or malformed input, and argparse's `2` on a usage error.
+missing or malformed input (one stderr line prefixed "parallel drift detection failed: "), and `2`
+on a usage error, such as a missing or non-integer `-ItemKey` or an unrecognized parameter.
 
 #### Synthetic Blocking Finding
 
@@ -958,7 +971,8 @@ on its own R1 through R5 loop for the drift finding, so halting it would deadloc
 that resolves the drift.
 
 The exclusion is applied **at the call site, before the later-started comparator runs**:
-`halted_item_keys` in `scripts/dev_tools/parallel_drift_detection_cli.py` drops the drifting key from
+`Get-ParallelDriftHaltedItemKey` in `.claude/lib/parallel-drift/ParallelDriftHalt.psm1` (the port of
+`halted_item_keys` in `scripts/dev_tools/parallel_drift_detection_cli.py`) drops the drifting key from
 each pair's candidate list, then halts the single remaining candidate, or applies the comparator when
 two remain. Because a recomputed pair holds two distinct canonical keys, the candidate list is always
 one or two entries and can never be empty. It remains true, and remains a real structural guarantee,

package/resources/claude-customizations/.claude/skills/parallel-remove/SKILL.md

@@ -108,8 +108,8 @@ Do not record a partial removal, and do not record the rejection itself in `muta
    removing the worktree — through the single deterministic CLI invocation below and through nothing
    else:
 
-   ```bash
-   poetry run python scripts/dev_tools/parallel_mutation_abandon_cli.py --item <key> --disposition abandon --confirm-abandon --pr <pr-number> --worktree <worktree-path>
+   ```shell
+   bash .claude/lib/bash/abandon-parallel-item.sh --item <key> --disposition abandon --confirm-abandon --pr <pr-number> --worktree <worktree-path>
    ```
 
    Executing the abandon disposition through ad hoc `gh pr close` or `git worktree remove` commands
@@ -146,14 +146,14 @@ The abandon path is guarded by the PreToolUse hook
 - A command carrying both tokens is allowed.
 - A command carrying neither is out of scope and is allowed unchanged.
 
-The two token values are declared once each in
-`scripts/dev_tools/parallel_mutation_abandon_cli.py` (the producer) and once each in the hook (the
-consumer), and the seam test
-`tests/scripts/dev_tools/test_parallel_abandon_token_seam.py` parses all three artifacts — the CLI,
-the hook, and the invocation line in step 5 above — at run time to prove they still agree. Renaming
-a token in one artifact without the identical rename in the other two fails that test. The
-invocation in step 5 is the file's only executable abandon command line, and the seam test parses
-that one line; do not add a second one.
+The two token values are declared once each in `.claude/lib/bash/abandon-parallel-item.sh` (the
+pushed-down producer), once each in `scripts/dev_tools/parallel_mutation_abandon_cli.py` (the retained
+Python parity reference), and once each in the hook (the consumer). The seam test
+`tests/scripts/dev_tools/test_parallel_abandon_token_seam.py` parses all four artifacts — the bundled
+entry point, the Python reference, the hook, and the invocation line in step 5 above — at run time
+to prove they still agree. Renaming a token in one artifact without the identical rename in the
+others fails that test. The invocation in step 5 is the file's only executable abandon command
+line, and the seam test parses that one line; do not add a second one.
 
 When the gate denies a command, the correct response is to add the confirmation marker
 deliberately, not to reformulate the command to evade the match. Reformulating to evade the gate

package/resources/claude-customizations/.claude/skills/python-change-budget-router/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: python-change-budget-router
-description: Budget-first routing and batch-scope contract for Python work. Estimate production-file scope, choose small vs large path, enforce the 3 production + 3 test per-batch cap, and halt the agent for scope expansion approval when the estimate exceeds the budget.
+description: Budget-first routing contract for Python work. Estimate production-file scope, choose small vs large path, and route direct-mode work of more than 3 production files to the orchestrated large path.
 ---
 
 # Python Change Budget Router
 
-Canonical guidance for deciding whether Python work stays on the small path (`python-typed-engineer` direct mode) or escalates to the full orchestration workflow, and for enforcing per-batch change budgets during execution.
+Canonical guidance for deciding whether Python work stays on the small path (`python-typed-engineer` direct mode) or escalates to the orchestrated large path through `/orchestrate` (the `orchestrator` agent).
 
 ## When to Use This Skill
 
@@ -14,50 +14,27 @@ Use this skill when:
 - Intake starts from a natural-language Python request.
 - An agent must decide the execution path before planning or implementation.
 - A direct-mode route must reject over-budget requests and switch to orchestrated flow.
-- An executor must confirm a batch fits within the 3 production + 3 test file cap before editing.
 
 ## Canonical Routing Rules
 
 1. Estimate rough change budget first based on likely **production Python files** touched.
 2. Route:
    - `1-3` production files (plus corresponding tests) → **small path** (`python-typed-engineer` direct mode).
-   - `>3` production files → **large path** (orchestration workflow with promotion, research, spec, planning, execution, and review).
-
-## Per-Batch Change Budget (Hard Gate)
-
-During Phase C execution:
-
-- A single batch may change at most **3 production files** and **3 test files**.
-- The default cap applies unless the user supplies an override of the form `budget: prod=<N>, test=<M>` in the initiating prompt.
-- A user override may be honored only if it complies with repo policy and approved scope. If the requested scope exceeds 3 production files overall, stop before execution and seek explicit approval.
-- If an override is requested, confirm compliance with repo policy before entering Phase C.
-
-## Scope Expansion Protocol
-
-When in-scope work is required beyond 3 production files, stop and return:
-
-- a one-paragraph justification for the additional files,
-- the exact additional file paths,
-- the smallest alternative that avoids expanding scope,
-
-and wait for explicit user approval before proceeding.
-
-Allowed minimal-seam exceptions (still within the 3-file cap) are:
-
-- introducing a minimal seam for testability (I/O boundary isolation, dependency injection),
-- typing changes required for Pyright cleanliness in the slice,
-- updating the smallest set of call sites needed to preserve a stable public API.
+   - More than 3 production files → **large path** (`/orchestrate`, the `orchestrator` agent). The large path has no production-file cap.
+3. Test files are not counted toward the routing threshold.
 
 ## Direct-Mode Rejection Rule
 
-If `python-typed-engineer` is invoked directly and estimated scope is `>3` production files:
+If `python-typed-engineer` is invoked directly and the estimated scope, or the scope discovered during implementation, is more than 3 production files:
 
-- Stop before implementation.
-- Return an explicit routing instruction to invoke the orchestrated workflow.
+- Stop before editing the 4th production file.
+- Report the production files already changed and the production files still required.
+- Return an explicit routing instruction to invoke `/orchestrate`.
+- Do not request an exception to the threshold; routing is the only path past it.
 
 ## Orchestrated Small-Path Requirements
 
-When routed through the orchestrator, the small path still requires lifecycle scaffolding before implementation:
+When routed through `/orchestrate`, the small path still requires lifecycle scaffolding before implementation:
 
 - invoke promotion and folder lifecycle steps through `vscode/runCommand` and extension access per `feature-promotion-lifecycle` when available. Use script or CLI fallback only when direct extension command execution is unavailable.
 - promote the potential item to a GitHub issue with `--work-mode minor-audit`,
@@ -75,5 +52,4 @@ Record in the agent response or logs:
 
 - estimated production file count,
 - chosen path (`small` or `large`),
-- rationale summary (1-3 bullets),
-- any requested budget override and its approval state.
+- rationale summary (1-3 bullets).

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

@@ -22,14 +22,17 @@
     ".claude/agents/staged-review.md",
     ".claude/agents/status-updater.md",
     ".claude/agents/task-researcher.md",
+    ".claude/hooks/enforce-batch-budget-route.ps1",
     ".claude/hooks/enforce-checkpoint-monotonic.ps1",
     ".claude/hooks/enforce-completion-consistency.ps1",
     ".claude/hooks/enforce-discovery-artifact-gate.ps1",
     ".claude/hooks/enforce-epic-invocation-origin.ps1",
     ".claude/hooks/enforce-epic-merge-gate.ps1",
     ".claude/hooks/enforce-epic-merge-gate-authorization.ps1",
+    ".claude/hooks/enforce-epic-merge-gate-resolution.ps1",
     ".claude/hooks/enforce-epic-wave-barrier.ps1",
     ".claude/hooks/enforce-epic-worktree-removal-gate.ps1",
+    ".claude/hooks/enforce-epic-worktree-removal-gate-resolution.ps1",
     ".claude/hooks/enforce-evidence-locations.ps1",
     ".claude/hooks/enforce-feature-folder-order.ps1",
     ".claude/hooks/enforce-model-routing-receipt.ps1",
@@ -158,8 +161,12 @@
     ".claude/lib/project-file-merge/ProjectFileMerge.psm1",
     ".claude/lib/project-file-merge/Resolve-MergeableConflict.ps1",
     ".claude/lib/ci-gate/Invoke-CiGateParser.ps1",
+    ".claude/lib/parallel-drift/ParallelDriftHalt.psm1",
+    ".claude/lib/parallel-drift/ParallelDrift.psm1",
+    ".claude/lib/parallel-drift/Invoke-ParallelDriftDetection.ps1",
     ".claude/rules/parallel-orchestration.md",
     ".claude/rules/shell.md",
+    ".claude/lib/bash/abandon-parallel-item.sh",
     ".claude/lib/bash/compute-cohorts.sh",
     ".claude/lib/bash/compute-concurrency-batches.sh",
     ".claude/lib/bash/parallel-cohorts.sh",
@@ -185,6 +192,7 @@
     ".claude/lib/worktree-resolution/WorktreeItemResolution.psm1",
     ".claude/lib/worktree-resolution/EpicScopeResolution.psm1",
     ".claude/lib/worktree-resolution/EpicScopeReadiness.psm1",
+    ".claude/lib/worktree-resolution/WorktreeRunResolution.psm1",
     ".claude/skills/mermaid-diagram/references/flowchart.md",
     ".claude/skills/mermaid-diagram/references/sequence.md",
     ".claude/skills/mermaid-diagram/references/class.md",

package/resources/claude-customizations/pack-manifests/powershell.json

@@ -6,7 +6,6 @@
     ".claude/agents/powershell-typed-engineer.md",
     ".claude/hooks/check-powershell-test-purity.ps1",
     ".claude/hooks/enforce-powershell-batch-budget.ps1",
-    ".claude/hooks/enforce-powershell-batch-budget-route.ps1",
     ".claude/skills/invoke-powershell-engineer/SKILL.md",
     ".claude/skills/powershell-change-budget-router/SKILL.md",
     ".claude/skills/powershell-orchestration-state-machine/SKILL.md",

package/resources/codex-and-agents-customizations/.agents/skills/invoke-powershell-engineer/SKILL.md

@@ -23,7 +23,6 @@ If the estimated scope exceeds the direct-mode budget, this skill defers to the
 - Files or entrypoints in scope (exact script or module paths and corresponding `*.Tests.ps1` paths).
 - Constraints, including public function or module contracts that must be preserved.
 - Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.
-- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.
 
 ## Output Paths
 

package/resources/codex-and-agents-customizations/.agents/skills/invoke-python-engineer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: invoke-python-engineer
-description: Invoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black, Ruff, Pyright, and Pytest with a three-production plus three-test per-batch budget and zero-regression quality gates.
+description: Invoke the python-typed-engineer worker to design, implement, and verify Python changes within typed repository boundaries. Applies Black, Ruff, Pyright, and Pytest with a 1-3 production-file direct-mode budget, routing to the orchestrated large path above it, and zero-regression quality gates.
 ---
 
 # Implement Python Skill
@@ -15,7 +15,7 @@ Use this skill when:
 - Estimated scope fits the small path (1-3 production files plus corresponding tests).
 - The toolchain (Black, Ruff, Pyright, Pytest) can be run in the current environment, or the user has explicitly authorized an unverified plan-only response.
 
-If the estimated scope exceeds the small-path budget, this skill defers to the orchestrated flow via `python-change-budget-router` instead of proceeding directly.
+If the estimated scope is more than 3 production files, this skill defers to the orchestrated large path (`.codex/prompts/orchestrate-work.md`) via `python-change-budget-router` instead of proceeding directly. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 
 ## Inputs
 
@@ -23,7 +23,6 @@ If the estimated scope exceeds the small-path budget, this skill defers to the o
 - Files or entrypoints in scope.
 - Constraints, including public APIs that must be preserved.
 - Optional approved plan. If none is supplied, the worker delegates plan authoring to `atomic_planner` before any edits.
-- Optional budget override in the form `budget: prod=<N>, test=<M>` subject to repo policy compliance.
 
 ## Output Paths
 

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

@@ -1,11 +1,11 @@
 ---
 name: python-change-budget-router
-description: Budget-first routing and batch-scope contract for Python work. Estimate production-file scope, choose small vs large path, enforce the 3 production + 3 test per-batch cap, and halt the agent for scope expansion approval when the estimate exceeds the budget.
+description: Budget-first routing contract for Python work. Estimate production-file scope, choose small vs large path, and route direct-mode work of more than 3 production files to the orchestrated large path.
 ---
 
 # Python Change Budget Router
 
-Canonical guidance for deciding whether Python work stays on the small path (`python-typed-engineer` direct mode) or escalates to the full orchestration workflow, and for enforcing per-batch change budgets during execution.
+Canonical guidance for deciding whether Python work stays on the small path (`python-typed-engineer` direct mode) or escalates to the orchestrated large path through `.codex/prompts/orchestrate-work.md`.
 
 ## When to Use This Skill
 
@@ -14,46 +14,23 @@ Use this skill when:
 - Intake starts from a natural-language Python request.
 - An agent must decide the execution path before planning or implementation.
 - A direct-mode route must reject over-budget requests and switch to orchestrated flow.
-- An executor must confirm a batch fits within the 3 production + 3 test file cap before editing.
 
 ## Canonical Routing Rules
 
 1. Estimate rough change budget first based on likely **production Python files** touched.
 2. Route:
    - `1-3` production files (plus corresponding tests) → **small path** (`python-typed-engineer` direct mode).
-   - `>3` production files → **large path** (orchestration workflow with promotion, research, spec, planning, execution, and review).
-
-## Per-Batch Change Budget (Hard Gate)
-
-During Phase C execution:
-
-- A single batch may change at most **3 production files** and **3 test files**.
-- The default cap applies unless the user supplies an override of the form `budget: prod=<N>, test=<M>` in the initiating prompt.
-- A user override may be honored only if it complies with repo policy and approved scope. If the requested scope exceeds 3 production files overall, stop before execution and seek explicit approval.
-- If an override is requested, confirm compliance with repo policy before entering Phase C.
-
-## Scope Expansion Protocol
-
-When in-scope work is required beyond 3 production files, stop and return:
-
-- a one-paragraph justification for the additional files,
-- the exact additional file paths,
-- the smallest alternative that avoids expanding scope,
-
-and wait for explicit user approval before proceeding.
-
-Allowed minimal-seam exceptions (still within the 3-file cap) are:
-
-- introducing a minimal seam for testability (I/O boundary isolation, dependency injection),
-- typing changes required for Pyright cleanliness in the slice,
-- updating the smallest set of call sites needed to preserve a stable public API.
+   - More than 3 production files → **large path** (`.codex/prompts/orchestrate-work.md`). The large path has no production-file cap.
+3. Test files are not counted toward the routing threshold.
 
 ## Direct-Mode Rejection Rule
 
-If `python-typed-engineer` is invoked directly and estimated scope is `>3` production files:
+If `python-typed-engineer` is invoked directly and the estimated scope, or the scope discovered during implementation, is more than 3 production files:
 
-- Stop before implementation.
-- Return an explicit routing instruction to invoke the orchestrated workflow.
+- Stop before editing the 4th production file.
+- Report the production files already changed and the production files still required.
+- Return an explicit routing instruction to invoke `.codex/prompts/orchestrate-work.md`.
+- Do not request an exception to the threshold; routing is the only path past it.
 
 ## Orchestrated Small-Path Requirements
 
@@ -75,5 +52,4 @@ Record in the agent response or logs:
 
 - estimated production file count,
 - chosen path (`small` or `large`),
-- rationale summary (1-3 bullets),
-- any requested budget override and its approval state.
+- rationale summary (1-3 bullets).

package/resources/codex-and-agents-customizations/.codex/agents/python-orchestrator.toml

@@ -15,7 +15,7 @@ Use the following repo-local skills as the canonical workflow source:
 
 Primary role:
 - Route Python delivery work through the correct small or large orchestration path.
-- Estimate change budget from likely affected Python production files and tests before selecting a path.
+- Estimate change budget from likely affected Python production files before selecting a path; test files are not counted toward the routing threshold.
 - Coordinate planning, execution, validation, and review until the mission is complete.
 
 Required delegated specialists:
@@ -28,7 +28,7 @@ Required delegated specialists:
 
 Routing and lifecycle rules:
 - Small path is allowed only for `1-3` production Python files plus corresponding tests.
-- Large path is required for `>3` production Python files or `>3` test files.
+- Large path is required for more than 3 (`>3`) production Python files. The large path has no production-file cap.
 - Treat `spawn_agent` availability as the mechanical availability signal for required delegated specialists.
 - If any required delegated handoff cannot be started, resumed, or completed with a receipt, stop and report blocked state; do not perform that delegated step locally.
 - If the canonical checkpoint belongs to an unrelated in-progress mission, stop with `checkpoint_conflict`.

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer-c1.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer-c2.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer-c3-elevated.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer-c3.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer-c4.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

package/resources/codex-and-agents-customizations/.codex/agents/python-typed-engineer.toml

@@ -29,7 +29,7 @@ Migration contract:
 
 ---
 name: python-typed-engineer
-description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 3-production + 3-test per-batch budget, and zero-regression quality gates.
+description: Project-scoped worker that implements and verifies Python changes within typed repository boundaries. Applies the Black -> Ruff -> Pyright -> Pytest toolchain, the 1-3 production-file direct-mode budget with routing to the orchestrated large path above it, and zero-regression quality gates.
 tools:
   - Read
   - Write
@@ -65,7 +65,7 @@ Language standards and toolchain are defined in `.agents/skills/python/SKILL.md`
 Follow the phased workflow defined by the preloaded skills:
 
 1. **Policy compliance** — apply `policy-compliance-order` to load mandatory repo policies before any change.
-2. **Routing and scope** — apply `python-change-budget-router` to estimate scope, select small vs large path, and enforce the 3 production + 3 test per-batch cap.
+2. **Routing and scope** — apply `python-change-budget-router` to estimate scope and select direct mode (1-3 production files) or, for more than 3 production files, large-path escalation through `.codex/prompts/orchestrate-work.md`. The large path has no production-file cap, and test files are not counted toward the routing threshold.
 3. **Plan and baseline** — apply `atomic-plan-contract` for Phase 0 baseline capture and atomic plan structure. Delegate plan authoring to `atomic_planner` when no plan is supplied.
 4. **Implement in batches** — apply the approved plan. After each batch, run targeted Ruff and Pyright on touched files plus targeted Pytest, and confirm per-file coverage.
 5. **Final QA gate** — apply `python-qa-gate` to run the full toolchain, enforce zero-regression deltas against the baseline, and produce the required reporting block before declaring completion.
@@ -86,7 +86,7 @@ If the marker is missing or malformed, fail closed to `full-feature`.
 
 Stop implementation and return to the user when:
 
-- the scope estimate or an in-flight batch would exceed the 3-production-file cap,
+- the scope estimate exceeds 3 production files in direct mode,
 - a file is near or would exceed the 500-line limit,
 - any QA gate delta is non-zero after self-correction,
 - the toolchain cannot be executed in the current environment (mark the change **unverified**),

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

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