Fix #16: kai init should be idempotent

[jschatz1]

Closes #16.

Auto-fix result: 🟡 opened as draft

Why:

• ✓ deterministic checks passed
• ✗ semantic judge unsure the change implements the issue
• ✗ code review found nothing blocking

What changed

add-init-idempotent-test

Files touched:

• cmd/kai/init_test.go

Verification

• Tests / typecheck: clean (unconfirmed) — build + tests passed
• Semantic judge: unsure — The diff only adds tests for the idempotent behavior (checking for "already initialized" message and --force bypass), but the actual implementation changes to the init logic (the production code in runInit, the --force flag, the idempotency check) are not present in the diff.
• Code review: approved — The test additions are well-structured and directly verify the idempotency requirement from the issue. They properly save/restore global state (kaiDir, initForce, os.Stderr), use `t.TempDir()…

Open questions for a human (why this stayed a draft):

• Does the production code for runInit actually contain the idempotency check and --force flag implementation?

---

Generated headlessly by kai · model z-ai/glm-5.1 · 52906 in / 6444 out tokens.