Roadmap: a self-verifying, current Go starter

[devantler]

🤖 Generated by the Daily AI Assistant

Where the product is

The previous roadmap (#67, closed) made the template frictionless, exemplary, and current: enriched README, complete AGENTS.md, a tested pkg/example, is_template enabled, Go version sourced from go.mod. A fresh strategy review (2026-05-31) of the live repo confirms the scaffold is in good shape and well-verified:

• CI genuinely verifies the scaffold. validate-go-project.yaml runs on every PR — enforced as a required workflow via the repository ruleset (the post-2024 replacement for org required workflows), alongside scan-for-workflow-vulnerabilities (zizmor) and enable-auto-merge. Verified live on PR feat: ship a minimal tested example package #74: build, test, golangci-lint, dead-code, MegaLinter, and Code-Quality coverage all ran. (The repo's own ci.yaml CI - Required Checks aggregator with empty job-results is a separate, trivially-passing status check — not the Go gate.) The README's CI/coverage claims are accurate.

So this is a mature template. The next theme is therefore incremental currency & polish, not a large feature push — honouring the minimal, idiomatic, current bias (don't add product features).

Children

• ci(deps): bring reusable-workflow pins current (v3.1.4 → v5.3.0) #77 — Bring reusable-workflow pins current (v3.1.4 → v5.3.0). ✅ Delivered by ci(deps): bring reusable-workflow pins current (v3.1.4 → v5.3.0) #79 (2026-05-31): release.yaml/todos.yaml now pin a84d9c0… # v5.3.0; main CI green confirms the v5 signatures match.
• Add a minimal .editorconfig for cross-editor consistency #78 — Add .editorconfig (minimal cross-editor consistency, good first issue). In flight via community PR Add a minimal .editorconfig for cross-editor consistency #80.

Closed / deferred (kept tight on purpose)

• Wire validate-go-project into ci.yaml — ci: wire the shared validate-go-project workflow so CI actually verifies the scaffold #76 closed as invalid: CI already runs it via the ruleset; wiring it into ci.yaml would double-run every job (verified before acting).
• govulncheck supply-chain scanning — high value, but not in validate-go-project, and the right home is the shared reusable workflow so every Go consumer inherits it. Belongs on reusable-workflows, tracked there — not a go-template child.
• Go 1.24+ tool directives for dev tooling — idiomatic, but adds the tool's dependency tree to every generated project's go.sum; rejected as scaffold bloat.

Cursor: last_strategy_review=2026-05-31, current_theme=currency·polish (mature template). #77 delivered; only #78 remains (community PR #80) — epic closes once it lands.