@danmoisan/drm-copilot-mcp 1.1.20 → 1.1.21

package/out/mcp-server.js

@@ -25001,39 +25001,39 @@ var LOGICAL_AGENT_ALIASES = {
 var BASE_PROFILES = {
   C1: {
     suffix: "c1",
-    model: "gpt-5.6-luna",
+    model: "gpt-6-luna",
     model_reasoning_effort: "low"
   },
   C2: {
     suffix: "c2",
-    model: "gpt-5.6-terra",
+    model: "gpt-6.1-sol",
     model_reasoning_effort: "medium"
   },
   C3: {
     suffix: "c3",
-    model: "gpt-5.6-terra",
+    model: "gpt-6.1-sol",
     model_reasoning_effort: "high"
   },
   C4: {
     suffix: "c4",
-    model: "gpt-5.6-sol",
+    model: "gpt-6-astra",
     model_reasoning_effort: "max"
   }
 };
 var C3_ELEVATED_PROFILE = {
   suffix: "c3-elevated",
-  model: "gpt-5.6-sol",
+  model: "gpt-6-astra",
   model_reasoning_effort: "high"
 };
 var FORCED_PERSONA_PROFILES = {
   "epic-planner": {
     suffix: "",
-    model: "gpt-5.6-sol",
+    model: "gpt-6-astra",
     model_reasoning_effort: "ultra"
   },
   "epic-orchestrator": {
     suffix: "",
-    model: "gpt-5.6-sol",
+    model: "gpt-6-astra",
     model_reasoning_effort: "ultra"
   }
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danmoisan/drm-copilot-mcp",
-  "version": "1.1.20",
+  "version": "1.1.21",
   "description": "Stdio MCP server exposing drm-copilot repo-automation tools.",
   "license": "MIT",
   "type": "commonjs",

package/resources/claude-customizations/.claude/lib/codex-routing/CodexDeployment.psm1

@@ -7,9 +7,9 @@
     `scripts/dev_tools/resolve_codex_deployment.py`. It resolves the exact Codex
     deployment agent, model, and reasoning effort for one delegation from the
     logical agent, the assessed complexity band, the execution context, and the
-    orchestration complexity ceiling. C3 defaults to Terra/high and elevates to
-    Sol/high only for an epic child or a C4 orchestration ceiling; the epic
-    planner and epic orchestrator personas are always forced to Sol/ultra. No
+    orchestration complexity ceiling. C3 defaults to Sol/high and elevates to
+    Astra/high only for an epic child or a C4 orchestration ceiling; the epic
+    planner and epic orchestrator personas are always forced to Astra/ultra. No
     model alias and no silent fallback is accepted.
 
     SINGLE-IMPLEMENTATION RULE. The orchestrator-state U6.X checks
@@ -81,20 +81,20 @@ $script:LOGICAL_AGENT_ALIASES = @{ 'feature-review' = 'feature-reviewer' }
 
 # The per-band deployment profiles (suffix, model, reasoning effort).
 $script:BASE_PROFILES = @{
-    C1 = @{ suffix = 'c1'; model = 'gpt-5.6-luna'; model_reasoning_effort = 'low' }
-    C2 = @{ suffix = 'c2'; model = 'gpt-5.6-terra'; model_reasoning_effort = 'medium' }
-    C3 = @{ suffix = 'c3'; model = 'gpt-5.6-terra'; model_reasoning_effort = 'high' }
-    C4 = @{ suffix = 'c4'; model = 'gpt-5.6-sol'; model_reasoning_effort = 'max' }
+    C1 = @{ suffix = 'c1'; model = 'gpt-6-luna'; model_reasoning_effort = 'low' }
+    C2 = @{ suffix = 'c2'; model = 'gpt-6.1-sol'; model_reasoning_effort = 'medium' }
+    C3 = @{ suffix = 'c3'; model = 'gpt-6.1-sol'; model_reasoning_effort = 'high' }
+    C4 = @{ suffix = 'c4'; model = 'gpt-6-astra'; model_reasoning_effort = 'max' }
 }
 
 # The profile a C3 delegation elevates to when the overlay applies.
-$script:C3_ELEVATED_PROFILE = @{ suffix = 'c3-elevated'; model = 'gpt-5.6-sol'; model_reasoning_effort = 'high' }
+$script:C3_ELEVATED_PROFILE = @{ suffix = 'c3-elevated'; model = 'gpt-6-astra'; model_reasoning_effort = 'high' }
 
 # The personas whose profile is forced regardless of band, context, or ceiling.
 # Their deployment agent is the logical agent itself (empty suffix).
 $script:FORCED_PERSONA_PROFILES = @{
-    'epic-planner'      = @{ suffix = ''; model = 'gpt-5.6-sol'; model_reasoning_effort = 'ultra' }
-    'epic-orchestrator' = @{ suffix = ''; model = 'gpt-5.6-sol'; model_reasoning_effort = 'ultra' }
+    'epic-planner'      = @{ suffix = ''; model = 'gpt-6-astra'; model_reasoning_effort = 'ultra' }
+    'epic-orchestrator' = @{ suffix = ''; model = 'gpt-6-astra'; model_reasoning_effort = 'ultra' }
 }
 
 

package/resources/claude-customizations/.claude/skills/execution-environment/SKILL.md

@@ -60,7 +60,7 @@ Two separate mechanisms restrict Bash command text. They are kept apart here bec
 - `.github/workflows/ci.yml` triggers on `push` to `main` and `development`, on `pull_request` to `main`, `development`, and `epic/**`, on `workflow_dispatch`, and on `merge_group` (`types: [checks_requested]`, added by issue #952), with no path filters. When the merge queue on `main` is enabled, every required check is produced by a `merge_group` run of `ci.yml` as well as by the pull-request run; `.github/workflows/README.md` (`## Triggers`) records the trigger set.
 - Jobs in `ci.yml` and their check names: `Change scope` (job `changes`, the change-scope decision below); `CI full run` (job `full-run-marker`, which runs only on a full run, marks that run as a valid base for later decisions, and is not a required check); `quality-checks7 / Code Quality & Tests (<python-version>)` on Python 3.10, 3.11, 3.12, and 3.13 (`_quality-checks.yml`: Black check, Ruff, Pyright, the Codex generator `--check`, the tier classification, Pytest with line and branch coverage, and the coverage-threshold check on the JSON report totals); `security-scan / Security Scanning` (its `safety check` step carries `continue-on-error: true` and does not fail the check); `docs-validation / Documentation Validation`; `build-check / Build Package`; `shell-coverage / Shell Coverage (Bats + kcov)`; `drm-copilot-extension-tests / drm-copilot Extension Tests (<os>)` on `ubuntu-latest` and `windows-latest`; `root-typescript-tests / Root TypeScript Tests (<os>)` on `ubuntu-latest` and `windows-latest`; `NPM Audit Gate / npm audit (<manifest>)` (the calling job carries the name `NPM Audit Gate`); and the `poshqc` group below.
 - PowerShell CI (`_poshqc.yml`): `poshqc / PowerShell QC static` (format and analyze on `windows-latest`); the shard matrix `poshqc / PowerShell QC shard 1`, `shard 2`, and `shard 3` (`Invoke-PoshQCTest -ShardIndex -ShardCount` over the scan folders of `config/poshqc-scan.json`, with coverage, on `windows-latest`); the aggregator `poshqc / PowerShell QC`, which requires the static and shard jobs to succeed, verifies shard completeness against a Pester discovery count, and merges shard coverage; and `poshqc / PowerShell hook suites (Linux)`, which runs only `tests/scripts/claude-hooks` and `tests/scripts/codex-hooks` on `ubuntu-latest` with coverage disabled. A new test file under a scanned folder is assigned to a shard automatically and is counted by the completeness check.
-- Change-scope decision (issue #962): the `Change scope` job runs `scripts/ci/Invoke-CiChangeScope.ps1` and publishes the job output `code`. The decision is `code=false` (docs-only) only on a `pull_request` event from this repository when every file changed since the newest successful `ci.yml` run on the pull-request branch whose `CI full run` job succeeded, and whose head commit is an ancestor of the current head, is on the allowlist `config/ci-docs-only-paths.json`. A path is allowlisted when it starts with `docs/features/active/`, `docs/features/completed/`, `docs/features/potential/`, or `docs/research/`, does not start with `docs/features/templates/` or `docs/features/potential/template.md`, and ends in `.md`, `.txt`, `.log`, `.json`, or `.xml`; the allowlist file itself is not allowlisted. Every other case is a full run (`code=true`): `push`, `merge_group`, and `workflow_dispatch` events, a fork pull request, unreadable run or job data, no earlier full green run, a missing or non-ancestor base, an empty diff, any path outside the allowlist, and any error. The decision step carries `continue-on-error: true` and the callers compare the output with `!= 'false'`, so a failed or missing decision also gives a full run.
+- Change-scope decision (issue #962): the `Change scope` job runs `scripts/ci/Invoke-CiChangeScope.ps1` and publishes the job output `code`. The decision is `code=false` (docs-only) only on a `pull_request` event from this repository, through one of two comparisons. Green-run base: every file changed since the newest successful `ci.yml` run on the pull-request branch whose `CI full run` job succeeded, and whose head commit is present and an ancestor of the current head, is on the allowlist `config/ci-docs-only-paths.json`; the reason is `DOCS_ONLY_SINCE_<green head sha>`. Merge-base fallback (issue #973): when the green-run step ends with no earlier full green run (`NO_FULL_GREEN_RUN`), a missing base (`BASE_NOT_PRESENT`), or a non-ancestor base (`BASE_NOT_ANCESTOR`), and the pull request's base ref is exactly `main`, the script computes `git merge-base` of the payload base SHA (`BASE_SHA`, from `github.event.pull_request.base.sha`; the base ref arrives as `BASE_REF`) and the head, lists the files changed since that merge base with the same diff arguments, and decides `DOCS_ONLY_SINCE_MERGE_BASE_<merge base sha>` when every changed file is allowlisted. Both comparisons run the diff with rename detection off, so both the old and the new path of a rename are classified. A path is allowlisted when it starts with `docs/features/active/`, `docs/features/archive/`, `docs/features/completed/`, `docs/features/epics/`, `docs/features/parallel/`, `docs/features/potential/`, or `docs/research/`, does not start with `docs/features/templates/` or `docs/features/potential/template.md`, and ends in `.md`, `.txt`, `.log`, `.json`, or `.xml`; the allowlist file itself is not allowlisted. Every other case is a full run (`code=true`): `push`, `merge_group`, and `workflow_dispatch` events, a fork pull request, unreadable run or job data, no earlier full green run or a missing or non-ancestor base when the base ref is not `main`, a merge base that cannot be resolved (`MERGE_BASE_UNRESOLVED`, for example a blank base SHA or a base commit missing from the checkout), a failed ancestry check, an empty diff, any path outside the allowlist, and any error. The decision step carries `continue-on-error: true` and the callers compare the output with `!= 'false'`, so a failed or missing decision also gives a full run.
 - Docs-only behavior (`code=false`): `ci.yml` passes `run-heavy: false` to `_quality-checks.yml`, `_security-scan.yml`, `_build-check.yml`, `_poshqc.yml`, `_shell-coverage.yml`, and `_drm-copilot-extension-tests.yml`. Each required job still starts under its full-run check name with every step skipped, so every required context reports `success` without running its suite. In `_poshqc.yml` the aggregator `poshqc / PowerShell QC` runs with every step gated, and `poshqc / PowerShell QC static`, the shard jobs, and `poshqc / PowerShell hook suites (Linux)` are skipped at job level. `docs-validation / Documentation Validation` runs in full. `root-typescript-tests`, `NPM Audit Gate`, and `CI full run` are skipped at job level. A `success` on a docs-only commit is therefore not evidence that the heavy suites pass for that commit; that evidence is the newest run whose `CI full run` job succeeded.
 - A commit that changes any path outside the allowlist (any code, workflow, configuration, script, test, or customization file) runs the full set of jobs, and its `CI full run` job marks it as a base for later docs-only decisions. A standalone `workflow_dispatch` of a reusable workflow, or a caller that omits `run-heavy`, also runs in full. `.github/workflows/README.md` (`## Change-Scope Decision (Issue #962)`) records the reason codes and the per-context behavior table.
 - Required contexts of ruleset 15241672, confirmed by the orchestrator through `gh api` on 2026-10-16: `drm-copilot-extension-tests / drm-copilot Extension Tests (ubuntu-latest)`, `drm-copilot-extension-tests / drm-copilot Extension Tests (windows-latest)`, `docs-validation / Documentation Validation`, `poshqc / PowerShell QC`, `shell-coverage / Shell Coverage (Bats + kcov)`, `security-scan / Security Scanning`, `quality-checks7 / Code Quality & Tests (3.10)`, `quality-checks7 / Code Quality & Tests (3.11)`, `quality-checks7 / Code Quality & Tests (3.12)`, `quality-checks7 / Code Quality & Tests (3.13)`, `build-check / Build Package`.

package/resources/claude-customizations/config/orchestration-routing.json

@@ -289,28 +289,28 @@
     "complexity_to_profile": {
       "C1": {
         "suffix": "c1",
-        "model": "gpt-5.6-luna",
+        "model": "gpt-6-luna",
         "model_reasoning_effort": "low"
       },
       "C2": {
         "suffix": "c2",
-        "model": "gpt-5.6-terra",
+        "model": "gpt-6.1-sol",
         "model_reasoning_effort": "medium"
       },
       "C3": {
         "suffix": "c3",
-        "model": "gpt-5.6-terra",
+        "model": "gpt-6.1-sol",
         "model_reasoning_effort": "high"
       },
       "C4": {
         "suffix": "c4",
-        "model": "gpt-5.6-sol",
+        "model": "gpt-6-astra",
         "model_reasoning_effort": "max"
       }
     },
       "c3_elevated_profile": {
       "suffix": "c3-elevated",
-      "model": "gpt-5.6-sol",
+      "model": "gpt-6-astra",
       "model_reasoning_effort": "high",
       "activation": {
         "operator": "any",
@@ -329,12 +329,12 @@
       "forced_personas": {
       "epic-planner": {
         "suffix": "",
-        "model": "gpt-5.6-sol",
+        "model": "gpt-6-astra",
         "model_reasoning_effort": "ultra"
       },
       "epic-orchestrator": {
         "suffix": "",
-        "model": "gpt-5.6-sol",
+        "model": "gpt-6-astra",
         "model_reasoning_effort": "ultra"
       }
     },

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

@@ -81,13 +81,13 @@ receipt's logical agent name.
 
 ## Fixed routing outcomes
 
-- C1: `gpt-5.6-luna`, low reasoning.
-- C2: `gpt-5.6-terra`, medium reasoning.
-- C3 standalone with a C3 ceiling: `gpt-5.6-terra`, high reasoning.
+- C1: `gpt-6-luna`, low reasoning.
+- C2: `gpt-6.1-sol`, medium reasoning.
+- C3 standalone with a C3 ceiling: `gpt-6.1-sol`, high reasoning.
 - C3 in either epic-child context, or C3 under a C4 ceiling:
-  `gpt-5.6-sol`, high reasoning through the `-c3-elevated` profile.
-- C4: `gpt-5.6-sol`, max reasoning.
-- `epic-planner` and `epic-orchestrator`: always `gpt-5.6-sol`, ultra
+  `gpt-6-astra`, high reasoning through the `-c3-elevated` profile.
+- C4: `gpt-6-astra`, max reasoning.
+- `epic-planner` and `epic-orchestrator`: always `gpt-6-astra`, ultra
   reasoning.
 
 If the exact model is unavailable, record `model_unavailable`, leave the work

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

@@ -79,7 +79,7 @@ issue number for it. Run at most one main-sync child per wave, then re-fetch the
 Launch all ready children in one bounded parallel wave. Before each launch, persist the
 epic-child topology receipt, reviewed complexity assessment, delegation receipt, and Codex
 model-routing receipt with the same `delegation_id`, then select the generated deployment agent.
-C3 epic children use the elevated Sol/High profile. The child prompt contains:
+C3 epic children use the elevated Astra/High profile. The child prompt contains:
 
 > `Epic mode: true. epic_feature_folder: <epic-slug>. integration_branch: epic/<epic-slug>-integration. epic_checkpoint_path: artifacts/orchestration/epic-orchestrator-state.json. PR base branch MUST be <integration_branch>, not main; pass --base <integration_branch> to gh pr create.`
 
@@ -137,12 +137,12 @@ remove its worktree. The worktree-removal hook denies removal before the matchin
 Route selection and model selection are independent. The deterministic file-count or marker
 route selects topology; the C1-C4 assessment selects a checked-in Codex deployment profile.
 
-- C1: `gpt-5.6-luna`, low.
-- C2: `gpt-5.6-terra`, medium.
-- standalone C3 with ceiling C3: `gpt-5.6-terra`, high.
-- epic C3 or C3 with a C4 sibling: `gpt-5.6-sol`, high.
-- C4: `gpt-5.6-sol`, max.
-- `epic-orchestrator`: `gpt-5.6-sol`, ultra.
+- C1: `gpt-6-luna`, low.
+- C2: `gpt-6.1-sol`, medium.
+- standalone C3 with ceiling C3: `gpt-6.1-sol`, high.
+- epic C3 or C3 with a C4 sibling: `gpt-6-astra`, high.
+- C4: `gpt-6-astra`, max.
+- `epic-orchestrator`: `gpt-6-astra`, ultra.
 
 Persist the topology and model-routing receipts before every child or `pr-author` delegation. The
 deployed agent type and actual model must match its receipts and start attestation. If the

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

@@ -97,7 +97,7 @@ the prepared worktree. Write one immutable launch specification under
 `wave_number: 0`, the planner checkpoint path, integration branch, bounded maximum, and one
 launch record per child. Every record supplies the unique launch/delegation ids, prepared
 worktree and branch, generated `orchestrator-cN` profile, exact model/reasoning/permissions, and
-prompt. C3 epic children use the elevated Sol/High profile. Monitor the returned durable status
+prompt. C3 epic children use the elevated Astra/High profile. Monitor the returned durable status
 path; a nonzero child exit or missing completion status blocks fan-in.
 
 The launch specification schema is:
@@ -118,7 +118,7 @@ The launch specification schema is:
       "feature_folder": "<final-active-feature-folder>",
       "issue_num": 123,
       "deployment_agent": "orchestrator-c3-elevated",
-      "model": "gpt-5.6-sol",
+      "model": "gpt-6-astra",
       "model_reasoning_effort": "high",
       "permissions": "orchestrator-workspace",
       "execution_context": "epic_preparation_child",

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

@@ -60,7 +60,7 @@ Two separate mechanisms restrict Bash command text. They are kept apart here bec
 - `.github/workflows/ci.yml` triggers on `push` to `main` and `development`, on `pull_request` to `main`, `development`, and `epic/**`, on `workflow_dispatch`, and on `merge_group` (`types: [checks_requested]`, added by issue #952), with no path filters. When the merge queue on `main` is enabled, every required check is produced by a `merge_group` run of `ci.yml` as well as by the pull-request run; `.github/workflows/README.md` (`## Triggers`) records the trigger set.
 - Jobs in `ci.yml` and their check names: `Change scope` (job `changes`, the change-scope decision below); `CI full run` (job `full-run-marker`, which runs only on a full run, marks that run as a valid base for later decisions, and is not a required check); `quality-checks7 / Code Quality & Tests (<python-version>)` on Python 3.10, 3.11, 3.12, and 3.13 (`_quality-checks.yml`: Black check, Ruff, Pyright, the Codex generator `--check`, the tier classification, Pytest with line and branch coverage, and the coverage-threshold check on the JSON report totals); `security-scan / Security Scanning` (its `safety check` step carries `continue-on-error: true` and does not fail the check); `docs-validation / Documentation Validation`; `build-check / Build Package`; `shell-coverage / Shell Coverage (Bats + kcov)`; `drm-copilot-extension-tests / drm-copilot Extension Tests (<os>)` on `ubuntu-latest` and `windows-latest`; `root-typescript-tests / Root TypeScript Tests (<os>)` on `ubuntu-latest` and `windows-latest`; `NPM Audit Gate / npm audit (<manifest>)` (the calling job carries the name `NPM Audit Gate`); and the `poshqc` group below.
 - PowerShell CI (`_poshqc.yml`): `poshqc / PowerShell QC static` (format and analyze on `windows-latest`); the shard matrix `poshqc / PowerShell QC shard 1`, `shard 2`, and `shard 3` (`Invoke-PoshQCTest -ShardIndex -ShardCount` over the scan folders of `config/poshqc-scan.json`, with coverage, on `windows-latest`); the aggregator `poshqc / PowerShell QC`, which requires the static and shard jobs to succeed, verifies shard completeness against a Pester discovery count, and merges shard coverage; and `poshqc / PowerShell hook suites (Linux)`, which runs only `tests/scripts/claude-hooks` and `tests/scripts/codex-hooks` on `ubuntu-latest` with coverage disabled. A new test file under a scanned folder is assigned to a shard automatically and is counted by the completeness check.
-- Change-scope decision (issue #962): the `Change scope` job runs `scripts/ci/Invoke-CiChangeScope.ps1` and publishes the job output `code`. The decision is `code=false` (docs-only) only on a `pull_request` event from this repository when every file changed since the newest successful `ci.yml` run on the pull-request branch whose `CI full run` job succeeded, and whose head commit is an ancestor of the current head, is on the allowlist `config/ci-docs-only-paths.json`. A path is allowlisted when it starts with `docs/features/active/`, `docs/features/completed/`, `docs/features/potential/`, or `docs/research/`, does not start with `docs/features/templates/` or `docs/features/potential/template.md`, and ends in `.md`, `.txt`, `.log`, `.json`, or `.xml`; the allowlist file itself is not allowlisted. Every other case is a full run (`code=true`): `push`, `merge_group`, and `workflow_dispatch` events, a fork pull request, unreadable run or job data, no earlier full green run, a missing or non-ancestor base, an empty diff, any path outside the allowlist, and any error. The decision step carries `continue-on-error: true` and the callers compare the output with `!= 'false'`, so a failed or missing decision also gives a full run.
+- Change-scope decision (issue #962): the `Change scope` job runs `scripts/ci/Invoke-CiChangeScope.ps1` and publishes the job output `code`. The decision is `code=false` (docs-only) only on a `pull_request` event from this repository, through one of two comparisons. Green-run base: every file changed since the newest successful `ci.yml` run on the pull-request branch whose `CI full run` job succeeded, and whose head commit is present and an ancestor of the current head, is on the allowlist `config/ci-docs-only-paths.json`; the reason is `DOCS_ONLY_SINCE_<green head sha>`. Merge-base fallback (issue #973): when the green-run step ends with no earlier full green run (`NO_FULL_GREEN_RUN`), a missing base (`BASE_NOT_PRESENT`), or a non-ancestor base (`BASE_NOT_ANCESTOR`), and the pull request's base ref is exactly `main`, the script computes `git merge-base` of the payload base SHA (`BASE_SHA`, from `github.event.pull_request.base.sha`; the base ref arrives as `BASE_REF`) and the head, lists the files changed since that merge base with the same diff arguments, and decides `DOCS_ONLY_SINCE_MERGE_BASE_<merge base sha>` when every changed file is allowlisted. Both comparisons run the diff with rename detection off, so both the old and the new path of a rename are classified. A path is allowlisted when it starts with `docs/features/active/`, `docs/features/archive/`, `docs/features/completed/`, `docs/features/epics/`, `docs/features/parallel/`, `docs/features/potential/`, or `docs/research/`, does not start with `docs/features/templates/` or `docs/features/potential/template.md`, and ends in `.md`, `.txt`, `.log`, `.json`, or `.xml`; the allowlist file itself is not allowlisted. Every other case is a full run (`code=true`): `push`, `merge_group`, and `workflow_dispatch` events, a fork pull request, unreadable run or job data, no earlier full green run or a missing or non-ancestor base when the base ref is not `main`, a merge base that cannot be resolved (`MERGE_BASE_UNRESOLVED`, for example a blank base SHA or a base commit missing from the checkout), a failed ancestry check, an empty diff, any path outside the allowlist, and any error. The decision step carries `continue-on-error: true` and the callers compare the output with `!= 'false'`, so a failed or missing decision also gives a full run.
 - Docs-only behavior (`code=false`): `ci.yml` passes `run-heavy: false` to `_quality-checks.yml`, `_security-scan.yml`, `_build-check.yml`, `_poshqc.yml`, `_shell-coverage.yml`, and `_drm-copilot-extension-tests.yml`. Each required job still starts under its full-run check name with every step skipped, so every required context reports `success` without running its suite. In `_poshqc.yml` the aggregator `poshqc / PowerShell QC` runs with every step gated, and `poshqc / PowerShell QC static`, the shard jobs, and `poshqc / PowerShell hook suites (Linux)` are skipped at job level. `docs-validation / Documentation Validation` runs in full. `root-typescript-tests`, `NPM Audit Gate`, and `CI full run` are skipped at job level. A `success` on a docs-only commit is therefore not evidence that the heavy suites pass for that commit; that evidence is the newest run whose `CI full run` job succeeded.
 - A commit that changes any path outside the allowlist (any code, workflow, configuration, script, test, or customization file) runs the full set of jobs, and its `CI full run` job marks it as a base for later docs-only decisions. A standalone `workflow_dispatch` of a reusable workflow, or a caller that omits `run-heavy`, also runs in full. `.github/workflows/README.md` (`## Change-Scope Decision (Issue #962)`) records the reason codes and the per-context behavior table.
 - Required contexts of ruleset 15241672, confirmed by the orchestrator through `gh api` on 2026-10-16: `drm-copilot-extension-tests / drm-copilot Extension Tests (ubuntu-latest)`, `drm-copilot-extension-tests / drm-copilot Extension Tests (windows-latest)`, `docs-validation / Documentation Validation`, `poshqc / PowerShell QC`, `shell-coverage / Shell Coverage (Bats + kcov)`, `security-scan / Security Scanning`, `quality-checks7 / Code Quality & Tests (3.10)`, `quality-checks7 / Code Quality & Tests (3.11)`, `quality-checks7 / Code Quality & Tests (3.12)`, `quality-checks7 / Code Quality & Tests (3.13)`, `build-check / Build Package`.

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

@@ -102,8 +102,8 @@ Apply the deterministic production-file axis before model selection:
   closed to the large orchestrator topology.
 - Outside the applicable budget, cross-cutting, mixed-language, or unsupported: deploy
   `orchestrator-<profile>` and let that agent run the large path.
-- Epic planning: deploy the forced `epic-planner` Sol/Ultra persona.
-- Prepared or manual epic execution: deploy the forced `epic-orchestrator` Sol/Ultra persona.
+- Epic planning: deploy the forced `epic-planner` Astra/Ultra persona.
+- Prepared or manual epic execution: deploy the forced `epic-orchestrator` Astra/Ultra persona.
 
 Only the production-file limit selects inside versus outside the language topology budget. The
 test-file estimate remains in the receipt and governs typed-engineer batching; it does not change
@@ -158,8 +158,8 @@ checked-in Codex deployment agent. Before every delegation:
 5. Require the `SubagentStart` model attestation to match the receipt before accepting mutation
    or completion.
 
-C3 defaults to Terra/High when it is the standalone orchestration ceiling. It elevates to
-Sol/High only for epic preparation/execution children or when a C4 sibling sets the ceiling to
+C3 defaults to Sol/High when it is the standalone orchestration ceiling. It elevates to
+Astra/High only for epic preparation/execution children or when a C4 sibling sets the ceiling to
 C4. If the required model/profile is unavailable, record `model_unavailable` and stop without a
 silent fallback.
 

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

@@ -275,7 +275,7 @@ If an exact signal or required path field is missing, set the relevant step to `
 8. Keep topology routing separate from C1-C4 model routing. Persist both topology and
    model-routing receipts and select the exact generated Codex deployment agent before every
    delegation.
-9. Use Terra/High for standalone ceiling-C3 work. Use Sol/High for C3 epic children or C3 work in
+9. Use Sol/High for standalone ceiling-C3 work. Use Astra/High for C3 epic children or C3 work in
    an orchestration whose monotonic ceiling is C4. Do not infer this overlay from file count.
 
 ## Small Path

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor-c1.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor-c1"
 description = "Converted subagent"
-model = "gpt-5.6-luna"
+model = "gpt-6-luna"
 model_reasoning_effort = "low"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor-c2.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor-c2"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "medium"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor-c3-elevated.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor-c3-elevated"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor-c3.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor-c3"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor-c4.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor-c4"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "max"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-executor.toml

@@ -1,6 +1,6 @@
 name = "atomic-executor"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner-c1.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner-c1"
 description = "Converted subagent"
-model = "gpt-5.6-luna"
+model = "gpt-6-luna"
 model_reasoning_effort = "low"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner-c2.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner-c2"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "medium"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner-c3-elevated.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner-c3-elevated"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner-c3.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner-c3"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner-c4.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner-c4"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "max"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/atomic-planner.toml

@@ -1,6 +1,6 @@
 name = "atomic-planner"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Applied rewrites:

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward-c1.toml

@@ -1,6 +1,6 @@
 name = "commit-steward-c1"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-luna"
+model = "gpt-6-luna"
 model_reasoning_effort = "low"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward-c2.toml

@@ -1,6 +1,6 @@
 name = "commit-steward-c2"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "medium"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward-c3-elevated.toml

@@ -1,6 +1,6 @@
 name = "commit-steward-c3-elevated"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "high"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward-c3.toml

@@ -1,6 +1,6 @@
 name = "commit-steward-c3"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward-c4.toml

@@ -1,6 +1,6 @@
 name = "commit-steward-c4"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "max"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/commit-steward.toml

@@ -1,6 +1,6 @@
 name = "commit-steward"
 description = "Generate a high-signal conventional commit message for the current repository based on staged changes only."
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 
 developer_instructions = """

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer-c1"
 description = "Converted subagent"
-model = "gpt-5.6-luna"
+model = "gpt-6-luna"
 model_reasoning_effort = "low"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer-c2"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "medium"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer-c3-elevated"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer-c3"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer-c4"
 description = "Converted subagent"
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "max"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "csharp-typed-engineer"
 description = "Converted subagent"
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 developer_instructions = '''
 Canonical migration source: .github/agents/csharp-typed-engineer.agent.md

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

@@ -1,6 +1,6 @@
 name = "epic-orchestrator"
 description = "Root-invoked epic execution coordinator that schedules prepared or manual epic features in dependency waves and drives integration fan-in and the final PR."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "ultra"
 default_permissions = "orchestrator-workspace"
 developer_instructions = '''
@@ -54,7 +54,7 @@ begin the normal epic lifecycle without requiring planner output.
 - Recompute longest-path waves as an integrity check without rewriting a prepared plan.
 - Persist each child topology receipt, complexity assessment, delegation receipt, and
   delegation-bound model-routing receipt before launch.
-- Select the generated deployment profile. Epic C3 children use Sol/High; C4 uses Sol/Max.
+- Select the generated deployment profile. Epic C3 children use Astra/High; C4 uses Astra/Max.
 - Launch all ready features in a bounded wave concurrently from the current integration tip.
 - Use `.codex/scripts/launch-epic-child-wave.ps1` with an immutable `epic-orchestrator` wave spec,
   exact profile values, and `max_parallel_features` from 1 through 8. Native `spawn_agent` is

package/resources/codex-and-agents-customizations/.codex/agents/epic-planner.toml

@@ -1,6 +1,6 @@
 name = "epic-planner"
 description = "Root-invoked epic planning coordinator that decomposes an epic, prepares every child through preflight, commits the planning state, and stops before execution."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "ultra"
 default_permissions = "orchestrator-workspace"
 developer_instructions = '''
@@ -47,7 +47,7 @@ stop. You may delegate to ordinary complexity-specific orchestrator profiles. Ne
 - Use isolated worktrees based on the integration branch.
 - Persist the epic-child topology receipt, delegation receipt, and delegation-bound model-routing
   receipt before selecting each generated `orchestrator-cN` deployment profile. Epic C3 work
-  uses the elevated Sol/High profile.
+  uses the elevated Astra/High profile.
 - Launch worktree children only through `.codex/scripts/launch-epic-child-wave.ps1` using one
   immutable `epic-planner` launch spec with `wave_number: 0`. Native `spawn_agent` is prohibited
   for these children because it does not provide the required worktree binding. Monitor and

package/resources/codex-and-agents-customizations/.codex/agents/feature-reviewer-c1.toml

@@ -1,6 +1,6 @@
 name = "feature-reviewer-c1"
 description = "Review a feature branch relative to a base branch, generate policy/code/feature audit artifacts, and trigger remediation planning when required."
-model = "gpt-5.6-luna"
+model = "gpt-6-luna"
 model_reasoning_effort = "low"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/feature-reviewer-c2.toml

@@ -1,6 +1,6 @@
 name = "feature-reviewer-c2"
 description = "Review a feature branch relative to a base branch, generate policy/code/feature audit artifacts, and trigger remediation planning when required."
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "medium"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/feature-reviewer-c3-elevated.toml

@@ -1,6 +1,6 @@
 name = "feature-reviewer-c3-elevated"
 description = "Review a feature branch relative to a base branch, generate policy/code/feature audit artifacts, and trigger remediation planning when required."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "high"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/feature-reviewer-c3.toml

@@ -1,6 +1,6 @@
 name = "feature-reviewer-c3"
 description = "Review a feature branch relative to a base branch, generate policy/code/feature audit artifacts, and trigger remediation planning when required."
-model = "gpt-5.6-terra"
+model = "gpt-6.1-sol"
 model_reasoning_effort = "high"
 
 developer_instructions = """

package/resources/codex-and-agents-customizations/.codex/agents/feature-reviewer-c4.toml

@@ -1,6 +1,6 @@
 name = "feature-reviewer-c4"
 description = "Review a feature branch relative to a base branch, generate policy/code/feature audit artifacts, and trigger remediation planning when required."
-model = "gpt-5.6-sol"
+model = "gpt-6-astra"
 model_reasoning_effort = "max"
 
 developer_instructions = """