fix(#186): rewrite commands page as a surface cheat sheet

[stiwicourage]

Summary

• Rewrote docs/commands.html as a toggle-driven cheat sheet for the two supported end-user surfaces: native PowerShell cmdlets and the standalone nova launcher.
• Kept the page aligned with the rest of the website by making PowerShell the first and default toggle state, while still letting users switch to Command-line.
• This was needed to implement Rewrite docs/commands.html as a toggle-driven cheat sheet for PowerShell cmdlets and the standalone nova launcher. #186 in line with Align NovaModuleTools end-user docs and public help with explicit CLI vs PowerShell surfaces. #184: the command reference should be a fast lookup page that keeps CLI and PowerShell guidance explicit instead of mixing surfaces or presenting internal entrypoints as the normal user path.
• Closes Rewrite docs/commands.html as a toggle-driven cheat sheet for PowerShell cmdlets and the standalone nova launcher. #186. Related to 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/commands.html.
• Review the page in three passes:
  1. header/hero/toggle setup
  2. the command cards and examples for each workflow area
  3. the script that applies the selected surface
• Check that PowerShell now appears first and is the default, matching the rest of the docs site.
• Check that end-user guidance no longer treats Invoke-NovaCli as the normal website-facing path and that Install-NovaCli remains the explicit PowerShell-only exception for installing the standalone launcher.
• Trade-off: the page is now more cheat-sheet-like and intentionally lighter on tutorial narrative, with deeper guides linked out instead of repeated inline.

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:
- git --no-pager diff --check -- docs/commands.html
- content checks confirming:
  - docs/commands.html ends with one trailing newline
  - Invoke-NovaCli does not appear on the page
  - the updated CLI examples are present
- follow-up checks after the toggle-order fix confirming:
  - PowerShell is the first toggle button
  - PowerShell is the default selected mode
  - initial visible content matches the PowerShell-first default

Reason executable validation was skipped:
- This change only rewrites docs/commands.html.
- No product behavior, release/version logic, workflow YAML, or package behavior changed.

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 website-docs change.

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

Compatibility impact:
- No runtime behavior changed.
- The user-facing impact is a clearer, faster command reference with stricter surface separation and a PowerShell-first toggle order that now matches the rest of the site.

Rollback:
- Revert docs/commands.html if the cheat-sheet format or default surface choice needs to be backed out.

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]

No application code in the PR — skipped Code Health checks.

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).