TabBeacon v0.8.1 — Codex Windows Hook console compatibility

TabBeacon v0.8.1

Candidate: 436ea8d643a880c7b537353e85176108c17c060a.
The Owner authorized publication of this exact candidate on 2026-10-10.
Merged source: a76ed15e758debf6b1635406bd03001695b58bdd; the merged tree exactly matches the authorized candidate. Tag: v0.8.1.

Fix Windows Hook presentation when the native Codex background command launcher
loses its originating console association. TabBeacon recovers only the proven
installed native Codex ancestor's console, retaining redirected Hook stdio,
bounded process ownership, worker cleanup and fail-open suppression. Daily agent
launch remains literally codex.

Windows command Hooks declare a two-second timeout, based on measured startup
tails after console recovery. Unix commands and historical MCP retain one second.
Configuration writes require a complete known generated owned declaration set;
third-party content is preserved and new Hook hashes require manual native /hooks
review. Installation or reconciliation must not automatically grant trust.

The release CI now requires an actually executed, qualified release-only Hook SLA
test. The final exact-head Windows CI ran one test and measured 153 ms against the
generated two-second declaration. This anchored COMSPEC measurement is separate
from real provider delivery and the historical sub-one-second performance target.

On 2026-10-10 the Owner completed one isolated attended native Codex 0.162.0 test
in Windows Terminal: manual Hook review, working green, tool activity green,
completion blue, no Hook timeout and normal exit/reset all passed. Native exit was
0; candidate binary, native entry/launcher/executable and Hook declarations matched
their admitted identities. All 11 isolated review hashes match the declarations.
The isolated config changed only through manual Hook trust and the native TUI
screen-reader-detection flag; its remaining bytes match the pre-review baseline.

This qualifies the current native 0.162.0 Windows Terminal path on the attended
host. It does not claim attended 0.159.2 delivery, repair arbitrary missing-worker
cold overhead, or guarantee latency on every host. The historical original
one-second timeout's precise causal phase remains UNPROVEN. Earlier synthetic
launcher evidence retains its synthetic scope.

Product source, dependencies, console ownership and configuration mutation logic
are unchanged from accepted head 20641846d098f9d908ef6858b9a24e5ca5c116da.
The 91 unaffected Hook cases, 440 synthetic launcher calls and independent source /
configuration safety review are reused. The executable is reused with its original
identity; the source crate was freshly verified at the final candidate. No L4,
launcher stress or full CI was repeated for this closeout.

Release artifacts and SHA256:

Artifact	SHA256
tabbeacon-0.8.1.crate	67AC37B1F95EC1A2EF1AB94B7FE5843B9A64BD1B96F083BB922852094C942E4C
tabbeacon-0.8.1-windows-x64.zip	6FAEB187A392494B1DF402F82067F2A3C0516F167276FD572FB74663524DC869
tabbeacon.exe	8BD5C5D884CF026C2B4F0CB19437E29EAE906E56E70A005BF3CE4B4D49368C88

The ZIP includes the executable, LICENSE, README and hotfix scope document. Existing
package bytes and checksums are unchanged; this attended-acceptance addendum is
carried in PR #121 and the closeout receipt without a status-only source commit.

Install from the official channel with cargo install tabbeacon --version 0.8.1 --locked.
Run tabbeacon setup codex for ownership-safe reconciliation, preserving existing presentation preferences and third-party declarations. Review changed Hook declarations manually in native /hooks; installation does not grant trust.