Verify compatibility with @moonshot-ai/kimi-code 0.14.1 and extend KIMI_TESTED_MINORS through 0.13/0.14. No runtime behavior change — this is a compat-certification patch.
Why
The kimi-code binary self-upgrades by default; operators were running 0.14.1 (two minors past the previously-verified 0.12.0), tripping the "newer than tested max" setup-probe warning. This patch certifies the jump and silences the warning for 0.13.x/0.14.x.
What was verified
Cumulative 0.12.0 → 0.14.1 audit (0.12.1 / 0.13.0 / 0.13.1 / 0.14.0 / 0.14.1) via the 4-reviewer playbook + an adversarial pass — unanimous COMPAT-PRESERVED — backed by a GREEN bun run smoke:real against the installed 0.14.1 binary: forced writes from review/challenge/ask/review_gate are hook-denied, autonomous pursue wrote zero files across a multi-turn budget, and a spawned swarm subagent's write is hook-denied.
Safety chain intact
PreToolCallHookPermissionPolicy is still permission index 0. The hook engine/runner, pre-tool-call-hook, stream-json writer, records/, and CLI argv are byte-identical 0.12.0→0.14.1 (the only session/hooks/ change is an additive Interrupt event type). Two compat-benign permission-stack changes: a new index-1 AgentSwarmExclusiveDeny (pure deny, can't pre-empt the hook; shifts auto-approve 4→5) and removal of the already-dead-in--p CwdOutsideFileWriteAsk. The new packages/protocol/ REST+WebSocket API (#612) is a separate, dormant transport off the -p path.
Feature scan
A dedicated spike confirmed 0.13/0.14 opened no new buildable feature surface: write-swarm (worktree isolation) and pursue --resume remain blocked upstream; the protocol API is dormant (no server binds). Nothing folds into this patch.
Compat marker: compat-verified-kimi-code-0.14.1