nccgs 2.0.0-rc.2 → 2.0.0-rc.3

package/.claude/nccgs/MEMORY.md

@@ -1,7 +1,7 @@
 # NCCGS — portable framework decisions
 
 NCCGS means **New Claude Code Game Studio** and targets **Claude Code**.
-This is the public 2.0.0-rc.2 release candidate, distributed through npm's next tag.
+This is the public 2.0.0-rc.3 release candidate, distributed through npm's next tag.
 It is not stable promotion. The package README and changelog describe release scope.
 Project-specific authorizations, provider sessions, budgets and internal development
 history are retained separately, outside the public package. Nothing in this file

package/.claude/nccgs/VERSION

@@ -1 +1 @@
-2.0.0-rc.2
+2.0.0-rc.3

package/.claude/nccgs/protocols/standalone-gates.md

@@ -1,6 +1,6 @@
 # NCCGS 2.0 RC — implementation and operation
 
-Version: **2.0.0-rc.2**. Target executor: **Claude Code**.
+Version: **2.0.0-rc.3**. Target executor: **Claude Code**.
 Framework tests and scoped native delivery evidence exist. Fresh end-to-end
 qualification of this exact RC and published-1.3 upgrade qualification are pending. Read [MEMORY.md](../MEMORY.md) before interpreting evaluation results.
 

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 2.0.0-rc.3 — 2026-10-07
+
+Published-1.3.0 upgrade correction on next; latest remains unchanged.
+
+- Fixed false overrides when a role generated by a 1.3.0 profile becomes a managed
+  file in 2.0. Existing generated fingerprints now identify unchanged agent files;
+  later user edits and explicit overrides still require review.
+- RC2 qualification exposed the issue in quality, balanced and inherit profiles.
+  The astra-claude path was unaffected. Original failed results are retained.
+- Release qualification uses the published 1.3.0 archive and the exact candidate
+  archive across four model profiles, owner settings and open task history,
+  override preservation, dry runs, explicit execution migration, rollback and
+  refusal of changed configuration/backups. See docs/UPGRADE-QUALIFICATION.md.
+- A new task executed by Claude Code through this exact release remains pending;
+  this correction does not promote stable or change the frozen game evaluation.
+
 ## 2.0.0-rc.2 — 2026-10-07
 
 Release documentation follow-up on next; latest remains unchanged.

package/MEMORY.md

@@ -1,7 +1,7 @@
 # NCCGS — portable framework decisions
 
 NCCGS means **New Claude Code Game Studio** and targets **Claude Code**.
-This is the public 2.0.0-rc.2 release candidate, distributed through npm's next tag.
+This is the public 2.0.0-rc.3 release candidate, distributed through npm's next tag.
 It is not stable promotion. See README.md and CHANGELOG.md for release scope.
 Project-specific authorizations, provider sessions, budgets and internal development
 history are retained separately, outside the public package. Nothing in this file

package/README.md

@@ -1,6 +1,6 @@
 # NCCGS — New Claude Code Game Studio
 
-**2.0.0-rc.2** is a release candidate for standalone game-development orchestration
+**2.0.0-rc.3** is a release candidate for standalone game-development orchestration
 in **Claude Code**, published on npm's **next** channel. The stable/latest channel
 is not promoted by this release.
 
@@ -21,7 +21,8 @@ and negative findings remain preserved in the development evidence.
 The release source includes the reviewed fixes to reviewer capacity, handoff schema
 guidance and standalone command syntax. The game case used a frozen framework with
 a session-only reviewer capacity override. This exact RC has not yet completed a
-fresh full game task or a published-1.3.0 upgrade qualification. Use a disposable
+fresh full game task. Published-1.3.0 upgrade scope is documented in
+[upgrade qualification](docs/UPGRADE-QUALIFICATION.md). Use a disposable
 project or backed-up copy while evaluating it. See [release status](docs/RELEASE-STATUS.md), [Vietnamese quick start](docs/HUONG-DAN-MIGRATE-VA-SU-DUNG.md), [release notes](CHANGELOG.md),
 [upgrading](UPGRADING.md), [delivery acceptance](.claude/nccgs/protocols/delivery-acceptance.md)
 and [portable framework decisions](MEMORY.md).
@@ -69,14 +70,14 @@ Requirements: Claude Code and Node.js 18+. Unity CLI/Pipeline is needed for live
 Unity operations. Run against a disposable Unity project first:
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject" --dry-run
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject"
-npx --yes nccgs@2.0.0-rc.2 doctor --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject" --dry-run
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 doctor --project "D:\path\to\UnityProject"
 ```
 
 Use nccgs@next to follow candidate releases, or pin the exact version above for
 repeatability. Use update for an existing installation only after reviewing its
-dry run and backup. Published-1.3.0 upgrade qualification is still pending for this RC.
+dry run and backup. See [the tested upgrade matrix](docs/UPGRADE-QUALIFICATION.md) and its limits.
 The installer preserves customized files and unrelated Claude settings, records
 overrides and backs up replacements. Do not use --force as an ordinary update path.
 
@@ -84,7 +85,7 @@ New installs default to standalone with `claude-standalone`. Existing installati
 without execution.json remain compatibility. To migrate explicitly:
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 migrate-execution --project "D:\path\to\UnityProject" --to standalone --model-profile claude-standalone --dry-run
+npx --yes nccgs@2.0.0-rc.3 migrate-execution --project "D:\path\to\UnityProject" --to standalone --model-profile claude-standalone --dry-run
 ```
 
 Inspect the dry run, then remove `--dry-run`. Omitting `--model-profile` preserves
@@ -96,7 +97,7 @@ task handling. Updating files never converts an old approval into a new one.
 Start a task session with native permissions already selected:
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 run --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 run --project "D:\path\to\UnityProject"
 ```
 
 New installations default to task autonomy `full`. Existing installations keep

package/UPGRADING.md

@@ -1,6 +1,6 @@
 # Upgrading NCCGS 2.0 RC
 
-Current candidate: **2.0.0-rc.2** on npm **next**. `latest` remains on the stable
+Current candidate: **2.0.0-rc.3** on npm **next**. `latest` remains on the stable
 release line. Pin an exact version when reproducing an installation.
 Read [release status](docs/RELEASE-STATUS.md) for what has and has not been verified.
 
@@ -13,9 +13,9 @@ Read [release status](docs/RELEASE-STATUS.md) for what has and has not been veri
 | Intentionally adopt standalone execution | `migrate-execution --to standalone` | Explicitly changes execution configuration; separate from updating files |
 | Resume work | `run` | Launches Claude Code with the project's configured obligations |
 
-**Published-1.3.0 upgrade qualification is pending.** The commands below document
-the supported interface; they are not evidence that this upgrade has passed.
-Try a complete copy of the project before applying an RC to active work.
+**Published-1.3.0 upgrade qualification is covered for the tested fixture matrix.**
+See [upgrade qualification](docs/UPGRADE-QUALIFICATION.md) for scope and the RC2
+issue corrected in RC3. Try a complete copy before applying an RC to active work.
 
 ## New installation
 
@@ -24,9 +24,9 @@ Unity project with Assets, Packages and ProjectSettings. Live Unity operations
 also require the appropriate Unity Editor/CLI integration.
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject" --dry-run
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject"
-npx --yes nccgs@2.0.0-rc.2 doctor --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject" --dry-run
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 doctor --project "D:\path\to\UnityProject"
 ```
 
 New installations select standalone execution and the claude-standalone model
@@ -41,9 +41,9 @@ open task records and evidence. Stop active NCCGS sessions before applying an
 update. Do not update a frozen evaluation in place.
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 update --project "D:\path\to\ProjectCopy" --dry-run
-npx --yes nccgs@2.0.0-rc.2 update --project "D:\path\to\ProjectCopy"
-npx --yes nccgs@2.0.0-rc.2 doctor --project "D:\path\to\ProjectCopy"
+npx --yes nccgs@2.0.0-rc.3 update --project "D:\path\to\ProjectCopy" --dry-run
+npx --yes nccgs@2.0.0-rc.3 update --project "D:\path\to\ProjectCopy"
+npx --yes nccgs@2.0.0-rc.3 doctor --project "D:\path\to\ProjectCopy"
 ```
 
 Inspect the dry-run changes before the second command. Ordinary updates preserve
@@ -67,20 +67,21 @@ After installing/updating, migrate only when the owner intends to adopt standalo
 Review any active task's pinned obligations before changing policy.
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 migrate-execution --project "D:\path\to\ProjectCopy" --to standalone --model-profile claude-standalone --dry-run
+npx --yes nccgs@2.0.0-rc.3 migrate-execution --project "D:\path\to\ProjectCopy" --to standalone --model-profile claude-standalone --dry-run
 ```
 
 Inspect the result, then repeat without `--dry-run` to apply. Omit
 `--model-profile` to preserve model routes. An update alone does not perform this
 migration. Schema-1 tasks retain their original gates/history; do not relabel them
-as schema-2, reuse stale approvals or reset consumed attempts. Finish under the
-pinned policy or explicitly scope subsequent work with retained lineage/evidence.
+as schema-2, reuse stale approvals or reset consumed attempts. A changed pipeline can block resuming an old task. Finish it before upgrading,
+or explicitly scope subsequent work with retained lineage/evidence; updating or
+rolling back execution settings does not re-approve an old task.
 
 The command archives configuration under `.nccgs/backups/execution/<ID>`. To
 preview restoration of that execution migration:
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 migrate-execution --project "D:\path\to\ProjectCopy" --rollback "MIGRATION_UUID" --dry-run
+npx --yes nccgs@2.0.0-rc.3 migrate-execution --project "D:\path\to\ProjectCopy" --rollback "MIGRATION_UUID" --dry-run
 ```
 
 Use the actual printed UUID; remove `--dry-run` only after reviewing the preview.
@@ -94,7 +95,7 @@ not an atomic transaction and may require manual recovery.
 ## Start and review work
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 run --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 run --project "D:\path\to\UnityProject"
 ```
 
 Use `/status` in Claude Code to inspect obligations. Use `/migrate-project` when
@@ -105,4 +106,4 @@ game quality, completion of a task or human acceptance.
 Existing projects that intentionally use Astra/Fable keep their configured chain.
 See [compatibility gates](.claude/nccgs/protocols/task-gates.md). Historical 1.4/1.5
 guides describe their original versions; this document governs the current RC's
-installation commands and release status.
+installation commands and release status.

package/VERSION

@@ -1 +1 @@
-2.0.0-rc.2
+2.0.0-rc.3

package/docs/HUONG-DAN-MIGRATE-VA-SU-DUNG.md

@@ -1,8 +1,9 @@
 # Hướng dẫn cài đặt và sử dụng NCCGS 2.0 RC
 
-Bản hiện tại: **2.0.0-rc.2**, kênh npm **next**. `latest` là kênh stable riêng.
-Đây là ứng viên phát hành; chưa kiểm chứng nâng cấp từ npm 1.3.0 hoặc chạy trọn một
-đầu việc mới bằng chính RC này. Xem [trạng thái phát hành](RELEASE-STATUS.md).
+Bản hiện tại: **2.0.0-rc.3**, kênh npm **next**. `latest` là kênh stable riêng.
+Đây là ứng viên phát hành. Nâng cấp từ npm 1.3.0 đã được kiểm chứng trong phạm vi
+[các tình huống thử](UPGRADE-QUALIFICATION.md); chạy trọn một đầu việc mới bằng
+chính RC này vẫn là bước riêng chưa hoàn tất. Xem [trạng thái phát hành](RELEASE-STATUS.md).
 
 ## Cài mới vào bản sao dự án
 
@@ -11,9 +12,9 @@ Chức năng điều khiển Unity cần thêm Editor/CLI phù hợp. Thay đư
 dự án của bạn; đọc kết quả xem trước rồi mới áp dụng:
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject" --dry-run
-npx --yes nccgs@2.0.0-rc.2 install --project "D:\path\to\UnityProject"
-npx --yes nccgs@2.0.0-rc.2 doctor --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject" --dry-run
+npx --yes nccgs@2.0.0-rc.3 install --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 doctor --project "D:\path\to\UnityProject"
 ```
 
 Có thể dùng `nccgs@next` để theo RC mới nhất; dùng số phiên bản cụ thể để tái lập.
@@ -35,7 +36,7 @@ mở lại phiên Claude Code.
 ## Bắt đầu một đầu việc rõ ràng
 
 ```powershell
-npx --yes nccgs@2.0.0-rc.2 run --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.3 run --project "D:\path\to\UnityProject"
 ```
 
 Trong Claude Code, cung cấp mục tiêu, phạm vi, yêu cầu cố định, phần được phép sửa
@@ -55,4 +56,4 @@ mong muốn, không phải bằng chứng model thực chạy. Chỉ gọi chuy
 Đạt test chưa tự động nghĩa là DONE. Phải có bằng chứng đúng source/contract,
 review hợp lệ và mọi gate áp dụng đều đạt. Nghiệm thu kỹ thuật và quyết định nghiệm
 thu của người dùng được ghi riêng. Một lượt thất bại phải được giữ cùng chi phí,
-nguyên nhân và kết quả sửa lại.
+nguyên nhân và kết quả sửa lại.

package/docs/RELEASE-STATUS.md

@@ -1,16 +1,16 @@
 # NCCGS 2.0 RC release status
 
-Current candidate: **2.0.0-rc.2**. Release channel: **next**. Latest/stable is not
+Current candidate: **2.0.0-rc.3**. Release channel: **next**. Latest/stable is not
 promoted by this candidate. Pin the exact version for reproducible evaluation.
 
 ## What the evidence supports
 
 | Check | Status and scope |
 |---|---|
-| Framework functional regression | Previous maintained source: 183 PASS, 0 FAIL, 6 Windows symlink skips across 189 tests. RC2 changes metadata/docs only; runtime implementation is compared with RC1 during packaging. |
+| Framework functional regression | Previous maintained source: 183 PASS, 0 FAIL, 6 Windows symlink skips across 189 tests. RC3 changes installer recognition of previously generated agents and adds a focused regression. Installer/policy suites and exact-archive upgrade qualification are rerun for this change. |
 | Scoped native delivery V2 case | 24/24 criteria,137 EditMode,52 PlayMode and independent unconditional Claude Code PASS. Operator-assisted; used a frozen framework with a session-only reviewer capacity override. |
 | RC package integrity | Release procedure verifies version consistency, public contents, documentation links, and install/doctor on a fresh disposable fixture using the packed archive. This is not an upgrade or provider task test. |
-| Upgrade from published npm 1.3.0 | PENDING — separate qualification step. Documented commands do not prove the upgrade. |
+| Upgrade from published npm 1.3.0 | Qualified within the disposable fixture matrix; RC2 exposed a generated-agent issue corrected in RC3. See [scope and limits](UPGRADE-QUALIFICATION.md). |
 | Fresh task through this exact RC | PENDING — separate qualification step. Earlier delivery evidence is not attributed to a new run. |
 | Human third-party acceptance | Separate decision; not supplied by installation, tests or this release status. |
 | Broad game quality/productivity | Not established. No universal quality, balance, cost or efficiency claim. |
@@ -29,14 +29,16 @@ change current defaults or add new delivery gates. Current installation guidance
 is in [UPGRADING.md](../UPGRADING.md) and the
 [Vietnamese quick start](HUONG-DAN-MIGRATE-VA-SU-DUNG.md).
 
-## RC2 change scope
+## RC3 change scope
 
 RC1 already standardized package metadata and removed private memory. RC2 finishes
 public documentation: current standalone defaults, exact-version npm commands,
 separate update/migration/rollback instructions, current role counts and visible
-historical boundaries. No runtime JavaScript, model routing, game code, acceptance
-threshold or frozen evaluation is changed. See [changelog](../CHANGELOG.md).
+historical boundaries. Those RC2 documentation edits changed no runtime JavaScript, model routing, game
+code, acceptance threshold or frozen evaluation. RC3 changes the installer only
+and adds its regression; no game or frozen evaluation is changed. See [changelog](../CHANGELOG.md).
 
 The major candidate communicates standalone defaults and explicit policy migration
 from the older compatibility workflow. Existing task obligations are retained.
-RC2 does not complete the two pending qualification steps or promote stable.
+RC3 corrects one installer defect exposed by upgrade qualification. The exact-RC
+Claude Code task remains pending; stable is not promoted.

package/docs/UPGRADE-QUALIFICATION.md

@@ -0,0 +1,45 @@
+# Published 1.3.0 upgrade qualification
+
+Target: **2.0.0-rc.3**. This is installation/configuration qualification on Windows
+with Node.js 24.12.0 using the published npm 1.3.0 archive and the exact RC3 archive.
+It does not establish Node 18, macOS/Linux, provider execution or gameplay results.
+
+## Tested scope
+
+- Fresh 1.3.0 installations with astra-claude, quality, balanced and inherit profiles;
+  update dry run, actual update, doctor and repeat update without content drift.
+- Owner source, project policy, custom Claude instructions/agents, local settings,
+  explicit permissions, environment and custom hooks sharing a managed hook group.
+- A task created by the real 1.3.0 CLI, with explicitly synthetic history/allowance
+  sentinels: task bytes and evidence are retained; an incomplete task cannot close.
+- Edited and deleted managed files are preserved and require migration review.
+  A successful update exit does not waive a failing doctor or approve overrides.
+- Malformed settings are rejected before project writes.
+- Explicit standalone migration, dry runs and exact restoration of captured
+  configuration; later edits and altered backup hashes prevent rollback.
+- Recovery from a complete pre-upgrade project backup, verified by file hashes and
+  the old doctor. Execution rollback alone is not a framework downgrade.
+
+## RC2 finding and correction
+
+RC2 falsely treated nccgs-game-designer as a local override when upgrading clean
+quality, balanced or inherit installations. The old profile had generated that
+agent outside its managed-file list; RC2 started managing it but ignored the
+recorded generation fingerprint. RC3 accepts unchanged recorded generated bytes
+as an update baseline. Real edits and explicit override records remain protected.
+
+Use RC3 directly from a backed-up 1.3.0 installation. If RC2 already recorded a
+pending override, review/rebase it through the documented migration workflow or
+recover the complete pre-upgrade backup before retrying RC3. Do not use --force
+or approve all overrides merely to suppress this warning.
+
+## Limits that still apply
+
+Ordinary update preserves model selection and compatibility obligations; adopting
+standalone is explicit. Preserving task bytes does not make old approvals current.
+The new pipeline can block an old task from resuming; finish before upgrading or
+create explicitly scoped continuation work while retaining history and evidence.
+
+Fixtures have Unity directory markers and sentinel source files. No Unity Editor
+or Claude worker is launched. The native exact-RC task is a separate pending step.
+Automated fixture results are not third-party human acceptance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nccgs",
-  "version": "2.0.0-rc.2",
+  "version": "2.0.0-rc.3",
   "description": "Unity-first game-studio operating system for Claude Code",
   "license": "MIT",
   "type": "module",

package/scripts/install.mjs

@@ -88,6 +88,7 @@ const overrideManifestPath = projectPath(".nccgs/framework-overrides.json");
 // even when a pre-existing file would otherwise be preserved or skipped.
 for (const relative of ["CLAUDE.md", ".claude/settings.json", ".nccgs/project.yaml", ".nccgs/execution.json", ".nccgs/backups", ".nccgs/agent-activation.json"]) projectPath(relative);
 const previousInstallState = readJsonIfPresent(installStatePath, "NCCGS install state");
+const previousActivation = readJsonIfPresent(projectPath(".nccgs/agent-activation.json"), "NCCGS agent activation state");
 const executionFile = projectPath(".nccgs/execution.json");
 const previousExecution = readJsonIfPresent(executionFile, "NCCGS execution policy");
 const existingProjectPolicy = fs.existsSync(projectPath(".nccgs/project.yaml"));
@@ -308,6 +309,15 @@ function planFrameworkFile(item) {
   }
   if (equivalentFiles(item.source, item.destination)) return { ...item, action: "current", override: null };
   if (!force && previous && matchesFingerprint(item.destination, previous)) return { ...item, action: "replace", override: null };
+  // Older profiles could generate optional agents outside install-state.files.
+  // When a later package starts managing one, its recorded generated bytes are
+  // a valid baseline. Real local edits and explicit overrides still need review.
+  const generated = previousActivation?.schemaVersion === 1 && item.relative.startsWith(".claude/agents/")
+    ? { sha256: previousActivation.generated?.[item.relative], canonicalSha256: previousActivation.generatedCanonical?.[item.relative] }
+    : null;
+  if (!force && previousInstallState && !previous && !existingOverride && matchesFingerprint(item.destination, generated)) {
+    return { ...item, action: "replace", override: null };
+  }
   if (force) return { ...item, action: "force-replace", override: null };
   return { ...item, action: "preserve", override: buildOverride(item, existingOverride, upstream, "preserve") };
 }

package/tests/framework.test.mjs

@@ -459,6 +459,44 @@ test("update replaces untouched files, preserves local overrides, and doctor gat
   }
 });
 
+test("update adopts unchanged generated agents newly tracked by the package, preserving real edits", () => {
+  const f = safetyFixture("nccgs-generated-adoption-");
+  try {
+    const installed = f.run("install", "--model-profile", "quality");
+    assert.equal(installed.status, 0, installed.stderr || installed.stdout);
+    const relative = ".claude/agents/nccgs-game-designer.md";
+    const file = path.join(f.project, relative);
+    const stateFile = path.join(f.project, ".claude/nccgs/install-state.json");
+    const generatedFile = path.join(f.project, ".nccgs/agent-activation.json");
+    const original = fs.readFileSync(file, "utf8");
+    // Older packages can generate a profile's optional agent without listing it
+    // in install-state.files. A later package can make that agent a core file.
+    const state = JSON.parse(fs.readFileSync(stateFile, "utf8"));
+    state.files = state.files.filter(item => item.relative !== relative);
+    fs.writeFileSync(stateFile, JSON.stringify(state));
+    const update = f.run("update");
+    assert.equal(update.status, 0, update.stderr || update.stdout);
+    const doctor = f.run("doctor");
+    assert.equal(doctor.status, 0, doctor.stderr || doctor.stdout);
+    assert.equal(fs.readFileSync(file, "utf8"), original);
+    assert.ok(JSON.parse(fs.readFileSync(stateFile)).files.some(item => item.relative === relative));
+
+    // A stored generated hash alone must never authorize replacing later edits.
+    const nextState = JSON.parse(fs.readFileSync(stateFile, "utf8"));
+    nextState.files = nextState.files.filter(item => item.relative !== relative);
+    fs.writeFileSync(stateFile, JSON.stringify(nextState));
+    assert.ok(JSON.parse(fs.readFileSync(generatedFile)).generated[relative]);
+    const customized = original + "\nOwner instruction: keep the custom design rule.\n";
+    fs.writeFileSync(file, customized);
+    const preserved = f.run("update");
+    assert.equal(preserved.status, 0, preserved.stderr || preserved.stdout);
+    assert.equal(fs.readFileSync(file, "utf8"), customized);
+    const manifest = JSON.parse(fs.readFileSync(path.join(f.project, ".nccgs/framework-overrides.json")));
+    assert.equal(manifest.overrides.find(item => item.path === relative).status, "pending_review");
+    assert.equal(f.run("doctor").status, 1);
+  } finally { f.dispose(); }
+});
+
 test("doctor accepts a legacy CRLF raw hash after Git normalizes the file to LF", () => {
   const temp = fs.mkdtempSync(path.join(os.tmpdir(), "nccgs-eol-test-"));
   try {