Systematic trace of the activation funnel (store listing -> docs setup guide -> in-app onboarding -> connect flow) after #113 showed a docs 404 bug had slipped through. Fixes found in this pass: - README.md and CONTRIBUTING.md still told developers to run `npm install -g opencode` (missing -ai), the exact 404 #113 fixed everywhere else. Same package-name fix applied here. - src/lib/diagnostics.ts: the health probe reported ok:true for any resolved fetch, including 401/403/404/500 responses. A wrong password or broken server therefore classified as "Health endpoint responded - connection actually works now.", contradicting the error shown right next to it. Health now requires a real 2xx; root-reachability probe explicitly opts out (requireOk: false) to keep its existing reachability-only semantics (already encoded in diagnostics-classify.test.ts). - docs-site/vs-termux: architecture explainer described /session/{id}/events and /session/{id}/chat, neither of which exists; the app actually uses /global/event and /session/{id}/prompt_async (src/lib/sdk.ts). - docs-site/features: opencode repo link pointed at github.com/opencode-ai/opencode instead of github.com/sst/opencode, the org used everywhere else in the docs. - Stale "v0.4.3" version strings (README x3, docs-site/download x2) bumped to v0.4.7, the actual latest shipped release confirmed live on GitHub Releases and the F-Droid repo index. Fixed the associated Android min-OS contradiction (7.0 vs 8.0+) to 7.0, matching the live F-Droid manifest's minSdkVersion 24. - Dropped stale "GPT-4" model naming on 3 docs-site pages, consistent with the model-agnostic policy already applied to the Play listing in #83. See PR body for the found-not-fixed list (Play Console listing drift, GitHub Sponsors not enabled, a Cloud-vs-waitlist messaging conflict) that need a product/human decision rather than a code fix. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
26 KiB
26 KiB