docs(agents): the merge-queue BLOCKED guidance names a required workflow main no longer requires

[devantler]

🤖 Generated by the Agentic Engineer

Evidence

The Merge queue section of AGENTS.md says main's ruleset requires the org-injected workflow ✅ Validate Go Project (.github/workflows/validate-go-project.yaml), and it gives a diagnosis procedure for a BLOCKED PR built around that workflow.

The live rulesets on devantler-tech/platform, read 2026-09-14, contain no rule requiring validate-go-project.yaml. The workflows rules require:

• .github/workflows/dependency-review.yaml
• .github/workflows/enable-auto-merge.yaml
• .github/workflows/scan-for-workflow-vulnerabilities.yaml

Require merge queue is also active. Unfiltered control: a platform PR head on the same day had 6 workflow runs, including all three required workflows, and 0 validate-go-project.yaml runs, while its checks settled green.

Audience and impact

This affects anyone diagnosing a PR that is BLOCKED on a green head. They will query for the wrong workflow, find 0 runs, and may conclude the head predates the requirement. The documented fix for that case moves the head, which is a write, for a requirement that does not exist.

Expected behaviour

The section names the workflows main actually requires, and it tells the reader to read the rulesets live instead of trusting a name written in the file.

Acceptance criteria

• The BLOCKED on a fully green head guidance names the currently required workflows, or reads them from gh api repos/devantler-tech/platform/rulesets.
• The run-count queries use a path taken from that live read, not a hard-coded validate-go-project.yaml.
• Nothing in the section states a required workflow that the ruleset does not enforce.

Rough size: S.