## Summary
- change the default socket device name from Zigbee插座控制器 to 智能插座
- update new default scenes, in-memory defaults, and Local Experience simulation data to use the new gateway name
- remove the duplicated Direct control section from the smart socket detail screen, keeping the main power control
- remove the unused direct-control strings
## Data behavior
- existing configured devices are not renamed
- existing persisted scenes are not migrated
- only newly created default content uses 智能插座
## Verification
- ./gradlew.bat :android:app:assembleDebug --no-daemon
- installed on mulator-5554
- confirmed the Local Experience device card shows 智能插座
- confirmed the socket detail screen has no Direct control section or duplicate ON/OFF buttons
Automated tests were not run.
Reviewed-on: #12
Co-authored-by: KremeCN <3265494849@qq.com>
## Summary
- rebuild the authenticated shell, device dashboard, device detail pages, scenes, activity timeline, account sheet, and settings experience
- redesign infrared remote management and controls, including custom remotes, learn-state handling, slot isolation, and safe default content
- add persisted theme controls with internal accent, color-style, and color-standard resolution while keeping dynamic color authoritative
- add ABox profile defaults for the three exact gateway device names, editable starter scenes, and custom infrared remotes
- persist real activity events for device commands, infrared actions, and scene execution
- stabilize navigation and back behavior, including duplicate top-back protection and removal of the unfinished predictive-back option
- update launcher icons and bilingual application name
## Verification
- `:android:app:assembleDebug`
- installed the debug APK on `emulator-5554`
- manually exercised device detail navigation, settings/theme navigation, infrared management, activity records, and repeated back actions
## Notes
- no automated test suite was run during the visual iteration cycle
- `docs/superpowers/**` and local reference repositories are excluded from this PR
Reviewed-on: #10
Co-authored-by: KremeCN <3265494849@qq.com>
## Summary
- replace the former three-provider model with two pre-login choices:
- **ABox**: authenticate through the vendor ABSDK on the current local network
- **Local experience**: establish a production simulation session without credentials, network access, or ABSDK calls
- remove the compatible-backend product/server scope and safely ignore legacy persisted compatible-provider values
- bind one process-wide `AbsdkBridge` for ABox session, socket, temperature/humidity, and infrared operations
- add production `:runtime:simulation` implementations and route device operations by the active provider
- retain provider-scoped username preferences, Keystore-encrypted automatic-login credentials, token recovery, logout, and session isolation
- add regression coverage for authentication gating, profile/session alignment, provider switching cleanup, routing, and simulation behavior
- align requirement, plan, architecture, and protocol documentation with LAN ABSDK access
## Verification
```text
./gradlew check testDebugUnitTest test
BUILD SUCCESSFUL (220 actionable tasks)
./gradlew :android:app:assembleDebug :android:app:assembleRelease
BUILD SUCCESSFUL (217 actionable tasks)
./gradlew :android:app:compileDebugAndroidTestKotlin
BUILD SUCCESSFUL
git diff --check
passed
```
Emulator smoke validation:
- provider selection displays ABox and Local experience only
- Local experience enters the authenticated route without credentials
- Local experience also enters while emulator Wi-Fi/data are disabled
- Local Sign out and Switch provider return to provider selection
- ABox opens the credential form; empty submission stays on login with the required-fields error
## Known constraints and accepted risks
- The vendor JAR uses cleartext HTTP and hardcodes `a-box.com.cn`; Debug and Release intentionally share the same ABox capability under the approved no-Release-exception decision. `@CleartextAbsdkTransport`, `usesCleartextTraffic`, and the architecture/protocol documents explicitly record this risk. This does not provide confidentiality or integrity.
- Real authenticated ABox and read-only hardware smoke validation is deferred because the gateway is currently unavailable locally. This PR does not claim that current-environment validation completed.
- The mapping from the vendor JAR's hardcoded hostname to the LAN gateway remains an external network/deployment prerequisite. The ABSDK JAR and bridge path remain identical to the previously hardware-validated `feat/moler-infrared-control` branch.
- `FakeDeviceCatalog` remains a temporary debug-only placeholder until the device-catalog module provides the production ABox catalog. ABox catalog requests are not routed to Local experience simulation.
Reviewed-on: #4
Co-authored-by: KremeCN <3265494849@qq.com>
KremeCN