Kernel v0.16.1 · TUI/Portal v0.10.4

New features and improvements

1. 01

   Context rebuild semantics are now explicit

   Kernel v0.16.1 clarifies what summarize does immediately, what waits for reconstruction, and when the runtime forces a rebuild.

   • Public system(action="summarize", rebuild=true) replaces the older rebuild-only/dry-run wording.
   • Summary markers now move through pending/done states, making delayed reconstruction easier to reason about.
   • The runtime documents the 0.75 proactive hint, the 1.0 hard forced-rebuild boundary, and the 0.6 recovery target in one place.

   Why it matters:Long-lived agents can now choose between continuing, applying pending summaries, or molting without guessing which layer owns the active provider context.

2. 02

   Runtime reliability and integration edges were tightened

   The kernel release also fixes multiple edges around token accounting, logging, empty responses, lifecycle signals, and addon/MCP documentation.

   • Token usage layout, since-molt session accounting, cache-miss telemetry, and refresh rebuild opt-in were clarified.
   • JSONL close races, streamed tool-call argument fallback logging, empty-response usage handling, and atomic chat-history writes were hardened.
   • Telegram dynamic slash commands, WeChat filename sanitization, lifecycle/nirvana safeguards, gitignore/secrets hygiene, and NoKV workbench metadata validation landed together.

   Why it matters:These changes reduce the number of cases where a live agent, its durable logs, and its prompt guidance disagree about what just happened.

3. 03

   TUI and Portal startup/replay paths are safer

   TUI/Portal v0.10.4 focuses on update flows, portal startup cleanup, replay reconstruction, and small UI/setup correctness fixes.

   • Portal startup timeout cleanup, replay-cache writer sharing, and the rehydrateDone deadlock fix improve replay reliability.
   • The /update-tui self-update command, explicit utility refresh behavior, runtime venv marker, and stricter config.json permissions make setup/update safer.
   • Verbose-toggle bottom anchoring, credential Esc handling, canonical recipe preview resolvers, inactive workflow cleanup, release docs, and normalized stars CSV whitespace round out the TUI polish.

   Why it matters:The release keeps local developer installations predictable while making the user-facing startup and replay surfaces less fragile.

4. 04

   The release window was audited end to end

   The public release log covers 84 commits, 34 merged PRs, 96 issue records updated in the Jul 1–3 release window, and 136 files changed with +7,665 / -1,378 lines across the kernel and TUI/Portal repositories.

   • TUI/Portal: 28 commits, 12 merged PRs, 40 issue records updated in the release window, 57 files changed, +1,798 / -583 lines.
   • Kernel: 56 commits, 22 merged PRs, 56 issue records updated in the release window, 79 files changed, +5,867 / -795 lines.
   • Gates covered TUI/Portal Go tests, portal web build, release binary builds, kernel compileall, focused 400-test pytest run, package build, twine checks, PyPI verification, and Homebrew audit/fetch.

   Why it matters:The contributor list intentionally includes human issue/PR authors from the release window even when a specific issue or PR was closed, rejected, or unmerged.