#242 feat: Enhance project.json schema support and VS Code integration

- Added `$schema` property injection in `nova init` for new projects, enabling VS Code IntelliSense and autocomplete.
- Introduced authoritative `Schema-Project.json` for project.json validation.
- Updated `Test-ProjectSchema` to validate against the new schema.
- Removed obsolete `Schema-Build.json` and `Schema-Pester.json`.
- Implemented `Export-NovaProjectJsonSchema` to copy the schema to the appropriate documentation directory.
- Updated documentation to reflect schema changes and IntelliSense support.
- Enhanced tests for schema validation and project.json writing functionality.

Author: stiwicourage

CHANGELOG.md

@@ -7,6 +7,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ### Added
 
+- `project.json` now has a single authoritative JSON schema hosted at `https://www.novamoduletools.com/schema/v{major}/project.json`.
+    - `Invoke-NovaBuild` exports the schema to `docs/schema/v{major}/project.json` during build, creating the directory when missing.
+    - `nova init` injects `"$schema": "https://www.novamoduletools.com/schema/v{major}/project.json"` into every scaffolded project.
+    - VS Code picks up the schema automatically to provide field validation, autocomplete, and hover descriptions while editing `project.json`.
+    - The two partial internal schemas (`Schema-Build.json`, `Schema-Pester.json`) are removed; `Schema-Project.json` is the new single source.
+
 ### Changed
 
 - `Get-NovaProjectInfo` now aligns its installed-version views with the existing CLI version contract.

RELEASE_NOTE.md

@@ -6,6 +6,8 @@ This file summarizes the release notes for NovaModuleTools. **UNRELEASED** chang
 
 ### Added
 
+- `nova init` now injects a `"$schema"` property into new projects pointing to the hosted versioned JSON schema, enabling VS Code IntelliSense, autocomplete, and hover descriptions while editing `project.json`.
+
 ### Changed
 
 - `Get-NovaProjectInfo` now matches the CLI version split on the PowerShell surface.

docs/project-json-reference.html

@@ -109,14 +109,13 @@ <h2>How to read this file</h2>
                         defaults
                         to a single <code>.nupkg</code> written to <code>artifacts/packages/</code>.</p>
                 </div>
-                <div class="notice notice--warning">
-                    <strong>Important compatibility note.</strong>
-                    <p>The runtime and shipped examples currently use some manifest and Pester fields more broadly than
-                        the JSON schema files explicitly enumerate. In practice, the current product and examples use
+                <div class="notice">
+                    <strong>Schema coverage.</strong>
+                    <p>The unified JSON schema covers all documented fields including
                         <code>Manifest.ReleaseNotes</code>, <code>Manifest.LicenseUri</code>,
-                        <code>Manifest.IconUri</code>, and <code>Pester.TestResult.OutputFormat</code>. The reference
-                        below documents the live behavior that the product uses today and calls out those schema gaps
-                        where they matter.</p>
+                        <code>Manifest.IconUri</code>, and <code>Pester.TestResult.OutputFormat</code>. VS Code picks
+                        up the schema automatically when the <code>$schema</code> field is present in
+                        <code>project.json</code>.</p>
                 </div>
             </section>
 
@@ -204,6 +203,15 @@ <h2>Complete example</h2>
 
             <section class="content-section" id="top-level">
                 <h2>Top-level project settings</h2>
+                <div class="notice">
+                    <strong>VS Code IntelliSense.</strong>
+                    <p>When <code>nova init</code> scaffolds a new project, it injects a <code>$schema</code> field
+                        that points to the versioned public schema at
+                        <code>https://www.novamoduletools.com/schema/v{major}/project.json</code>. VS Code picks this
+                        up automatically to provide field validation, autocomplete, and hover descriptions while you
+                        edit <code>project.json</code>. You can add the field manually to any existing project by
+                        inserting it as the first key in the file.</p>
+                </div>
                 <div class="table-scroll">
                     <table>
                         <thead>
@@ -215,6 +223,14 @@ <h2>Top-level project settings</h2>
                         </tr>
                         </thead>
                         <tbody>
+                        <tr>
+                            <td><code>$schema</code></td>
+                            <td>Optional URI pointing to the versioned JSON schema for this file.</td>
+                            <td>Injected automatically by <code>nova init</code></td>
+                            <td>Enables VS Code IntelliSense, field validation, and hover descriptions while editing
+                                <code>project.json</code>.
+                            </td>
+                        </tr>
                         <tr>
                             <td><code>ProjectName</code></td>
                             <td>Name of the module and the output folder under <code>dist/</code>.</td>