The worker set the accessory policy after AppKit had already registered it as a Dock app, so 11 of 15 launches showed Foreground for about 30 ms. Now it sets LSUIElement in its main bundle's info before the kernel starts AppKit, and fails to start unless the policy came up as accessory. tests/scripts/dock-macos.sh samples each worker's type from its start until the first tile; on the Mac mini 30 launches were all UIElement, and the shipped worker fails it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
FAIL
- crates/ely-lok/src/ffi/accessory.rs:38 — The worker still registers briefly as a foreground application:
sharedApplicationinitializes AppKit under the parent bundle's regular identity before line 42 sets the accessory policy. On macOS 27.0.1 arm64, I built this revision and launched the worker under the shipped Doc/Table/Show bundle identities five times each. Eleven of fifteen launches reportedForegroundbeforeUIElement; one ElyTable launch reported those states at 0.1602 s and 0.1892 s respectively. All launches still loaded documents and painted tiles (.work/R6.12-r1/dock-repeat.log). This leaves a startup window for the second Dock entry and disproves the claim that the worker registers as UIElement from the outset; bundled apps default to the Dock-visible regular policy (Apple documentation). Establish the worker's agent identity before AppKit first registers it, preserving the main application's regular identity, and add a bundled-startup regression test that rejects anyForegroundobservation while checking document loading and rendering.