TabBeacon 0.6.1

TabBeacon 0.6.1 release notes

TabBeacon 0.6.1 is the current public release.

Codex compatibility

Codex setup now selects its conservative command-Hook profile from explicit
local capability evidence. A reported Codex version is diagnostic only; it is
not mutation authority. When Hooks are explicitly available, a fresh setup
uses codex-hooks-command-v1, whose Hook parsing remains forward-compatible
and fail-open for unknown fields.

The profile retains eleven synchronous command-Hook lifecycle declarations,
the one-second fail-open timeout, and manual /hooks trust review. Daily use
remains literal codex; TabBeacon adds no launcher, PATH shadow, PTY wrapper,
or global daemon.

Persistent title and visual identity

Provider Visual Identity v2 carries provider identity into activity workers.
Provider, runtime, and workspace occupy independent title slots, so a worker
keeps the provider identity while workspace identity remains stable.

Persistent Windows title output uses Unicode-wide VT transport. The normal
path does not call SetConsoleTitleW. A newly published worker leaves the
originating Hook to write its first complete frame, while an already-active
worker renders without replacing that title.

Windows worker reliability

Worker and cleanup-observer standard streams are explicitly NUL-backed, but
that alone does not constrain all inherited Windows handles. v0.6.1 also uses
PROC_THREAD_ATTRIBUTE_HANDLE_LIST to allowlist the exact detached handles
passed to those long-lived descendants. OS-level sentinel-pipe and EOF tests
prove they do not retain ambient Codex redirected pipes after a Hook root exits.

The Hook model remains synchronous and fail-open. It does not promise
sub-second completion when Windows PowerShell startup is saturated, and it does
not make all Hooks asynchronous.

Out of scope

This release does not add a native Windows Terminal tab icon, XAML
integration, or Windows Terminal injection.