Repository navigation
The proof the last patch published is now real, and three narrow gaps it left are closed. A defects-and-tests patch: no defaults, presets or features change.
The group-cycle check passes where it should
tests/live/interactions.sh now sets its own premise (perMonitorApps: false, original icon style) instead of inheriting the owner's config. A probe dock pinned to an empty headless output had every window filtered out, so the step that removes a group and re-creates one from running apps could never observe its running app — the check was red on the promoted v4.13.1 tree. With the premise set, both transitions are read from the probe's own model: the app returns to the running row, then moves back into a group. Measured two-sided: the check fails on a copy with refreshDock() removed and passes here.
The symbolic folder look shares the broken-icon fallback
DockFolderItem's symbolic art draws DockIconArt.settledSource instead of its own raw source. One owner settles the decode and substitutes application-x-executable when it fails, and the folder tile logs no second Error decoding line. A live step pins a zero-byte *-symbolic.svg and reads the drawn source and its decode status.
A spelling cannot keep a dead popup open
DockFolderLogic.toggleFolderPin normalises ~/… and absolute paths on both sides before closing the stack. A live step pins ~/…, opens it and unpins the absolute path; the old guard left the popup floating.
v4.13.1's note is corrected
The v4.13.1 release page claimed the live interactions suite passed the group cycle; that did not reproduce on the promoted tree, and the page now says so.
Verification
300 Node + 149 Python unit tests, qmllint 0 errors, and the structure, security, i18n, manifest and plugin gates pass. Live interactions (both icon fallbacks, the unreadable folder, both group transitions, both unpin spellings), presets, label-metrics, indicators, ipc-roundtrip and teardown pass. tasks is not claimed: on this desk its probe model has no pinned tile while hidden, a pre-existing harness precondition outside this patch. The owner's config (cfac0a4a03ee820e6a4e227de7cb6536) was byte-identical across the checks, with no probe process, headless output or scratch directory left behind, and the shell was restarted onto this tree.
Upgrade
omarchy plugin update omadock --yesthen restart the shell (omarchy restart shell) so the running dock loads this tree.
🤖 Generated with Codebuff
Co-Authored-By: Codebuff noreply@codebuff.com