[DRSDavidSoft]

Immediate styled TUI startup

The former splash was literal unstyled text emitted at main entry, before
Bubble Tea initialized terminal colors. It did not use the TUI palette, and
classic Windows conhost did not yet have VT processing enabled. The remote
attachment path also printed another unstyled connecting caption and performed
independent snapshot/catalog and UI/RF preference reads sequentially before the
first TUI frame.

The immediate startup frame now shares the TUI's cyan/violet palette and rounded
panel geometry, with a fixed-slot chip emblem and terminal identity. Rendering is
pure and does not wait for settings, network, UART, welcome audio or TUI setup.
It fits the current terminal width, collapses on narrow terminals, sanitizes
caption controls, and never claims a percentage or connected board. Explicit
interactive presentation uses a private true-color renderer; ambient build-log
NO_COLOR/TERM=dumb does not make it white. Classic Windows VT processing is
enabled before the first frame. Redirected CLI output, helper processes and
explicit web --no-tui remain free of the splash.

The duplicate remote connecting text is removed. Independent snapshot/catalog
reads run concurrently under the existing eight-second context; UI/RF settings
reads run concurrently under the existing four-second context. Authentication,
ownership, navigation event-cursor handshake, runtime safety, original errors
and cancellation remain required. Board connection is still managed by the TUI's
existing asynchronous lifecycle; startup decoration never opens or actuates it.
There is no animation worker or minimum splash delay to race the TUI or keep it
waiting. Bubble Tea replaces the frame through its normal alternate-screen handoff.

Focused tests cover width bounds, ANSI colors, fixed chip slots, sanitized copy,
redirected-output silence, parallel read barriers, cancellation and failure
retention. tui-preview --page startup renders the actual presentation without
hardware access. A rendered preview is not a screenshot of the production console
or a measured cold-launch timing claim.

[DRSDavidSoft]

Deployed through the primary-owned updater, operation op-3016c490777def2a, terminal_verified=true. Exact source: 5cc3890; source digest: a56a94dabd3822cb74ec5bafa98fd04d087d4aced073e30b24688b0278d85456; executable SHA256: e783ba66e4fde64157d74f08c48f5f2337f1338fb1ec2c881e10050fa40e6453. Read-only post-restart verification showed the native TUI active on dashboard, board connected, all 16 RF bindings preserved including the four deliberately disabled rules, and Pealayer paused/connected. Focused startup/parallel bootstrap tests passed through the stable Go runner; go vet passed; package Win32 resources, Web typecheck/bundle, C ABI smoke and libavrdude adapter verification passed. The pure rendered preview exposed and verified a chip-slot alignment correction. Browser local-file visual capture was blocked; no workaround was attempted. Actual cold-launch timing and native console screenshot acceptance remain unmeasured. No board flash, RF learn/save or physical actuator test was started.

[DRSDavidSoft]

Final main b0111ae was packaged after every required PR gate passed, without admin overrides. Cafe's primary-owned updater accepted host artifact ff6b93d7f6bf6d5709dec778ab62be76d566207857e937285b31bfacc647f195, source digest acf6b11a3ffb2ed5a77a4fa1b06e9df95c1d50643d3128540fa13fb1ecf217f5. Operation op-0a9e88bbae11baf4 completed; fresh process/source digest and on-disk executable hash match. Native TUI is active on dashboard with console visible, board connected/error-free, programming inactive, RF learning inactive and all 16 bindings/4 intentionally disabled rules preserved. Pealayer is on merged main, connected and paused. No firmware/EEPROM, RF mapping or actuator command was used. Build verified Web typecheck/bundle, resources, C ABI smoke and programmer callback adapter; full hosted gates plus the stable-path selected CLI/config/control/RPC/TUI suites passed before packaging. Generated build output is preserved in a named stash; other worktrees/stashes remain intact. Open PR count is zero across all three requested repositories. Cold-launch visual timing, physical/playing/soak acceptance are not inferred from these receipts.