HomeChiefLinkInkTests: name NSView.display unambiguously (fix the base's test build)
Fixes the base's red fast tier. #24002 (cc027d84) added HomeChiefLinkInkTests with #selector(NSView.display). AppKit has both display() and display(_:), so the selector is ambiguous and CmuxNextAppTests no longer builds. Every PR's cmux-next fast tier has been red since, for example jobs 119640111188, 119641860268 and 119642938745 at 4f516576.
Change
One line: #selector(NSView.display as (NSView) -> () -> Void). Only the test changes; no app code.
Tests
cmux-ci run --class light --script scripts/ci/package-test-lane.sh --ref a88c965e4f52b14b92dfc4553e4333a01c6a808b --arg=suite --arg=Packages/macOS/CmuxNext --arg=HomeChiefLinkInkTestsbuilds CmuxNextAppTests and runs the test. The result goes in a comment.- Red on base: the fast tier jobs above fail at
HomeChiefLinkInkTests.swift:23:116: error: ambiguous use of 'display'.
Observed / Not run
Observed: the base's fast-tier errors. Fleet results are pending at the time of writing. Not run: nothing else; this is test-only.
Changelog
none
No capture: test-only change.
Agent session: cosmic-gray
🤖 Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3-3x.png)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the red cmux-next fast tier by disambiguating #selector(NSView.display) in HomeChiefLinkInkTests. AppKit has both display() and display(_:), so the bare selector is ambiguous and CmuxNextAppTests no longer compiles — every PR's fast tier has been red since #24002.
The fix casts the selector as (NSView) -> () -> Void. Test-only change; no app code is modified.