Skip to content

fix(runtime-host): close M4 readiness gaps - #2419

Merged
M4n5ter merged 1 commit into
mainfrom
feat/runtime-host-m4-closure
Aug 7, 2026
Merged

fix(runtime-host): close M4 readiness gaps#2419
M4n5ter merged 1 commit into
mainfrom
feat/runtime-host-m4-closure

Conversation

@M4n5ter

Copy link
Copy Markdown
Member
English

Summary

  • let admitted heartbeat and cron fires enter the Runtime Host root authority without conflicting with the coordinator's own reservation
  • persist admitted-fire deferrals and settle fires as failed with a visible lastError after the durable retry window instead of retrying forever
  • separate owner-neutral TUI presentation contracts and provider catalog data from embedded Runtime and writer Store composition
  • enforce a default-deny dependency boundary for Runtime Host TUI, maka run, and live inspect across static, dynamic, re-exported, aliased, and workspace-package imports
  • cover heartbeat and cron execution through a real production Host, plus Desktop-to-TUI PTY control transfer through two real UDS clients
  • keep the Windows exclusion inventory current for the new POSIX integration coverage

Compatibility boundaries

  • M4 remains a pre-cutover adapter milestone: production ownership stays on the single embedded Runtime until the atomic M5 switch
  • Desktop: complete Runtime Host message queue parity #2262 remains an independent Desktop presentation follow-up and is intentionally not part of this M4 closure
  • no embedded fallback or second Runtime writer is introduced on any Runtime Host adapter path

Validation

  • @maka/runtime: 3306 passed, 3 platform skips
  • @maka/runtime-host: 738 passed
  • CLI: 516 passed
  • full repository TypeScript typecheck
  • full repository Biome lint and format check
  • Windows test inventory check: 68 declarations
  • real OpenRouter Free Runtime Host smoke for maka run
  • real tmux/PTY Runtime Host TUI smoke using the active XDG home, with the model returning the exact expected response
  • production Host heartbeat, cron, deletion, and two-client PTY continuity integration tests

Closes#2010.

简体中文

概要

  • 让已经接纳的 heartbeat 与 cron fire 正常进入 Runtime Host root authority,不再与 coordinator 自己持有的 reservation 冲突
  • 持久化 admitted fire 的 defer;超过 durable retry window 后写入可见 lastError 并收敛为失败,不再无限静默重试
  • 将 owner-neutral 的 TUI presentation contract 与 provider catalog 从 embedded Runtime、writer Store composition 中拆出
  • 为 Runtime Host TUI、maka run 与 live inspect 建立默认拒绝的 dependency boundary,覆盖静态、动态、re-export、alias 与 workspace package import
  • 通过真实 production Host 验证 heartbeat 与 cron,并通过两个真实 UDS client 验证 Desktop 到 TUI 的 PTY 控制权转移
  • 为新增 POSIX 集成测试同步更新 Windows 排除清单

兼容边界

  • M4 仍是 cutover 前的 adapter milestone:在 M5 原子切换前,production 继续只使用唯一 embedded Runtime owner
  • Desktop: complete Runtime Host message queue parity #2262 继续作为独立的 Desktop presentation follow-up,不属于本次 M4 收口范围
  • 所有 Runtime Host adapter path 均未引入 embedded fallback 或第二个 Runtime writer

验证

  • @maka/runtime:3306 项通过,3 项平台跳过
  • @maka/runtime-host:738 项通过
  • CLI:516 项通过
  • 全仓 TypeScript typecheck
  • 全仓 Biome lint 与 format check
  • Windows 测试清单检查:68 条声明
  • 使用 OpenRouter Free 完成真实 Runtime Host maka run 冒烟测试
  • 直接使用当前 XDG Home,通过真实 tmux/PTY 完成 Runtime Host TUI 冒烟测试,模型返回精确预期文本
  • production Host heartbeat、cron、delete 与双 Client PTY continuity 集成测试

关闭 #2010

@M4n5ter
M4n5ter merged commit 7827096 into mainAug 7, 2026
12 checks passed
@M4n5ter
M4n5ter deleted the feat/runtime-host-m4-closure branch August 7, 2026 09:05
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Tracking] Runtime Host M4 Desktop-first client adapters

1 participant

@M4n5ter