refactor(android): remove orphaned legacy screens#102809
Merged
Merged
Conversation
Member
Author
|
Land-ready proof:
Behavioral sweep:
Known proof gaps: none. |
vincentkoc
marked this pull request as ready for review
July 9, 2026 13:02
Member
Author
|
Merged via squash.
|
This was referenced Jul 9, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 10, 2026
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.
What Problem This Solves
Two legacy Android Compose surfaces remained after their only entry points were removed:
SettingsSheetwas orphaned whenPostOnboardingTabswas deleted in17777b3a9ff.ChatSheetContentwas orphaned when itsChatSheetwrapper was deleted incd86107a10f.The dead files retained about 1,600 lines of unreachable UI, stale source-inventory entries, and several unused Android helpers and design-token accessors.
Why This Change Was Made
ChatScreen.apps/android/style.md.Current
ShellScreencontinues to own the activeChatScreenpath, andSettingsScreensremains the active settings implementation.User Impact
No intended behavior change. This removes unreachable Android code and stale generated inventory while preserving the active chat and settings surfaces.
Evidence
tbx_01kx3df9b86as54x9y3q425gha./apps/android/gradlew -p apps/android --no-daemon app:lintPlayDebug app:ktlintCheck app:testPlayDebugUnitTest app:assemblePlayDebugpnpm native:i18n:checkpnpm check:changedSettingsSheetorChatSheetContentsymbol remains.