Summary

• Added a new existing-project Agentic Copilot apply/refresh workflow through
  Invoke-NovaAgenticCopilotScaffold and % nova copilot.
• This change was needed because Nova could add the Agentic Copilot scaffold during
  Initialize-NovaModule, but it did not have a supported way to add or refresh that scaffold in an already
  existing project.
• Release impact: both prerelease and future stable releases. The repository is currently on
  3.0.2-preview, but the new public cmdlet/CLI workflow and docs are user-facing behavior for the next
  stable release as well.
• Follow-up before release readiness: reviewer findings still need to be resolved for existing-project
  scaffold completeness and nova copilot --confirm/-c behavior/docs alignment.

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 the new public workflow: src/public/InvokeNovaAgenticCopilotScaffold.ps1,
  src/private/scaffold/GetNovaAgenticCopilotScaffoldWorkflowContext.ps1,
  src/private/scaffold/InvokeNovaAgenticCopilotScaffoldWorkflow.ps1, and the policy changes in
  src/private/scaffold/InitializeNovaModuleAgenticCopilotScaffold.ps1.
• Then review CLI routing and help wiring in src/private/cli/, src/resources/cli/help/copilot.psd1,
  and src/resources/cli/NovaCliHelp.txt.
• Finish with documentation alignment across
  docs/NovaModuleTools/en-US/Invoke-NovaAgenticCopilotScaffold.md, docs/commands.html,
  docs/core-workflows.html, README.md, CHANGELOG.md, and RELEASE_NOTE.md.
• Known limitations / follow-up:
  • Existing-project scaffold apply may still point users at formatting helper/test files that are not
    copied by the approved write policy.
  • nova copilot --confirm/-c behavior and docs are not yet reconciled.

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:

Ran: pwsh -NoLogo -NoProfile -File ./run.ps1
Result: passed

Additional checks already exercised during the change:
- Test-MarkdownCommandHelp passed for docs/NovaModuleTools/en-US/Invoke-NovaAgenticCopilotScaffold.md
- ./scripts/build/Sync-AgenticCopilotScaffold.ps1 passed
- HelpUri updates across docs/NovaModuleTools/en-US/*.md validated structurally

Not yet exercised directly:
- No explicit end-to-end real-project run of % nova copilot
- No explicit direct Invoke-NovaBuild run recorded outside the repository quality loop
- No CI helper or publish/release path execution

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 user-facing workflow addition, not a release-automation change.

Primary release risk is not semantic versioning or publish automation; it is behavioral consistency:
1. existing-project scaffold refresh may reference files it does not actually copy
2. nova copilot --confirm/-c behavior appears inconsistent with current docs/help

Recommended before calling this release-ready:
- resolve the two reviewer findings
- run an end-to-end apply/refresh against a real existing project root
- re-check changelog/release-note wording against the final shipped behavior after those fixes