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
apps/shared/RemoteClawKit/ contains three legacy OpenClaw* directories that parallel the active RemoteClaw* directories. The legacy dirs are dead code: they are NOT declared in Package.swift and NOT imported by any Swift target.
Partial-rename leftover from the macOS native-app rebrand work (PR #124 / #222 era). The new dirs were created and Package.swift updated; the old dirs were left in place but excluded from the build manifest.
This was surfaced indirectly via:
A REBRAND_LEAKAGE finding that flagged apps/shared/RemoteClawKit/Sources/OpenClawKit/GatewayNodeSession.swift as containing openclaw markers (the file is dead code; markers are stale rebrand state inside an orphaned dir)
find apps -name '*OpenClaw*' -not -path '*/.build/*' returns only the 2 Kotlin protocol files (intentional retain — see Out of Scope)
Out of scope
apps/android/.../protocol/OpenClawProtocolConstants.kt and its test — these are intentional cross-implementation protocol-name retention (Android channel uses upstream's wire-protocol naming for compat). Address separately if at all.
The OpenClaw_OpenClaw.bundle and similar artifacts under .build/ — build cache, not source.
Estimated effort
~30 minutes (delete + 2 swift builds + 1 swift test).
Problem
apps/shared/RemoteClawKit/contains three legacyOpenClaw*directories that parallel the activeRemoteClaw*directories. The legacy dirs are dead code: they are NOT declared inPackage.swiftand NOT imported by any Swift target.Sources/OpenClawKit/Sources/RemoteClawKit/(58 files)Sources/OpenClawChatUI/Sources/RemoteClawChatUI/(16 files)Tests/OpenClawKitTests/Tests/RemoteClawKitTests/(20 files)Total: 16 git-tracked files in 3 dirs to delete.
Evidence
apps/shared/RemoteClawKit/Package.swiftdeclares targets:RemoteClawProtocol→Sources/RemoteClawProtocolRemoteClawKit→Sources/RemoteClawKitRemoteClawChatUI→Sources/RemoteClawChatUIRemoteClawKitTests→Tests/RemoteClawKitTestsNo declaration references
OpenClawKit,OpenClawChatUI, orOpenClawKitTests.apps/macos/Package.swiftlikewise references onlyRemoteClawKit/RemoteClawChatUI/RemoteClawProtocoltargets.Likely origin
Partial-rename leftover from the macOS native-app rebrand work (PR #124 / #222 era). The new dirs were created and Package.swift updated; the old dirs were left in place but excluded from the build manifest.
This was surfaced indirectly via:
apps/shared/RemoteClawKit/Sources/OpenClawKit/GatewayNodeSession.swiftas containingopenclawmarkers (the file is dead code; markers are stale rebrand state inside an orphaned dir)Proposed work
Then verify:
Acceptance criteria
apps/shared/RemoteClawKit/Package.swiftunchanged (was already correct)cd apps/shared/RemoteClawKit && swift buildsucceedscd apps/shared/RemoteClawKit && swift testsucceedscd apps/macos && swift buildsucceeds (downstream consumer)bash scripts/ci/check-rebrand-leakage.sh --allexits 0find apps -name '*OpenClaw*' -not -path '*/.build/*'returns only the 2 Kotlin protocol files (intentional retain — see Out of Scope)Out of scope
apps/android/.../protocol/OpenClawProtocolConstants.ktand its test — these are intentional cross-implementation protocol-name retention (Android channel uses upstream's wire-protocol naming for compat). Address separately if at all.OpenClaw_OpenClaw.bundleand similar artifacts under.build/— build cache, not source.Estimated effort
~30 minutes (delete + 2 swift builds + 1 swift test).