Windows native TUI health alpha — CLI179 / Node145

Windows native ongoing TUI health software alpha: CLI179 / Node145 / existing Hub139. Both complete npm archives and both official GitHub archives below are byte-identical to the original four-gated build from exact merged main2793c6a18be3dd111477f0686bd89a4140b072eb. Stable/latest unchanged; original-device/model adoption remains separate.

Windows health binds immutable config.node_id, launch marker, exact remote, PID and birth before reporting an owned connection. Unknown clears stale evidence; proven death/connection loss reaches the existing Hub guard. AppServer/auth checks remain intact. Native Windows fake-Codex CI reports current Hub running health and completes two same-turn Dashboard tasks without duplication.

Node145 npm full verification: 2026-10-13T21:34:54.320360+00:00, 601333B, SHA256 e1d6d3382ec1655dea6881927da83570a84be942faf97c2e49103e4f161e2804.
CLI179 npm full verification: 2026-10-13T21:34:55.293656+00:00, 2127323B, SHA256 b7264ef5bc621d7fc973da66d1b84cec1b5382d960a35bd8ab5f65c70401c386; SHA1 66b71fa32cc2409ed243d51e831bdd331019d1f0 and SHA512 match registry. Both full archives equal their gated and official GitHub bytes. Registry gitHead is absent; provenance is explicit main input/ancestry plus full gated byte equality.

Historical CLI workflow38468145147 FAILURE remains: npm publish returned success but post-publish registry verification timed out after900s at21:30:24Z. Later independent complete download passed; no rebuild, rerun, republish or retag occurred. Immutable release-manifest.json records the earlier asset-creation checkpoint (Node registry=true, CLI=false); later verification is recorded here without rewriting assets. These are npm archives, not native exe/dmg/app installers.

Install from the immutable archives or npm exact179/145/139 in a fresh private prefix. See docs/tests/release-v2.3.0-preview.179.md and release-v2.5.0-preview.145.md; bind the exact paired entrypoint. Adoption goes through the original lifecycle owner's normal maintenance procedure, preserving node/thread/cwd/model/provider/login; this release does not restart/adopt a live node. Rollback178/144 retains compatible private V2 state and native health returns to unknown. Existing deploy/hub and deploy/fleet runbooks define startup/ports/proxy and secure sources. Git restores software only; original private data require authorized backups. Hub vault recovery is NOT COVERED.