fix: restore nested private helper coverage and sync site docs

 - expand Pester CodeCoverage paths so nested src/private folders are included in artifacts/coverage.xml
 - stop build test support files from shadowing manifest helper coverage and add mirrored duplicate-validation tests
 - update the public site for scaffold version defaults, explicit coverage paths, and corrected versioning examples

Author: stiwicourage

docs/core-workflows.html

@@ -124,7 +124,9 @@ <h2>Create the project</h2>
                         path syntax such as <code>% nova init ~/Work</code>.</p>
                 </div>
                 <p>Both scaffold styles ask the same core project questions, and both now offer an optional Agentic
-                    Copilot starter package after the Git prompt. Before the first question, Nova also checks whether a
+                    Copilot starter package after the Git prompt. The starting version prompt now defaults to
+                    <code>0.1.0-preview</code>, so new projects begin on Nova's prerelease-friendly starter line unless
+                    you choose a different version. Before the first question, Nova also checks whether a
                     newer NovaModuleTools release is available and warns without blocking the scaffold flow. When you
                     enable Git in either scaffold style, Nova also creates or updates a default <code>.gitignore</code>
                     in the generated project root so common local and CI artifact paths are ignored without
@@ -147,8 +149,9 @@ <h2>Create the project</h2>
                     entry point, and a strict file-ending rule for changed or generated text
                     files.</p>
                 <p>The generated <code>project.json</code> also starts with Nova's standard <code>Pester</code>
-                    defaults, including a disabled <code>CodeCoverage</code> block you can enable later without
-                    hand-authoring the structure.</p>
+                    defaults, including a disabled <code>CodeCoverage</code> block with explicit source coverage paths
+                    for <code>src/public/</code>, nested <code>src/private/</code> helper folders, and
+                    <code>src/classes/</code>, so you can enable coverage later without hand-authoring the structure.</p>
                 <p>When you answer <code>Yes</code>, Nova also asks for a short project name used in generated guidance
                     placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the short name is
                     <code>Nova</code>, but it could also have been <code>NMT</code>.</p>

docs/getting-started.html

@@ -195,6 +195,8 @@ <h2>4. Scaffold the packaged example</h2>
                 </div>
                 <p>Nova asks for the project name, description, version, author, minimum PowerShell version, whether
                     Git should be initialized, and whether Nova should add the optional Agentic Copilot starter package.
+                    The starting version prompt now defaults to <code>0.1.0-preview</code>, so new projects begin on
+                    Nova's prerelease-friendly starter line unless you choose a different version.
                     Before the first question, Nova also checks whether a newer NovaModuleTools release is available and
                     warns without blocking the scaffold flow.
                     When you enable Git, Nova also creates or updates a default <code>.gitignore</code> in the new
@@ -219,8 +221,9 @@ <h2>4. Scaffold the packaged example</h2>
                     Nova then creates a project folder under the path you selected.</p>
                 <p>The generated <code>project.json</code> also starts with Nova's standard <code>Pester</code>
                     defaults, including an opt-in <code>CodeCoverage</code> block with <code>Enabled=false</code>,
-                    shared <code>src/</code> coverage paths, JaCoCo output in <code>artifacts/coverage.xml</code>, and
-                    a <code>90</code> percent target you can enable later.</p>
+                    explicit source coverage paths for <code>src/public/</code>, nested <code>src/private/</code>
+                    helper folders, and <code>src/classes/</code>, JaCoCo output in <code>artifacts/coverage.xml</code>,
+                    and a <code>90</code> percent target you can enable later.</p>
                 <p>If you enable the Agentic package, Nova also asks for a short project name used in generated guidance
                     placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the short name is
                     <code>Nova</code>, but it could also have been <code>NMT</code>.</p>

docs/project-json-reference.html

@@ -176,6 +176,19 @@ <h2>Complete example</h2>
     ]
   },
   "Pester": {
+    "CodeCoverage": {
+      "Enabled": false,
+      "Path": [
+        "src/public/*.ps1",
+        "src/private/*.ps1",
+        "src/private/*/*.ps1",
+        "src/private/*/*/*.ps1",
+        "src/classes/*.ps1"
+      ],
+      "CoveragePercentTarget": 90,
+      "OutputPath": "artifacts/coverage.xml",
+      "OutputFormat": "JaCoCo"
+    },
     "TestResult": {
       "Enabled": true,
       "OutputFormat": "NUnitXml"
@@ -626,10 +639,11 @@ <h2><code>Pester</code> settings</h2>
                         <tr>
                             <td><code>Pester.CodeCoverage.Path</code></td>
                             <td>Declares which source files the coverage run analyzes.</td>
-                            <td><code>src/public/*.ps1</code><br><code>src/private/**/*.ps1</code><br><code>src/classes/*.ps1</code>
+                            <td><code>src/public/*.ps1</code><br><code>src/private/*.ps1</code><br><code>src/private/*/*.ps1</code><br><code>src/private/*/*/*.ps1</code><br><code>src/classes/*.ps1</code>
                             </td>
                             <td>These defaults ship in new starter projects so coverage can be enabled without
-                                hand-authoring the file list.
+                                hand-authoring the file list, including nested helper folders such as
+                                <code>src/private/build/manifest/</code> and <code>src/private/quality/duplicates/</code>.
                             </td>
                         </tr>
                         <tr>
@@ -661,9 +675,10 @@ <h2><code>Pester</code> settings</h2>
                     </table>
                 </div>
                 <p class="tiny-note">Starter projects now include the full <code>Pester.CodeCoverage</code> block with
-                    <code>Enabled=false</code>, so turning coverage on usually means changing only that switch. At
-                    runtime, <code>Test-NovaBuild</code> also lets you override verbosity and render mode temporarily
-                    with <code>-OutputVerbosity</code> and <code>-OutputRenderMode</code>.</p>
+                    <code>Enabled=false</code> and the explicit default source globs shown above, so turning coverage on
+                    usually means changing only that switch. At runtime, <code>Test-NovaBuild</code> also lets you
+                    override verbosity and render mode temporarily with <code>-OutputVerbosity</code> and
+                    <code>-OutputRenderMode</code>.</p>
                 <p>When you enable coverage, Nova writes JaCoCo output to <code>artifacts/coverage.xml</code> and fails
                     the test workflow if the measured percentage is lower than
                     <code>Pester.CodeCoverage.CoveragePercentTarget</code>.</p>

docs/versioning-and-updates.html

@@ -174,7 +174,7 @@ <h3>How Nova chooses the bump label</h3>
                     instead of jumping to <code>1.0.0</code>. Nova prints one warning that you should set
                     <code>1.0.0</code> manually once the API is stable. Preview mode stays unchanged.
                 </p>
-                <pre><code>0.1.0-preview + Patch -> 0.0.2
+                <pre><code>0.0.1 + Patch -> 0.0.2
 0.1.0 + Minor -> 0.2.0
 0.1.0 + Major -> 0.2.0</code></pre>
                 <p>When Git tags exist, Nova uses commits since the latest tag. When Git-based inference is unavailable