feat(#146): enhance Nova version bump behavior with major-zero advisory

- Implement tests for major-zero advisory messages during version bumps
- Update CHANGELOG.md to reflect new warning behavior for stable 0.y.z bumps
- Modify CLI output to include guidance on setting 1.0.0 once stable

Author: stiwicourage

.github/prompts/markdown.promt.md

@@ -0,0 +1,64 @@
+# Markdown Wrapper Enforcer (Strict)
+
+## Purpose
+
+Force ALL output to be wrapped in a Markdown code block using this exact format:
+
+~~~markdown
+<content>
+~~~
+
+## Rules (strict)
+
+1. The response MUST start with exactly:
+
+~~~markdown
+
+2. The response MUST end with exactly:
+~~~
+
+3. There MUST be no text before or after the wrapper.
+
+4. The entire response MUST be inside the wrapper.
+
+5. If the format cannot be followed, DO NOT answer.
+
+Inner content rules
+
+- Inside the outer ~~~markdown block:
+    - Use triple backticks (```) for code examples.
+    - Always include language hints when relevant.
+
+⸻
+
+Example (correct nesting)
+
+## Example Section
+
+Run the build:
+
+```zsh
+% nova build
+```
+
+Or in PowerShell:
+
+```powershell
+PS> Invoke-NovaBuild
+```
+
+Self-check
+
+Before returning:
+
+-Starts with ~~~markdown?
+-Ends with ~~~?
+-Code blocks use triple backticks?
+
+If any check fails → regenerate.
+
+Expected behavior
+
+- Safe nested Markdown (no fence collisions)
+- Copy/paste ready
+- Consistent formatting across all generated content

.github/prompts/pr-description.prompt.md

@@ -0,0 +1,151 @@
+markdown
+
+# NovaModuleTools PR Description Generator
+
+## Purpose
+
+Generate a complete, high-quality pull request description for NovaModuleTools based on a change summary, commits, or
+diff.
+
+The output MUST follow the NovaModuleTools PR template exactly and be concise, precise, and reviewer-focused.
+
+---
+
+## Inputs
+
+- Change description, commit messages, or diff (required)
+- Optional: issue number, workflow touched, commands affected
+
+---
+
+## Instructions
+
+Analyze the provided input and:
+
+1. Infer the intent of the change (bugfix, feature, refactor, CI, docs, etc.)
+2. Identify impacted areas (CLI, PowerShell, CI/CD, packaging, docs, etc.)
+3. Detect validation steps performed (or infer what should have been run)
+4. Highlight reviewer entry points (key files, workflows, or commands)
+5. Identify risks, breaking changes, or follow-ups
+
+Be pragmatic: if information is missing, make reasonable assumptions but call them out briefly.
+
+---
+
+## Output format
+
+You MUST return the PR description using this exact structure:
+
+---
+
+## Summary
+
+- What changed?
+- Why was this change needed?
+- Link the issue, discussion, or follow-up work (for example `Closes #123`).
+
+---
+
+## Affected area
+
+Select all relevant:
+
+- [ ] `nova` CLI or command routing
+- [ ] Public PowerShell cmdlet behavior
+- [ ] Scaffolding or `project.json` handling
+- [ ] Build, test, analyzer, coverage, or CI helper flow
+- [ ] Package, raw upload, or package metadata workflow
+- [ ] Publish, release, semantic-release, or GitHub Actions automation
+- [ ] Self-update or notification preference behavior
+- [ ] Contributor documentation (`README.md`, `CONTRIBUTING.md`, repository workflow docs)
+- [ ] End-user docs (`docs/*.html`)
+- [ ] Command help (`docs/NovaModuleTools/en-US/*.md`)
+- [ ] `src/resources/example/`
+- [ ] Dependency or manifest changes (`package.json`, workflow dependencies, release tooling)
+- [ ] Security-sensitive change
+- [ ] Documentation-only change
+- [ ] Other
+
+---
+
+## Review guidance
+
+- Highlight the main code path or workflow reviewers should start with.
+- Call out the primary files or folders changed (for example `src/public/`, `src/private/cli/`, `scripts/build/ci/`,
+  `.github/workflows/`, `docs/`, or `src/resources/example/`).
+- Call out any trade-offs, follow-up work, or known limitations.
+
+---
+
+## Validation
+
+Mark relevant checks:
+
+- [ ] `Invoke-NovaBuild`
+- [ ] `Test-NovaBuild`
+- [ ] `./scripts/build/Invoke-ScriptAnalyzerCI.ps1`
+- [ ] `./scripts/build/ci/Invoke-NovaModuleToolsCI.ps1`
+- [ ] Targeted Nova workflow validated (`% nova build`, `% nova test`, `% nova merge`, `% nova deploy`,
+  `% nova publish`,
+  `% nova release`, `% nova update`, `% nova notification`, or `% nova init` as relevant)
+- [ ] Docs/example only; executable validation not needed
+
+Validation notes:
+
+```
+<Fill with commands, outputs, or justification>
+```
+
+---
+
+## Documentation and release follow-up
+
+- [ ] `README.md` reviewed and updated if needed
+- [ ] `CONTRIBUTING.md` reviewed and updated if needed
+- [ ] `CHANGELOG.md` reviewed and updated if relevant
+- [ ] Command help updated if CLI or cmdlets changed
+- [ ] End-user docs updated if workflows changed
+- [ ] Examples updated if real usage changed
+- [ ] No documentation updates needed
+
+---
+
+## Maintainability, compatibility, and risk
+
+- [ ] Code Health / maintainability impact considered
+- [ ] No breaking change
+- [ ] Breaking change
+- [ ] Security-sensitive change
+- [ ] CI, workflow, or release-pipeline impact
+- [ ] Dependency-review impact
+
+Risk, rollout, or rollback notes:
+
+```
+<Describe impact, migration, rollback, or follow-up>
+```
+
+---
+
+## Style rules
+
+- Be concise and technical (no fluff)
+- Prefer bullet points over paragraphs
+- Be explicit about workflows (especially CI/CD and release flow)
+- Always think like a reviewer: "Where do I start reading?"
+- Never leave sections empty — infer or justify
+
+---
+
+## Example invocation
+
+Generate PR description from:
+
+- Commit: "fix: resolve ambiguous -w CLI parameter parsing"
+- Files changed: `src/private/cli/Invoke-NovaCli.ps1`
+
+---
+
+## Expected behavior
+
+The output should be ready to paste directly into a GitHub PR without edits.

CHANGELOG.md

@@ -14,8 +14,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Keep stable `Update-NovaModuleVersion` / `% nova bump` releases on the SemVer major-zero development line.
     - When the current stable version is `0.y.z` and commit history implies a breaking change, Nova now plans the next
       minor version instead of auto-jumping to `1.0.0`.
-    - The bump result still reports the detected `Major` label and now prints guidance about manually setting `1.0.0`
-      once the software is stable.
+  - Stable `0.y.z` bump results now print one warning about manually setting `1.0.0` once the software is stable,
+    while breaking-change bumps still report the detected `Major` label.
     - `-Preview` behavior is unchanged.
 
 ### Deprecated

README.md

@@ -218,9 +218,9 @@ These switches keep the behavior explicit and opt-in:
 - `Invoke-NovaRelease -ContinuousIntegration` forwards that CI intent through the nested build/bump boundaries and then
   restores the built module again after publish
 
-When Nova reports that a breaking-change bump was detected while the current stable version is still `0.y.z`, it also
-prints guidance about manually setting `1.0.0` once the software is stable. Preview bumps keep their current behavior
-and are not remapped by this rule.
+When the current stable version is still `0.y.z`, Nova also prints one warning that major version zero is still the
+initial-development line and that `1.0.0` must be set manually once the software is stable. Preview bumps keep their
+current behavior and are not remapped by this rule.
 
 Useful local helper:
 

docs/NovaModuleTools/en-US/Update-NovaModuleVersion.md

@@ -173,16 +173,16 @@ Re-imports the built `dist/<ProjectName>/<ProjectName>.psd1` first and then runs
 PS> Update-NovaModuleVersion -WhatIf
 
 What if: Performing the operation "Update module version using Major release label" on target "project.json".
-WARNING: Major version zero (0.y.z) is for initial development, so Nova keeps breaking-change bumps on the 0.y.z line and plans the next minor version instead of 1.0.0. Set 1.0.0 manually once the software is stable; after that, automatic major-version bumps work normally.
+WARNING: Major version zero (0.y.z) is for initial development, so Nova keeps stable bumps on the 0.y.z line and plans breaking-change bumps as the next minor version instead of 1.0.0. Set 1.0.0 manually once the software is stable; after that, automatic major-version bumps work normally.
 
 PreviousVersion: 0.1.0
 NewVersion: 0.2.0
 Label: Major
 CommitCount: 34
 ```
 
-Shows how breaking-change commits stay on the `0.y.z` initial-development line for stable bumps, while still warning
-that `1.0.0` should be set manually when the API becomes stable.
+Shows how stable `0.y.z` bumps still warn that `1.0.0` must be set manually when the API becomes stable, while
+breaking-change commits on that line continue to plan the next minor version instead of jumping straight to `1.0.0`.
 
 ## PARAMETERS
 

docs/versioning-and-updates.html

@@ -166,10 +166,12 @@ <h3>How Nova chooses the bump label</h3>
                     <li><strong>Patch</strong> for <code>fix:</code> commits and all other cases</li>
                 </ul>
                 <p>While your project is still on a stable <code>0.y.z</code> version, Nova treats SemVer major zero as
-                    the initial-development phase. A breaking-change bump still reports the detected
-                    <strong>Major</strong> label, but the planned stable version stays on the <code>0.y.z</code> line by
-                    advancing to the next minor version instead of jumping to <code>1.0.0</code>. Nova also prints a
-                    reminder to set <code>1.0.0</code> manually once the API is stable. Preview mode stays unchanged.
+                    the initial-development phase. Stable bumps stay on the <code>0.y.z</code> line, and a
+                    breaking-change
+                    bump still reports the detected <strong>Major</strong> label while advancing to the next minor
+                    version
+                    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.0.1 + Patch -> 0.0.2
 0.1.0 + Minor -> 0.2.0

src/private/cli/FormatNovaCliCommandResult.ps1

@@ -47,29 +47,7 @@ function Format-NovaCliVersionUpdateResult {
         'Version plan:'
     }
 
-    $summary = "$summaryPrefix $( $Result.PreviousVersion ) -> $( $Result.NewVersion ) | Label: $( $Result.Label ) | Commits: $( $Result.CommitCount )"
-    $advisoryMessage = Get-NovaCliVersionUpdateAdvisoryMessage -Result $Result
-    if ( [string]::IsNullOrWhiteSpace($advisoryMessage)) {
-        return $summary
-    }
-
-    return @(
-        $summary
-        $advisoryMessage
-    ) -join [Environment]::NewLine
-}
-
-function Get-NovaCliVersionUpdateAdvisoryMessage {
-    [CmdletBinding()]
-    param(
-        [Parameter(Mandatory)][object]$Result
-    )
-
-    if ($Result.PSObject.Properties.Name -notcontains 'AdvisoryMessage') {
-        return $null
-    }
-
-    return $Result.AdvisoryMessage
+    return "$summaryPrefix $( $Result.PreviousVersion ) -> $( $Result.NewVersion ) | Label: $( $Result.Label ) | Commits: $( $Result.CommitCount )"
 }
 
 function Format-NovaCliCommandResult {

src/private/cli/InvokeNovaCliCommandRoute.ps1

@@ -45,34 +45,55 @@ function Invoke-NovaCliBumpCommand {
         [Parameter(Mandatory)][pscustomobject]$InvocationContext
     )
 
+    $commandOutput = @(Invoke-NovaCliParsedCommand -InvocationContext $InvocationContext -ParserCommand 'ConvertFrom-NovaBumpCliArgument' -ActionCommand 'Update-NovaModuleVersion' 3>&1)
+    $capturedOutput = Read-NovaCliCapturedOutput -OutputRecords $commandOutput
+    Write-NovaCliCapturedWarning -WarningMessages $capturedOutput.WarningMessages
+    return $capturedOutput.Result
+}
+
+function Read-NovaCliCapturedOutput {
+    [CmdletBinding()]
+    param(
+        [object[]]$OutputRecords = @()
+    )
+
     $warningMessages = @()
-    $result = Invoke-NovaCliParsedCommand -InvocationContext $InvocationContext -ParserCommand 'ConvertFrom-NovaBumpCliArgument' -ActionCommand 'Update-NovaModuleVersion' -WarningAction SilentlyContinue -WarningVariable warningMessages
-    Write-NovaCliCapturedWarning -WarningMessages $warningMessages -SkippedMessage (Get-NovaCliVersionUpdateAdvisoryMessage -Result $result)
-    return $result
+    $result = $null
+    foreach ($outputRecord in @($OutputRecords)) {
+        if ($outputRecord -is [System.Management.Automation.WarningRecord]) {
+            $warningMessages += $outputRecord
+            continue
+        }
+
+        $result = $outputRecord
+    }
+
+    return [pscustomobject]@{
+        Result = $result
+        WarningMessages = @($warningMessages)
+    }
 }
 
 function Write-NovaCliCapturedWarning {
     [CmdletBinding()]
     param(
-        [object[]]$WarningMessages = @(),
-        [string]$SkippedMessage
+        [object[]]$WarningMessages = @()
     )
 
-    foreach ($message in (Get-NovaCliReplayWarningMessage -WarningMessages $WarningMessages -SkippedMessage $SkippedMessage)) {
+    foreach ($message in (Get-NovaCliReplayWarningMessage -WarningMessages $WarningMessages)) {
         Write-Warning $message
     }
 }
 
 function Get-NovaCliReplayWarningMessage {
     [CmdletBinding()]
     param(
-        [object[]]$WarningMessages = @(),
-        [string]$SkippedMessage
+        [object[]]$WarningMessages = @()
     )
 
     $messages = foreach ($warningMessage in @($WarningMessages)) {
         $text = ConvertTo-NovaCliWarningMessageText -WarningMessage $warningMessage
-        if ([string]::IsNullOrWhiteSpace($text) -or $text -eq $SkippedMessage) {
+        if ( [string]::IsNullOrWhiteSpace($text)) {
             continue
         }