feat(#212): add nova copilot command for Agentic Copilot scaffold

- Introduced `Invoke-NovaAgenticCopilotScaffold` for applying or refreshing the Agentic Copilot workflow in existing projects.
- Added `% nova copilot` command for CLI usage.
- Updated help documentation and examples for the new command.

Author: stiwicourage

.github/agents/docs-site.agent.md

@@ -14,6 +14,7 @@ Keep the GitHub Pages documentation under `docs/*.html` accurate, user-focused,
 - Update `docs/*.html` when end-user workflows, examples, or website wording change.
 - Preserve the separation between CLI-oriented website docs and PowerShell cmdlet help.
 - Check whether source, tests, help docs, and website docs still agree after a change.
+- Keep command-surface-toggle pages honest by splitting CLI-only and PowerShell-only wording into the matching `data-command-visibility` blocks instead of mixing both spellings in shared prose.
 
 ## Inputs to inspect
 
@@ -37,15 +38,18 @@ Keep the GitHub Pages documentation under `docs/*.html` accurate, user-focused,
 - Treat `docs/*.html` as end-user website docs, not cmdlet help.
 - Keep CLI and cmdlet surfaces clearly separated.
 - Mention PowerShell-only commands in CLI-oriented docs only when there is no CLI equivalent for that scenario, such as installing NovaModuleTools with `Install-Module`.
+- On pages with the surface toggle, only show `--option` spellings in command-line-visible blocks and only show `-Parameter` spellings in PowerShell-visible blocks unless the wording is fully surface-neutral.
 
 ## Definition of done
 
 - The changed website docs reflect the current behavior.
 - CLI-oriented docs do not drift into cmdlet-help wording.
+- Surface-specific labels, flags, and parameter names match the active website command surface.
 - Relevant contributor docs and changelog were reviewed for follow-up impact.
 
 ## Must not do
 
 - Must not mix cmdlet syntax into CLI docs when a CLI variant exists.
+- Must not leave shared always-visible HTML copy with both CLI flags and PowerShell parameters when the page already has the command-surface toggle.
 - Must not use `docs/*.html` as a duplicate of `docs/NovaModuleTools/en-US/*.md`.
 - Must not leave installation/documentation exceptions implicit; state them clearly.

.github/instructions/documentation-separation.instructions.md

@@ -20,6 +20,10 @@ NovaModuleTools has multiple documentation surfaces with different audiences. Ke
 - Do not write cmdlet help markdown as if it were `nova` CLI documentation.
 - Use CLI syntax in CLI-oriented website docs when a CLI variant exists.
 - Use cmdlet syntax in help markdown and PowerShell-specific contributor guidance.
+- On website pages that support the command-surface toggle, keep surface-specific wording behind the matching visibility gate.
+    - CLI-only flags, labels, and guidance belong in elements marked with `data-command-visibility="command-line"`.
+    - PowerShell-only parameters, labels, and guidance belong in elements marked with `data-command-visibility="powershell"`.
+    - Shared prose should stay surface-neutral instead of mixing `--option` and `-Parameter` spellings in the same always-visible paragraph.
 
 ## Allowed exception
 
@@ -33,6 +37,7 @@ NovaModuleTools has multiple documentation surfaces with different audiences. Ke
 - Does this page describe a `nova` workflow or a PowerShell cmdlet workflow?
 - If a `nova` command exists, is the website doc using it instead of the cmdlet?
 - If a cmdlet is shown in website docs, is it there because no CLI variant exists?
+- If the page uses the command-surface toggle, do the visible labels, flags, and parameter names match the selected surface?
 - Would an end user mistake this page for cmdlet help?
 
 ## Follow-up expectations

.github/skills/docs-site/SKILL.md

@@ -24,17 +24,20 @@ Use this skill when changing `docs/*.html`, end-user examples, installation guid
 - Use CLI-oriented examples when the workflow has a `nova` variant.
 - Mention PowerShell cmdlets only when no CLI equivalent exists for that scenario.
 - Keep installation guidance explicit about PowerShell-only steps such as `Install-Module`.
+- On pages with the command-surface toggle, keep option/parameter wording aligned with the active surface by using `data-command-visibility="command-line"` and `data-command-visibility="powershell"` blocks instead of one shared paragraph that mixes CLI flags with PowerShell parameters.
 - Recheck the matching command-help markdown when public behavior changes.
 
 ## Common pitfalls
 
 - Mixing `Get-/Set-/Invoke-/Install-` cmdlets into CLI docs where `nova` exists
+- Leaving `--option` text visible in PowerShell mode, or `-Parameter` text visible in command-line mode, because the surrounding prose was not split by `data-command-visibility`
 - Duplicating cmdlet help text in website docs instead of adapting it for end users
 - Forgetting that `docs/NovaModuleTools/en-US/*.md` and `docs/*.html` serve different audiences
 - Updating website docs without reviewing changelog or contributor-doc impact
 
 ## Verification
 
 - Read the touched HTML page as an end-user flow
+- Toggle the page mentally between PowerShell and command-line surfaces and confirm the visible option/parameter names still match that surface
 - Check whether the same behavior is documented consistently in help markdown or contributor docs
 - Use docs-only validation when no executable behavior changed

CHANGELOG.md

@@ -7,6 +7,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ### Added
 
+- Added `Invoke-NovaAgenticCopilotScaffold` and `% nova copilot` for applying or refreshing Nova's managed Agentic Copilot scaffold in an existing project root.
+    - The workflow reads `ProjectName` and `Description` from `project.json`, requires a `ShortName` on every run for token replacement, and fails clearly when the project metadata or short name is invalid.
+    - Nova refreshes only the approved managed Agentic Copilot paths under `.github/` plus `AGENTS.md` and `CONTRIBUTING.md`, while `README.md`, `CHANGELOG.md`, and `RELEASE_NOTE.md` are created only when they are missing.
+    - The new cmdlet and CLI route prompt before overwriting managed scaffold content by default, and support non-interactive execution only through `-OverrideWarning` / `--override-warning` / `-o`.
+
 ### Changed
 
 ### Deprecated
@@ -433,4 +438,3 @@ This release was yanked because it removed the implicit `Pester` dependency, bef
 [0.0.6]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.5...Version_0.0.6
 [0.0.5]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.4...Version_0.0.5
 [0.0.4]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.3...Version_0.0.4
-

README.md

@@ -176,6 +176,19 @@ Direct PowerShell cmdlets such as `Publish-NovaModule`, `Deploy-NovaPackage`, an
 
 The module does not export a PowerShell alias named `nova`. Install the bundled launcher with `Install-NovaCli` when you want `% nova ...` available directly from your shell.
 
+### Apply or refresh the Agentic Copilot scaffold
+
+Use the dedicated scaffold command when you want to add Nova's maintained Agentic Copilot workflow to an existing project, or refresh an older scaffold to Nova's latest managed version:
+
+```powershell
+PS> Invoke-NovaAgenticCopilotScaffold -ShortName NMT
+% nova copilot --short-name NMT
+```
+
+The target directory must contain a valid `project.json`. Nova reads `ProjectName` and `Description` from that file, requires `ShortName` on every run for token replacement, and refreshes only the Nova-managed Agentic Copilot paths under `.github/` plus `AGENTS.md` and `CONTRIBUTING.md`. Existing `README.md`, `CHANGELOG.md`, and `RELEASE_NOTE.md` are preserved and are created only when they are missing.
+
+By default the scaffold flow prompts before it overwrites the managed paths. Use `-OverrideWarning` or `--override-warning` only when you intentionally want a non-interactive apply. The CLI also supports the short form `% nova copilot -n NMT -o`. Use `-WhatIf` or `--what-if` when you want to preview the operation without changing files.
+
 ### Reload the built module while iterating
 
 Use the built output during development so you validate the same shape CI uses:

RELEASE_NOTE.md

@@ -6,6 +6,11 @@ This file summarizes the release notes for NovaModuleTools. **UNRELEASED** chang
 
 ### Added
 
+- Added `Invoke-NovaAgenticCopilotScaffold` and `% nova copilot` for adding or refreshing Nova's managed Agentic Copilot workflow in an existing project.
+    - The workflow reads `ProjectName` and `Description` from `project.json`, requires an explicit `ShortName` on every run, and stops with a clear validation error when the target project metadata is missing or invalid.
+    - Nova refreshes only its managed Agentic Copilot files and folders, while `README.md`, `CHANGELOG.md`, and `RELEASE_NOTE.md` are created only when they are missing.
+    - The command prompts before overwrite by default and supports non-interactive execution only through `-OverrideWarning` / `--override-warning` / `-o`.
+
 ### Changed
 
 ### Deprecated
@@ -195,4 +200,3 @@ This release was yanked because it removed the implicit `Pester` dependency befo
 ## [0.0.4] - 2024-06-25
 ### Added
 - First PowerShell Gallery release of NovaModuleTools with the initial module workflow support.
-

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

@@ -1,7 +1,7 @@
 ---
 document type: cmdlet
 external help file: NovaModuleTools-Help.xml
-HelpUri: ''
+HelpUri: 'https://www.novamoduletools.com/packaging-and-delivery.html#upload'
 Locale: en-US
 Module Name: NovaModuleTools
 ms.date: 04/25/2026

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

@@ -1,7 +1,7 @@
 ---
 document type: cmdlet
 external help file: NovaModuleTools-Help.xml
-HelpUri: ''
+HelpUri: 'https://www.novamoduletools.com/project-json-reference.html'
 Locale: en-US
 Module Name: NovaModuleTools
 ms.date: 05/06/2026

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

@@ -1,7 +1,7 @@
 ---
 document type: cmdlet
 external help file: NovaModuleTools-Help.xml
-HelpUri: ''
+HelpUri: 'https://www.novamoduletools.com/versioning-and-updates.html#notification-preferences'
 Locale: en-US
 Module Name: NovaModuleTools
 ms.date: 04/25/2026

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

@@ -1,7 +1,7 @@
 ---
 document type: cmdlet
 external help file: NovaModuleTools-Help.xml
-HelpUri: ''
+HelpUri: 'https://www.novamoduletools.com/core-workflows.html#scaffold'
 Locale: en-US
 Module Name: NovaModuleTools
 ms.date: 04/25/2026