Skip to content

context.md

Latest commit

 

History

History
156 lines (143 loc) · 10 KB

context.md

File metadata and controls

156 lines (143 loc) · 10 KB
Raw

OpenCode Mobile — Ownership Context

App: cc.agentlabs.opencode (OpenCode Mobile). Expo/React Native Android client for a user self-hosted opencode AI coding server. Owner: VIBE TECHNOLOGIES, LLC.

GOAL (verbatim)

  1. No bugs — opencode mobile works end to end.
  2. Publish on F-Droid (if not).
  3. Publish on Google Play (if not).
  4. Use App-Store-Optimization + growth-hacking skills to optimize store listings.
  5. Reach 1k downloads.
  6. Keep goal/design/plan/progress in this file.

Success = published + functional on BOTH stores AND 1k verified downloads.

DESIGN / ARCHITECTURE NOTES

  • Sessions list reads home-scoped (session.list({roots:true}) via clientForDirectory(serverHome)) when connection has no explicit directory. Create must use the SAME scope or new sessions are invisible (bug #10).
  • CUA smoke test = Android emulator + vision-LLM driving the app, with a real opencode server on the runner host (10.0.2.2:4096). This is the E2E gate.
  • Telemetry (Sentry) is opt-in, default OFF.

CURRENT STATE (2026-06-01)

  • tsc: clean. Build APK CI: green. No open PRs.
  • v0.4.2 APK public (GitHub release). Play: Draft, blocked on human App-content console declarations (answers pre-drafted in distribution/PLAY-APP-CONTENT-ANSWERS.md).
  • F-Droid: mainline MR #39530 filed (real path); self-hosted repo deprioritized (androguard v2+v3 dup-signature bug).
  • BUG #10 (sessions empty after connect/create): fix committed a536466. Pre-fix smoke (run 26786055765) reproduced it exactly. Fix smoke run cancelled (server install hang) → UNVERIFIED. Re-verifying now.
  • Version mismatch: package.json 0.4.2 vs android/app/build.gradle versionName 0.4.1.

PLAN

  • P1 Verify #10 fix via CUA smoke (E2E green — run 26803479355).
  • P1 Reconcile version (gradle versionName → 0.4.2).
  • P2 Scan for other E2E bugs — found+fixed 2nd scope bug (open/send path); connect flow reviewed clean (serverHome populated on connect, self-heals).
  • P3 Play: human completes App-content + production rollout (gated).
  • P3 F-Droid: track MR #39530 (gated on maintainer review).
  • P4 ASO: refine listing copy/keywords with ASO skill.
  • P4 Growth: execute launch posts in distribution/launch/ for downloads.

PROGRESS LOG

  • 2026-06-01: Resumed under /take-ownership. tsc clean, build green. Confirmed #10 is a real reproduced bug; fix logic verified sound (create+list share home scope). Spotted version mismatch. Wrote this file.
  • 2026-06-01: Fixed gradle versionName 0.4.1→0.4.2 (commit 0615ab8).
  • 2026-06-01: Refactored #10 scope rule into one pure helper sessionScopeDirectory() so list/create can't drift; added node:test regression guard (4/4 pass), npm test script, excluded tests from app tsc (commit bed0b6f).
  • 2026-06-01: Found + fixed a SECOND scope bug (commit 66b89f7): freshly created home-scoped session was opened/sent via default CWD client because nav carried no directory param. createSession now stamps scope dir onto session; create-nav passes it. Same root cause as #10, open/send path. tsc + tests green.
  • 2026-06-02: ✅ SMOKE GREEN on 66b89f7 (run 26803479355). CUA vision-LLM scenario connect_and_verify_sessions: "Result: success in 9 steps — connected to server and a session is listed in Sessions." The exact pre-fix failure ("list still empty after create") is gone. #10 verified END-TO-END. Goal #1 core path proven working.
  • ASO/growth assets already authored (distribution/: aso-audit, listings, launch kit, graphics). Blocker is EXECUTION (human Play console publish + posting from owner accounts), not content.

WHAT ONLY THE HUMAN OWNER CAN DO (gated)

  • Play Console: complete App content declarations + production rollout (answers in distribution/PLAY-APP-CONTENT-ANSWERS.md). No admin/API access from here.
  • F-Droid: respond to mainline MR #39530 maintainer review.
  • Growth: post launch content from real accounts (HN/PH/Reddit/X) to drive installs.
  • These are why "published on both stores + 1k downloads" cannot be closed by the agent.

RUNTIME BUG AUDIT (2026-06-02)

Full runtime audit (stores + screens + sdk). Outcome:

  • FIXED (059b5cc): sendMessage stale-closure — send-failure after a session switch flashed error on / refetched the wrong session. Now scoped to the sent session.
  • DISMISSED w/ evidence: message.removed handler is dead code (events.ts never forwards it); part-without-sessionID guard is adequate (server always sends it; the proposed "require message exists" fix would drop pre-message streamed parts).
  • Connections, SSE reconnect/backoff, optimistic cleanup, FlatList keys, effect deps, settings persistence, attachment handling: reviewed clean.

F-DROID + PLAY PUBLISH PUSH (2026-06-02) — agent-controlled paths found

  • DISCOVERY: self-hosted F-Droid repo is ALREADY LIVE at https://dzianisv.github.io/opencode-mobile/fdroid/repo (index 200), but STALE — serving old package ai.opencode.mobile @ v0.4.1. publish-fdroid succeeded for v0.3.2/0.4.0/0.4.1, then FAILED from v0.4.2 on.
  • ROOT CAUSE: androguard (in fdroidserver) crashes on the CI APK's v2+v3 signature block pair: parse_v2_v3_signature -> "'NoOverwriteDict' object has no attribute 'append'". Published release asset is v2-only and parses fine.
  • FIX (c66f4fb): force v1+v2-only signing — gradle flags + a deterministic apksigner re-sign step in publish-fdroid.yml (expo prebuild regenerates build.gradle, so the workflow step is the real guarantee). Cut v0.4.3 / versionCode 5.
  • Tag v0.4.3 pushed → triggered: Build, CUA smoke, Publish F-Droid (run 26806570933), Publish Google Play (run 26806570940, uploads to INTERNAL track, status=completed — doesn't need the production App-content console gate). Monitoring.
  • DISCOVERY: a Publish-to-Google-Play workflow runs on tags (r0adkll/upload-google-play, track=internal, versionCode=github.run_number so always monotonic). Agent-reachable.
  • ✅ PLAY INTERNAL: run 26806570940 SUCCEEDED — v0.4.3 uploaded to Play internal track.
  • F-Droid run 26806570933 FAILED again: SAME androguard error, but in the v2 block parse (self._v2_blocks.append). Root cause = androguard==4.1.4 pin (added 2026-06-01), NOT v3. Last working publish (v0.4.1, May) used androguard 4.1.3.
  • VERIFIED LOCALLY: androguard 4.1.3 + fdroidserver 2.4.4 parse the v2-only APK and get_first_signer_certificate succeeds (the call that crashed under 4.1.4).
  • FIX (eea84a3): pin androguard==4.1.3. Re-pointed tag v0.4.3 → re-run F-Droid (run 26808062042). Play uses run_number so re-tag doesn't collide.

SESSION CLOSE (2026-06-02)

Agent-executable surface EXHAUSTED for this session. Done + verified:

  • Goal #1 (no bugs / E2E): ✅ CUA smoke GREEN (run 26803479355). Fixed 2 scope bugs (#10 list + open/send) and version mismatch. tsc + unit tests green.
  • F-Droid: mainline MR #39530 filed; IzzyOnDroid doc now filing-ready & verified (commit 67773fc).
  • ASO/growth content authored. Blocked (need owner identity/creds; shared browser also offline now):
  • IzzyOnDroid: file inclusion issue at codeberg.org/IzzyOnDroid/repodata (Codeberg acct).
  • Play: complete App content + production rollout (Play Console, legal attestation).
  • Growth: post launch kit from owner accounts → drive to 1k installs.

CEO CYCLE (2026-06-02, second) — read-only/headless env

Environment was fully read-only: git commit, npm, tsc, node --test, gh, curl, WebFetch all permission-gated. Worked with file edits + read tools only.

  • Ran a 3-way parallel read-only re-audit (session-scope / SDK+SSE / chat UI). Judged all findings; rejected 5 with evidence (logged in .autopilot/state.md).
  • FOUND + FIXED a 4th scope-drift bug (app/(tabs)/index.tsx:218, onCreateInDirectory): navigated with raw user input dir.trim() instead of server-authoritative session.directory → "Failed to load session" on a freshly created custom-directory session if the server normalizes the path. Mirrors sibling paths (lines 193/235). Type-safe by construction; uncommitted (no commit perms this session).
  • Reconciled the privacy-policy URL across all owner docs to the canonical https://opencode.vibebrowser.app/privacy (was split with agentlabs.cc in 3 spots; it's a legal attestation field in Play Console). Fixed stale v0.4.2→v0.4.3 AAB ref.
  • Hardened the owner approval queue with exact, ordered steps in .autopilot/state.md (C0 commit/push → C1 host privacy policy → C2 Play production → C3 run verifications → C4 verify F-Droid index → C5 IzzyOnDroid → C6 growth → C7 mainline MR).
  • NOT verifiable this session (queued as C3/C4): typecheck/test/CI green, live F-Droid v0.4.3 index check. Blocked by tooling, not by missing work. No downloads faked.

CEO CYCLE (2026-06-02, third) — tooling available; verified bucket-A closed

Env had working git (read + commit, NOT push), npm, tsc, node --test, gh, curl.

  • Committed the prior cycle's tree: ee7082a (custom-dir scope-drift fix) + c8458cd (privacy-URL/version doc reconcile). git push was permission-DENIED → queued as owner step C0 (not retried, per gated-means-irreversible rule).
  • typecheck green (tsc --noEmit clean); test green (node --test → 4/4 pass).
  • F-Droid v0.4.3 is now LIVE (the big open gap). Publish run 26808062042 on the androguard==4.1.3 pin commit (eea84a3) = success; live index-v1.json now serves {'cc.agentlabs.opencode': ['0.4.3']} (was stale ai.opencode.mobile 0.4.1 all prior cycle). The earlier v0.4.3 run 26806570933 failed on the same androguard 4.1.4 bug because it ran on the pre-pin commit c66f4fb; the re-tag re-ran it green.
  • Play internal track v0.4.3 publish (26808061960) = success.
  • CUA smoke v0.4.3 (26808062132) in-flight at cycle end; identical app code already green on 26805768987 → E2E verified-equivalent.
  • Verified blockers still down: privacy URL opencode.vibebrowser.app/privacy → HTTP 000 (not deployed, blocks Play prod C1); Play listing → 404 (production not rolled out C2).
  • Bucket-A is closed by the agent. Remaining work is human-gated (C0 push, C1 privacy host, C2 Play prod, C3 IzzyOnDroid, C4 growth, C5 mainline MR) — all in state.md. No downloads claimed or faked.