fix: expand e2e coverage and docs for session sync compatibility

.agents/skills/opencode-sync-sandbox/SKILL.md

@@ -19,10 +19,20 @@ Follow this workflow whenever a task changes sync behavior, config handling, com
    - `bun run build`
 6. Run full isolated E2E before declaring success:
    - `./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh`
-7. Report exact evidence: what changed, what tests ran, and E2E artifact path.
+   - Run E2E variants that directly exercise the features changed in this task
+     (for example: sessions, secrets, or other changed sync flags/paths).
+7. Report exact evidence: what changed, what tests ran, and an E2E artifact review.
 
 Do not skip E2E for changes that affect sync workflows, path resolution, repo operations, or command execution.
 
+## E2E Reporting Requirements
+
+- Do not report the E2E artifact path unless the user explicitly asks for it.
+- Read `results/summary.json`, command result payloads under `results/`, and relevant `logs/*.log` tails.
+- Summarize the executed flow, pass/fail status, key warnings/errors, and any suspicious signals.
+- If warnings exist, explain whether they are expected, tolerated, or need follow-up.
+- For feature-flagged runs, report the exact artifact-level behavior for each changed feature (including restart requirements when relevant).
+
 ## Sandbox Rules
 
 - Keep all E2E state inside `.memory/e2e/runs/<run-id>/`.
@@ -44,6 +54,10 @@ Use this clone to confirm command/server/tool behavior and avoid assumptions.
   - `./.agents/skills/opencode-sync-sandbox/scripts/preflight.sh`
 - Full two-instance GitHub E2E:
   - `./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh`
+  - Enable secrets coverage:
+    `./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh --enable-secrets`
+  - Enable session database coverage (implies secrets):
+    `./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh --enable-sessions`
 
 For additional usage flags, run:
 

README.md

@@ -117,11 +117,18 @@ Sync your opencode sessions (conversation history from `/sessions`) across machi
 
 Synced session data:
 
-- `~/.local/share/opencode/storage/session/` - Session files
-- `~/.local/share/opencode/storage/message/` - Message history
-- `~/.local/share/opencode/storage/part/` - Message parts
+- `~/.local/share/opencode/opencode.db` - Primary SQLite session database (current opencode versions)
+- `~/.local/share/opencode/opencode.db-wal` and `~/.local/share/opencode/opencode.db-shm` - SQLite sidecars synced with `opencode.db` when present (for WAL consistency)
+- `~/.local/share/opencode/storage/session/` - Legacy session files (pre-SQLite migration compatibility)
+- `~/.local/share/opencode/storage/message/` - Legacy message history (pre-SQLite migration compatibility)
+- `~/.local/share/opencode/storage/part/` - Legacy message parts (pre-SQLite migration compatibility)
 - `~/.local/share/opencode/storage/session_diff/` - Session diffs
 
+opencode handles JSON-to-SQLite migration automatically when `opencode.db` is missing, so syncing both
+formats supports users who have not migrated yet and users already on SQLite.
+
+After pulling session changes, restart opencode to ensure the latest session state is loaded.
+
 ### Prompt Stash (private repos only)
 
 Sync your stashed prompts and prompt history across machines by setting `"includePromptStash": true`. This requires `includeSecrets` to also be enabled since prompts may contain sensitive data.