docs: reconcile AGENTS.md 'Test Workflows' convention with the ci.yaml [Test]-job reality

[devantler]

🤖 Generated by the Daily AI Assistant

Part of #252 (roadmap: complete · consistent · secure).

Problem

AGENTS.md → Test Workflows prescribes a convention that the repo does not actually follow:

Test workflows ... must: 1. Be named test-<workflow-name>.yaml. 2. Trigger on pull_request to main and push to main. ...

In reality there are no test-*.yaml files. Reusable workflows are tested as [Test] jobs inside ci.yaml (e.g. [Test] Publish .NET Library - Dry Run), aggregated by CI - Required Checks. The prescribed per-workflow-file split appears to be carried over from the sibling devantler-tech/actions repo (where each action does have a test-*.yaml). A contributor or agent following AGENTS.md literally would create the wrong structure.

Proposed direction

Reconcile doc and reality — the cheaper, lower-risk option is to update the doc to describe the actual ci.yaml [Test]-job model (job naming [Test] <Workflow> - <Scenario>, dry-run/fixture conventions, the CI - Required Checks aggregation, if: ${{ !cancelled() }}). If the maintainer instead prefers the standalone-file model, that is a larger restructure and should be its own decision. Default proposal: document what exists.

Acceptance criteria

• AGENTS.md Test Workflows matches how tests are actually structured in this repo.
• No contradiction between the doc and ci.yaml.

Rough size

Small (docs only).