TUI/Portal v0.10.7

New features and improvements

1. 01

   /projects becomes a live admin network switcher

   The running process inventory now powers /projects, giving operators a compact way to move between several agent networks without losing topology context.

   • TUI #620 lets an operator select an admin/orchestrator agent to switch context; non-admin members remain visible for topology awareness, and a curated /kanban detail subset shows lifecycle, process uptime, molt count, and live topology.
   • TUI #639 clarifies the agent grouping and presents the kanban-on-a-projects-view layout.

   Why it matters:Multiple networks are easier to operate when switching context and checking health are one keystroke away.

2. 02

   Faster, safer mail history and rendering

   Email is a primary asynchronous surface for long-running agents, so this release makes history loading, stale-result handling, and rendering behavior predictable across views.

   • TUI #632 bounds and pages history on demand: the newest 200 entries load in about 50 ms, exact counting runs asynchronously, and JSONL is the authoritative replay source rather than SQLite interior-hole results.
   • TUI #631 gates asynchronous history results to their owning model, preventing stale or cross-view mutations after navigation.
   • TUI #637 renders mail once from the live mailbox cache instead of fetching and rendering again on every view switch.
   • TUI #638 shows full local timestamps in list, detail, and Ctrl+O views.
   • TUI #640 aligns Ctrl+O mailbox rendering with the default view so both show the same content.

   Why it matters:A fast mailbox is useful only when its timestamps, content, and asynchronous updates remain trustworthy during a long session.

3. 03

   Runtime compatibility, diagnostics, and documentation

   The release keeps the TUI-side runtime path compatible, makes daemon accounting honest, and updates the repository guidance operators and contributors rely on.

   • TUI #636 fixes the impossible daemon CLI cache-hit display by normalizing cached-input accounting so TokenTotals.Input includes cached input.
   • TUI #617 recognizes both the legacy lingtai_kernel layout and the new lingtai.kernel runtime namespace; this is a TUI/Portal compatibility shim, not a kernel release.
   • TUI #630 simplifies architecture-document checks, while #618 clarifies /btw inquiry semantics.
   • TUI #629 and #628 refresh the lifelong Digital Scientist narrative and distributed-architecture ownership; #633 adds “learn from every setback” to the Covenant; #616 simplifies the README and moves the beginner guide to the website; #642 updates the Discord invitation across README variants.

   Why it matters:A small compatibility shim reduces upgrade coordination, while accurate diagnostics and current documentation reduce operational guesswork.

4. 04

   Four platform archives and Homebrew distribution

   The tag workflow publishes macOS and Linux archives for amd64 and arm64. Each archive contains both lingtai-tui and lingtai-portal plus a SHA-256 sidecar, and the supported Homebrew tap is updated from the tagged source archive.

   • Published archives: darwin-amd64 (7a73db99…), darwin-arm64 (27d4d082…), linux-amd64 (dd2374bd…), and linux-arm64 (645feedc…); full checksums are in Validation.
   • The Homebrew formula uses the tagged source archive https://github.com/Lingtai-AI/lingtai/archive/refs/tags/v0.10.7.tar.gz with SHA-256 6bdde2c41a588cccdf54e32732f5c2c6a89df1c2279cde3f7cbca572d05f4dcf.
   • GitHub is retiring the macos-13 Intel runner used for darwin-amd64; that automated job failed while darwin-arm64, linux-amd64, and linux-arm64 passed.
   • The darwin-amd64 archive was manually rebuilt and uploaded. Its SHA-256 is byte-identical to the intended artifact, so Intel-macOS users have a verifiable build.

   Why it matters:Publishing the recovered archive and its checksum keeps Intel-macOS support verifiable instead of silently dropping a platform.

5. 05

   Release-window accounting and validation

   This archive records the strict v0.10.6..v0.10.7 window rather than implying that unrelated kernel work shipped with this tag.

   • The window contains 30 commits: 22 non-merge and 8 merge, with 16 merged PRs. The human contributor is @huangzesen; three daily star-count commits were authored by github-actions[bot] and are automation, not human authorship.
   • The exact candidate passed Go vet, all TUI and Portal tests, and versioned builds of both lingtai-tui and lingtai-portal at v0.10.7.
   • Six Discord invitation occurrences were audited with no legacy links; the candidate worktree was clean with exact commit/tree match and no tag/version collision before publication.
   • The public GitHub release is v0.10.7, draft=false, prerelease=false, published 2026-07-13T17:30:33Z.

   Why it matters:Separating the TUI candidate, the strict attribution window, and automation makes this release record auditable without attributing unfinished joint-kernel work to it.