nccgs 2.0.0-rc.1 → 2.0.0-rc.2

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.1 release candidate, distributed through npm's next tag.
+This is the public 2.0.0-rc.2 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.1
+2.0.0-rc.2

package/.claude/nccgs/constitution.md

@@ -38,7 +38,7 @@ Explicit migration archives configuration and does not rewrite task history.
 
 Task records under `.nccgs/tasks/` are authoritative and `task close` enforces all
 stages. Markdown DONE labels cannot replace them. Read routes from `pipeline.json`;
-load only the selected execution workflow. Twelve core roles are active; enable
+load only the selected execution workflow. Thirteen roles are active by default; enable
 optional specialists when their expertise changes the next action.
 
 For meaningful project work:

package/.claude/nccgs/protocols/bounded-repair.md

@@ -1,4 +1,4 @@
-# Bounded source repair — unreleased preview
+# Bounded source repair — 2.0 RC
 
 The Unity phase-2 retest exhausted a repair worker's 22 native turns while exploring
 parameters in a scratch harness. It made no gameplay change and left a PARTIAL

package/.claude/nccgs/protocols/model-routing.md

@@ -2,8 +2,8 @@
 
 NCCGS runs in Claude Code. Resolve execution obligations independently of models.
 `pipeline.json` is the routing source; generated catalog/frontmatter and
-[routing.generated.md](../routing.generated.md) must match it. Twelve core roles
-load by default; 35 optional specialists remain in `agent-library/` until needed.
+[routing.generated.md](../routing.generated.md) must match it. Thirteen roles
+load by default; 34 optional specialists remain in `agent-library/` until needed.
 
 ## Standalone default
 

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

@@ -1,8 +1,8 @@
-# NCCGS 1.5 preview — implementation and operation
+# NCCGS 2.0 RC — implementation and operation
 
-Version: **2.0.0-rc.1**. Target executor: **Claude Code**.
-This is framework functionality with synthetic regression tests, pending real-runtime
-pilot validation. Read [MEMORY.md](../MEMORY.md) before interpreting evaluation results.
+Version: **2.0.0-rc.2**. 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.
 
 ## Policies and migration
 

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

@@ -1,4 +1,7 @@
-<!-- Historical 1.5 development document. Current release scope and limitations are in the package README.md and CHANGELOG.md. -->
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](../MEMORY.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
 
 # Claude Code pilot and benchmark protocol
 

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

@@ -1,4 +1,4 @@
-# Standalone Claude Code execution — v1.5 preview
+# Standalone Claude Code execution — 2.0 RC
 
 Read `.claude/nccgs/MEMORY.md`. NCCGS means New Claude Code Game Studio. Only
 real Claude Code execution supplies NCCGS orchestration evidence. Codex maintenance,

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

@@ -1,7 +1,7 @@
 # Executable task gates
 
 This document specifies compatibility/schema-1 gates. For standalone/schema-2
-contracts and payloads use [the v1.5 guide](standalone-gates.md) and
+contracts and payloads use [the standalone gate guide](standalone-gates.md) and
 [standalone execution](standalone.md). Existing tasks retain their original gates.
 
 Run the installed tool as `node .claude/nccgs/tools/task.mjs COMMAND ...`, or use

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 2.0.0-rc.2 — 2026-10-07
+
+Release documentation follow-up on next; latest remains unchanged.
+
+- Unified current version labels and exact-version npm install, doctor, run and migration commands.
+- Replaced the obsolete Vietnamese Astra/Fable-default guide with standalone RC instructions.
+- Separated file update, explicit execution migration and guarded rollback; documented that rollback is not a full package downgrade.
+- Corrected active role counts and current workflow/project-policy guidance.
+- Added a release-status matrix and visible historical labels instead of hidden comments.
+- Retained RC1, frozen evaluation evidence and internal history. No runtime JavaScript, game source, model routing or acceptance threshold changed.
+- Packaging validation covers public contents, local documentation links, version consistency and fresh install/doctor. Published-1.3.0 upgrade qualification and a fresh exact-RC task remain pending.
+
 ## 2.0.0-rc.1 — 2026-10-07
 
 Release channel: next. This candidate does not replace the stable/latest tag.

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.1 release candidate, distributed through npm's next tag.
+This is the public 2.0.0-rc.2 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.1** is a release candidate for standalone game-development orchestration
+**2.0.0-rc.2** 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.
 
@@ -22,7 +22,7 @@ The release source includes the reviewed fixes to reviewer capacity, handoff sch
 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
-project or backed-up copy while evaluating it. See [release notes](CHANGELOG.md),
+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,9 +69,9 @@ 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.1 install --project "D:\path\to\UnityProject" --dry-run
-npx --yes nccgs@2.0.0-rc.1 install --project "D:\path\to\UnityProject"
-npx --yes nccgs@2.0.0-rc.1 doctor --project "D:\path\to\UnityProject"
+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"
 ```
 
 Use nccgs@next to follow candidate releases, or pin the exact version above for
@@ -84,7 +84,7 @@ New installs default to standalone with `claude-standalone`. Existing installati
 without execution.json remain compatibility. To migrate explicitly:
 
 ```powershell
-node "D:\path\to\NCCGS\scripts\cli.mjs" migrate-execution --project "D:\path\to\UnityProject" --to standalone --model-profile claude-standalone --dry-run
+npx --yes nccgs@2.0.0-rc.2 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 +96,7 @@ task handling. Updating files never converts an old approval into a new one.
 Start a task session with native permissions already selected:
 
 ```powershell
-node "D:\path\to\NCCGS\scripts\cli.mjs" run --project "D:\path\to\UnityProject"
+npx --yes nccgs@2.0.0-rc.2 run --project "D:\path\to\UnityProject"
 ```
 
 New installations default to task autonomy `full`. Existing installations keep
@@ -131,7 +131,10 @@ Independent review uses Opus/high. These aliases are requested routes. Real Clau
 model resolution and provider access must be verified in the target session.
 Historical `astra-claude` routes remain available under compatibility execution.
 
-## Verification and limits
+## Maintainer verification and limits
+
+These commands run from a source/package checkout. They are not extra steps for
+users installing with npx, and do not initiate a Claude Code game run.
 
 ```text
 npm run policy:build

package/UPGRADING.md

@@ -1,197 +1,108 @@
-# Upgrading NCCGS
-
-## 2.0.0-rc.1 on the next channel
-
-This is an opt-in release candidate. Keep a complete project backup and evaluate
-on a copy. The stable/latest channel remains separate. Read CHANGELOG.md first.
-A fresh packaged install/doctor check is part of RC packaging; qualification of
-an upgrade from the published 1.3.0 package and a fresh end-to-end RC task remain
-pending. Do not treat the accepted delivery V2 case as proof of those two checks.
-
-New installations use standalone execution. Existing execution policies and
-legacy tasks retain their original obligations; an update does not silently
-migrate or reset them. Follow the explicit migration procedure below only when
-that policy change is intended. Earlier sections describe historical source releases.
-
-Always inspect a dry run and preserve project policy.
-
-## Bounded repair (unreleased source change)
-
-Fresh standalone `purpose: repair` reservations require `workPacket` and one fresh
-handoff. See [the packet schema and limits](docs/BOUNDED-REPAIR.md). The source CLI
-installs `.nccgs/templates/repair-packet.json` for new projects. Existing reserved
-dispatches remain legacy, with their original evidence and budgets; no retroactive
-packet enforcement or quota reset occurs. Reopen Claude Code after managed hooks
-are updated. Preserve the frozen failed game cases and test in a fresh copy.
-
-## Task autonomy (unreleased source change)
-
-New installs select `.nccgs/autonomy.json` mode `full`; updates preserve existing
-policy, including `guarded` for older projects without that file. Use
-`nccgs update --autonomy full` for the owner's requested change, then launch/resume
-with `nccgs run`. Native permission selection is session scoped; global settings
-are unchanged. Existing deny rules, destructive-action guards and evidence gates
-remain in force. Hook commands now resolve from the project root even after
-outside-directory work; updates replace their legacy relative form once.
-
-Autonomy policy is a canonical task input. Existing open tasks need input refresh
-and fresh affected evidence after this update; their history and spent quotas
-are not reset. Preserve frozen benchmark installations/results separately.
-
-## 1.5.0-preview.1: explicit standalone migration
-
-Read [the v1.5 guide](docs/NCCGS-1.5.md). Use this checkout's CLI or a locally packed
-archive; this preview has not been published to npm. New installs use standalone
-Claude Code execution. Existing installs without execution.json remain compatibility;
-ordinary update preserves model profile, execution obligations, tasks and evidence.
-
-After updating managed files, preview `migrate-execution --to standalone --dry-run`.
-It changes execution policy only. Add `--model-profile claude-standalone` when also
-changing model routes. Apply by removing `--dry-run`. Review the reported archive
-under `.nccgs/backups/execution/<ID>` and reopen Claude Code after settings changes.
-
-`migrate-execution --rollback ID --dry-run` previews restoration; removing
-`--dry-run` restores only when current configuration and backup hashes still match.
-Later user edits or altered archives block rollback. Caught migration failures
-restore captured configuration. An OS kill can leave a prepared archive requiring
-manual recovery; this is not a crash-atomic multi-file transaction.
-
-Schema-1 tasks keep their original gates/history. Do not reinterpret them as schema-2
-or clone them to reset consumed budgets. Finish them under compatibility configuration,
-or retain them as blocked/history and open explicitly scoped new work with recorded
-lineage. Fresh benchmarks must not reuse contaminated CP0 solutions.
-
-The sections below describe historical versions and their original defaults.
-
-## 1.4.1: input freshness, durable evidence and installation safety
-
-Follow the [1.4.1 guide](docs/NCCGS-1.4.1.md). Map governing inputs and generated
-build destinations in `.nccgs/inputs.json`. Runtime observations and raw sources
-now live under `.nccgs/evidence/runtime/`; temporary bindings remain local.
-
-For an open 1.4 task, run `task migrate-evidence --id ID`, then
-`task refresh-inputs --id ID --reason TEXT` and record fresh stage evidence.
-History, risk and consumed review rounds are preserved. A refresh cannot waive
-review or acceptance. Closed old records remain historical and doctor reports
-missing evidence. Keep original task/evidence files for rollback.
-
-This patch keeps the existing Astra/Fable/Product Owner chain. The proposed
-standalone architecture belongs to 1.5.
-
-## 1.4.0: risk-based implementation and bounded review
-
-Read the [1.4 guide](docs/NCCGS-1.4.md). Routing now comes from
-`.claude/nccgs/pipeline.json`; generated files are checked for drift. Twelve core
-agents are active by default; 35 additional roles are available through `agents
---enable`. Project customizations are preserved for explicit migration review.
-
-Astra must map existing checks, closure artifacts and manual decisions into
-`.nccgs/gates.json`, referencing the current project policy hash. A 1.2 policy with
-embedded `profile_contracts` needs migration to the canonical `pipeline_policy`
-reference. Do not discard project requirements during this migration.
-
-Task records now enforce implementation -> independent review -> report -> Astra
-check -> Product Owner acceptance. Missing observed effort blocks the gate; requested
-settings alone do not prove runtime behavior. Each workflow loads only its selected
-Astra or legacy branch. The legacy instructions later in this document apply only
-to explicitly selected legacy profiles.
-
-Version 1.4 adds FAST/STANDARD/CONTROLLED implementation routes and two core roles:
-`nccgs-fast-implementer` and the read-only `nccgs-task-scout`. The existing Unity
-implementer becomes the deep CONTROLLED lead. The library now has 47 roles.
-Review limits are enforced at 2/3/3 rounds; re-recording implementation preserves
-the counter. An explicit external `task extend-review --id ID --reason TEXT
---rounds N` can add rounds without waiving review or acceptance. Context/time
-budgets are advisory; they are not automatic stop timers.
-
-Old task records without `risk`, `implementationRoute`, or `reviewBudget` cannot
-continue through the new gates. Keep them as history, initialize a new task with
-the appropriate `--risk` (default STANDARD), and record fresh stage evidence.
-Do not copy prior approvals into the new task or recreate a current task to reset
-an exhausted budget. Reopen Claude Code after updating model settings and verify
-the actual selected implementation model/effort.
-
-## Astra / Opus / Fable routing
-
-New installations default to `astra-claude`: Astra plans and owns documents;
-Sonnet/medium handles FAST, Opus 5.5/medium handles STANDARD, and Opus 5.5/high handles CONTROLLED; Fable/high reviews; Claude hands the reviewed report to
-Astra; Astra checks it; the Product Owner accepts before DONE. See the
-[handoff protocol](.claude/nccgs/protocols/astra-claude.md).
-
-Existing projects keep their profile unless explicitly changed. In each Unity
-project, run `npx nccgs@latest update --model-profile astra-claude --dry-run`, inspect
-it, then remove `--dry-run`. Source checkouts can use `node <NCCGS>/scripts/cli.mjs`
-instead of `npx nccgs@latest`. Publishing alone does not update installed projects.
-Use `install` instead of `update` for a new installation. Require Claude Code
-2.1.280+ and access to Sonnet, Opus 5.5, and Fable. Review any
-preserved agent/settings overrides so the observed model and effort match policy.
-The configurator preserves unrelated shared settings and backs up replacements;
-existing sessions and local/environment overrides still require a runtime check.
-
-## Earlier update behavior
+# Upgrading NCCGS 2.0 RC
+
+Current candidate: **2.0.0-rc.2** 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.
+
+## Choose the operation
+
+| Situation | Operation | Effect |
+|---|---|---|
+| No NCCGS installation | `install` | Adds framework and initial project policy |
+| Existing NCCGS installation | `update` | Updates managed files; preserves project-owned policy and customizations |
+| 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.
+
+## New installation
+
+Requirements: Node.js 18+, Claude Code with access to the selected models, and a
+Unity project with Assets, Packages and ProjectSettings. Live Unity operations
+also require the appropriate Unity Editor/CLI integration.
 
 ```powershell
-cd "D:\path\to\UnityProject"
-npx nccgs@latest update --dry-run
-npx nccgs@latest update
-npx nccgs@latest doctor
+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"
 ```
 
-Version 1.1.1 makes updates hash-aware, line-ending-aware, and override-aware.
-Managed files that still match the previous install state update automatically;
-CRLF/LF conversion alone is accepted as the same text. Genuine project-modified or
-intentionally missing framework files are preserved and recorded in
-`.nccgs/framework-overrides.json` as `pending_review`. The rest of the framework is
-updated normally, so `--force` is no longer required to get past intentional local
-customizations. Existing `.nccgs/project.yaml` remains project-owned and is never
-blindly overwritten.
-
-When pending overrides are reported, open a fresh Claude Code session and run
-`/migrate-project` once. The workflow reviews and rebases each override, migrates the
-project policy when needed, and records approval of the final hashes. A direct
-`doctor` remains red until pending override review is complete. Use `--force` only
-when you intentionally want to back up and discard every detected customization.
-
-NCCGS 1.1.1 also names its specialized review command `/nccgs-code-review` to avoid
-colliding with Claude Code's built-in `/code-review` command.
-
-When the installer reports that project migration is required, open a new Claude
-Code session and run one command:
-
-```text
-/migrate-project
-/status full
+New installations select standalone execution and the claude-standalone model
+profile. External review is off by default; manual/project acceptance obligations
+still apply when required. New task autonomy defaults to full, activated by `run`;
+OS restrictions, explicit deny rules and evidence/destructive-action guards remain.
+
+## Update an existing installation
+
+Back up the complete project first, including .claude, .nccgs, source, settings,
+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"
 ```
 
-The workflow retains review, plan, apply, and verify internally. Do not run it after
-an ordinary update when the installer reports `No project migration required`.
-
-The migration plan must move schema 1 policy to schema 2, choose a model profile,
-enable departments, configure context packets and orchestration, preserve closure
-artifacts, verify hooks, and resolve obsolete global skills. Keep
-`.claude/settings.local.json` local. Commit shared `.claude/` and `.nccgs/`; nested
-`.nccgs/.gitignore` excludes backups and runtime audit events.
-
-Use `--model-profile inherit` during installation if pinned models are unavailable.
-All replaced shared framework/settings files are backed up under
-`.nccgs/backups/<timestamp>/`.
-
-## Reviewed design handoffs (2026-10-04 source preview)
-
-New standalone installs enable `designReviewRequired: true` in
-`.nccgs/execution.json`. Existing files and frozen tasks retain their pinned
-policy; an update does not manufacture design approval. To adopt this gate in an
-existing project, finish/archive active work, explicitly enable that field, and
-initialize fresh tasks. Do not alter historical policy or reset spent quotas.
-See [the design lifecycle](.claude/nccgs/protocols/design-lifecycle.md).
-
-The gate requires an independently reviewed, closed design task before dependent
-feature implementation. Ready local fixes with explicit acceptance have a narrow
-exemption. It checks traceability/current evidence, not whether the design is fun
-or whether all semantics are correct. Human judgement and independent review remain.
-
-Game Designer is now active by default. Design-review findings must include
-`acceptanceImpact` (`none`, `false-pass`, `missing-coverage`, `authority-gap`).
-Unresolved non-none impacts block PASS even when labelled MEDIUM/LOW or ACCEPTED.
-Use fresh review records after updating; never relabel old findings to manufacture
-approval. See the source-preview acceptance report for the remaining document gaps.
+Inspect the dry-run changes before the second command. Ordinary updates preserve
+model profile, execution policy and project customizations. A project with no
+execution.json retains compatibility obligations; selecting a model profile alone
+does not migrate its execution policy. Existing autonomy settings are preserved.
+
+Changed or intentionally missing managed files are recorded in
+`.nccgs/framework-overrides.json`. Resolve pending overrides through the project's
+reviewed migration workflow; do not use `--force` just to make doctor green. Keep
+the project's canonical requirements and applicable gates. Reopen Claude Code
+after changing hooks, settings or managed agents.
+
+If update reports that NCCGS is not installed, use the exact RC `install` command
+above after checking the target. Some legacy CLI messages mention `@latest`;
+that selects the stable channel and does not select this RC.
+
+## Optional execution-policy migration
+
+After installing/updating, migrate only when the owner intends to adopt standalone.
+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
+```
+
+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.
+
+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
+```
+
+Use the actual printed UUID; remove `--dry-run` only after reviewing the preview.
+Rollback refuses changed current configuration or altered backup hashes and
+requires a compatible framework version. It restores execution configuration,
+**not a complete package downgrade**. A full recovery uses the complete project
+backup. Do not install 1.3.0 over an RC project and assume task-schema downgrade
+is safe. Caught migration failures restore captured configuration; an OS kill is
+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"
+```
+
+Use `/status` in Claude Code to inspect obligations. Use `/migrate-project` when
+the installer/doctor reports project migration or override review is required.
+Installation and doctor checks prove package/setup integrity, not Claude execution,
+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.

package/VERSION

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

package/docs/BOUNDED-REPAIR.md

@@ -1,4 +1,4 @@
-# Bounded source repair — unreleased preview
+# Bounded source repair — 2.0 RC
 
 Read the [complete bounded repair protocol](../.claude/nccgs/protocols/bounded-repair.md).
 It is installed in every project at `.claude/nccgs/protocols/bounded-repair.md`,

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

@@ -1,60 +1,58 @@
-# Hướng dẫn migrate và sử dụng NCCGS 1.4
+# Hướng dẫn cài đặt và sử dụng NCCGS 2.0 RC
 
-Đọc [hướng dẫn vận hành 1.4](NCCGS-1.4.md) trước khi bắt đầu task. Luồng mặc định:
-Astra lập kế hoạch/tài liệu → Sonnet/medium (FAST) hoặc Opus 5.5/medium (STANDARD), high (CONTROLLED) triển khai → Fable/high review →
-report cho Astra → Astra kiểm tra → bạn nghiệm thu.
+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).
 
-## Cài hoặc nâng cấp
+## Cài mới vào bản sao dự án
 
-Trong từng Unity project, chạy `npx nccgs@latest update --model-profile astra-claude
---dry-run`. Đọc kết quả, bỏ `--dry-run` để áp dụng, rồi chạy `npx nccgs@latest doctor`.
-Dùng CLI `scripts/cli.mjs` với `--project <UnityProject>` nếu cài từ mã nguồn.
-Dùng `install` thay `update` nếu chưa cài. Update giữ profile hiện tại nếu không
-truyền `--model-profile`. Cần Node.js 18+ và Claude Code tương thích các model.
+Cần Node.js 18+, Claude Code và Unity project có Assets, Packages, ProjectSettings.
+Chức năng điều khiển Unity cần thêm Editor/CLI phù hợp. Thay đường dẫn ví dụ bằng
+dự án của bạn; đọc kết quả xem trước rồi mới áp dụng:
 
-## Astra chuẩn bị migration
+```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"
+```
 
-Astra kiểm tra tài liệu chuẩn, `.nccgs/project.yaml`, yêu cầu kiểm chứng, artifact
-và manual gate đang có. Giữ nguyên các bảo đảm hiện hành; chỉ giảm gate khi bạn đã
-quyết định rõ ràng.
+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.
+Cài mới mặc định dùng Claude Code standalone, không yêu cầu Astra/Fable. Dự án cũ
+vẫn giữ nghĩa vụ đã cấu hình; không tự bỏ một bước duyệt chỉ vì cài RC.
 
-Với policy cũ chứa `profile_contracts`, chuyển sang tham chiếu
-`pipeline_policy: .claude/nccgs/pipeline.json`. Map đầy đủ nghĩa vụ của dự án vào
-`.nccgs/gates.json` và điền hash project policy đã kiểm tra. Sau đó cung cấp plan
-migration cho Claude. Không tự thay model/effort của route đã chọn hoặc Fable trong profile này.
+## Dự án đã cài NCCGS
 
-Claude chạy `/migrate-project` theo plan của Astra, xử lý override đã được phân tích,
-kiểm chứng, rồi qua Fable review. Tùy chỉnh local được bảo toàn để review; không dùng
-`--force` chỉ để làm biến mất cảnh báo. Mở phiên Claude mới sau khi đổi cấu hình.
+Sao lưu toàn bộ dự án và dừng phiên đang chạy. Dùng `update` thay `install`, luôn
+xem `--dry-run` trên bản sao trước. Update giữ cấu hình dự án và các tùy chỉnh;
+không dùng `--force` chỉ để xóa cảnh báo. Đọc [hướng dẫn nâng cấp](../UPGRADING.md)
+để xử lý override, task đang mở, chuyển execution policy và khôi phục.
 
-## Vận hành hằng ngày
+Nâng cấp file và chuyển sang standalone là hai thao tác riêng. Nếu muốn chuyển
+execution policy, dùng `migrate-execution --to standalone --dry-run` theo hướng dẫn.
+Không tự đổi task cũ, xóa lịch sử hay đặt lại số lượt đã dùng. Sau thay hook/cấu hình,
+mở lại phiên Claude Code.
 
-Có 12 agent lõi hoạt động mặc định, 35 vai trò tùy chọn trong thư viện. Bật/tắt vai
-trò bổ sung bằng `agents --enable/--disable`; lựa chọn được giữ qua update. 36 workflow
-chỉ nạp nhánh Astra hoặc legacy tương ứng với profile hiện tại.
+## Bắt đầu một đầu việc rõ ràng
 
-Astra cung cấp plan và gate; Claude khởi tạo/bind task, triển khai và ghi bằng chứng.
-Fable review độc lập trên cùng snapshot. Chỉ sau PASS mới ghi report; Astra và bạn
-quyết định các bước cuối ngoài phiên Claude. `task close` kiểm tra toàn bộ chuỗi.
-Schema và lệnh chi tiết có trong [hướng dẫn 1.4](NCCGS-1.4.md).
+```powershell
+npx --yes nccgs@2.0.0-rc.2 run --project "D:\path\to\UnityProject"
+```
 
-Khởi tạo với `task init --risk FAST|STANDARD|CONTROLLED`; mặc định STANDARD. Giới
-hạn review tương ứng là 2/3/3, không xóa khi ghi lại implementation. Hết vòng mà
-chưa có PASS dùng được thì dừng và báo bằng chứng; chỉ quyết định gia hạn rõ ràng
-từ ngoài phiên Claude qua `task extend-review` mới cho phép review thêm. Các mốc
-context/thời gian là hướng dẫn, không phải giới hạn được tool tự thực thi.
+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
+và điều kiện nghiệm thu. NCCGS lập hợp đồng công việc, phân loại mức rủi ro, gọi
+worker phù hợp, thu bằng chứng kiểm tra và yêu cầu review độc lập trước khi đóng.
 
-Chỉ gọi task scout khi thiếu thông tin; giữ một đầu mối triển khai. Đủ tiêu chí,
-test qua và không còn blocker thì bàn giao, không thêm phạm vi suy đoán. Chỉ chạy
-lại kiểm tra khi input đổi, có lỗi hoặc có bằng chứng mới. Câu hỏi chủ quan cần
-chuyển thành bản chơi thử để bạn đánh giá.
+- `/work`: triển khai thay đổi.
+- `/design`: làm rõ thiết kế/yêu cầu; tính năng có design gate phải được review trước.
+- `/audit`: kiểm tra mà không sửa source.
+- `/test`, `/review`: kiểm chứng và review theo hợp đồng.
+- `/status`: xem trạng thái, bằng chứng và việc còn chặn.
 
-Sau nâng cấp, task cũ thiếu risk/route/review budget phải tạo lại dưới ID mới và
-ghi bằng chứng mới; giữ bản cũ làm lịch sử, không tái sử dụng approval cũ.
+Có 47 vai trò trong thư viện, 13 vai trò bật mặc định. FAST yêu cầu Sonnet/medium;
+STANDARD Opus/medium; CONTROLLED Opus/high; reviewer Opus/high. Đây là cấu hình
+mong muốn, không phải bằng chứng model thực chạy. Chỉ gọi chuyên gia khi cần.
 
-`/status` đọc trạng thái và gate còn thiếu. Cấu hình model/effort yêu cầu được phân
-biệt với quan sát runtime. Thiếu bằng chứng effort thực chạy thì task chưa đủ điều
-kiện bàn giao. Report là file; NCCGS chưa tự gửi giữa ứng dụng.
-
-Các profile `quality`, `balanced`, `inherit` giữ quy trình cũ trong từng
-`references/legacy.md`. Chọn chúng là chủ động dùng luồng legacy.
+Đạ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.

package/docs/NCCGS-1.3.md

@@ -1,3 +1,8 @@
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
+
 # NCCGS 1.3 — tài liệu phiên bản trước
 
 Hướng dẫn đang dùng đã chuyển sang [NCCGS 1.4](NCCGS-1.4.md). Đường dẫn này được

package/docs/NCCGS-1.4.1.md

@@ -1,3 +1,8 @@
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
+
 # NCCGS 1.4.1 — reliable inputs and evidence
 
 This patch strengthens installation, verification and historical evidence. It keeps

package/docs/NCCGS-1.4.md

@@ -1,3 +1,8 @@
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
+
 # NCCGS 1.4 — chọn model theo rủi ro và giới hạn vòng review
 
 NCCGS dùng một nguồn cấu hình tại `.claude/nccgs/pipeline.json`:

package/docs/NCCGS-1.5-IMPLEMENTATION-PLAN.md

@@ -1,4 +1,7 @@
-<!-- Historical 1.5 development document. Current release scope and limitations are in the package README.md and CHANGELOG.md. -->
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
 
 # Kế hoạch triển khai NCCGS 1.5 và đánh giá điều kiện phát hành 2.0
 

package/docs/NCCGS-1.5-PILOT.md

@@ -1,4 +1,7 @@
-<!-- Historical 1.5 development document. Current release scope and limitations are in the package README.md and CHANGELOG.md. -->
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
 
 # Claude Code pilot and benchmark protocol
 

package/docs/NCCGS-1.5.md

@@ -1,4 +1,7 @@
-<!-- Historical 1.5 development document. Current release scope and limitations are in the package README.md and CHANGELOG.md. -->
+> Historical development/reference document. Version, status, commands and plans
+> below describe their original scope, not the current package defaults. Read
+> [current release guidance](RELEASE-STATUS.md) before use. Research/benchmark proposals
+> do not automatically add requirements to a delivery contract.
 
 # NCCGS 1.5 preview — implementation and operation
 

package/docs/PHASE-1-OPERATIONS.md

@@ -1,8 +1,8 @@
 # Phase 1: durable verification and bounded continuation
 
-This is the phase-1 maintenance change to NCCGS 1.5 preview. It does not promote
-the framework to stable, change model routing, implement games, or change the frozen
-three-track projects. Native Claude validation is a separate release gate.
+These verification and continuation mechanisms originated in the 1.5 preview
+and are included in 2.0 RC. Historical test descriptions below retain their original
+scope. See [current release status](RELEASE-STATUS.md) for completed and pending checks.
 
 ## Run a verification once
 

package/docs/PHASE-2-OPERATIONS.md

@@ -1,8 +1,8 @@
 # Phase 2: measured acceptance and a protected repair cycle
 
-This source patch remains NCCGS 1.5 preview. It changes standalone task gates and
-dispatch accounting. It does not tune a game, change model routing, promote a release,
-or rewrite the frozen Unity evaluations.
+These acceptance and dispatch mechanisms originated in the 1.5 preview and are
+included in 2.0 RC. They do not tune a game or rewrite frozen evaluations. See
+[current release status](RELEASE-STATUS.md) for validation scope.
 
 The owner revised the evaluation scope on 2026-10-04: NCCGS must support delivery
 from brief through implementation, testing and acceptance. Product balance research

package/docs/PROJECT-POLICY.md

@@ -8,7 +8,8 @@ verification, closure, or Unity execution for the project.
 
 - project stage and platforms;
 - enabled departments and bounded orchestration;
-- `astra-claude`, `quality`, `balanced`, or `inherit` model profile and fallback policy;
+- execution policy and external/manual acceptance obligations;
+- `claude-standalone`, `astra-claude`, `quality`, `balanced`, or `inherit` model profile and fallback policy;
 - canonical sources for product, design, architecture, planning, art, narrative,
   audio, and release;
 - protected/user-owned/generated paths and hand-tuned settings;
@@ -19,13 +20,16 @@ verification, closure, or Unity execution for the project.
 
 ## Model policy
 
-The default `astra-claude` profile assigns planning and canonical documents to Astra,
-FAST implementation to Sonnet/medium, STANDARD to Opus 5.5/medium, CONTROLLED to Opus 5.5/high, and independent review to Fable/high.
-The report is handed to Astra only after Fable PASS; Astra checks it before Product
-Owner acceptance. All these gates apply even to FAST work and lean closure. See
-[the protocol](../.claude/nccgs/protocols/astra-claude.md). No silent inherited model
-or lower effort may satisfy a required stage. Legacy profile selection explicitly
-opts out of this chain and ordinary updates preserve the existing selection.
+New installations use standalone execution with `claude-standalone`: Sonnet/medium
+for FAST, Opus/medium for STANDARD, Opus/high for CONTROLLED and Opus/high for
+independent review. These are requested aliases and effort, not runtime observations.
+Execution policy lives separately in `.nccgs/execution.json`; changing a model
+profile does not remove task gates or migrate compatibility execution.
+
+Existing compatibility projects selecting `astra-claude` retain Astra planning,
+Fable review and their configured approval chain. See the
+[compatibility protocol](../.claude/nccgs/protocols/astra-claude.md). Ordinary
+updates preserve existing selections and obligations.
 
 Use `quality` when result quality is primary and all model tiers are available. Use
 `balanced` when leadership coordination does not need Opus by default. Use `inherit`
@@ -43,11 +47,12 @@ translate YAML conditions: Astra must preserve and map all existing safeguards.
 See [task gates](../.claude/nccgs/protocols/task-gates.md) for evidence formats.
 
 `contract.taskTiers` selects each task's implementation class and review limit.
-`task init --risk` defaults to STANDARD; FAST allows two recorded reviews and
+Compatibility `task init --risk` defaults to STANDARD; standalone intake uses its
+classifier and explicit risk evidence. FAST allows two recorded reviews and
 STANDARD/CONTROLLED allow three. Re-recording implementation does not reset the
 counter. Only an explicit external `task extend-review` decision adds rounds.
-An exhausted budget is not acceptance. Context and elapsed-time budgets guide
-planning and escalation but are not enforced runtime caps.
+An exhausted budget is not acceptance. Planning estimates do not extend configured
+dispatch/session/check limits. Read the active execution policy and actual ledger.
 
 ## Canonical sources and context
 

package/docs/RELEASE-STATUS.md

@@ -0,0 +1,42 @@
+# NCCGS 2.0 RC release status
+
+Current candidate: **2.0.0-rc.2**. 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. |
+| 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. |
+| 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. |
+
+## Public package boundary
+
+The package contains the CLI, framework roles/protocols/hooks, project scaffold,
+public guidance, tests and attributed third-party assets. Root and installed
+MEMORY.md contain portable operating principles only. Project-specific permission
+statements, account/session details, provider budgets, raw game/evaluation files
+and internal closeout history are retained outside the npm package.
+
+Historical 1.3/1.4/1.5 documents are explicitly labeled as historical. Their old
+version names, pending states, proposed research and compatibility commands do not
+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
+
+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).
+
+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.

package/docs/WORKFLOWS.md

@@ -1,12 +1,15 @@
-# NCCGS workflows
+# NCCGS workflows — 2.0 RC
 
-The default `astra-claude` profile applies the
-[Astra/Claude handoff protocol](../.claude/nccgs/protocols/astra-claude.md) to every
-workflow below. Astra owns planning and documents; Claude implements with
-Sonnet/medium for FAST, Opus 5.5/medium for STANDARD, or Opus 5.5/high for CONTROLLED; Fable/high independently reviews before the report goes to Astra.
-Astra checks the report and the Product Owner accepts before DONE. Each dispatcher
-loads only `references/astra.md` or `references/legacy.md` for the selected profile.
-Task records and executable gates follow the [1.4 guide](NCCGS-1.4.md).
+New installations use standalone Claude Code execution with the claude-standalone
+model profile. The coordinator owns intake, planning, dispatch, verification and
+reporting; a separate Claude Code reviewer owns the verdict. External/manual
+acceptance is required only by the configured policy and approved contract.
+See [standalone execution](../.claude/nccgs/protocols/standalone.md) and
+[standalone gates](../.claude/nccgs/protocols/standalone-gates.md).
+
+Existing compatibility projects retain their Astra/Fable or legacy chain; select
+obligations from execution.json before model routing. Updates do not silently
+convert those projects. See [upgrading](../UPGRADING.md).
 
 ## Risk tiers
 
@@ -16,28 +19,29 @@ Task records and executable gates follow the [1.4 guide](NCCGS-1.4.md).
 | STANDARD | Ordinary feature or coordinated change | Contract, context packet, one standard implementer, independent verification, closure; 3 review rounds |
 | CONTROLLED | Architecture, compatibility, dependency, migration, security, release | One deep implementation lead, impact/decision record, relevant specialists, rollback, full gates; 3 review rounds |
 
-`task init --risk FAST|STANDARD|CONTROLLED` records the risk and route; omission
-means STANDARD. FAST uses `nccgs-fast-implementer`; CONTROLLED uses
-`nccgs-unity-implementer` as its deep lead. Use the read-only `nccgs-task-scout`
-only when a specific fact is missing. All tiers retain Fable review, Astra checking,
-and explicit Product Owner acceptance; FAST keeps its plan/report concise.
+Standalone intake is classified conservatively; ready local fixes may use FAST,
+ordinary features STANDARD, and cross-system/high-risk work CONTROLLED. Compatibility
+tasks also support explicit risk. FAST uses nccgs-fast-implementer; CONTROLLED uses
+nccgs-unity-implementer as its deep lead. Use the read-only task scout only for a
+specific missing fact. All tiers retain independent review and applicable contract
+gates; standalone review requests Opus/high.
 
 Stop when criteria and relevant checks pass without actionable blockers. Avoid
 speculative scope expansion, duplicate reviewers, and repeated green checks.
 Rerun only for changed inputs, failures, or new evidence. Subjective questions go
 to a playable test. Exhausted review rounds require an evidence-backed stop or an
 explicit external `task extend-review`; re-recording implementation does not reset
-them. Context/time budgets are advisory and do not waive any gate.
+them. Configured dispatch, supervised session and verification limits remain effective;
+advisory planning estimates never extend them or waive a gate.
 
 ## End-to-end work
 
 ```text
-request -> Astra plan/documents and gate manifest
-  -> Claude risk/domain routing and context readiness
-  -> one-owner implementation nodes
-  -> verification evidence
-  -> independent Fable review for every code change
-  -> report -> Astra check -> Product Owner acceptance
+request -> approved contract, mode, risk and design readiness
+  -> reserved Claude Code worker with bounded ownership
+  -> verification tied to current source and contract
+  -> independent reviewer verdict
+  -> report and configured external/manual acceptance
   -> task close after all executable gates pass
 ```
 
@@ -60,15 +64,16 @@ available when a user wants a bounded workflow or output.
 
 ## Role composition examples
 
-Astra plans a gameplay feature; optional game-designer consultation may support it.
+The standalone coordinator routes feature design to the game designer and obtains
+independent design review before dependent implementation when required.
 One gameplay programmer owns implementation; a Unity systems specialist may support
 a separate bounded concern where needed, followed by verification. A UI feature
 has one UI implementation owner; UX, accessibility, or Unity UI specialists join only
 for a concrete question or distinct deliverable, followed by independent verification.
 
 CONTROLLED network-save work can enable optional technical architect, network
-programmer and security engineer roles. Fable reviews FAST, STANDARD and CONTROLLED
-code changes. Optional roles are activated explicitly; the default loads twelve roles.
+programmer and security engineer roles. The standalone reviewer reviews all three
+risk tiers. Optional roles are activated explicitly; the default loads 13 of 47 roles.
 
 ## Evidence states
 

package/package.json

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