Repository navigation
docs: advance Kimi Code baseline to 2.3.1 - #60
Merged
Merged
Conversation
Pin the audited baseline to @moonshot-ai/kimi-code@2.3.1 (peeled 684bae9ea6a4), the 37-commit / 481-path non-linear range that includes the 2.3.0 release. - CAPABILITIES.md / KNOWN_ISSUES.md: Last verified 2026-10-23, re-pinned upstream links, manifest 64 -> 65, models.*.upgrade recorded as readable-but-unrendered. - gitBranch: PR #4201 shipped, so the host's Git read is an asynchronous cache and a first-frame null is normal; the HUD HEAD fallback is a regular display path (KI-2 rewritten, prep comments and the cold-Git fixture version updated). - KI-8 gains the 2.3.x seam evidence, KI-20 the trust-store and session lock note. - Archive: 2.2.0 -> 2.3.1 delta added; the 0.36.1 "session titles default-off" statement marked superseded (issue #58 follow-up). - New docs/upstream-2.3.1-review.md, allow-listed in .gitignore, with the #54 and #58 evidence. - READMEs and both showcase pages follow the baseline; HUD_VERSION is untouched.
Three additive regressions for the 2.3.1 baseline, none touching runtime behaviour: - wire-row-classes: new fixture interleaving both changeNotifier.snapshot shapes, proving the 65th manifest record folds as a no-op through the fold, persisted-state and render comparisons. - management-service: a 2.3.x tui.toml (auto_session_title present, disable_feedback_survey absent) survives install twice and comes back byte-for-byte after uninstall. - render-runtime: [models."x".upgrade] subtables leave provider attribution and the quota gate unchanged and leak no migration text.
This was referenced Oct 23, 2026
Closed
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Consumer-side baseline advancement to Kimi Code 2.3.1 (tag
71a07ca316d3…, peeled684bae9ea6a4…; workspace root gate already green on 2.2.0 → 2.3.1):gitBranch: nullis the normal path and HUD's HEAD fallback is the regular display path), KI-8/KI-20 annotationsdocs/upstream-2.3.1-review.mdwith the full review (evidence @commit, membership checks, impact matrix)docs/capabilities-archive.md: Baseline delta (2.2.0 → 2.3.1); session-title default-off note marked superseded in 2.3.0 (closes the [kimi-code-watch] 上游 PR #4200:TUI 自动会话标题默认开启,会话标题默认值声明与基线审查需 parity #58 follow-up item)CLI_VERSION = '2.3.1'(release-metadata gate);.gitignorewhitelist entry for the new review docchangeNotifier.snapshotfolds to a no-op; 2.3.x-shaped tui.toml install/uninstall stays idempotent;[models."x".upgrade]subtable leaves provider attribution and quota gating untouchedVerification
npm test— 826 tests, 825 pass, 1 pre-existing skip (5 new tests added, zero existing assertions changed)KIMI_HUD_RELEASE_CHECK=1 node --test test/release-metadata.test.mjs— greenCloses the doc side of #54 evidence collection; #54 and #58 get their closing comments after merge.