Kernel v0.17.1 · TUI/Portal v0.11.0

New features and improvements

1. 01

   Verified kernel artifacts and a source-only TUI release

   Kernel v0.17.1 and TUI/Portal v0.11.0 keep exact source provenance while using distribution paths appropriate to each project.

   • Kernel v0.17.1 publishes 18 GitHub assets, matching Gitee bytes, and 15 wheels plus one sdist on PyPI.
   • TUI/Portal v0.11.0 keeps the public GitHub tag and source release; Homebrew builds from that exact tag source archive.
   • Future TUI tag workflows create the source release and update Homebrew without building or publishing platform archives, checksums, bundle manifests, or Gitee binary bundles.
   • The six platform assets already published before the source-only decision remain preserved; no release history or public asset was deleted.

   Why it matters:Source releases keep the public contract simple while preserving exact, auditable provenance.

2. 02

   Telegram Task Cards make long work visible

   Long-running work can expose truthful elapsed time, active work, completed evidence, not-started steps, the next gate, and the current blocker in one resident card.

   • Programmable renderers update independently from ordinary chat replies.
   • Formatting fallback paths preserve readable status when rich rendering fails.
   • Backend failures remain visible instead of being flattened into generic progress text.

   Why it matters:Visible, evidence-backed progress reduces uncertainty during long work.

3. 03

   A clearer project-first TUI startup journey

   When no project is active, the TUI opens with an explicit project chooser and creation journey instead of an ambiguous empty shell.

   • Create, choose, migrate, and resume decisions are presented as distinct actions.
   • Project helpers and slash-command wording use the same mental model.
   • Legacy and nested project discovery paths remain compatible without silently rewriting projects.

   Why it matters:The first screen now explains the next real decision instead of exposing implementation state.

4. 04

   Daemon and runtime execution are more resilient

   Daemon execution gains broader coding-backend support and stronger lifecycle, cancellation, notification, prompt, and artifact-preservation contracts.

   • New external coding backends include Qwen Code, Oh-My-Pi, Kimi Code, and Cursor Agent.
   • Restart-safe registry and terminal-state handling reduce lost or duplicated outcomes.
   • Prompt/tool contracts, cancellation semantics, and failed-run artifacts are easier to inspect and recover.

   Why it matters:More explicit execution contracts make long-running automation easier to trust and recover.

5. 05

   Model, setup, namespace, and platform contracts are explicit

   The release aligns current model defaults and setup guidance while clarifying runtime packaging, Windows support, configuration, and environment-variable ownership.

   • Codex-family defaults and preset capability bundles are refreshed for current supported models.
   • Runtime imports and packaged scripts continue converging on one public lingtai namespace.
   • PowerShell-native execution improves Windows support without leaking platform mechanisms into core contracts.

   Why it matters:Inspectable choices and clear ownership reduce upgrade and operating guesswork.