Restore and clarify deploy help links and update tests

[stiwicourage]

Summary

• Improved the read-only update-notification status experience behind Get-NovaUpdateNotificationPreference by adding -Verbose guidance that explains whether Nova is reading a stored preference or falling back to the built-in default.
• Updated the mirrored private-helper test and the cmdlet help so the user-facing behavior, examples, and recovery guidance match the shipped implementation.
• This was needed to align issue refactor(Get-NovaUpdateNotificationPreference): align with terminal-ux-design principles #217 with the terminal UX guidance without changing the normal output object shape or the broader self-update workflow. Closes refactor(Get-NovaUpdateNotificationPreference): align with terminal-ux-design principles #217.

Affected area

• 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, 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 (project.json, workflow dependencies, release tooling)
• Security-sensitive change
• Documentation-only change
• Agentic Copilot Workflow + scaffold mirror + scaffold-sync guardrail test.
• Other

Review guidance

• Start with src/private/update/GetNovaUpdateNotificationPreferenceStatus.ps1, where the last commit adds the verbose-only status explanation while keeping the returned object unchanged.
• Then review tests/private/update/GetNovaUpdateNotificationPreferenceStatus.Tests.ps1 for the stored-settings and default-settings paths, and docs/NovaModuleTools/en-US/Get-NovaUpdateNotificationPreference.md for the help/examples update.
• Release impact is low: this affects the current 3.0.2-preview line and would flow unchanged into the next stable release, but it does not change publish/version semantics or the release pipeline.

Validation

• 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:

pwsh -NoLogo -NoProfile -Command "Invoke-NovaBuild; Import-Module ./dist/NovaModuleTools/NovaModuleTools.psd1 -Force; Test-MarkdownCommandHelp -Path ./docs/NovaModuleTools/en-US/Get-NovaUpdateNotificationPreference.md -DetailView"
pwsh -NoLogo -NoProfile -File ./scripts/build/Invoke-ScriptAnalyzerCI.ps1
pwsh -NoLogo -NoProfile -File ./run.ps1

run.ps1 covered the normal repository quality loop, including ScriptAnalyzer, build, and Test-NovaBuild.
No release automation or package/publish path changed in the last commit.

Documentation and release follow-up

• README.md reviewed and updated if contributor workflow, architecture, CI, release, or automation changed
• CONTRIBUTING.md reviewed and updated if contribution expectations or review guidance changed
• CHANGELOG.md reviewed and updated if the change matters to users, maintainers, or contributors
• RELEASE_NOTE.md reviewed and updated if the change affects public cmdlet usage, CLI usage, configuration semantics, or migration expectations
• docs/NovaModuleTools/en-US/ help updated if a public command or CLI behavior changed
• docs/*.html updated if end-user workflows or examples changed
• src/resources/example/ reviewed and updated if the real-world project layout, package model, or upload workflow changed
• No documentation, changelog, release-note, or example updates were 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:

Low risk. The last commit is limited to notification-preference status messaging, tests, and help/release text.

Compatibility:
- Normal Get-NovaUpdateNotificationPreference output remains the same.
- The change only adds clearer guidance on the -Verbose path.

Rollback:
- Revert the GetNovaUpdateNotificationPreferenceStatus helper change and its matching test/help/changelog/release-note updates.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[codescene-delta-analysis]

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.

[codescene-delta-analysis]

Code Coverage Gates Passed
Overall Coverage: 99.4% (required = 95%)
New & Changed Code Coverage: 100% (required = 99%)

Review details by gate

• Overall Coverage

  • Pass/Fail Reason:
    The overall coverage gate was checked for all code and meets the goal: 99.4% covered >= threshold = 95%
  • Action:
    You have 292 files with a sum of 3297 covered and 19 uncovered lines of code.

• New & Changed Code Coverage

  • Pass/Fail Reason:
    New or changed code meets coverage goal: 100% covered >= threshold = 99%
  • Action:
    You modified 1 files, and covered 13 added/modified lines of code.