Fix documentation inconsistencies between examples and actual API

[Copilot]

Documentation examples used non-existent properties (EndTime, StdOut, StdErr) instead of actual API properties (SystemOutput, SystemError). This would cause compilation errors for users copying examples.

Changes

README.md & ARCHITECTURE.md

• Corrected property names in code examples: StdOut → SystemOutput, StdErr → SystemError
• Removed references to non-existent EndTime property

TestResult.cs

• Fixed XML documentation grammar: "when execution" → "when executing"

Package metadata

• Enhanced NuGet tags to include junit and test-results for better discoverability
• Updated description to match README tagline

AGENTS.md

• Removed broken reference to non-existent .github/agents/README.md

Example

Before (would not compile):

var result = new TestResult
{
    Name = "Test1",
    Outcome = TestOutcome.Passed,
    StdOut = "output",
    EndTime = DateTime.UtcNow
};

After (correct API):

var result = new TestResult
{
    Name = "Test1",
    Outcome = TestOutcome.Passed,
    SystemOutput = "output"
};

Original prompt

Please examine the technical documentation of the TestResults repository and determine if documentation changes should be made. This also includes repository documentation such as the README.md and other markdown files used by GitHub.

Custom agent used: Documentation Writer
Expert technical writer specializing in maintaining README, ARCHITECTURE, and markdown documentation, writing XML documentation comments for APIs, ensuring documentation accuracy and clarity, and following markdown and spelling standards.

---

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