feat(#112): clean up PowerShell help content (#120)

- Remove CLI syntax and GNU-style options from `Get-Help` pages
- Update examples to use PowerShell cmdlet syntax instead of CLI commands

Author: stiwicourage

CHANGELOG.md

@@ -118,6 +118,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
       easier to scan and less visually cramped.
   - The getting started and core workflows guides now let readers switch between PowerShell and command-line
     examples, including the local-publish-plus-`pwsh` handoff for `Get-ExampleGreeting` and fresh-process `pwsh`
+
+- Clean the generated PowerShell cmdlet help so `Get-Help` pages no longer mix in `nova` launcher syntax or GNU-style
+  CLI options.
     import/reload validation from the command-line path.
   - The command reference, working-with-modules, packaging-and-delivery, versioning-and-updates, and troubleshooting
     guides now use the same centered command-surface header and PowerShell/command-line example switching model.

docs/NovaModuleTools/en-US/Deploy-NovaPackage.md

@@ -63,10 +63,10 @@ raw repository named `LocalNexus` from `Package.Repositories`.
 ### EXAMPLE 2
 
 ```powershell
-% nova deploy --repository LocalNexus
+PS> Deploy-NovaPackage -Repository LocalNexus -WhatIf
 ```
 
-Runs the same raw package upload flow through the Nova CLI.
+Previews the raw package upload flow and the resolved destination URLs without uploading artifacts.
 
 ### EXAMPLE 3
 

docs/NovaModuleTools/en-US/Get-NovaUpdateNotificationPreference.md

@@ -26,16 +26,13 @@ PS> Get-NovaUpdateNotificationPreference [<CommonParameters>]
 ## DESCRIPTION
 
 `Get-NovaUpdateNotificationPreference` returns the current user preference that controls whether
-`Update-NovaModuleTool` / `Update-NovaModuleTools` and `% nova update` may select prerelease versions of
-`NovaModuleTools`.
+`Update-NovaModuleTool` / `Update-NovaModuleTools` may select prerelease versions of `NovaModuleTools`.
 
-The same stored preference is also used by `Update-NovaModuleTool` (alias: `Update-NovaModuleTools`) and `% nova update`
-when they decide whether a prerelease self-update is eligible.
+The same stored preference is also used by `Update-NovaModuleTool` (alias: `Update-NovaModuleTools`) when it decides
+whether a prerelease self-update is eligible.
 
 Stable self-updates remain available and do not require prerelease eligibility.
 
-If you prefer the Nova CLI surface, run `% nova notification` to view the same preference.
-
 ## EXAMPLES
 
 ### EXAMPLE 1
@@ -50,10 +47,11 @@ preference is stored.
 ### EXAMPLE 2
 
 ```text
-% nova notification
+PS> Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications
+PS> Get-NovaUpdateNotificationPreference
 ```
 
-Shows the same prerelease self-update state from the Nova CLI entrypoint.
+Shows the stored preference after prerelease self-updates have been disabled.
 
 ## PARAMETERS
 
@@ -77,15 +75,13 @@ Returns the prerelease self-update state, the always-available stable-update sta
 
 ## NOTES
 
-Use `PS> Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications` or `$ nova notification --disable` /
-`$ nova notification -d` to stop prerelease self-updates from being eligible.
+Use `Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications` to stop prerelease self-updates from being
+eligible.
 
-Use `PS> Set-NovaUpdateNotificationPreference -EnablePrereleaseNotifications` or `$ nova notification --enable` /
-`$ nova notification -e` to allow prerelease self-updates again.
+Use `Set-NovaUpdateNotificationPreference -EnablePrereleaseNotifications` to allow prerelease self-updates again.
 
-When prerelease notifications are enabled again, `Update-NovaModuleTool` / `Update-NovaModuleTools` and `% nova update`
-may again select a prerelease target. Prerelease self-updates still require explicit confirmation before the update
-proceeds.
+When prerelease notifications are enabled again, `Update-NovaModuleTool` / `Update-NovaModuleTools` may again select a
+prerelease target. Prerelease self-updates still require explicit confirmation before the update proceeds.
 
 ## RELATED LINKS
 

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

@@ -74,10 +74,10 @@ prompt flow to the copied `project.json`.
 ### EXAMPLE 4
 
 ```text
-% nova init --example --path ~/Work
+PS> Initialize-NovaModule -Example -Path ~/Work -WhatIf
 ```
 
-Runs the same example-based scaffold flow through the `nova` CLI.
+Shows what the example-based scaffold flow would create without writing files.
 
 ## PARAMETERS
 

docs/NovaModuleTools/en-US/Invoke-NovaBuild.md

@@ -40,10 +40,10 @@ The command:
 6. copies project resources into the built module output
 
 To update the installed `NovaModuleTools` module itself, use `Update-NovaModuleTool` (alias:
-`Update-NovaModuleTools`) or `% nova update`.
+`Update-NovaModuleTools`).
 
-Use `Set-NovaUpdateNotificationPreference`, `Get-NovaUpdateNotificationPreference`, or the `% nova notification`
-commands when you want to control whether prerelease self-updates are eligible.
+Use `Set-NovaUpdateNotificationPreference` or `Get-NovaUpdateNotificationPreference` when you want to control whether
+prerelease self-updates are eligible.
 
 If `Invoke-NovaBuild` detects that a newer `NovaModuleTools` release or prerelease is available after the build, the
 warning includes the recommended update command together with the release notes link from the installed module

docs/NovaModuleTools/en-US/Invoke-NovaCli.md

@@ -29,31 +29,17 @@ PS> Invoke-NovaCli [[-Command] <string>] [[-Arguments] <string[]>] [-WhatIf] [-C
 
 Use it when you need scripted routing inside PowerShell, for example in tests, automation, or wrapper functions.
 
-Use the installed `nova` launcher when you want the end-user CLI experience. The module does not export `nova` as a
-PowerShell alias.
+`Invoke-NovaCli` routes the same top-level command names as the bundled command-line launcher, but it keeps the entry
+surface explicit for PowerShell callers.
 
-`Invoke-NovaCli` routes the same top-level commands that the launcher supports, including `% nova info`, `% nova
-version`, `% nova --version`, `% nova --help`, `% nova build`, `% nova test`, `% nova package`, `% nova deploy`, `% nova
-init`, `% nova bump`, `% nova update`, `% nova notification`, `% nova publish`, and `% nova release`.
+Use `-Command` to select the routed command and `-Arguments` when a routed command needs additional raw arguments.
 
-Mutating routed commands forward CLI `--verbose`/`-v` and `--what-if`/`-w` to the underlying cmdlet. Routed CLI
-`--confirm`/`-c` is handled by the shared CLI confirmation flow so the launcher never exposes PowerShell's interactive
-`Suspend` prompt.
-
-Only the supported mutating `nova` commands accept `--confirm`/`-c`. Read-only routes and `% nova init` reject the CLI
-confirm flag with a clear validation error.
+When `-Command` is omitted, `Invoke-NovaCli` routes to the root help view.
 
 Direct PowerShell cmdlets such as `Invoke-NovaBuild`, `Publish-NovaModule`, `Deploy-NovaPackage`,
 `Update-NovaModuleVersion`, and `Invoke-NovaRelease` keep their native `-WhatIf` and `-Confirm` behavior when called
 directly.
 
-Use `% nova <command> --help` or `% nova <command> -h` when you want short CLI help for a specific command.
-
-Use `% nova --help <command>` or `% nova -h <command>` when you want long CLI help for a specific command.
-
-The launcher help is CLI-native and uses CLI option spellings such as `--repository` and `-r`. Use PowerShell
-`Get-Help` when you want cmdlet help instead.
-
 ## EXAMPLES
 
 ### EXAMPLE 1
@@ -67,68 +53,44 @@ Routes the build workflow through the explicit PowerShell cmdlet entrypoint.
 ### EXAMPLE 2
 
 ```text
-PS> Invoke-NovaCli -Command publish -Arguments @('--local') -WhatIf
+PS> Invoke-NovaCli -Command version
 ```
 
-Routes the local publish workflow while keeping native PowerShell `-WhatIf` on the outer call.
+Routes the version workflow through the explicit PowerShell cmdlet entrypoint.
 
 ### EXAMPLE 3
 
 ```text
-PS> Invoke-NovaCli -Command init -Arguments @('--example', '--path', '~/Work')
+PS> Invoke-NovaCli -Command update -WhatIf
 ```
 
-Starts the example scaffold flow from the explicit PowerShell cmdlet entrypoint.
+Routes the self-update workflow while previewing the outer PowerShell action.
 
 ### EXAMPLE 4
 
 ```text
-% nova build --confirm
+PS> Invoke-NovaCli -Command notification
 ```
 
-Runs the routed build workflow through the launcher-facing CLI surface and uses the shared CLI confirmation flow.
+Routes the notification-preference status workflow through the explicit PowerShell cmdlet entrypoint.
 
 ### EXAMPLE 5
 
 ```text
-% nova version --installed
-```
-
-Returns the locally installed version of the current project/module.
-
-### EXAMPLE 6
-
-```text
-% nova --version
-```
-
-Returns the installed `NovaModuleTools` module version.
-
-### EXAMPLE 7
-
-```text
-% nova update
-```
-
-Runs the self-update flow through the launcher-oriented CLI surface.
-
-### EXAMPLE 8
-
-```text
-% nova notification --disable
+PS> Invoke-NovaCli -Command build -Confirm
 ```
 
-Disables prerelease self-update eligibility through the launcher-facing CLI surface.
+Prompts before the routed build workflow starts.
 
 ## PARAMETERS
 
 ### -Command
 
-Top-level Nova command to route. Defaults to `--help`.
+Top-level Nova command to route. When omitted, the cmdlet routes to the root help view.
 
 ```yaml
 Type: System.String
-DefaultValue: --help
+DefaultValue: (root help view)
 SupportsWildcards: false
 Aliases: [ ]
 ParameterSets:
@@ -147,6 +109,8 @@ HelpMessage: ''
 
 Raw routed argument list for the selected Nova command.
 
+Use this parameter when a routed command needs additional command-specific arguments.
+
 ```yaml
 Type: System.String[]
 DefaultValue: ''
@@ -187,10 +151,11 @@ Returns the same output that the selected routed Nova command returns.
 Use `Invoke-NovaCli` directly when you need the underlying PowerShell command in scripts, tests, or command dispatch
 scenarios.
 
-Install the bundled `nova` launcher with `Install-NovaCli` when you want `% nova ...` available from your shell.
+Install the bundled command-line launcher with `Install-NovaCli` when you want the same routed command surface from
+your shell.
 
 `Invoke-NovaCli` uses `SupportsShouldProcess` so the outer PowerShell call still surfaces native `-WhatIf` and
-`-Confirm`, while routed CLI `--confirm`/`-c` stays inside the shared CLI confirmation flow.
+`-Confirm` support.
 
 ## RELATED LINKS
 

docs/NovaModuleTools/en-US/New-NovaModulePackage.md

@@ -87,10 +87,10 @@ when `Package.Types` is omitted or resolves to `NuGet`.
 ### EXAMPLE 2
 
 ```text
-% nova package
+PS> New-NovaModulePackage -WhatIf
 ```
 
-Runs the same packaging workflow through the `nova` CLI.
+Previews the build, test, and packaging workflow without writing a package artifact.
 
 ### EXAMPLE 3
 

docs/NovaModuleTools/en-US/NovaModuleTools.md

@@ -32,7 +32,7 @@ Shows whether prerelease update notifications are enabled. Stable release notifi
 
 ### `PS> Install-NovaCli`
 
-Installs the bundled `nova` launcher into a user command directory on macOS or Linux.
+Installs the bundled command-line launcher into a user command directory on macOS or Linux.
 
 ### `PS> Invoke-NovaBuild`
 
@@ -73,7 +73,7 @@ Builds, tests, and publishes the current project either locally or to a reposito
 
 ### `PS> Set-NovaUpdateNotificationPreference`
 
-Enables or disables whether prerelease self-updates are eligible for `Update-NovaModuleTool` and `% nova update`.
+Enables or disables whether prerelease self-updates are eligible for `Update-NovaModuleTool`.
 
 ### `PS> Update-NovaModuleVersion`
 

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

@@ -43,11 +43,7 @@ Use repository mode when you want to publish the built module to a registered Po
 This command supports `-WhatIf` and `-Confirm` through PowerShell `SupportsShouldProcess`. Use `-WhatIf` to preview the
 resolved publish target and workflow without building, testing, or publishing.
 
-When you run the same workflow through `% nova publish --confirm` / `% nova publish -c`, the CLI handles confirmation
-before
-the routed publish starts. `Y` / `Yes` and `A` / `Yes to All` continue, `N` / `No` and `L` / `No to All` cancel the
-publish with a non-zero exit code, and `S` / `Suspend` is treated as cancel because nested PowerShell prompts are not
-supported in CLI mode.
+Use `-Confirm` when you want PowerShell to prompt before the publish workflow starts.
 
 ## EXAMPLES
 
@@ -80,10 +76,10 @@ Builds, tests, and publishes the module to `PSGallery`.
 ### EXAMPLE 4
 
 ```text
-% nova publish --repository PSGallery --api-key $PSGALLERY_API
+PS> Publish-NovaModule -Repository PSGallery -Confirm
 ```
 
-Runs the same publish flow through the `nova` CLI.
+Prompts before the repository publish workflow starts.
 
 ### EXAMPLE 5
 
@@ -215,8 +211,6 @@ source project or from `dist/`.
 `Publish-NovaModule` uses `SupportsShouldProcess`, so `Get-Help Publish-NovaModule -Full` should surface native
 `-WhatIf` and `-Confirm` support.
 
-The CLI-specific `% nova publish --confirm` / `% nova publish -c` prompt is separate from native PowerShell `-Confirm`.
-It never opens a nested PowerShell `Suspend` prompt.
 
 ## RELATED LINKS
 

docs/NovaModuleTools/en-US/Set-NovaUpdateNotificationPreference.md

@@ -32,17 +32,13 @@ PS> Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications [-WhatI
 ## DESCRIPTION
 
 `Set-NovaUpdateNotificationPreference` manages the user preference that controls whether
-`Update-NovaModuleTool` / `Update-NovaModuleTools` and `% nova update` may select prerelease versions of
-`NovaModuleTools`.
+`Update-NovaModuleTool` / `Update-NovaModuleTools` may select prerelease versions of `NovaModuleTools`.
 
-The same stored preference is also used by `Update-NovaModuleTool` (alias: `Update-NovaModuleTools`) and `% nova update`
-when they decide whether a prerelease self-update can be selected.
+The same stored preference is also used by `Update-NovaModuleTool` (alias: `Update-NovaModuleTools`) when it decides
+whether a prerelease self-update can be selected.
 
 Stable self-updates remain available and do not require prerelease eligibility.
 
-If you prefer the Nova CLI surface, use `% nova notification --disable` / `% nova notification -d` and
-`% nova notification --enable` / `% nova notification -e` for the same stored preference.
-
 ## EXAMPLES
 
 ### EXAMPLE 1
@@ -51,8 +47,7 @@ If you prefer the Nova CLI surface, use `% nova notification --disable` / `% nov
 PS> Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications
 ```
 
-Turns off prerelease self-update eligibility and restricts `Update-NovaModuleTool` / `% nova update` to stable releases
-only.
+Turns off prerelease self-update eligibility and restricts `Update-NovaModuleTool` to stable releases only.
 
 ### EXAMPLE 2
 
@@ -61,23 +56,23 @@ PS> Set-NovaUpdateNotificationPreference -EnablePrereleaseNotifications
 ```
 
 Turns prerelease self-update eligibility back on, which allows `Update-NovaModuleTool` /
-`Update-NovaModuleTools` and `% nova update` to consider a prerelease target again.
+`Update-NovaModuleTools` to consider a prerelease target again.
 
 ### EXAMPLE 3
 
 ```text
-% nova notification --disable
+PS> Set-NovaUpdateNotificationPreference -DisablePrereleaseNotifications -WhatIf
 ```
 
-Uses the Nova CLI entrypoint to disable prerelease self-update eligibility.
+Previews the change that would disable prerelease self-update eligibility.
 
 ### EXAMPLE 4
 
 ```text
-% nova notification --enable
+PS> Set-NovaUpdateNotificationPreference -EnablePrereleaseNotifications -Confirm
 ```
 
-Uses the Nova CLI entrypoint to re-enable prerelease self-update eligibility.
+Prompts before the preference is changed to allow prerelease self-updates again.
 
 ## PARAMETERS
 
@@ -201,7 +196,6 @@ Returns the current prerelease self-update state, the always-available stable-up
 
 Use this command together with `Get-NovaUpdateNotificationPreference` when you want to confirm the stored setting.
 
-Use `% nova notification` when you want to view the same setting through the CLI surface.
 
 ## RELATED LINKS