v2.4.3 — exact Kimi Code 2.3.3 certification

Exact Kimi Code 2.3.3 compatibility

Plugin 2.4.3 certifies exact @moonshot-ai/kimi-code@2.3.3 for all eight native-v2 operations. Plugin and CLI version numbers are independent; previous exact certifications remain supported, and legacy-v1 remains limited to explicitly pinned binaries through 0.41.x.

• Add exact 2.3.3 to the production, swarm-activation and reviewed hook-schema gates. Unknown patches, prereleases and mismatched version components still refuse.
• Preserve no-plan enforcement, hook verification, trusted-root confinement, concurrency, finite budgets, session/process ownership and durable swarm recovery.
• Expand the upstream audit to cover the authenticated web-activation server explicitly. The new upstream changes are inactive-swarm guidance and UI model/effort confirmation; activation endpoints and the load-bearing enforcement construction are unchanged.
• Refresh current compatibility documentation while retaining historical certification evidence.

Validation

• Four independent source reviews; exact-tag scan: 15 tests / 92 assertions.
• Plan ON reproduces the known bypass; plan OFF denies ordinary Write and EnterPlanMode.
• Swarm OFF produces zero children; activated ON proves two distinct child journals, correlated write denials and verified deactivation.
• Candidate smoke: 19 pass / 125 assertions, no skips, 323.93s.
• Final production smoke: 19 pass / 125 assertions, no skips, 312.83s. Child-authored 278-byte patch; user tree clean; worktree removed; out-of-root writes denied.
• Compiled exact-version gates pass under Node and Bun for both distributions; independent change and documentation reviews resolved.
• Package validation: 232 files, both compiled distributions, isolated hook setup/check, version refusal and MCP protocol checks.
• Final isolated full check: 1,306 pass / 28 expected opt-in skips / 0 fail, 16,518 assertions across 79 files, 247.64s. Frozen dependencies and vulnerability audit passed.

The first full-suite run detected untracked, byte-identical iCloud conflict copies in generated output. They were quarantined; final validation uses an isolated checkout outside the synced folder. No functional implementation change or paid model retry was required.

See certification evidence.

Publication does not update installed host plugins, re-pin hooks or change the operator's CLI binary. The known upstream plan-file bypass remains; all no-plan closures remain mandatory.

Release commit 826e5c146cfdfeb15d50539a8a97cb0022ec35dc passed CI run 40487996480, including Linux full/package checks and the Windows compiled spawn lane.

Publication verified

Publish run 40488600813 succeeded through npm OIDC. npm kimi-plugin-cc@2.4.3 has SHA-1 841d9e6df5937b25a4a391e351e8b503ca5f84b1; its tarball is byte-identical to the validated CI artifact. A fresh registry installation passed isolated setup/check for both Claude Code and Codex using exact CLI 2.3.3; both compiled runtime mirrors match the release checkout. No installed host configuration was changed.