AGENTS.md Validation section describes a ruleset and repo that no longer exist

[devantler]

🤖 Generated by the Daily AI Engineer

Evidence

AGENTS.md's Validation section claims a repository ruleset named "Require workflows to pass before merging for Go" injects the shared devantler-tech/reusable-workflows validate-go-project workflow on every PR and the merge queue, and instructs "do not wire validate-go-project into ci.yaml".

Verified live (2026-07-17):

• gh api repos/devantler-tech/go-template/rulesets?includes_parents=true lists no such ruleset — the workflow-injection rulesets applying here are DependencyReview, EnableAutoMerge, and ScanGitHubActions; required status checks come from "Require status checks to pass" (context: CI - Required Checks).
• devantler-tech/reusable-workflows was archived 2026-07-10 (merged into devantler-tech/actions), so the repo reference is stale regardless.

Audience & impact

Agents and contributors follow AGENTS.md as the canonical instruction file; a wrong validation topology misleads every future change here (e.g. "don't wire validate-go-project into ci.yaml" may now be inverted advice).

Expected behaviour

AGENTS.md describes the validation gate that actually exists.

Acceptance criteria

• Re-derive the live validation topology: which workflow/ruleset runs Go build/test/lint on a Go-touching PR and the merge queue today (note: docs-only PRs appear path-filtered — verify with a .go-touching PR's check set, don't guess).
• Rewrite the Validation section (and the "don't wire into ci.yaml" guidance if inverted) to match, dropping the reusable-workflows reference.

Rough size: XS–S (investigation + one docs edit).

[coderabbitai]

🔗 Related PRs

#139 - ci: repoint reusable workflows to devantler-tech/actions v8.0.0 [merged]
#140 - chore(deps): Bump devantler-tech/actions/aggregate-job-checks from 7.1.3 to 8.0.0 [merged]
#161 - ci: harden Copilot setup workflow [merged]
#165 - feat: expose canonical instructions to Gemini CLI [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!