release v0.2.22 - #146
Merged
Merged
release v0.2.22#146
Conversation
…oint at GitHub Releases); fix the glued docs-table row
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 changed
Release v0.2.22. Version bumped, and the in-repo changelog mirror is gone.
Version bump + doc refs —
package.json/package-lock.json→0.2.22; everyv0.2.21reference inREADME.md,README.en.md,docs/README.md,docs/index.mdbumped.docs/presets-design.mdcarried a "Phase 1 尚未合入 main,main = bb9f2f6(release v0.2.21)" note describing pre-merge state — it now reads as history, since Phase 1 shipped in this release.Drop the in-repo changelog mirror.
docs/README.mdcarried a hand-maintained copy of every release note (v0.2.21 down to v0.1.0) — the same text that lives on the GitHub Releases page. Keeping it meant writing release notes twice on every release, and the two drifted apart. The section is now a one-line pointer to GitHub Releases. (README.md/README.en.mdnever had a changelog section, so there was nothing to delete there — their only version references are the beta notice and the git-install example.)Fixed a pre-existing formatting bug found while doing (2): in
docs/README.mdthe| [Media visibility design] … |table row (added by (feat) image and file blocks stay visible to the engine — placeholder projection + host-meter media price (#117) #144) had been glued onto the## 📦 Releasesheading line, so Markdown rendered the row as part of the heading and the design doc was missing from the Documents table. The row is back inside the table.Verification
grep -rn "0\.2\.21" --include=*.md(excludingnode_modules/dist/worktrees) leaves exactly one hit: the intentional historical note indocs/presets-design.md.src/changes: this branch ismain@818a9f1(pre-flight green: typecheck clean, 327/327 tests, build clean) plus docs and the version bump, so runtime behavior is untouched. CI runs the full suite on this PR.Release notes preview (to be posted on the GitHub Release page)
v0.2.22 — 14 substantive commits since v0.2.21: 4 features, 1 kernel upgrade, 8 fixes, 1 test guard.
Features
[+N images]range-row marker ([multimodal] image block 在 ACP 投影层完全不可见:同一份 acp_status 两套标尺、range 表对图片区间记 0 token、图片-only 事件无 bare ref 且不受内核保护 #117 / (feat) image and file blocks stay visible to the engine — placeholder projection + host-meter media price (#117) #144)~/.dsh/settings.yaml+/acp config((feat) hot-reload engine settings via settings.yaml + /acp config (phase 1; supersedes #76) #130, phase 1 of 运行时设置集成(阶段一):接入宿主 ctx.settings —— settings.yaml 热生效 + /acp config 命令 #75)verifiedReadings, trim nudge bodies ((feat) frame model-written summaries, record verified readings, slim nudges (drop unchanged-injection elision) #143)config.preset— five tiers ((feat) one-word nudge presets via config.preset (five tiers) #129)Fixes
offset/limit((fix) page large-block decompress output with offset/limit so one recovery can't flood or get silently trimmed #118)rawOutputso pre-upgrade session logs stay openable ((bug) compaction/summary persists non-format members (tier/topic/kernelBlockId/…) — pre-2.0.9 v0 session logs become unopenable after host upgrade #141 / (fix) persist block-ledger fields in rawOutput, not as top-level members — session logs stay openable after a host upgrade (#141) #142)Chore
Test
Credits — merged PR authors, issue reporters, and the authors of superseded PRs: