fix(#187): clean up public help surface

[stiwicourage]

Summary

• Removed Invoke-NovaCli from the user-facing PlatyPS/public help surface and removed legacy Invoke-NovaRelease -PublishOption guidance from public help.
• Updated the help index and related-links so the documented help surface now matches the intended public PowerShell experience without promoting the routed CLI cmdlet as end-user guidance.
• Added regression coverage in tests/NovaCommandModel.Tests.ps1 so user-facing help discovery does not expose Invoke-NovaCli and Invoke-NovaRelease help does not document -PublishOption.
• This was needed to implement Remove Invoke-NovaCli and legacy release publish-option guidance from PlatyPS/public help. #187 in line with Align NovaModuleTools end-user docs and public help with explicit CLI vs PowerShell surfaces. #184: public help should keep the PowerShell help surface explicit and should not carry legacy or internal-facing guidance.
• Closes Remove Invoke-NovaCli and legacy release publish-option guidance from PlatyPS/public help. #187. Related to Align NovaModuleTools end-user docs and public help with explicit CLI vs PowerShell surfaces. #184.
• Closes Align NovaModuleTools end-user docs and public help with explicit CLI vs PowerShell surfaces. #184

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

Review guidance

• Start with docs/NovaModuleTools/en-US/Invoke-NovaRelease.md, docs/NovaModuleTools/en-US/NovaModuleTools.md, and the removed docs/NovaModuleTools/en-US/Invoke-NovaCli.md.
• Then review tests/NovaCommandModel.Tests.ps1 to see the regression coverage that keeps the help surface aligned with the intended public documentation boundary.
• The main trade-off is intentional: Invoke-NovaCli still exists at runtime, but it is no longer treated as part of the user-facing PlatyPS help surface.
• No production PowerShell behavior changed; this is a help-surface cleanup plus matching test update.

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:

Executed:
- pwsh -NoLogo -NoProfile -File ./run.ps1

Result:
- PSScriptAnalyzer: no findings
- Tests Passed: 685
- Failed: 0
- Skipped: 0
- NotRun: 0

Notes:
- An earlier validation pass exposed a help-test expectation that still assumed user-facing PublishOption help.
- The help test was updated to reflect the intended public help surface, then the full repository quality loop passed.

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:

This is a low-risk public-help cleanup.

Stable vs prerelease impact:
- None. project.json, Publish.yml, versioning logic, and release semantics are unchanged.

Compatibility impact:
- Runtime behavior stays the same.
- The user-facing change is documentation-only: Invoke-NovaCli and legacy PublishOption guidance are no longer presented in PlatyPS/public help.

Rollback:
- Restore the removed/edited help markdown files and the matching test expectations together if the repository later decides to expose that legacy help surface again.

Important

Do not use a public pull request to disclose a vulnerability before coordinated handling.
Use the private reporting path in SECURITY.md for new security issues.

[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: 100.0% (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: 100.0% covered >= threshold = 95%
  • Action:
    You have 281 files with a sum of 2874 covered and 1 uncovered lines of code.

• New & Changed Code Coverage

  • Pass/Fail Reason:
    No executable lines of code changed. (The change touched 0 files).