kanon status silently succeeds when kanon.yaml is missing

[kelos-bot]

When the Kanon home has been initialized but kanon.yaml is missing, kanon status reports only the source git status and exits 0 instead of surfacing that the home is incomplete.

Repro:

1. kanon init --home /tmp/kanon-home
2. Delete /tmp/kanon-home/kanon.yaml
3. Run kanon status --home /tmp/kanon-home

Observed:

• The command prints the git status for the source repo.
• It does not mention that kanon.yaml is missing.
• Exit code is 0.

Why this is confusing:

• validate, diff, and apply fail clearly when the config is missing, but status makes the home look healthy.
• A first-time user can think Kanon is set up correctly even though the source state is incomplete.

Expected:

• status should either fail with a missing-config error or emit a clear warning that the Kanon home has not been initialized.

Tested with a fresh init repo and a removed kanon.yaml in the same home.

[kelos-bot]

🤖 Kelos Task Status

Task kanon-triage-issues-51a5b8075fbf has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kanon Triage Report

Kind: kind/bug
Priority: priority/important-soon — User-facing CLI command reports a healthy-looking status and exits 0 even though required source state is missing.
Actor: actor/kelos — The scope is concrete and objectively testable: make kanon status fail or warn when kanon.yaml is missing, with CLI tests.

Status: STILL VALID

Evidence:

• No merged PRs referencing kanon status silently succeeds when kanon.yaml is missing #65 were found with gh pr list --state merged --search "65", and recent git history did not show commits matching kanon status silently succeeds when kanon.yaml is missing #65 or the status/missing-config keywords.
• Current status prints source git status, then calls opts.plan(); when that returns a missing-config error, it explicitly returns nil: https://github.com/kelos-dev/kanon/blob/3f2ad4b/internal/cli/root.go#L193-L197
• The missing-config check is specifically for <home>/kanon.yaml: https://github.com/kelos-dev/kanon/blob/3f2ad4b/internal/cli/root.go#L583-L590
• LoadConfig still reads <home>/kanon.yaml directly when no explicit config path is provided, so deleting that file still produces the suppressed error path: https://github.com/kelos-dev/kanon/blob/3f2ad4b/internal/core/config.go#L35-L40
• The command and config file are still current surfaces; this is not outdated. Open issue Missing 'kanon init' hint when kanon.yaml does not exist #13 is related missing-config UX, but it covers raw missing-config errors/init hints rather than status silently succeeding.

Duplicates found: None found

Recommendation: KEEP OPEN