diff --git a/docs/assets/icon.png b/docs/assets/icon.png index 4e4b5340..8140afcc 100644 Binary files a/docs/assets/icon.png and b/docs/assets/icon.png differ diff --git a/docs/core-workflows.html b/docs/core-workflows.html index f62e2606..247df09c 100644 --- a/docs/core-workflows.html +++ b/docs/core-workflows.html @@ -261,19 +261,29 @@

Reload safely after changes

inside a long-lived interactive PowerShell session, switch to the PowerShell view and do the full remove/build/import loop.

-
+
When local publish changes the story. -

PS> Publish-NovaModule -Local and % nova publish --local reload the - published - module from the local install path after a successful publish. That is different from the normal - build/import loop, which works from dist/.

+

Publish-NovaModule -Local reloads the published module from the local install path + after a successful publish. That is different from the normal build/import loop, which works + from dist/.

-
+ +
CI/self-hosting note.

When a later command in the same session must switch back to the built dist/ module, - use Invoke-NovaBuild -ContinuousIntegration or % nova build - --continuous-integration - so Nova restores the built module state automatically.

+ use Invoke-NovaBuild -ContinuousIntegration so Nova restores the built module state + automatically.

+
+ diff --git a/docs/getting-started.html b/docs/getting-started.html index b794f351..89e31dcb 100644 --- a/docs/getting-started.html +++ b/docs/getting-started.html @@ -123,10 +123,15 @@

2. Install the module

you plan to use the standalone command-line launcher later.

-

After import, you can use the PowerShell cmdlets directly. If you explicitly need the routed Nova - command surface from PowerShell, use Invoke-NovaCli.

-

Expected result: commands such as Get-NovaProjectInfo, Invoke-NovaBuild, - and nova resolve in your PowerShell session.

+ +

After import, you can use the PowerShell cmdlets directly.

+

Expected result: commands such as Get-NovaProjectInfo and + Invoke-NovaBuild resolve in your PowerShell session.

@@ -145,18 +150,20 @@

3. Choose PowerShell or CLI entrypoints

PowerShell cmdlets in pwsh You are already inside pwsh. - Import the module once, then use cmdlets directly. Use Invoke-NovaCli - only when you explicitly want the routed CLI surface from PowerShell. - + Import the module once, then use cmdlets directly. Standalone nova launcher You want to run Nova from zsh or bash on macOS/Linux. - Install the launcher once with Install-NovaCli. + Install the launcher once with Install-NovaCli before you expect + nova to resolve in your shell.
+

Install the standalone launcher on macOS/Linux

PS> Install-NovaCli

By default, the launcher is installed to ~/.local/bin/nova. If that directory is not @@ -233,8 +240,8 @@

5. Build and test the example

-

6. Import the built module and run a command

-

Now take the built module into the environment you want to use and run the example command.

+

6. Run the example command from the built or locally published module

+

Now take the generated module into the environment you want to use and run the example command.

Use the built module

diff --git a/docs/index.html b/docs/index.html index e73a5bf2..8faa4a96 100644 --- a/docs/index.html +++ b/docs/index.html @@ -187,10 +187,12 @@

Concepts

Recommended first 15-minute path

  1. Install the module and import it into PowerShell.
    2. -
  2. Scaffold the packaged example with PS> Initialize-NovaModule -Example.
    3. -
  3. Build with PS> Invoke-NovaBuild.
    4. -
  4. Test with PS> Test-NovaBuild.
    5. -
  5. Import the built example module and run PS> Get-ExampleGreeting.
    6. +
  6. If you want the nova launcher on macOS/Linux, install it with + Install-NovaCli.
    7. +
  7. Open Getting Started and keep the page + on your chosen PowerShell or command-line surface.
    8. +
  8. Scaffold the packaged example, then build and test it.
    9. +
  9. Run the example command from the built or locally published module.

This path proves the tool works, shows the real folder structure, and gives you a runnable module before you start customizing anything.

diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index 65c296f9..178e7efb 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -217,13 +217,14 @@

Build errors point into the generated .psm1

Install-NovaCli says it is for macOS/Linux only

Likely cause: that is the current intended behavior. The standalone launcher is for macOS/Linux shell use.

-

Fix: on Windows, import the module and use the PowerShell cmdlets directly. If you - explicitly need the routed CLI surface from PowerShell, call Invoke-NovaCli.

+

Fix: on Windows, import the module and use the PowerShell cmdlets directly. The + standalone nova launcher is a separate macOS/Linux install path, not something that + appears automatically after Import-Module.

PS> Import-Module NovaModuleTools
 PS> Get-NovaProjectInfo
-PS> Invoke-NovaCli version
-

Success looks like: you can run Nova commands from PowerShell on Windows without - installing the standalone launcher.

+PS> Invoke-NovaBuild +

Success looks like: the NovaModuleTools cmdlets work in your PowerShell session on + Windows, and you do not need a separate launcher install for that workflow.

See entrypoint guidance

diff --git a/docs/working-with-modules.html b/docs/working-with-modules.html index 17a5ef2f..c5179b0e 100644 --- a/docs/working-with-modules.html +++ b/docs/working-with-modules.html @@ -199,11 +199,18 @@

Use local publish intentionally

Use local publish when you want to simulate a real installed-module experience. Use the normal build/import loop when you just want fast iteration in dist/.

-
+
Do not confuse local publish with local release. -

Invoke-NovaRelease -Local publishes locally too, but it - does not import the published module into the current session afterward. That - special import behavior belongs to Publish-NovaModule -Local.

+

Publish-NovaModule -Local reloads the published module into the current PowerShell + session after success. Invoke-NovaRelease -Local publishes locally too, but it does + not import the published module afterward.

+
+