Template pull requests run no .NET build and test gate

[devantler]

🤖 Generated by the Agentic Engineer

Evidence

AGENTS.md says a repository ruleset injects the shared run-dotnet-tests workflow on every pull request and merge-queue entry, building and testing the solution on Ubuntu, Windows and macOS. That is not what happens today.

• The rulesets that apply to this repository (read 2026-09-15) contain exactly three workflow rules: dependency review, enable-auto-merge, and GitHub Actions scanning. None of them runs run-dotnet-tests.
• No run-dotnet-tests run appears in this repository's recent Actions history.
• fix(tests): opt the scaffold into Microsoft.Testing.Platform #423's checks are zizmor, CodeQL, dependency review, CodeRabbit, the required-checks aggregator and Validate Scaffold. None of them builds or tests the solution on all three platforms.

Impact

Nothing in CI builds or tests the scaffold across platforms. The xUnit v3 4.0 upgrade (#394) broke dotnet test for two weeks, and the only signal was the non-required Validate Scaffold job (#422). Maintainers and agents reading AGENTS.md believe a gate exists that does not.

Expected

Either a required check builds and tests the solution on pull requests, or AGENTS.md stops claiming one exists.

Acceptance criteria

• Find out whether the org-level .NET workflow ruleset was removed, retargeted, or never matched this repository. Reading organization rulesets needs org-admin access.
• Restore a required .NET build and test check for this repository, or record why it is intentionally absent.
• Update AGENTS.md (Feature flags and Validation sections) to describe the gate that actually exists.

Size

Small in this repository. Restoring an organization ruleset is a settings change outside it.

Blocker: maintainer authority: re-add dotnet-template to the organization .NET workflow ruleset's repository targeting | authority | last-verified 2026-09-15: effective rules on main lack the run-dotnet-tests workflow rule; last injected run 2026-06-10 | asked slack 2026-09-15

[devantler]

🤖 Generated by the Agentic Engineer

Root cause found: the organization's .NET workflow rule stopped applying to this repository on 2026-06-10

The shared test workflow did run here, until 2026-06-10. This repository's Actions history has 117 run-dotnet-tests runs, and the last one ran on 2026-06-10 at 09:33Z. go-template lost its injected validate-go-project runs the same day (last run 05:13Z).

The rules still exist; they no longer target the templates. The effective rules on main (repos/<repo>/rules/branches/main) read today:

Repository	Organization workflow rules that apply
ksail	dependency review, enable auto-merge, workflow scanning, validate-go-project (ruleset 10320335)
go-template	dependency review, enable auto-merge, workflow scanning
dotnet-template	dependency review, enable auto-merge, workflow scanning

All three repositories have identical custom property values, so the language rules are not selected by a property. They must target repositories by name or by an explicit list, and the two templates dropped out of it. Organization rulesets can only be read or changed with organization-admin access, which the agents do not have.

Why I am not adding a test job to ci.yaml instead. Both templates document the injected workflow as the design, and go-template#76 records why: calling it from ci.yaml as well would run every job twice. Putting the templates back in the rules' targeting restores the gate without that double run. It also brings AGENTS.md back in line with reality, so no documentation change is needed.

Blocker: maintainer authority: re-add dotnet-template (and go-template) to the organization's language workflow rulesets' repository targeting (.NET rule; Go rule 10320335) | authority | last-verified 2026-09-15: effective rules on main lack both language workflow rules; last injected runs 2026-06-10