LingTai TUI/Portal v0.10.7
LingTai TUI/Portal v0.10.7
TUI-first release — This tag publishes the independently locked TUI/Portal release at commit
5fb554b69f966b39cb9eca32a70c84d628714d18(tree05c068dbc5e50832d2d5d425099c104290acd2f4). The coordinated kernel/PyPI release and final bilingual website archive are intentionally handled later, after the active joint kernel work reaches its release boundary.
Highlights
/projects becomes an admin network switcher
TUI #620 transforms /projects into an admin network switcher backed by the live process inventory. Operators can select any admin/orchestrator agent to switch context, while non-admin members remain visible for topology awareness. The detail pane includes a curated /kanban subset: lifecycle, process uptime, molt count, and live topology.
Faster, safer mail history and rendering
- #632 bounds and pages email history on demand; the newest 200 entries load in about 50 ms, with JSONL as the authoritative replay source.
- #631 gates asynchronous mail-history results to their owning model, preventing stale or cross-view mutations.
- #637, #638, and #640 render mail once from the live cache, show complete local timestamps, and align Ctrl+O mailbox rendering with the default view.
Runtime, diagnostics, and documentation polish
- #636 fixes impossible daemon CLI cache-hit displays by normalizing cached-input accounting.
- #639 clarifies agent grouping in
/projects. - #617 supports both the legacy
lingtai_kernellayout and the newlingtai.kernelruntime namespace. - #630 simplifies architecture-document checks.
- #618 clarifies
/btwinquiry semantics. - #642 updates the Discord invitation across all README variants.
Complete merged-PR ledger
The strict v0.10.6..v0.10.7 release window contains 16 merged PRs:
- #642 — docs(readme): update Discord invite
- #640 — fix(tui): align Ctrl+O mailbox rendering
- #639 — fix(tui): clarify and group agents in /projects
- #638 — fix(tui): show full timestamps for mailbox mail
- #637 — fix(tui): render mail once from mailbox cache
- #636 — fix(tui): normalize daemon CLI cached input
- #633 — docs(covenant): learn from every setback
- #632 — perf(tui): speed up large Email history loading
- #631 — fix(tui): gate async mail history results
- #630 — test: simplify architecture document checks
- #629 — docs: present LingTai as a lifelong Digital Scientist
- #628 — docs: establish distributed architecture systems
- #620 — feat(tui): turn projects into admin network switcher
- #618 — docs(tui): clarify /btw inquiry semantics
- #617 — refactor(runtime): support lingtai namespace migration
- #616 — simplify README and move beginner guide to website
Release-window accounting
- Range:
v0.10.6..v0.10.7 - Commits: 30 total (22 non-merge, 8 merge)
- Merged PRs: 16
- Human contributor: @huangzesen
- Automation:
github-actions[bot]authored three daily star-count commits; automation is not counted as human authorship.
Validation
The exact locked candidate passed the release gate:
- Go vet clean
- all TUI and Portal tests passed
- both
lingtai-tuiandlingtai-portalbuilt with thev0.10.7version - six Discord invitation occurrences audited with no legacy links remaining
- clean candidate worktree, exact commit/tree match, and no tag/version collision before publication
Installation and assets
The tag-triggered repository workflow builds four platform archives—macOS and Linux on amd64 and arm64. Every archive contains both lingtai-tui and lingtai-portal and is accompanied by a SHA-256 file. The same workflow updates the supported Homebrew tap after computing the tagged source archive checksum.