add release workflow like kelos-dev/kelos

[gjkim42]

add release workflow like kelos-dev/kelos

[kelos-bot]

🤖 Kelos Task Status

Task kanon-triage-issues-df67b59808e9 has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kanon Triage Report

Kind: kind/feature — request for new CI/CD functionality (a GitHub Actions release workflow). It does not add or change a CLI command, flag, or kanon.yaml schema, so it is not kind/api.
Priority: priority/important-soon — directly requested by the maintainer; release automation unblocks distributing kanon binaries to users.
Actor: actor/kelos — concrete, well-scoped change (mirror the release workflow from kelos-dev/kelos) with objectively verifiable acceptance (a .github/workflows/release.yaml that builds/publishes on tag). No new CLI/config surface, no breaking changes, and Go releases run on the standard GITHUB_TOKEN — no external service setup required.

Status: STILL VALID

Evidence:

• .github/workflows/ currently contains only ci.yaml and label.yaml — no release workflow exists.
• No merged PRs or commits reference a release workflow (gh pr list --state merged --search "12" → empty; git log --grep=release → empty).
• Makefile already has a build target (CGO_ENABLED=0 go build -o bin/kanon .) the release workflow can build on; ci.yaml establishes the existing actions/setup-go@v5 + go-version-file: go.mod pattern to follow.
• The reference repo kelos-dev/kelos provides a concrete template the worker can adapt.

Duplicates found: None found — open issues #2 (backup plan for apply), #3 (interactive mode), #7 (render-adapter roadmap), and #10 (managed subagents) are all unrelated to release automation.

Recommendation: KEEP OPEN