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
The v2026.3.11 upstream sync (#2379, merged 2026-04-17 as 5809662258) left apps/shared/RemoteClawKit/Sources/RemoteClawKit/GatewayChannel.swift referencing three symbols whose source files are classified EXCLUDE-GUT in HQ disposition and never made it into the fork:
ThrowingContinuationSupport — referenced at GatewayChannel.swift:48
GatewayDeviceAuthPayload — referenced at GatewayChannel.swift:439, 450
GatewayConnectChallengeSupport — referenced at GatewayChannel.swift:618
Running swift test on apps/shared/RemoteClawKit currently fails with:
error: cannot find 'ThrowingContinuationSupport' in scope
error: cannot find 'GatewayDeviceAuthPayload' in scope
error: cannot find 'GatewayConnectChallengeSupport' in scope
These symbols were deliberately gutted as part of the CLI-native auth cleanup (Pi-embedded device auth was replaced with CLI-native auth). The consumers in GatewayChannel.swift were not cleaned up in the same pass.
Impact
RemoteClawKit module does not compile → RemoteClawChatUI does not compile → RemoteClawKitTests cannot build/run.
Existing ChatViewModelTests, GatewayNodeSessionTests, etc. are all blocked.
CI does not catch this because there are currently no macOS/Swift build or test jobs in .github/workflows/.
Scope
Identify the code paths in GatewayChannel.swift that reference the gutted symbols.
Determine the correct disposition per section (GUT the call sites, stub them, or surface for discussion if any path is actually needed for current gateway operation).
Verify swift build and swift test --filter ChatViewModelTests succeed after the fix on macOS.
Acceptance criteria
swift build on apps/shared/RemoteClawKit succeeds on macOS.
swift test --filter ChatViewModelTests runs (all tests pass or clear rationale for any expected failures).
GatewayChannel.swift no longer references ThrowingContinuationSupport, GatewayDeviceAuthPayload, or GatewayConnectChallengeSupport.
Context
The v2026.3.11 upstream sync (#2379, merged 2026-04-17 as
5809662258) leftapps/shared/RemoteClawKit/Sources/RemoteClawKit/GatewayChannel.swiftreferencing three symbols whose source files are classifiedEXCLUDE-GUTin HQ disposition and never made it into the fork:ThrowingContinuationSupport— referenced atGatewayChannel.swift:48GatewayDeviceAuthPayload— referenced atGatewayChannel.swift:439, 450GatewayConnectChallengeSupport— referenced atGatewayChannel.swift:618Running
swift testonapps/shared/RemoteClawKitcurrently fails with:These symbols were deliberately gutted as part of the CLI-native auth cleanup (Pi-embedded device auth was replaced with CLI-native auth). The consumers in
GatewayChannel.swiftwere not cleaned up in the same pass.Impact
RemoteClawKitmodule does not compile →RemoteClawChatUIdoes not compile →RemoteClawKitTestscannot build/run.ChatViewModelTests,GatewayNodeSessionTests, etc. are all blocked..github/workflows/.Scope
GatewayChannel.swiftthat reference the gutted symbols.swift buildandswift test --filter ChatViewModelTestssucceed after the fix on macOS.Acceptance criteria
swift buildonapps/shared/RemoteClawKitsucceeds on macOS.swift test --filter ChatViewModelTestsruns (all tests pass or clear rationale for any expected failures).GatewayChannel.swiftno longer referencesThrowingContinuationSupport,GatewayDeviceAuthPayload, orGatewayConnectChallengeSupport.Related
apps/shared/OpenClawKit/Sources/OpenClawKit/DeviceAuthPayload.swift— "gutted: device auth payload — CLI-native auth"apps/shared/OpenClawKit/Sources/OpenClawKit/GatewayConnectChallengeSupport.swift— "gutted: gateway connect challenge — CLI-native auth"apps/shared/OpenClawKit/Sources/OpenClawKit/ThrowingContinuationSupport.swift— "dead: async utility only used by gutted commands"