Add VersionMark tool version tracking following template updates

[Copilot]

Pull Request

Description

Implements VersionMark integration to track tool versions across all build jobs, matching the TemplateDotNetTool pattern.

Key Changes:

• .versionmark.yaml: Defines version extraction for 11 tools (dotnet, git, node, npm, dotnet-sonarscanner, pandoc, weasyprint, sarifmark, sonarmark, reqstream, buildmark, versionmark)

  • SonarMark entry uses dotnet tool list --global (follows BuildMark pattern - tool installs itself globally)

• .config/dotnet-tools.json: Added VersionMark 0.1.0, updated ReqStream 1.1.0 → 1.2.0

• .github/workflows/build.yaml: Added version capture/upload to all jobs:

  • quality-checks: Captures dotnet, git, versionmark
  • build (2 jobs): Captures dotnet, git, dotnet-sonarscanner, versionmark
  • integration-test (6 jobs): Added sparse checkout, tool restore; captures dotnet, git, versionmark
  • build-docs: Downloads all captures, aggregates into docs/buildnotes/versions.md

• .gitignore: Added docs/buildnotes/versions.md to exclude auto-generated version report from repository

• docs/buildnotes/definition.yaml: Added docs/buildnotes/versions.md to input-files list to include auto-generated tool versions in Build Notes PDF

Result: Comprehensive tool version manifest auto-generated during CI builds in docs/buildnotes/versions.md for reproducibility and compliance. The versions report is automatically included in the generated Build Notes PDF documentation.

Type of Change

• New feature (non-breaking change which adds functionality)
• Documentation update

Related Issues

N/A - Template consistency update

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully: dotnet build --configuration Release
• All tests pass: dotnet test --configuration Release
• Code produces zero warnings

Code Quality

• Code formatting is correct: dotnet format --verify-no-changes
• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Linting

• Markdown linter passes: npx markdownlint-cli2 "**/*.md" "#node_modules"
• Spell checker passes: npx cspell "**/*.{md,cs}" --no-progress
• YAML linter passes: yamllint .

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated ARCHITECTURE.md (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

Tested locally: dotnet versionmark --capture --job-id "test" -- dotnet git versionmark successfully captures and aggregates versions. The workflow generates the version report at docs/buildnotes/versions.md during CI runs. This file is auto-generated and excluded from the repository via .gitignore, but is included in the Build Notes PDF through the Pandoc definition file.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Malcolmnixon]

@copilot I think you forgot to modify the docs/buildnotes definition so it actually includes the auto-generated versions.md file.

[Copilot]

@copilot I think you forgot to modify the docs/buildnotes definition so it actually includes the auto-generated versions.md file.

Fixed in commit dcbb220. Added docs/buildnotes/versions.md to the input-files list in docs/buildnotes/definition.yaml so the auto-generated versions file is included in the Build Notes PDF.