Kernel v0.19.0 · TUI/Portal v0.12.0

New features and improvements

1. 01

   One tool protocol across the runtime and channels

   LingTai Tool Protocol v2 now gives model-facing tools one predictable action/input envelope while preserving each integration's real ownership and side-effect boundaries.

   • Web, email, system, daemon, Psyche, Telegram, IMAP, Feishu, WeChat, WhatsApp, and Cloud Mail surfaces now use the common ToolFamily contract instead of bespoke call shapes.
   • Web search and browse preserve complete outputs, while channel adapters keep transport stdout protocol-only and expose rate-limit or retry states honestly.
   • The result is a smaller model-facing grammar without pretending that different channels have identical operational semantics.

   Why it matters:New tools and channels become easier to learn, audit, and compose, while failures remain attributable to the integration that actually owns them.

2. 02

   Long-running work is visible through a complete Task Card lifecycle

   Task Card is now a declarative intrinsic producer with an explicit terminal lifecycle, a Telegram projection that respects programmable intent, and a TUI viewer for the current artifact.

   • Agents can start, inspect, retry, stop, and remove one truthful Task Card watch instead of leaving stale progress behind.
   • Telegram keeps its transport-specific projection and automatic composition, while the programmable frame controls only task state and active/inactive intent.
   • The TUI adds /taskcard so operators can open the same current artifact without scraping chat history.

   Why it matters:People can see what a long job is doing, whether it is still active, and when its progress artifact has been deliberately retired.

3. 03

   Install, update, and removal now have one canonical lifecycle

   The Lingtai-AI/lingtai repository now owns the complete POSIX and PowerShell lifecycle; the public website mirrors those exact bytes instead of carrying an independent installer fork.

   • Stable install.sh and install.ps1 entrypoints cover install and update, with canonical fix, verify, dev, and removal children behind them.
   • New remove.sh and remove.ps1 delete only receipt-owned installation state, preserve user configuration, secrets, presets, projects, auth, and shared tooling, and remain idempotent on a second run.
   • Web parity checks fail loud on any mirror drift, so documentation and copy-paste URLs cannot silently diverge from the maintained lifecycle source.

   Why it matters:Users get one documented lifecycle and one ownership boundary instead of platform-specific scripts drifting apart over time.

4. 04

   Mail, notification, and operator surfaces fail more honestly

   A broad reliability pass makes channel retries, notification delivery, live logs, credential handling, and the mail conversation rail more bounded and observable.

   • Telegram rate limits propagate their real retry contract; WeChat and Cloud Mail retry failed wake delivery; Feishu keeps MCP stdio protocol-only; filesystem mail polling is sliced instead of monopolizing a turn.
   • Concurrent daemon terminal wakes and synthetic notification calls remain schema-valid, and live SQLite readers see current data.
   • The TUI mail rail gains clearer focus/collapse/mouse behavior, consistent credential-family handling, and faster live network refreshes that avoid rescanning mail history.

   Why it matters:Operators get fewer silent stalls and clearer evidence when a transport, retry, or live view is the thing that actually failed.