You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3c99486
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(record): spread the request scope into manifest re-resolution and show it in the request log
The manifest lane hand-picked the scope and lease keys to forward; a key added
to ResolveDeviceFlags later would be dropped silently on this lane. Admission
(namesSessionWithoutTarget) already proves the request states no device, udid,
serial, platform, or target, so spreading its flags carries exactly the scope
and lease keys — now and later — while the manifest still decides family and
identity. This deletes LeaseDiscoveryContext, its key list, and the helper.
The resolve_target_device phase now echoes the requested udid and simulator
set when the request states them, so a manifest-first recovery is provable
from the request log alone (the maintainer's scoped-set evidence requirement).
Pinned: dropping the spread fails all three recovery scope pins; dropping
either echoed field fails the new phase test.
0 commit comments