* fix(sessions): use active connection client directly, remove roots filter Root cause A: loadSessions was calling clientForDirectory(serverHome) which scoped the session list to /home/azureuser — a different project than the server's active CWD. Sessions in the current project (e.g. opencode-mobile) were never returned. Root cause B: roots:true filtered out sessions that have a parentID (sub-task / AUTO-REVIEW sessions), hiding valid sessions from the list. Fix: use connState.client directly (the connection's active directory) and drop the roots filter so all sessions for that project are visible. Also adds a verify_session_list CUA smoke scenario that navigates back to the sessions tab after creating a session and asserts the list is non-empty — covering the regression path that was previously untested. * fix(sessions): fetch serverHome in addConnection so loadSessions shows correct sessions Root cause: addConnection() built the HTTP client but never fetched serverHome (only loadConnections and setActiveConnection did). When the user adds a new connection (fresh install / first sign-in), serverHome = null, so loadSessions fell through to connState.client (the server's CWD). On this dev server the CWD is the deploy directory — 11 old May-19 sessions that are not the user's recent work sessions. Fix: addConnection now fetches currentProject + serverHome via the same Promise.all as setActiveConnection, before calling set(). This ensures loadSessions immediately uses clientForDirectory(serverHome) → the global project → the user's actual recent parent sessions. Also adds --opencode-url flag to the CUA smoke script, which appends a connect_and_verify_sessions scenario that reproduces the regression: python scripts/android-cua-smoke.py --opencode-url http://100.108.64.76:4096 * fix(sessions): recover home scope after fresh connect Resolve stale deploy-only session list by recovering server home during first load and keeping regression coverage in default Android CUA smoke and CI. * chore(release): bump version to 0.4.0
22 lines
1.0 KiB
Markdown
22 lines
1.0 KiB
Markdown
## Modality
|
|
Real feature test on Android emulator + real OpenCode server via ADB/vision smoke.
|
|
|
|
## Setup
|
|
1. Ensure Android SDK tools in PATH:
|
|
- `export PATH="/tmp/android-sdk/platform-tools:/tmp/android-sdk/emulator:$PATH"`
|
|
2. Ensure emulator is booted (`emulator-5554`) and app installed.
|
|
3. Load Azure OpenAI env:
|
|
- `source ~/.env.d/azure-openai.env`
|
|
|
|
## Steps
|
|
1. Launch app and clear prior state if needed.
|
|
- Expected: app opens to sessions or onboarding without crash.
|
|
2. Run connect-and-verify smoke against real server:
|
|
- `python3 scripts/android-cua-smoke.py --model gpt-5.4 --include-xml --max-steps 40 --opencode-url http://100.108.64.76:4096`
|
|
- Expected: scenario `connect_and_verify_sessions` returns success.
|
|
3. Confirm script-level regression path:
|
|
- Expected: `verify_session_list` scenario also succeeds.
|
|
|
|
## Pass criterion
|
|
Both session-list scenarios (`verify_session_list`, `connect_and_verify_sessions`) pass in one run, proving sessions list renders non-empty after connect when server has sessions.
|