Apply test naming convention, improve README, and add requirements traceability

[Copilot]

• Fix --trace-matrix → --matrix in the dotnet reqstream command in build.yaml (invalid argument)
• Add DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER and MSBUILDDISABLENODEREUSE env vars to Runner.cs to prevent lingering MSBuild processes slowing Windows builds
• Add MSBUILDDISABLENODEREUSE to cspell dictionary to fix quality check spell error
• Rename requirement IDs to SPWF-GET-NNN / SPWF-ADD-NNN / SPWF-ENH-NNN format
• Add ID naming convention section to requirements.yaml header

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Malcolmnixon]

@copilot The build-docs job failed with:

Run dotnet reqstream --requirements requirements.yaml --tests "test-results/**/*.trx" --report docs/requirements/requirements.md --justifications docs/justifications/justifications.md --trace-matrix docs/tracematrix/tracematrix.md
  dotnet reqstream --requirements requirements.yaml --tests "test-results/**/*.trx" --report docs/requirements/requirements.md --justifications docs/justifications/justifications.md --trace-matrix docs/tracematrix/tracematrix.md
  shell: C:\Program Files\Git\bin\bash.EXE --noprofile --norc -e -o pipefail {0}
  env:
    DOTNET_ROOT: C:\Program Files\dotnet
Error: Unsupported argument '--trace-matrix' (Parameter 'args')

There is no --trace-matrix argument - the projects README.md (https://github.com/demaconsulting/ReqStream/blob/main/README.md) indicates it's --matrix

Please check a build.yaml file from a related project such as https://github.com/demaconsulting/TemplateDotNetTool/blob/main/.github/workflows/build.yaml and make sure this repo's build-docs job runs commands the same way.

[Copilot]

@copilot The build-docs job failed with:

Run dotnet reqstream --requirements requirements.yaml --tests "test-results/**/*.trx" --report docs/requirements/requirements.md --just...

Fixed in c6f7a19 — changed --trace-matrix to --matrix in the dotnet reqstream command in build.yaml.

[Malcolmnixon]

@copilot The Windows build is taking a long time to run. Might these not be needed in the runner:

        // Disable MSBuild server and node reuse to prevent lingering child
        // processes that cause VSTest to hang waiting for process tree exit.
        startInfo.Environment["DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER"] = "1";
        startInfo.Environment["MSBUILDDISABLENODEREUSE"] = "1";

[Copilot]

@copilot The Windows build is taking a long time to run. Might these not be needed in the runner:

        // Disable MSBuild server and node reuse to prevent lingering child

...

Added in c990261 — DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER and MSBUILDDISABLENODEREUSE are now set on the ProcessStartInfo in Runner.cs before spawning each child process, which should prevent lingering MSBuild nodes from slowing down the Windows build.

[Malcolmnixon]

@copilot Quality check failures - pleas run the lint checks and fix.

[Copilot]

@copilot Quality check failures - pleas run the lint checks and fix.

Fixed in c1f2f8e — the quality check was failing because MSBUILDDISABLENODEREUSE wasn't in the cspell dictionary. Added it to .cspell.json to resolve the spell check error.

[Malcolmnixon]

@copilot I disagree with the requirements ID format currently used - I believe it should be SPWF-GET-001 to SPWF-GET-006 for getting the version information, and SPWF-ADD-001 to SPWF-ADD-006 for adding packages.