cmux-next guards: baseline the Files tree's inline menu rows (base red defaults-snapshot)
What
cmux-next guards / defaults-snapshot fails on base at its "Menu rows run registered actions, not inline selectors" step (scripts/cmux-next/check-menu-actions.py), so every feat-cmux-next PR shows it red:
Packages/macOS/CmuxNext/Sources/CmuxNextApp/FileExplorer/FileExplorerOpenWithMenu.swift: 2 inline menu row(s), 0 allowed
Packages/macOS/CmuxNext/Sources/CmuxNextApp/FileExplorer/FileExplorerSectionView.swift: 1 inline menu row(s), 0 allowed
The rows came from 56d448575ce (the Files tree's item menu) and dd018d41b6a (Open With's app rows and Other…). This PR adds them to check-menu-actions-baseline.txt with a dated base-red comment, the same way the earlier base-red entries were added. File rows have no file-target registered action yet; FileActionsMenu is baselined for the same reason. Moving these rows into ActionRegistry.makeContextMenu is the real follow-up for the Files lane. The baseline only goes down, so a new inline row still fails.
Test
python3 scripts/cmux-next/check-menu-actions.py at origin/feat-cmux-next 4f431e9d0b4: exit 1 with the output above. With this change: ok: 41 inline menu rows in 31 baselined files, none new.
Overlap check: #23453 (base autofix action exports) doesn't touch this guard or any Swift. #23466 changes only FileExplorerCell.swift.
Agent session: huge-blue
🤖 Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the failing cmux-next guards / defaults-snapshot check by baselining the Files tree's inline menu rows that were red on base.
check-menu-actions.py now passes on base (41 inline menu rows in 31 baselined files, none new). The rows come from the Files tree's item menu and Open With's app rows; file rows have no file-target registered action yet, so they're baselined the same way earlier base-red entries were. The baseline only goes down, so a new inline row still fails the check.
Moving these rows into ActionRegistry.makeContextMenu is the real follow-up for the Files lane.