feat(#194): enhance NovaModule initialization with update notifications

- Add non-blocking update warning for newer NovaModuleTools releases before interactive scaffold questions
- Ensure existing .gitignore rules are preserved while adding Nova-managed entries
- Update documentation to reflect new behavior in initialization workflows

Author: stiwicourage

.github/agents/reviewer.agent.md

@@ -28,6 +28,7 @@ Review changes for correctness, maintainability, test coverage, workflow safety,
 - Flag Nova-managed validation that bypasses `Test-NovaBuild` with direct `Invoke-Pester`.
 - Flag any PSScriptAnalyzer rule excludes or suppressions; the code should be fixed instead.
 - Flag unresolved ScriptAnalyzer findings from `run.ps1` or `Invoke-ScriptAnalyzerCI.ps1`; they should be fixed instead of deferred.
+- Flag every changed or generated text file if they do not exactly have one trailing newline with no extra blank lines at the bottom.
 
 ## Inputs to inspect
 

.github/agents/test-engineer.agent.md

@@ -18,6 +18,8 @@ Improve or maintain the repository's Pester coverage, coverage-gate behavior, an
 - Use `.github/instructions/testing-policy.instructions.md` as the test-design source of truth while shaping `tests/**/*.ps1`.
 - Use `.github/instructions/psscriptanalyzer.instructions.md` when changing tests, test helpers, or analyzer/CI helpers so the repo-standard analyzer workflow stays intact.
 - Keep CI coverage output compatible with the CodeScene workflow.
+- Before handoff, review every changed or generated text file and normalize it to exactly one trailing newline with no extra blank lines at the bottom.
+
 
 ## Inputs to inspect
 

CHANGELOG.md

@@ -18,6 +18,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
       - The generated guidance now requires `docs/<ProjectName>/en-US/*.md` to stay valid PlatyPS help with YAML metadata and build-compatible structure, tells agents to use the documented `New-MarkdownCommandHelp` / `Update-MarkdownCommandHelp` / `Test-MarkdownCommandHelp` workflow instead of replacing command help with plain Markdown that breaks `nova build`, and requires a matching help file for every new public entry point in the same change.
       - The generated PowerShell guidance now requires agents to review every changed or generated text file before handoff and normalize the file ending to exactly one trailing newline with no extra blank lines at the bottom.
     - When Git is enabled during either scaffold flow, Nova now creates or updates a default `.gitignore` in the generated project root and appends only the missing Nova-managed artifact entries instead of overwriting existing ignore rules.
+    - `Initialize-NovaModule` and `% nova init` now check for newer NovaModuleTools releases before the first interactive scaffold question and reuse the same non-blocking update warning behavior already used by build.
 
 
 ### Changed

RELEASE_NOTE.md

@@ -7,6 +7,7 @@ This file summarizes public cmdlet, CLI, configuration, and migration changes fo
 ### Added
 - `Initialize-NovaModule` and `% nova init` now offer an optional Agentic Copilot starter package in both the minimal and example interactive scaffold flows.
     - The starter package follows a filtered mirror of Nova's maintained agentic guidance so newly scaffolded projects receive a broader Nova-style agentic baseline without Nova-specific surfaces.
+  - Before the first interactive scaffold question, Nova now also warns when a newer NovaModuleTools release is available by reusing the same non-blocking update warning behavior already used by `build`.
 
 ### Changed
 

docs/NovaModuleTools/en-US/Initialize-NovaModule.md

@@ -27,7 +27,8 @@ PS> Initialize-NovaModule [-Path <string>] [-Example] [-WhatIf] [-Confirm] [<Com
 
 `Initialize-NovaModule` creates a new project folder, the standard `src/` layout, and a starter `project.json` file.
 
-The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. When Git initialization is enabled, Nova also creates or updates a default `.gitignore` in the generated project root so common local and CI artifact paths such as `artifacts/`, `dist/`, `run.ps1`, and `reload.ps1` are ignored from the start. Existing `.gitignore` files are preserved and only receive the missing Nova-managed entries. When you enable the Agentic package, Nova also asks for a project short name used in generated guidance placeholders such as `Invoke-<ShortName>*`; for NovaModuleTools the short name is `Nova`, but it could also have been `NMT`. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json`
+The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. Before the first interactive question, Nova checks whether a newer `NovaModuleTools` release is available and warns without blocking the scaffold flow. When Git initialization is enabled, Nova also creates or updates a default `.gitignore` in the generated project root so common local and CI artifact paths such as `artifacts/`, `dist/`, `run.ps1`, and `reload.ps1` are ignored from the start. Existing `.gitignore` files are preserved and only receive the missing Nova-managed entries. When you enable the Agentic package, Nova also asks for a project short name used in generated guidance placeholders such as `Invoke-<ShortName>*`; for NovaModuleTools the short name is `Nova`, but it could also have been
+`NMT`. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json`
 `Manifest.PowerShellHostVersion` compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated `dist` module files, command-help ownership, source-mirrored test guidance, guidance that ScriptAnalyzer findings reported by
 `run.ps1` must be fixed before handoff, explicit PSScriptAnalyzer workflow guidance for `./scripts/build/Invoke-ScriptAnalyzerCI.ps1`, `./run.ps1`, and focused `Invoke-ScriptAnalyzer` usage, explicit public/private PowerShell file ownership rules, best-effort source/helper-script maintainability guidance plus separate test-design guidance delivered through Agentic Copilot files, explicit valid-PlatyPS help guidance for `docs/<ProjectName>/en-US/*.md` that uses `New-MarkdownCommandHelp`, `Update-MarkdownCommandHelp`, and `Test-MarkdownCommandHelp`, and a strict file-ending rule for changed or generated text files. For the standard scaffold, the interactive flow also includes optional basic Pester support.
 
@@ -37,7 +38,7 @@ Use this command when you want to start a new module in the NovaModuleTools stru
 
 Use `-Path` when you want to create the project under a specific base directory. Positional path syntax is no longer supported.
 
-Use `-Example` when you want the scaffold to start from the packaged example project instead of the minimal default layout. The example flow keeps the example source, resource, and test files, skips the Pester enable/disable question, and applies the interactive metadata values to the copied `project.json`. The standard and example flows share the same inline validation and retry behavior for interactive answers, including the optional Agentic Copilot setup prompt after the Git question. When Git is enabled in either flow, Nova also ensures the generated project root has the default `.gitignore` entries for local and CI artifacts without overwriting any existing `.gitignore` content. When you answer `Yes`, Nova asks for the short project name, adds the same starter package to either scaffold style, and merges the example README instead of replacing it with the generic starter README outright.
+Use `-Example` when you want the scaffold to start from the packaged example project instead of the minimal default layout. The example flow keeps the example source, resource, and test files, skips the Pester enable/disable question, and applies the interactive metadata values to the copied `project.json`. The standard and example flows share the same upfront Nova update warning, inline validation and retry behavior for interactive answers, and optional Agentic Copilot setup prompt after the Git question. When Git is enabled in either flow, Nova also ensures the generated project root has the default `.gitignore` entries for local and CI artifacts without overwriting any existing `.gitignore` content. When you answer `Yes`, Nova asks for the short project name, adds the same starter package to either scaffold style, and merges the example README instead of replacing it with the generic starter README outright.
 
 This command supports `-WhatIf` and `-Confirm` through PowerShell `SupportsShouldProcess`. Use `-WhatIf` to preview the scaffold target after the interactive answers have been collected, without creating folders, writing `project.json`, or initializing Git.
 

docs/commands.html

@@ -174,10 +174,12 @@ <h3>Start a new project</h3>
                         <div class="surface-note" data-command-visibility="powershell">
                             <p><strong>Cmdlet:</strong> <code>Initialize-NovaModule</code></p>
                         </div>
-                        <p>Create the minimal scaffold or the example scaffold for a new module project. When Git is
-                            enabled, 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 overwriting existing
-                            rules. Both interactive flows can also add the optional Agentic Copilot starter package,
+                        <p>Create the minimal scaffold or the example scaffold for a new module project. Before the
+                            first interactive question, Nova checks whether a newer NovaModuleTools release is
+                            available and warns without blocking the scaffold flow. When Git is enabled, 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 overwriting existing rules. Both
+                            interactive flows can also add the optional Agentic Copilot starter package,
                             which follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test
                             expectations, <code>project.json</code> <code>Manifest.PowerShellHostVersion</code>
                             compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated

docs/core-workflows.html

@@ -124,10 +124,12 @@ <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. 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 overwriting existing rules. The Agentic prompt
-                    defaults to <code>No</code>, and the package follows Nova's maintained agentic guidance through a
+                    Copilot starter package after the Git prompt. 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
+                    overwriting existing rules. The Agentic prompt defaults to <code>No</code>, and the package
+                    follows Nova's maintained agentic guidance through a
                     filtered starter mirror, including
                     Nova build/test/package expectations, <code>project.json</code>
                     <code>Manifest.PowerShellHostVersion</code> compatibility guidance, strict ScriptAnalyzer guidance

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.
+                    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
                     project root so common local and CI artifact paths start ignored without overwriting existing ignore
                     rules.

src/private/build/InvokeNovaBuildWorkflow.ps1

@@ -15,7 +15,7 @@ function Invoke-NovaBuildWorkflow {
     Build-Manifest -ProjectInfo $projectInfo
     Build-Help -ProjectInfo $projectInfo
     Copy-ProjectResource -ProjectInfo $projectInfo
-    Invoke-NovaBuildUpdateNotificationSafely
+    Invoke-NovaModuleUpdateNotificationSafely
 
     if ($continuousIntegrationRequested) {
         $null = Import-NovaBuiltModuleForCi -ProjectInfo $projectInfo
@@ -35,13 +35,3 @@ function Invoke-NovaBuildDuplicateValidation {
     Assert-BuiltModuleHasNoDuplicateFunctionName -ProjectInfo $ProjectInfo
 }
 
-function Invoke-NovaBuildUpdateNotificationSafely {
-    [CmdletBinding()]
-    param()
-
-    try {
-        Invoke-NovaBuildUpdateNotification
-    } catch {
-        $null = $_
-    }
-}

src/private/cli/ConfirmNovaCliAction.ps1

@@ -43,16 +43,27 @@ function Invoke-NovaCliConsoleReadKey {
 
 function Invoke-NovaCliNativeConsoleReadKey {
     [CmdletBinding()]
-    param([scriptblock]$Reader = {[Console]::ReadKey($true)})
+    param([scriptblock]$Reader)
+
+    if ($null -eq $Reader) {
+        $Reader = Get-NovaCliNativeConsoleReadKeyReader
+    }
 
     return & $Reader
 }
 
+function Get-NovaCliNativeConsoleReadKeyReader {
+    [CmdletBinding()]
+    param()
+
+    return [scriptblock]::Create('[Console]::ReadKey($true)')
+}
+
 function Get-NovaCliConsoleReadKeyReader {
     [CmdletBinding()]
     param()
 
-    return {Invoke-NovaCliNativeConsoleReadKey}
+    return [scriptblock]::Create('Invoke-NovaCliNativeConsoleReadKey')
 }
 
 function Read-NovaCliPromptKey {