Repository navigation
feat(macos): edit Device aliases with account and target ownership - #475
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…/pr475-continuity-1601 # Conflicts: # CHANGELOG.md # docs/ai-tooling.md
bloodf
marked this pull request as ready for review
November 7, 2026 20:30
bloodf
changed the base branch from
recovery/beans-device-aliases-20261106
to
main
November 7, 2026 21:37
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds native AppKit account alias editing for known Devices. Draft text stays separate from the model; Cancel produces no intent. Account/connection epochs, target membership and view lifetime reject stale prompts, including observed removal/reappearance and known/unknown ABA. Blank text resets the account alias through the existing local API.
Final candidate
7a76dc644030c165f3f326cc4e3191e466408ae2, treeeb84d4af59169ced4401d624c25b9799e9c7d2ad, normally includes maina8a631ebafter legitimate stack merges. Main memory UI/form changes from344/362 remain intact. All paths outside the seven-path AppKit delta are identical to main.Retained evidence: one independent objective APPROVE_SOURCE_ONLY at923a1cfc, zero findings; four affected DeviceNamePromptTests passed there. Six path blobs, API, alias producer/admission functions, test bindings and Swift runner are unchanged. The seventh path preserves the same five alias translations while retaining main's added translations. The net patch equals the reviewed patch except Git index hashes/hunk positions. This qualifies affected-input reuse, not execution of the entire new tree.
Current docs checker and whitespace check exited0. No dedicated Swift lint command/config exists. Original Apple logs/hashes remain preserved; historical native Markdown/Swift builds passed at923, and no new build was run under the current ordinary lint/unit/review policy.
Remote optional checks were queued/pending at qualification, not reported as PASS. Main protection API reports no branch protection, rulesets/branch rules are empty and there are no unresolved review conversations. Normal expected-SHA merge uses the serialized owned repository lock.
Full suite, physical accessibility/hardware and E2E remain NOT RUN/deferred. Follow-up: keyboard Rename/Cancel, VoiceOver label/focus, navigation/removal sheet dismissal, and real paired-device alias/reset propagation. Already-sent transport revocation and production/hardware readiness are not claimed.