nccgs 2.1.1 → 3.0.0-rc.2

package/.claude/skills/localization/SKILL.md

@@ -1,135 +0,0 @@
----
-name: localization
-description: "Sets up and configures Unity Localization, including locales, String/Asset Tables, CJK font support, and Addressables workflows. Use when the user wants to add languages to a project, translate UI text, support Asian (CJK) languages with TMP fonts, or mentions i18n, l10n, multilingual support, or making a game support multiple languages."
----
-
-This guide covers setting up and configuring Unity Localization, including locales, String and Asset Tables, Addressables integration, and CJK font support via Asset Tables.
-
-## 0. Package Installation Check
-Before doing anything else, verify that the Localization packages is installed. Many APIs in this skill will fail silently or throw confusing errors if the package isn't present.
-1. **Check:** Use `UnityEditor.PackageManager.Client.List(true)` to check for `com.unity.localization`.
-2. **Install:** If missing, use `Client.Add("com.unity.localization")`.
-3. **Wait:** Do not proceed until `Client.List` confirms installation.
-
-## 1. Localization Settings & Locales
-If `LocalizationEditorSettings.ActiveLocalizationSettings` is null, you must find or create it:
-1. **Find:** Use `AssetDatabase.FindAssets("t:LocalizationSettings")`. If found, load the first one and assign it to `LocalizationEditorSettings.ActiveLocalizationSettings`.
-2. **Create:** If not found, create a new instance and save it to `Assets/Localization/LocalizationSettings.asset`. Use `ScriptableObject.CreateInstance<LocalizationSettings>()` followed by `AssetDatabase.CreateAsset()`.
-3. **Activate:** Set `LocalizationEditorSettings.ActiveLocalizationSettings = settings`.
-4. **Locales:** Ensure locales (en, fr, de, etc.) exist. Create them if missing and add them to settings using `LocalizationEditorSettings.AddLocale(locale)`.
-
-## 2. Modifying Localization Tables
-Programmatic changes to String or Asset tables require notification to the Editor.
-Always create the required asset tables, unless there is already an existing one in the project.
-
-### **Safe Population Pattern**
-When populating tables from a dataset, match by `Locale.Identifier.Code` explicitly. The order of `GetLocales()` is not guaranteed to match your input data array — assuming it does will cause silent data mismatches that are very hard to debug.
-For **Asset Tables**, use the GUID of the asset: `table.GetEntry(sharedId) ?? table.AddEntry(sharedId, guid);`.
-
-### **Refresh & Notification**
-After any modification (adding keys, updating values), notify the Editor so it can refresh its internal state. Skipping this will leave the Editor showing stale data until the next reimport.
-1. Call `EditorUtility.SetDirty(collection)`, `EditorUtility.SetDirty(collection.SharedData)`, on each modified `Table`.
-2. **Unity 6+ Notification:** `LocalizationEditorSettings.EditorEvents.RaiseCollectionModified(sender, collection);`
-3. Always call `AssetDatabase.SaveAssets()` at the end.
-
-## 3. UI Localization and Layout
-### **Namespacing & Conflicts**
-- **Always qualify names:** Use `UnityEngine.UI.Image`, `UnityEngine.UI.VerticalLayoutGroup`, `UnityEngine.UI.ScrollRect`, `UnityEngine.UI.Mask`, `UnityEngine.UI.CanvasScaler`, `UnityEngine.UI.GraphicRaycaster`, `UnityEngine.UI.ContentSizeFitter`, `UnityEngine.UI.LayoutRebuilder`, etc. 
-- `UnityEngine.UI` is both a namespace and a class container, so unqualified names produce `CS0118` (namespace used like a type). Full qualification avoids this entirely.
-- **Single Instance:** Always check `GameObject.Find("YourCanvasName")` and destroy the old one before creating a new one.
-- **No Debug Dropdown:** NEVER create a manual UI dropdown or debug menu to change the locale. The Localization package has a built-in way to do this properly (e.g., via the "Localization Scene Controls" window for previews).
-
-### **Localized String Events (Robust Binding)**
-- **Check Component Type:** Identify if the target is `TextMeshPro` or legacy `UnityEngine.UI.Text`.
-- **Bind Correctly:** add the public `UnityEngine.Localization.Components.LocalizeStringEvent`
-  component and wire it yourself — set `StringReference` to the table entry, then add an
-  `OnUpdateString` listener that assigns the value to the text component (`TMP_Text.text` for
-  TextMeshPro, `UnityEngine.UI.Text.text` for legacy Text).
-
-  Do **not** reflect into `UnityEditor.Localization.Plugins.TMPro.LocalizeComponent_TMPro` or its
-  UGUI counterpart. Those are `internal` (measured on Localization 1.5.12), so reaching them means
-  routing around access control to reach an API Unity makes no stability commitment about — it can
-  change or disappear in any package release. `LocalizeStringEvent` is public and does the same job
-  with the wiring made explicit.
-- **Layout Rebuild:** After setting localized text or populating a list, call `UnityEngine.UI.LayoutRebuilder.ForceRebuildLayoutImmediate(parentTransform)` to ensure dimensions update.
-
-## 4. Asian Language Font Support (CJK)
-Avoid TMP Fallback Fonts for CJK locales. Use **Asset Table Font Swapping** for each specific locale instead — fallbacks are unreliable and hard to debug when glyphs are missing.
-
-1. **Use locale-specific fonts:** Western fonts like Arial or Liberation Sans don't contain CJK glyphs, which results in "tofu" (square blocks). Always use a font designed for the target language:
-   - For **Simplified Chinese (zh-Hans)**: Use `msyh.ttc` (Microsoft YaHei) or equivalent.
-   - For **Japanese (ja)**: Use `msgothic.ttc` (MS Gothic) or equivalent.
-   - For **Korean (ko)**: Use `malgun.ttf` (Malgun Gothic) or equivalent.
-   - If system font copying fails, stop and report it. Do not substitute with a Western font.
-2. **Robust Font Creation:** Create dynamic `TMP_FontAsset` from imported fonts.
-3. **Multi-Atlas & Dynamic:** CJK character sets are too large for static atlases; a single atlas will run out of space immediately.
-   - `fontAsset.atlasPopulationMode = AtlasPopulationMode.Dynamic;`
-   - `fontAsset.isMultiAtlasTexturesEnabled = true;`
-4. **Sub-Assets:** Save atlas and material as sub-assets, or they'll be lost on reimport: `AssetDatabase.AddObjectToAsset(fontAsset.atlasTexture, fontAsset);`. 
-    - Explicitly link the material's texture: `fontAsset.material.mainTexture = fontAsset.atlasTexture;` and set both as dirty before saving.
-5. **Addressables:** Every asset referenced in an Asset Table must be marked as Addressable. 
-    - Do not reference assets inside a `Resources/` folder in an Asset Table. This causes `OperationException: Failed to load sub-asset` errors. If an asset is in `Resources/`, copy it to `Assets/Fonts/` or similar before making it Addressable.
-    - If a font asset is deleted and recreated, the new GUID must be manually updated in the Asset Table and re-added to Addressables.
-6. **Specialized Types:** For TextMesh Pro font swapping, prefer `LocalizedTmpFont` over `LocalizedAsset<TMP_FontAsset>` to avoid implicit conversion errors.
-7. **Build Requirement:** After updating Asset Tables or Addressable groups, trigger a build: `AddressableAssetSettings.BuildPlayerContent();`.
-
-### **Verification Step**
-Before concluding any CJK localization task:
-1. **The Tofu Check:** Switch the editor locale to `zh-Hans`, `ja`, and `ko`. Inspect the UI. If any characters appear as squares (tofu), the font setup has FAILED.
-2. **Asset Table Check:** Verify that the `AssetTable` for the CJK locale points to the correct CJK `TMP_FontAsset`, NOT a default Western font.
-3. **Multi-Atlas Check:** Confirm `isMultiAtlasTexturesEnabled` is `true` on the CJK font assets.
-
-## 5. Automatic Layout (UGUI)
-- **Parent:** `VerticalLayoutGroup` with `Child Control Height: True`, `Child Force Expand Height: False`.
-- **Labels:** Each label must have a `ContentSizeFitter` set to `Vertical Fit: Preferred Size`.
-- **TMP:** Set `Enable Word Wrapping: True` and `Overflow: Overflow`.
-
-### Notes when translating an existing project
-- **Minimal Code Changes**: Never modify code unrelated to localization. Use a static helper class (e.g., `L10n`) to wrap `LocalizationSettings.StringDatabase.GetLocalizedString` for easy injection into existing scripts.
-- **Robust Mapping Strategy**: When mapping existing UI text to keys, sort keys by string length (descending) and match longest strings first. This prevents short strings (like "NO") from matching parts of longer sentences. Use case-insensitive matching where appropriate.
-- **Component Event Listeners**: When setting up `LocalizeStringEvent` via script, avoid `UnityEventTools.AddPersistentListener` as it often fails to set the dynamic mode (Mode 0) correctly. 
-Instead, use the **SerializedObject Pattern** described in Section 3 to explicitly set `m_MethodName` to `set_text` and `m_Mode` to `0`. Persistent listeners **MUST** point to a method on a `UnityEngine.Object`; lambdas will fail.
-- **Initialization & Refresh**: 
-    - `LocalizationEditorSettings.CreateStringTableCollection` expects a **directory path** (e.g., `Assets/Localization`), not a full asset path.
-    - Always call `lEvent.RefreshString()` after assigning a `LocalizedString` reference programmatically to update the UI immediately.
-    - Ensure keys are added to **all** tables in a collection (en, de, ja, etc.) to avoid "No translation found" errors.
-- **Namespaces & Linq**: Always include `using System.Linq;` when searching collections and `using UnityEngine.Localization;` when working with locales or tables.
-- **Verification**: After modifying tables or addressables, run `AddressableAssetSettings.BuildPlayerContent()` and switch the Editor locale to verify changes. Check `LocalizationSettings.Instance` status after activation.
-- **Smart Strings**: Set up smart strings where needed. Inspect the context of each string by taking the entire UI it is on, and any scripts that affect it, into account. Set the context on the string table to ensure translations make sense.
-
-## 6. Recommended Translation Strategy
-To efficiently translate an existing project, follow this multi-step workflow:
-
-1. **Extraction & Component Setup:**
-   - **Find all occurrences:** Scan all scenes and prefabs for strings in code and UI components (Legacy `UnityEngine.UI.Text`, `TextMeshPro`, buttons, etc.).
-   - **Shared Table:** Create a central String Table (e.g., `UIStrings`) with the base language and a "Context" column for each key to guide translators.
-   - **Attach Components:** For every UI element found, attach a `LocalizeStringEvent` (for text) and a `LocalizedFont` helper (for font swapping).
-   - **Validation:** Ensure these components are set up with persistent listeners (`EditorAndRuntime`) so they update in the Editor immediately when the locale changes.
-
-2. **Context-Aware Translation:**
-   - **Translate:** Once the table is populated, provide translations for each locale.
-   - **Context is King:** Always refer to the "Context" column or inspect the UI layout to ensure the translation fits the intended meaning and space.
-   - **Grammar & Tone:** Ensure the tone matches the game's style. For example, use imperative verbs for buttons (e.g., German: "Lauf!" instead of "Laufen") and correct pluralization for labels (e.g., "Punkte" instead of "Punkt").
-
-3. **Quality Assurance (QA):**
-   - **Scene Controls:** Use `Window > Asset Management > Localization Scene Controls` or script: `LocalizationSettings.SelectedLocale = LocalizationSettings.AvailableLocales.GetLocale("de");`.
-   - **Visual Inspection:** Methodically inspect every prefab and scene in the base language and all target languages.
-   - **Layout Fit:** Check for text overflows or "tofu" (missing glyphs). Adjust font sizes or use `ContentSizeFitter` if strings are too long.
-
-
-## API Reference
-For detailed API usage, common namespace conflicts, Addressables patterns, and font repair steps, see [references/api-notes.md](references/api-notes.md).
-
-## 7. Accelerated Localization Workflow
-To localize an entire project efficiently, use a batch processing script that handles all scenes in one pass.
-
-**Ask before acting:** Before running any batch operation, confirm with the user:
-> "This will open every scene in the project, attach `LocalizeStringEvent` components, and save all modified scenes. This cannot be undone automatically. Shall I proceed?"
-
-Only proceed once the user has confirmed. The batch processor template is in [resources/L10nBatchProcessor.cs](resources/L10nBatchProcessor.cs).
-
-### **Technical Tips for Speed**
-- **Table References:** Use `TableReference` names (strings) instead of GUIDs — they are easier to read and maintain.
-- **Batch Refresh:** Use `LocalizationSettings.Instance.ForceRefresh()` after modifications to force the UI to update in the editor.
-- **Font Swap Automation:** Create the `GameAssets` table once and use a script to re-assign `LocalizeFontEvent` to all labels in one pass.
-- **LocalizedFontAsset component:** The template is in [resources/LocalizedFontAsset.cs](resources/LocalizedFontAsset.cs).

package/.claude/skills/localization/resources/L10nBatchProcessor.cs

@@ -1,69 +0,0 @@
-using UnityEngine;
-using UnityEditor;
-using UnityEditor.SceneManagement;
-using UnityEngine.UI;
-using UnityEditor.Events;
-using UnityEngine.Events;
-using UnityEngine.Localization.Components;
-using System.Collections.Generic;
-
-/// <summary>
-/// Batch-processes all scenes in the project, attaching LocalizeStringEvent components
-/// to every Text element whose content matches a key in the provided mapping.
-///
-/// Only call LocalizeAll() after confirming with the user — it modifies and saves every scene.
-/// </summary>
-public static class L10nBatchProcessor
-{
-    public static void LocalizeAll(Dictionary<string, string> mapping, string table)
-    {
-        string[] scenes = AssetDatabase.FindAssets("t:Scene");
-        foreach (var guid in scenes)
-        {
-            var path = AssetDatabase.GUIDToAssetPath(guid);
-            var scene = EditorSceneManager.OpenScene(path, OpenSceneMode.Single);
-            LocalizeHierarchy(mapping, table);
-            EditorSceneManager.MarkSceneDirty(scene);
-            EditorSceneManager.SaveScene(scene);
-        }
-    }
-
-    static void LocalizeHierarchy(Dictionary<string, string> mapping, string table)
-    {
-        var allText = Object.FindObjectsByType<Text>(FindObjectsInactive.Include, FindObjectsSortMode.None);
-        foreach (var text in allText)
-        {
-            foreach (var kvp in mapping)
-            {
-                if (!text.text.Contains(kvp.Key)) continue;
-
-                var lse = text.gameObject.GetComponent<LocalizeStringEvent>()
-                    ?? text.gameObject.AddComponent<LocalizeStringEvent>();
-                lse.StringReference = new UnityEngine.Localization.LocalizedString(table, kvp.Value);
-
-                // Wire the listener through the public UnityEventTools API. The persistent-call
-                // fields could be written directly through SerializedObject instead, but those
-                // are private serialized names with no compatibility guarantee — and it isn't
-                // necessary. A delegate to Text's public `text` setter, handed to
-                // AddPersistentListener, serializes to exactly the same thing: target = the Text
-                // component, method = set_text, mode = EventDefined (dynamic), call state =
-                // EditorAndRuntime. Measured on Unity 6000.5.7f1.
-                //
-                // The setter has no C# method-group name, so the delegate is built by name.
-                // That is reflection over a *public* member, which is fine; reaching for the
-                // private m_* fields would not be.
-                var setText = (UnityAction<string>)System.Delegate.CreateDelegate(
-                    typeof(UnityAction<string>), text, "set_text");
-
-                for (int i = lse.OnUpdateString.GetPersistentEventCount() - 1; i >= 0; i--)
-                {
-                    UnityEventTools.RemovePersistentListener(lse.OnUpdateString, i);
-                }
-                UnityEventTools.AddPersistentListener(lse.OnUpdateString, setText);
-
-                EditorUtility.SetDirty(lse);
-                break;
-            }
-        }
-    }
-}

package/.claude/skills/localize-game/SKILL.md

@@ -1,22 +0,0 @@
----
-name: localize-game
-description: Plans, implements, or reviews internationalization and localization across strings, fonts, layout, input, assets, culture, and LQA using the project's supported locales.
-allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Agent, AskUserQuestion, WebSearch, WebFetch
----
-
-# Localize Game
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/localize-game/references/astra.md

@@ -1,27 +0,0 @@
-# Localize Game — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Plans, implements, or reviews internationalization and localization across strings, fonts, layout, input, assets, culture, and LQA using the project's supported locales.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-For code changes: task init with Astra's plan and --risk FAST|STANDARD|CONTROLLED
-(default STANDARD), bind the session, and use the recorded implementation route.
-Keep one accountable implementer; use the scout only for missing facts. Implement,
-run relevant checks, and run task check --id ID --target review before requesting
-independent Fable review. Keep only one Fable review in flight for the task. Fix actionable findings
-within scope and re-review only within the remaining task budget. Re-recording
-implementation does not reset that budget. Exhaustion without a usable PASS means
-stop with evidence for an explicit external decision, never automatic approval.
-After task check --target report passes, write and record the report for Astra.
-Stop at AWAITING_ASTRA_CHECK. Astra checking and explicit Product Owner acceptance
-happen outside the Claude implementation session. FAST uses concise plan/report
-artifacts and keeps the full acceptance chain.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/localize-game/references/legacy.md

@@ -1,7 +0,0 @@
-# Localize Game
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Read locale scope, canonical terminology, UI/content sources, existing localization architecture, and platform constraints. Route writing, UI, accessibility, content, and Unity specialists as needed. Preserve stable string IDs, context, placeholders, plurals, fallback, font coverage, layout expansion, and extraction determinism. Use the official `localization` Unity Skill for Unity operation mechanics. Do not invent locale scope or approve translations without review evidence.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/migrate-project/SKILL.md

@@ -1,22 +0,0 @@
----
-name: migrate-project
-description: Reviews, plans, applies, and verifies adoption or upgrade of NCCGS in an existing Unity project. Preserves canonical truth, ownership, closure safeguards, model policy, local settings, and rollback while replacing obsolete workflow machinery.
-allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Agent, AskUserQuestion
----
-
-# Migrate project
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/migrate-project/references/astra.md

@@ -1,30 +0,0 @@
-# Migrate project — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Domain objective: Reviews, plans, applies, and verifies adoption or upgrade of NCCGS in an existing Unity project. Preserves canonical truth, ownership, closure safeguards, model policy, local settings, and rollback while replacing obsolete workflow machinery.
-
-Work only inside the supplied plan and assigned write set. Activate an optional
-specialist with the agents command only when its domain is required. Keep one writer
-per path and use official Unity Skills for Editor/assets/runtime operations.
-
-For code changes: task init with Astra's plan and --risk FAST|STANDARD|CONTROLLED
-(default STANDARD), bind the session, and use the recorded implementation route.
-Keep one accountable implementer; use the scout only for missing facts. Implement,
-run relevant checks, and run task check --id ID --target review before requesting
-independent Fable review. Keep only one Fable review in flight for the task. Fix actionable findings
-within scope and re-review only within the remaining task budget. Re-recording
-implementation does not reset that budget. Exhaustion without a usable PASS means
-stop with evidence for an explicit external decision, never automatic approval.
-After task check --target report passes, write and record the report for Astra.
-Stop at AWAITING_ASTRA_CHECK. Astra checking and explicit Product Owner acceptance
-happen outside the Claude implementation session. FAST uses concise plan/report
-artifacts and keeps the full acceptance chain.
-
-Default to full inventory/apply/verify using Astra's existing migration plan.
-Preserve project overrides and backups; missing planning inputs go back to Astra.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/migrate-project/references/legacy.md

@@ -1,19 +0,0 @@
-# Migrate project
-
-Treat brownfield adoption and migrations explicitly requested by the installer as CONTROLLED work. Read the complete [migration procedure](../references/procedure.md). Default to `full` when no mode is given. Do not require migration merely because NCCGS was updated when the installer reported `No project migration required`.
-
-When `.nccgs/framework-overrides.json` exists, treat every `pending_review` entry as preserved project truth, not installer debris. Compare the project version with the current NCCGS version, keep or rebase the customization deliberately, and record the decision in the migration plan. Only after every pending item has been reviewed and the final bytes or intentional absence are correct, run `node .claude/nccgs/tools/approve-overrides.mjs --project . --approve-pending`. Never approve first to make `doctor` green.
-
-## Modes
-
-- `full` (default): run review, plan, apply, and verify in one invocation. Continue across phase boundaries without asking for ceremonial approval. Pause only for an unresolved Product Owner decision, destructive action, external side effect, or authority outside the current request.
-- `review`: read-only inventory and KEEP/ADAPT/MIGRATE/DEPRECATE/REMOVE/MISSING classification.
-- `plan`: write a dated reversible plan and proposed schema-2 policy without overwriting project truth.
-- `apply`: execute an approved plan in validated batches with backups.
-- `verify`: prove policy, routing, hooks, Unity integration, evidence, closure, and a representative work path.
-
-Migration decisions must cover canonical sources, ownership/protected paths, architecture, Unity tooling, model profile/fallback, enabled departments, context packets, verification baselines, closure safeguards, Git tracking, local settings, preserved framework overrides, obsolete global skills, and rollback.
-
-In `full` mode, write the plan before applying it, preserve the same evidence and rollback guarantees as the individual modes, and stop safely if review finds a decision that would materially change project truth. A reversible plan created within the same invocation is approved for in-scope application unless project policy explicitly requires a separate approval.
-
-Never remove reports, registers, checklists, user settings, source assets, or legacy instructions until their live purpose is mapped and the Product Owner approves the replacement. Do not infer canon from code. Return batches, commits, preserved evidence, unresolved decisions, rollback, and final migration state.

package/.claude/skills/migrate-project/references/procedure.md

@@ -1,96 +0,0 @@
-# Brownfield migration procedure
-
-## Full run
-
-`/migrate-project` without a mode executes Review -> Plan -> Apply -> Verify as one
-CONTROLLED operation. Keep the phase boundaries in the migration record, but do not
-make the user invoke each phase separately. Continue automatically when changes are
-reversible, backed up, within the requested adoption/migration scope, and do not
-alter unresolved project truth. Stop before apply only when review exposes a genuine
-Product Owner decision, destructive action, external side effect, or authority gap.
-
-If the NCCGS installer and current schema indicate that an ordinary framework update
-requires no project migration, report that fact and do not manufacture migration work.
-
-## Review
-
-1. Inspect repository status and project root without modifying it.
-2. Inventory Unity version, packages, scenes/assets, code assemblies, tests, build
-   targets, CLI/Pipeline setup, and installed Unity Skills.
-3. Locate current project instructions, canonical design/architecture/planning,
-   requirement/story registries, QA evidence, session state, hooks, agents, skills,
-   closure/completion artifacts, safety checklists, and release machinery.
-4. Identify conflicts in authority, duplicated Unity instructions, unsafe ownership,
-   token-heavy context loading, redundant reports, stale global routing signals,
-   machine-local settings, and legacy engine support.
-5. Classify each relevant artifact KEEP/ADAPT/MIGRATE/DEPRECATE/REMOVE/MISSING.
-6. Determine whether closure should be `lean`, `linked`, or `strict`. Preserve the
-   strongest active safeguard until the PO explicitly accepts a weaker model.
-7. Determine the project model profile, enabled departments, permitted fallback,
-   orchestration depth/parallelism, context-packet locations, and hook compatibility.
-8. If `.nccgs/framework-overrides.json` exists, inspect every override. Diff its
-   preserved bytes or intentional absence against the installed upstream version,
-   and distinguish a still-needed project policy from a customization now supplied
-   by NCCGS. Line-ending-only differences are not overrides.
-
-## Plan
-
-Create `.nccgs/migrations/<date>-migration-plan.md` with:
-
-- current-state summary and canonical-source map;
-- proposed `.nccgs/project.yaml` values;
-- proposed model/department/orchestration/context policy and any compatibility
-  fallback needed for the user's Claude Code subscription or context mode;
-- proposed closure mode, canonical record, linked artifacts, completion rules, and
-  any legacy safeguard that must block DONE;
-- ordered reversible batches and dependencies;
-- exact broad/irreversible decisions requiring PO authority;
-- backup/rollback method;
-- an explicit KEEP/REBASE/RETIRE decision for every pending framework override;
-- validation for each batch and final end-to-end proof.
-
-Prioritize authority and policy conflicts, then model/routing conflicts, Unity
-integration, canon mapping, ownership, context isolation, closure safeguards,
-traceability/evidence, lifecycle hooks, workflow replacement, and cleanup.
-
-## Apply
-
-- Start from a known repository status and preserve unrelated changes.
-- Apply one coherent batch, inspect diff, run its validation, and update migration
-  status before continuing.
-- Never rewrite project canon from implementation inference without PO acceptance.
-- Do not delete or collapse legacy completion reports/registers/checklists until the
-  configured closure model preserves their safety purpose and the PO approves it.
-- Back up removals and conflicting framework files. Do not remove project assets or
-  source merely because their folder layout differs from NCCGS examples.
-- Preserve `.claude/settings.local.json` and other machine-specific files. Merge the
-  managed hook fragment into shared settings without erasing unrelated permissions,
-  hooks, or local paths.
-- Do not leave two active agents/skills advertising mutually exclusive Unity
-  execution bridges. Disable obsolete global routing signals outside the repository
-  through an explicit user action.
-- Preserve pending framework overrides while reviewing them. Rebase each retained
-  override onto the newly installed upstream content when needed. After all entries
-  match the migration decisions, run
-  `node .claude/nccgs/tools/approve-overrides.mjs --project . --approve-pending`.
-  Approval records the final hashes; it is the last apply step, never a substitute
-  for the review.
-
-## Verify
-
-Check installation integrity, schema-2 project policy, model profile/fallback,
-role/workflow catalogs, bounded delegation, hook health, context packet freshness,
-canonical map, requirements/state, Unity Skills integrity, CLI/Pipeline operation,
-relevant tests, runtime evidence, and subjective-gate routing. Verify that required
-linked artifacts block DONE in `linked` or `strict` mode. Use a small representative
-task or dry run when product changes are not authorized. Run `npx nccgs@latest doctor`
-and require zero pending framework overrides before declaring migration complete.
-
-## Astra-owned planning exception
-
-Under astra-claude, Astra owns the migration plan, policy decisions, and canonical
-document changes. Claude may inventory and implement a supplied migration plan;
-full must pause at missing Astra inputs instead of creating a replacement plan.
-Code changes use the task's risk-selected route (CONTROLLED migration: Opus 5.5/high),
-Fable review within the recorded round budget, a report to Astra, Astra checking,
-and explicit Product Owner acceptance before DONE. See the profile handoff protocol.

package/.claude/skills/milestone-review/SKILL.md

@@ -1,22 +0,0 @@
----
-name: milestone-review
-description: Evaluates milestone progress, scope, quality, risk, evidence, and release trajectory against approved goals without disguising incomplete work as percentage completion.
-allowed-tools: Read, Glob, Grep, Bash, Agent
----
-
-# Milestone Review
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/milestone-review/references/astra.md

@@ -1,12 +0,0 @@
-# Milestone Review — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Astra owns this workflow and its canonical outputs. Claude only inspects relevant
-inputs and returns factual constraints, missing information, or proposed amendments.
-Do not create a replacement plan/document or sign off as Astra.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/milestone-review/references/legacy.md

@@ -1,7 +0,0 @@
-# Milestone Review
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Remain read-only unless asked to update records. Compare approved milestone outcomes with feature closures, evidence, defects, dependencies, PO gates, and repository/build state. Report achieved outcomes, incomplete gates, scope movement, forecast assumptions, top risks, and decision options. Use evidence-based confidence rather than arbitrary completion percentages.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.

package/.claude/skills/nccgs-code-review/SKILL.md

@@ -1,22 +0,0 @@
----
-name: nccgs-code-review
-description: Performs a read-only code review against requirements, architecture, Unity constraints, ownership, tests, performance, security, and regression risk.
-allowed-tools: Read, Glob, Grep, Bash, Agent
----
-
-# Code Review
-
-Resolve execution policy from .nccgs/execution.json before model routing. Missing
-execution.json means compatibility; model profile alone never removes obligations.
-
-- standalone: load the [shared standalone procedure](../../nccgs/protocols/standalone.md)
-  for this workflow, using its intake, mode, bounded domain steps and report rules.
-  Do not load the compatibility branches or inherit their external approval chain.
-- compatibility: read models.profile from .nccgs/project.yaml and load exactly one:
-  astra-claude uses [Astra/Claude procedure](references/astra.md); quality, balanced
-  or inherit uses [Legacy procedure](references/legacy.md). Existing task records
-  retain their original gates even after project execution policy changes.
-
-Unknown execution policies or model profiles are configuration errors. External
-review in standalone is off, advisory or required according to execution policy;
-configured routes do not prove actual provider model or effort.

package/.claude/skills/nccgs-code-review/references/astra.md

@@ -1,21 +0,0 @@
-# Code Review — astra-claude
-
-Read [the pipeline protocol](../../../nccgs/protocols/astra-claude.md) and
-[generated routing](../../../nccgs/routing.generated.md). Use Astra's supplied plan,
-requirements, and exact context references. Never substitute a legacy procedure.
-
-Run task check --id ID --target review before invoking the independent reviewer
-selected by pipeline.json on the final snapshot; proceed only when allowed.
-Read raw requirements, diff, affected callers, and verification evidence. Return
-PASS, CHANGES_REQUIRED, or BLOCKED with findings, severity, locations, and evidence.
-Do not fix code. BLOCKER/HIGH findings and unmet required criteria prevent PASS.
-Record the review through task record; return fixes to the implementer and review
-again after relevant changes within the task's remaining review rounds. Review is
-mandatory even for FAST work. Cover concrete distinct risks; do not expand scope
-with speculative improvements or repeat checks without changed inputs, failures,
-or new evidence. A valid recorded review consumes a round, including a negative
-verdict. Stop at exhaustion with evidence; only an explicit external extension
-permits more rounds. An existing PASS at the limit may proceed to reporting.
-
-Use [task gate commands](../../../nccgs/protocols/task-gates.md) for evidence and
-state transitions. Report outcome, evidence, pending decisions, and next owner.

package/.claude/skills/nccgs-code-review/references/legacy.md

@@ -1,7 +0,0 @@
-# Code Review
-
-Read `.nccgs/project.yaml`, `.nccgs/state.md`, and the active context packet when present. Preserve Product Owner authority and unrelated work.
-
-Read the context packet, final diff, governing decisions, affected callers, and tests. Route distinct Unity, networking, security, performance, or UI lenses when needed. Report only actionable findings with severity, exact evidence, impact, and remediation direction. Verify that tests assert requirements and that serialized/lifecycle behavior is addressed. Do not edit or praise generally; state when no material issue is found.
-
-Return outcome, evidence, affected records, blockers or decisions, residual risk, and the exact next workflow. Do not claim DONE unless this is the `closure` skill and every configured gate passes.