TabBeacon v0.7.2

TabBeacon v0.7.2 Codex subagent Hook stability hotfix

v0.7.2 fixes a Codex Hook stability failure in which child/subagent activity
could interfere with the root tab's presentation and visible Hook failures or
one-second timeouts could appear during a real parent-plus-subagent turn.

Root and subagent isolation

• Child and subagent lifecycle/tool events are identified and ignored before
  they can mutate root presentation state.
• Stop continues to normalize to WaitingUser plus ResultReady. ResultReady now
  remains visible through a bounded static activity-worker lease after the
  one-shot Stop Hook exits.
• Generation, session, workspace, terminal, predecessor, and cleanup ownership
  stay explicit. Worker launch failures remain fail-open.

Exact legacy transport convergence

An installation with the exact TabBeacon-owned historical Codex MCP Hybrid
declarations can converge transactionally to the current command-v1 Hook
transport. Similar, partial, modified, or otherwise ambiguous declarations are
refused rather than guessed.

The migration preserves unrelated third-party Hooks, MCP servers, Codex
configuration, title ownership, and backup/recovery state. When TabBeacon's
managed Hook definitions change, Codex requires a fresh manual /hooks trust
review. v0.7.2 does not bypass or pre-approve that review.

Qualification terminal safety

Active v0.7.2 qualification and visual paths now register each temporary
Windows Terminal window with a unique run ID, fixed anchor TabItem, and exact
ancestor HWND. Cleanup revalidates that complete identity and refuses ambiguous
or mismatched ownership; broad Windows Terminal process/window termination is
forbidden.

Unchanged product boundaries

v0.7.2 adds no provider and no new presentation feature. Daily agent launch
remains literal codex. The release adds no wrapper, fake executable, PATH
shadow, PTY host, global daemon, Hook-trust bypass, or automatic mutation of an
Owner's production Codex configuration or trust state.