fix: correct and source Unity version claims in skills, rules, and data

Checked each version-specific claim against Unity docs, release notes,
package changelogs, and staff posts:

- Built-in pipeline: deprecated starting in 6.5, still in 6.7 LTS, no
  removal version announced
- Package signing in 6.3 warns on unsigned packages; it does not
  require signatures
- CGPROGRAM is not formally deprecated; it is not SRP Batcher compatible
- Distributed Authority ships in NGO 2.0 on Unity 6, not Unity 6.4
- Core ECS packages ship with the Editor from 6.4, versioned with it
- URP Render Graph is the default since 6.0; Compatibility Mode was
  removed in 6.3
- Surface Cache GI is a preview planned for 6.7 LTS
- URP and Built-in per-object light limits restated from the docs
- CoreCLR is an experimental desktop player in the 6.7 alpha, with no
  published performance figures
- HDRP and Unity AI statements match Unity's own wording

Affected skills gain a Sources section with the links and check date.
deprecated_patterns.json reasons for CGPROGRAM, Camera.main, and Mono
are corrected too.

Closes #32

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MpEiWjv38TrdFcgqU8ER5L

Author: TMHSDigital

README.md

@@ -103,7 +103,7 @@ Restart Cursor, then open **your Unity project** (not this repository) and ask t
 |:---------|:-------|
 | **URP** (Universal) | Primary -- recommended for all new projects |
 | **HDRP** (High Definition) | Supported -- maintenance mode guidance |
-| **Built-in** (Legacy) | Migration guidance -- deprecated in Unity 6.5 |
+| **Built-in** (Legacy) | Migration guidance -- deprecated starting in Unity 6.5 |
 
 </details>
 
@@ -145,7 +145,7 @@ Restart Cursor, then open **your Unity project** (not this repository) and ask t
 | **Visual Scripting** | Script Graphs, State Graphs, Subgraphs, custom nodes |
 | **Testing** | Edit Mode and Play Mode tests with Unity Test Framework 2.x |
 | **Addressables** | Async asset loading, groups, labels, remote content delivery |
-| **Platform Targeting** | Platform defines, IL2CPP/CoreCLR backends, build settings |
+| **Platform Targeting** | Platform defines, IL2CPP and Mono backends (CoreCLR status), build settings |
 
 ## Rules (8)
 

docs/index.md

@@ -54,7 +54,7 @@ For a detailed walkthrough, see the [Getting Started guide](GETTING-STARTED.md).
 |:---------|:-------|
 | **URP** (Universal) | Primary -- recommended for all new projects |
 | **HDRP** (High Definition) | Supported -- maintenance mode guidance |
-| **Built-in** (Legacy) | Migration guidance -- deprecated in Unity 6.5 |
+| **Built-in** (Legacy) | Migration guidance -- deprecated starting in Unity 6.5 |
 
 ## How it works
 

mcp-server/data/deprecated_patterns.json

@@ -20,7 +20,7 @@
   {
     "legacy": "CGPROGRAM / ENDCG",
     "replacement": "HLSLPROGRAM / ENDHLSL with URP or HDRP shader libraries",
-    "reason": "CG shaders use the legacy built-in pipeline surface shader compiler. HLSL is required for SRP (URP/HDRP) and gives access to modern shader features.",
+    "reason": "Not formally deprecated, but CG shaders pull in Built-in include files and are not SRP Batcher compatible. Unity's URP upgrade guide recommends converting them to HLSLPROGRAM with the URP or HDRP shader libraries.",
     "since_version": "2019.3"
   },
   {
@@ -44,7 +44,7 @@
   {
     "legacy": "Camera.main (called every frame)",
     "replacement": "Cache Camera.main in a field during Awake/Start",
-    "reason": "Camera.main performs FindGameObjectWithTag internally each call. In Unity 2020+, it is cached per frame, but caching it yourself is still clearer and avoids null-check overhead.",
+    "reason": "Since Unity 2020.2 the engine caches the main camera, so Camera.main no longer searches by tag. It is still a native call; cache it in a field for code that runs many times per frame, and refresh it when the main camera changes.",
     "since_version": "N/A (best practice)"
   },
   {
@@ -62,7 +62,7 @@
   {
     "legacy": "Mono scripting backend",
     "replacement": "IL2CPP scripting backend",
-    "reason": "Mono is being phased out. IL2CPP provides better performance, smaller builds on most platforms, and is the only backend available on consoles, iOS, and WebGL.",
+    "reason": "IL2CPP is the recommended backend for release builds: it is ahead-of-time compiled and is required on iOS, WebGL, and consoles. Mono stays useful for fast iteration. Unity plans to replace Mono with CoreCLR in Unity 7.0; the CoreCLR desktop player is experimental in the Unity 6.7 alpha.",
     "since_version": "2021.2"
   },
   {

rules/shader-conventions.mdc

@@ -11,7 +11,7 @@ standards-version: 1.10.0
 - Always specify a Fallback shader for compatibility
 - Use properties block for all tweakable values
 - Name properties with underscore prefix: _MainTex, _Color, _Metallic
-- Use HLSLPROGRAM / ENDHLSL blocks, not the deprecated CGPROGRAM / ENDCG
+- Use HLSLPROGRAM / ENDHLSL blocks, not CGPROGRAM / ENDCG (CG shaders are not SRP Batcher compatible and pull in Built-in includes)
 - Include SRP Batcher compatibility: use CBUFFER_START(UnityPerMaterial) for properties in URP/HDRP
 - Minimize shader variants: use shader_feature_local over multi_compile when possible
 - Use half precision where full float is unnecessary (mobile especially)

skills/ecs-dots/SKILL.md

@@ -9,7 +9,7 @@ standards-version: 1.10.0
 
 ## Status in 2026
 
-The Data-Oriented Technology Stack (DOTS) is now a core part of the Unity engine, not an experimental package. As of Unity 6.4, the Entities package (1.4/1.7) is integrated into the core engine packages. ECS is production-ready for:
+The Data-Oriented Technology Stack (DOTS) is now a core part of the Unity engine, not an experimental package. In Unity 6.4, Entities, Collections, Mathematics, and Entities Graphics became core packages: they ship with the Editor and their version matches it (Entities 6.4 in Unity 6.4). On Unity 6.0 to 6.3, install the Entities 1.x package. ECS is production-ready for:
 
 - Massive entity counts (thousands to millions)
 - High-performance simulations and physics
@@ -182,7 +182,7 @@ Mix ECS with GameObjects for incremental adoption:
 
 - Use ECS for simulation-heavy systems (AI, pathfinding, particles)
 - Keep GameObjects for UI, cameras, and player controllers
-- Hierarchy V2 (Unity 6.5 opt-in) allows viewing GameObjects and Entities in the same window
+- The new Hierarchy window (opt in under Preferences > General) shows entities alongside GameObjects from Unity 6.5
 
 ## When to Use ECS
 
@@ -197,3 +197,10 @@ Mix ECS with GameObjects for incremental adoption:
 - UI-heavy applications
 - Rapid prototypes where iteration speed matters more than performance
 - Teams unfamiliar with data-oriented programming (learning curve is steep)
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- What's new in Unity 6.4 (core ECS packages): <https://docs.unity3d.com/6000.5/Documentation/Manual/WhatsNewUnity64.html>
+- What's new in Unity 6.5 (Hierarchy window): <https://docs.unity3d.com/6000.6/Documentation/Manual/WhatsNewUnity65.html>

skills/networking/SKILL.md

@@ -90,7 +90,7 @@ The older `[ServerRpc]` / `[ClientRpc]` attributes still compile, but new code s
 - Transfer ownership for player-controlled objects: `NetworkObject.ChangeOwnership(clientId)`
 - Check ownership: `IsOwner`, `IsServer`, `IsClient`, `IsLocalPlayer`
 
-### Distributed Authority (Unity 6.4)
+### Distributed Authority (NGO 2.0+, Unity 6)
 
 New mode for client-hosted games with shared authority:
 - No dedicated server required
@@ -173,3 +173,9 @@ public class PlayerCombat : NetworkBehaviour
 - **Interpolation**: Smooth remote player movement between network updates.
 - **Prediction**: Client predicts the result of its own input immediately. Server corrects if the prediction was wrong.
 - **Always validate on the server**: Never trust client data in competitive games.
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- Netcode for GameObjects 2.0 changelog (Distributed Authority): <https://docs.unity3d.com/Packages/com.unity.netcode.gameobjects@2.0/changelog/CHANGELOG.html>

skills/platform-targeting/SKILL.md

@@ -64,7 +64,7 @@ Use preprocessor directives for platform-specific code:
 |---------|----------|-------------|------------|
 | **IL2CPP** | Production builds, all platforms | Excellent (AOT compiled) | Slower |
 | **Mono** | Editor iteration, quick testing | Good | Fast |
-| **CoreCLR** | Experimental (Unity 6.7 desktop) | Excellent (2-3x over Mono) | Moderate |
+| **CoreCLR** | Experimental desktop player in the Unity 6.7 alpha; not for production. Unity 7.0 plans to replace Mono with CoreCLR | Not yet published by Unity | Not yet published |
 
 IL2CPP is the recommended backend for all release builds. It compiles C# to C++ for native performance and makes reverse engineering harder.
 
@@ -159,3 +159,9 @@ if (ap != null && ap.ThermalStatus.ThermalMetrics.WarningLevel > WarningLevel.No
 ```
 
 Supports: Samsung (Android), PS4, PS5, Xbox. Adjusts rendering quality, framerate targets, and CPU/GPU workload based on device thermal state.
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- CoreCLR scripting and serialization update, June 2026 (Unity staff): <https://discussions.unity.com/t/coreclr-scripting-and-serialization-update-june-2026/1723299>

skills/project-setup/SKILL.md

@@ -13,7 +13,7 @@ Call `analyze_project` with the project root to read the editor version, install
 
 ## Target Version
 
-Unity 6.3 LTS is the recommended baseline for new projects. Unity 6.4 adds opt-in features like Agentic AI tools and core Entities integration. Always use the Unity Hub to manage installations and create projects from verified templates.
+Unity 6.3 LTS (supported until December 2027) is the recommended baseline for new projects. Newer Tech Stream releases add features such as core ECS packages (Unity 6.4); Unity AI (Assistant, the Unity MCP server, and Generators) is in open beta for Unity 6 and later. Always use the Unity Hub to manage installations and create projects from verified templates.
 
 ## Recommended Folder Structure
 
@@ -84,7 +84,7 @@ Always commit `.meta` files. Unity uses them to track asset GUIDs, import settin
 
 - **URP (Universal Render Pipeline)**: Default choice for all new projects in 2026. Covers mobile through high-end console and PC. Active development with Render Graph backend, physical light units, and SCGI (Surface Caching Global Illumination).
 - **HDRP (High Definition Render Pipeline)**: Maintenance mode. Use only for existing projects that depend on HDRP-specific features like volumetric fog or area lights. No new major features planned.
-- **Built-in Render Pipeline**: Officially deprecated in Unity 6.5. Do not start new projects with Built-in. Migration to URP is recommended for all legacy projects.
+- **Built-in Render Pipeline**: Deprecated starting in Unity 6.5 and still available in Unity 6.7 LTS; Unity has not announced a removal version. Do not start new projects with Built-in, and plan a migration to URP for existing ones.
 
 ## Project Settings Recommendations
 
@@ -121,7 +121,7 @@ Install these packages for most projects:
 | Unity UI | `com.unity.ugui` | Legacy Canvas UI (still valid for world-space) |
 | UI Toolkit | (built-in) | Modern UI for menus, HUD, editor tools |
 
-As of Unity 6.3, packages must be signed for core standards compliance. The Package Manager shows trust indicators for verified packages. Prefer verified packages over unverified third-party sources.
+From Unity 6.3 the Package Manager checks signatures on tarball packages. Unsigned packages are not blocked; they show a "Signature: Missing" warning. A package with an invalid signature shows an error and should be removed. Prefer Unity-signed and verified packages, and pin third-party packages to a specific version or commit.
 
 ## Project Initialization Checklist
 
@@ -133,3 +133,11 @@ As of Unity 6.3, packages must be signed for core standards compliance. The Pack
 6. Configure Player Settings (scripting backend, input handling)
 7. Set up quality levels with per-level URP Render Pipeline Assets
 8. Create initial scene with proper lighting setup
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- Render pipelines strategy for 2026 (Unity staff): <https://discussions.unity.com/t/render-pipelines-strategy-for-2026/1710004>
+- Package signatures (Unity 6.3 manual): <https://docs.unity3d.com/6000.3/Documentation/Manual/upm-signature.html>
+- Unity 6 release and support dates: <https://unity.com/releases/unity-6/support>

skills/render-pipeline-detection/SKILL.md

@@ -14,8 +14,8 @@ Before giving pipeline-specific advice, call the `analyze_project` MCP tool with
 ## Current Pipeline Landscape (2026)
 
 - **URP (Universal Render Pipeline)**: The default and actively developed pipeline. Use for all new projects.
-- **HDRP (High Definition Render Pipeline)**: In maintenance mode. No new features planned beyond Switch 2 support. Existing HDRP projects can continue, but new projects should prefer URP.
-- **Built-in Render Pipeline (BiRP)**: Officially deprecated as of Unity 6.5. Supported through Unity 6.7 LTS but not recommended for any new work.
+- **HDRP (High Definition Render Pipeline)**: Unity plans no new HDRP features and focuses its maintenance on stability, regressions, and critical issues; Switch 2 support is the one area in active work. Existing HDRP projects can continue, but new projects should prefer URP.
+- **Built-in Render Pipeline (BiRP)**: Deprecated starting in Unity 6.5. It is still available in Unity 6.7 LTS and Unity commits to supporting it until at least the end of 2028; no removal version has been announced. Not recommended for new work.
 
 ## Detection at Edit Time
 
@@ -102,7 +102,7 @@ Add custom scripting defines in Project Settings > Player > Scripting Define Sym
 ### Shader Program Blocks
 
 - URP/HDRP: Use `HLSLPROGRAM` / `ENDHLSL`
-- Built-in: Used `CGPROGRAM` / `ENDCG` (deprecated)
+- Built-in: Traditionally `CGPROGRAM` / `ENDCG`. Not formally deprecated, but CG shaders are not SRP Batcher compatible, so convert them when moving to URP or HDRP.
 
 ### Post-Processing
 
@@ -123,14 +123,14 @@ Add custom scripting defines in Project Settings > Player > Scripting Define Sym
 
 | Feature | URP | HDRP | Built-in |
 |---------|-----|------|----------|
-| Per-object light limit | Configurable (default 8) | Virtually unlimited | 8 (forward) |
+| Per-object light limit | Forward: 1 main + up to 8 additional. Forward+: no per-object limit (per-camera limits apply) | Virtually unlimited | Pixel Light Count (Quality settings) lit per pixel, up to 4 per vertex, the rest by spherical harmonics |
 | Area lights | Baked only | Real-time | Baked only |
 | Volumetric lighting | Light cookies/fog | Full volumetric | Third-party |
-| Global Illumination | SCGI (6.7), Lightmaps | Ray tracing, Path tracing | Lightmaps |
+| Global Illumination | Lightmaps, Adaptive Probe Volumes; Surface Cache GI in preview, planned for Unity 6.7 LTS | Ray tracing, Path tracing | Lightmaps |
 
 ### Render Graph Backend
 
-Both URP and HDRP use the Render Graph backend as of Unity 6.3. This enables:
+URP uses Render Graph by default from Unity 6.0. URP Compatibility Mode (the non-Render Graph path) was removed in Unity 6.3, so custom URP passes must use the Render Graph API. HDRP is also built on Render Graph. This enables:
 - Automatic render pass optimization
 - Dynamic resource allocation
 - Reduced CPU overhead for complex rendering setups
@@ -158,3 +158,13 @@ public override void RecordRenderGraph(RenderGraph renderGraph, ContextContainer
 ### HDRP to URP
 
 Consider this for projects that do not need HDRP-exclusive features. HDRP is in maintenance mode, while URP continues to receive new features. Conversion requires shader and material updates, as the two pipelines use different shader libraries.
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- Render pipelines strategy for 2026 (Unity staff): <https://discussions.unity.com/t/render-pipelines-strategy-for-2026/1710004>
+- Upgrade to Unity 6.3 (URP Compatibility Mode removal): <https://docs.unity3d.com/6000.3/Documentation/Manual/UpgradeGuideUnity63.html>
+- Light limits in URP: <https://docs.unity3d.com/6000.3/Documentation/Manual/urp/lighting/light-limits-in-urp.html>
+- Surface Cache GI preview (Unity staff): <https://discussions.unity.com/t/surface-cache-gi-preview/1720494>
+- Converting Built-in shaders to URP (CGPROGRAM and SRP Batcher): <https://docs.unity3d.com/6000.3/Documentation/Manual/urp/urp-shaders/birp-urp-custom-shader-upgrade-guide.html>

skills/shader-development/SKILL.md

@@ -35,7 +35,7 @@ Surface shaders (`#pragma surface`) are a Built-in Render Pipeline feature. Sinc
 
 ## HLSL Shader Structure for URP
 
-All modern Unity shaders use `HLSLPROGRAM` blocks. The legacy `CGPROGRAM` is deprecated for scriptable render pipelines.
+Write `HLSLPROGRAM` blocks for URP and HDRP. `CGPROGRAM` is not formally deprecated, but it pulls in Built-in include files and CG shaders are not SRP Batcher compatible, so Unity's URP upgrade guide says to convert them to HLSL.
 
 ```hlsl
 Shader "Custom/BasicUnlit"
@@ -202,3 +202,10 @@ UNITY_INSTANCING_BUFFER_START(Props)
     UNITY_DEFINE_INSTANCED_PROP(half4, _Color)
 UNITY_INSTANCING_BUFFER_END(Props)
 ```
+
+## Sources
+
+Version-specific statements above were checked on 2026-10-10 against:
+
+- Converting Built-in shaders to URP (CGPROGRAM and SRP Batcher): <https://docs.unity3d.com/6000.3/Documentation/Manual/urp/urp-shaders/birp-urp-custom-shader-upgrade-guide.html>
+- Render pipelines strategy for 2026 (Unity staff): <https://discussions.unity.com/t/render-pipelines-strategy-for-2026/1710004>