kanon validate should report a missing kanon.yaml with a Kanon error

[kelos-bot]

Repro:

1. Create an empty directory.
2. Run kanon validate --home <empty-dir>.

Actual:

open /tmp/.../kanon.yaml: no such file or directory

Expected:

• A Kanon-authored error that names the missing config file and the command context.
• Ideally a hint to run kanon init when the home has not been initialized yet.

Why this matters:

• This is a common first-run mistake for a new user who tries to validate before initializing the home.
• The current error looks like a low-level filesystem failure rather than an actionable CLI message, which makes onboarding rougher.

This is distinct from malformed kanon.yaml parsing errors; it is specifically about the missing config file case.

[kelos-bot]

🤖 Kelos Task Status

Task kanon-triage-issues-210a24e33cee has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kanon Triage Report

Kind: kind/bug
Priority: priority/important-soon — User-facing first-run/onboarding error from a common command, with a clear and low-risk fix path.
Actor: actor/kelos — Scope is concrete error handling plus tests; no CLI/API/schema design is required.

Status: DUPLICATE

Evidence:

• No merged PRs were found by gh pr list --state merged --search "96", and no recent commit messages matched 96 or the issue-title keywords.
• Current code still returns the raw config read failure: core.LoadConfig reads <home>/kanon.yaml with os.ReadFile and returns the error directly. validateCommand returns opts.loadConfig() errors directly, so it does not add validate-specific context or an init hint.
• Reproduced on ed22fa0e4e1bd8b1f63c303e82843ecf74dfd455 with go run . --home <empty-dir> validate: output is still open <empty-dir>/kanon.yaml: no such file or directory.
• Missing 'kanon init' hint when kanon.yaml does not exist #13 already tracks the same missing-kanon.yaml raw error, explicitly including validate, and asks for the same kanon init remediation hint at the same config-load site. kanon status silently succeeds when kanon.yaml is missing #65 is related but not a duplicate because it is about status silently succeeding when the config is missing.

Duplicates found: #13 (covers missing kanon.yaml raw errors for validate and other commands, with the same expected init hint)

Recommendation: CLOSE as a duplicate of #13.