feat(#194): enhance guidance for file formatting and review processes

- Update documentation to require every changed or generated text file to end with exactly one trailing newline and no extra blank lines at the bottom.
- Add instructions for reviewing file endings before handoff in multiple documentation files.

Author: stiwicourage

.github/agents/powershell-developer.agent.md

@@ -16,6 +16,7 @@ Implement PowerShell command and helper changes in the NovaModuleTools style.
 - Preserve Nova's `project.json`-driven build model; do not add hand-written source `.psm1` or module `.psd1` files.
 - Read `project.json` `Manifest.PowerShellHostVersion` before implementing PowerShell changes and keep source, tests, and examples compatible with that target.
 - Add or update source-mirrored tests and PlatyPS-compatible help docs for the changed behavior.
+- Before handoff, review every changed or generated text file and normalize it to exactly one trailing newline with no extra blank lines at the bottom.
 
 ## Inputs to inspect
 
@@ -44,6 +45,7 @@ Implement PowerShell command and helper changes in the NovaModuleTools style.
 - Production code and tests both reflect the intended behavior.
 - Build output still comes from Nova-generated `dist/` files, not hand-authored module files in `src/`.
 - Any ScriptAnalyzer findings reported by `run.ps1` or `Invoke-ScriptAnalyzerCI.ps1` are resolved.
+- Every changed or generated text file has been checked and ends with exactly one trailing newline and no extra blank lines at the bottom.
 - Docs/changelog review is complete.
 - The relevant validation commands have been run.
 

.github/copilot-instructions.md

@@ -98,8 +98,8 @@ For documentation-only changes, executable validation may be skipped if no code
 
 ## File formatting rule
 
-- Modified or created text files must end with exactly one trailing newline.
-- Do not leave multiple blank lines at the end of edited files.
+- Before handoff, review every changed or created text file and ensure it ends with exactly one trailing newline and no extra blank lines at the bottom.
+- Do not leave any edited file with extra blank lines at the end, even if the functional code change is already complete.
 - Do not alter internal whitespace just to enforce the trailing newline rule.
 
 ## Safety constraints

.github/instructions/powershell-coding-standards.instructions.md

@@ -67,7 +67,7 @@ Use this file when changing `src/public/`, `src/private/`, or PowerShell build/r
 - Do not stack multiple blank lines.
 - Avoid decorative blank lines inside short blocks.
 - Keep one blank line between top-level declarations when a file contains more than one declaration.
-- Modified or created text files, including `.ps1` files, must end with exactly one trailing newline and no extra blank lines after the final statement.
+- Every changed or generated text file, including `.ps1` files, must end with exactly one trailing newline and no extra blank lines at the bottom.
 
 ## Maintainability rules
 
@@ -81,3 +81,4 @@ Use this file when changing `src/public/`, `src/private/`, or PowerShell build/r
 - Recheck `tests/ArchitectureGuardrails.Tests.ps1` when changing layering or helper placement.
 - Run `./run.ps1` before considering a code change complete.
 - Resolve any ScriptAnalyzer findings that `./run.ps1` reports before handoff.
+- Before handoff, review the changed/generated text files and normalize any file endings that violate the single-trailing-newline rule.

.github/prompts/implement-issue.prompt.md

@@ -19,12 +19,13 @@ Implement the issue in the NovaModuleTools repository using the repository-local
 7. Implement the smallest maintainable fix.
 8. Do not add PSScriptAnalyzer excluded rules or suppressions; fix analyzer findings in the code.
 9. If `run.ps1` or `Invoke-ScriptAnalyzerCI.ps1` reports ScriptAnalyzer findings, fix them before handoff instead of only reporting the failure.
-10. Add or update the matching source-mirrored Pester file for every changed `src/**/*.ps1` file; if the behavior is genuinely cross-cutting, document which integration/guardrail test owns it and why a mirrored unit test is not practical.
-11. Add or update PlatyPS-compatible help under `docs/<ProjectName>/en-US/` when public commands or public classes change.
-12. Review `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, `RELEASE_NOTE.md`, help docs, and `docs/*.html` as applicable.
-13. If a commit message is requested, derive it from `$GIT_BRANCH_NAME` and the implemented change using the repository's Conventional Commit rules.
-14. Run the relevant validation, then summarize what changed, why, and how it was verified.
-15. If that summary is returned as Markdown or copy-ready UI output, format it according to the `markdown-authoring` skill (`.github/skills/markdown-authoring/SKILL.md`).
+10. Before handoff, review every changed or generated text file and normalize it to exactly one trailing newline with no extra blank lines at the bottom.
+11. Add or update the matching source-mirrored Pester file for every changed `src/**/*.ps1` file; if the behavior is genuinely cross-cutting, document which integration/guardrail test owns it and why a mirrored unit test is not practical.
+12. Add or update PlatyPS-compatible help under `docs/<ProjectName>/en-US/` when public commands or public classes change.
+13. Review `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, `RELEASE_NOTE.md`, help docs, and `docs/*.html` as applicable.
+14. If a commit message is requested, derive it from `$GIT_BRANCH_NAME` and the implemented change using the repository's Conventional Commit rules.
+15. Run the relevant validation, then summarize what changed, why, and how it was verified.
+16. If that summary is returned as Markdown or copy-ready UI output, format it according to the `markdown-authoring` skill (`.github/skills/markdown-authoring/SKILL.md`).
 
 ## Repository-specific reminders
 

.github/skills/powershell-module-development/SKILL.md

@@ -34,6 +34,7 @@ Use this skill when changing public commands, private helpers, CLI routing suppo
 - Keep ScriptAnalyzer strict: do not add excluded rules, suppression attributes, or settings that hide analyzer findings.
 - Keep `run.ps1`-style local checks ordered as ScriptAnalyzer first, then `Invoke-NovaBuild`, then `Test-NovaBuild`.
 - If `run.ps1` or `Invoke-ScriptAnalyzerCI.ps1` reports ScriptAnalyzer findings, fix them before handoff instead of just reporting the failure.
+- Before handoff, review every changed or generated text file and normalize it to exactly one trailing newline with no extra blank lines at the end.
 - Add or update PlatyPS-compatible help under `docs/<ProjectName>/en-US/` when public commands or public classes change.
 - Add or update the source-mirrored Pester test file for every changed `src/**/*.ps1` file.
 

CHANGELOG.md

@@ -15,6 +15,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
     - The generated architect/design prompt now requires final design packages and issue/work item drafts to be returned as copy-ready Markdown using the project Markdown authoring guidance.
   - The generated guidance now explicitly keeps Agentic Copilot projects on the Nova build model, treats `.psm1` / `.psd1` files as generated `dist` output, requires PlatyPS-compatible help for public commands/classes, expects one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests, and now asks for a short project name so placeholders such as `Invoke-<ShortName>*` can be replaced in the generated starter files.
       - The generated guidance now keeps local `run.ps1` quality loops ordered as ScriptAnalyzer, `Invoke-NovaBuild`, then `Test-NovaBuild`, and tells agents to fix ScriptAnalyzer findings reported by `run.ps1` instead of excluding, suppressing, or handing them off unresolved.
+    - The generated PowerShell guidance now requires agents to review every changed or generated text file before handoff and normalize the file ending to exactly one trailing newline with no extra blank lines at the bottom.
 
 ### Changed
 

README.md

@@ -506,7 +506,7 @@ Packaged resources that ship with the module, including:
 - the packaged example project under `src/resources/example/`
 - the Agentic Copilot starter package under `src/resources/agentic-copilot/`
 
-The example project is both a shipped resource and a maintained working reference. The Agentic Copilot starter package is generated from Nova's repository-local agentic guidance, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, generated `dist` module files, command-help ownership, source-mirrored test guidance, and guidance that ScriptAnalyzer findings reported by `run.ps1` must be fixed before handoff. When the init flow adds that starter package, it also asks for a short project name so scaffolded guidance can replace placeholders such as `Invoke-<ShortName>*`. Run
+The example project is both a shipped resource and a maintained working reference. The Agentic Copilot starter package is generated from Nova's repository-local agentic guidance, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, generated `dist` module files, command-help ownership, source-mirrored test guidance, guidance that ScriptAnalyzer findings reported by `run.ps1` must be fixed before handoff, and a strict file-ending rule for changed or generated text files. When the init flow adds that starter package, it also asks for a short project name so scaffolded guidance can replace placeholders such as `Invoke-<ShortName>*`. Run
 `./scripts/build/Sync-AgenticCopilotScaffold.ps1` after changing `.github/agents/`, `.github/instructions/`,
 `.github/skills/`, `.github/prompts/`, or `.github/copilot-instructions.md` so future scaffolds and `dist` stay in sync.
 

RELEASE_NOTE.md

@@ -12,6 +12,7 @@ This file summarizes public cmdlet, CLI, configuration, and migration changes fo
     - Generated architect/design guidance now requires final design packages and issue/work item drafts to be returned as copy-ready Markdown using the project Markdown authoring guidance.
   - Generated implementation/test guidance now keeps projects on Nova build/test/package workflows, treats `.psm1` / `.psd1` files as generated output, calls out PlatyPS help plus one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests, and now asks for a short project name so placeholders such as `Invoke-<ShortName>*` can be replaced in the generated starter files.
       - Generated quality-loop guidance now keeps ScriptAnalyzer first and tells agents to fix ScriptAnalyzer findings reported by `run.ps1` instead of excluding, suppressing, or handing them off unresolved.
+    - Generated PowerShell guidance now requires agents to review every changed or generated text file before handoff and normalize the file ending to exactly one trailing newline with no extra blank lines at the bottom.
 
 ### Changed
 

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

@@ -27,7 +27,8 @@ PS> Initialize-NovaModule [-Path <string>] [-Example] [-WhatIf] [-Confirm] [<Com
 
 `Initialize-NovaModule` creates a new project folder, the standard `src/` layout, and a starter `project.json` file.
 
-The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. When you enable the Agentic package, Nova also asks for a project short name used in generated guidance placeholders such as `Invoke-<ShortName>*`; for NovaModuleTools the short name is `Nova`, but it could also have been `NMT`. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated `dist` module files, command-help ownership, source-mirrored test guidance, and guidance that ScriptAnalyzer findings reported by `run.ps1` must be fixed before handoff. For the standard scaffold, the interactive flow also includes optional basic Pester support.
+The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. When you enable the Agentic package, Nova also asks for a project short name used in generated guidance placeholders such as `Invoke-<ShortName>*`; for NovaModuleTools the short name is `Nova`, but it could also have been `NMT`. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated `dist` module files, command-help ownership, source-mirrored test guidance, guidance that ScriptAnalyzer findings reported by
+`run.ps1` must be fixed before handoff, and a strict file-ending rule for changed or generated text files. For the standard scaffold, the interactive flow also includes optional basic Pester support.
 
 If you enter an invalid answer during the interactive flow, `Initialize-NovaModule` reports the validation problem immediately and retries that prompt before it continues to the next question.
 

docs/commands.html

@@ -179,9 +179,9 @@ <h3>Start a new project</h3>
                             maintained agentic guidance through a filtered starter mirror, including Nova build/test
                             expectations, <code>project.json</code> <code>Manifest.PowerShellHostVersion</code>
                             compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated
-                            <code>dist</code> module files, command-help ownership, source-mirrored test guidance, and
+                            <code>dist</code> module files, command-help ownership, source-mirrored test guidance,
                             instructions to fix ScriptAnalyzer findings reported by <code>run.ps1</code> before
-                            handoff.
+                            handoff, and a strict file-ending rule for changed or generated text files.
                         </p>
                         <p>If you enable the Agentic package, Nova also asks for a short project name used in generated
                             guidance placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the