Restructure requirements.yaml into Model, Serialization, and Runtime sections

[Copilot]

Pull Request

Description

Reorganizes requirements.yaml from a single flat "Functional Requirements" section into logical sections aligned with the library's primary concerns:

• Model — test outcome types (Passed, Failed, Error, Timeout, NotExecuted, Inconclusive, Aborted, Pending, Warning), output streams, and error/stack trace capture (REQ-FUNC-009–017, 020–021)
• Serialization — cross-cutting serialization requirements: auto-format identification, format conversion, and round-trip preservation (REQ-FUNC-005, 018–019)
  • TRX Serialization — TRX serialize/deserialize (REQ-FUNC-001–002)
  • JUnit Serialization — JUnit serialize/deserialize (REQ-FUNC-003–004)
• Runtime — .NET 8, 9, and 10 support (REQ-FUNC-006–008)

The "Serialization" parent section groups TRX and JUnit as sub-sections, and holds the requirements that are not specific to either format (auto-identification, conversion, round-trip preservation) at the parent level.

All 21 requirement IDs, titles, justifications, and test references are unchanged — structural reorganization only.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

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 unit 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

Quality Checks

Please run the following checks before submitting:

• Spell checker passes: cspell "**/*.{md,cs}"
• Markdown linter passes: markdownlint "**/*.md"
• 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

No functional changes — requirements content is identical, only the section hierarchy changed.

---

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

[Malcolmnixon]

@copilot There may want to be a "Serialization" section with "TRX Serialization" and "JUnit Serialization" being sub-sections - the reason for this is that there are some serialization-based requirements not specific to TRX or JUnit.

[Copilot]

@copilot There may want to be a "Serialization" section with "TRX Serialization" and "JUnit Serialization" being sub-sections - the reason for this is that there are some serializati...

Done in 769a82c. The cross-cutting requirements (REQ-FUNC-005 auto-identify, REQ-FUNC-018 conversion, REQ-FUNC-019 round-trip) now sit directly under a parent "Serialization" section, with "TRX Serialization" and "JUnit Serialization" as sub-sections beneath it.