Drop NVIDIA-as-default preseed (v0.2.1)

Pre-shipping a `defaultProvider=nvidia` + `defaultModel=qwen3-coder-480b`
seed in settings.json baked in an implicit "NVIDIA is the recommended
free option" without an actual key behind it. Fresh installs landed on
NVIDIA active with an empty key file, and the first chat silently failed
until the user dug into provider settings.

- postinstall.sh: strip defaultProvider/defaultModel from settings.json
  instead of setting them. NVIDIA stays in models.json as one available
  provider alongside the others; no implicit preference.
- build-bootstrap.sh: stop creating an empty `~/.config/nvidia/api-key`
  placeholder in the HOME skel. Provider keys are user-supplied through
  the dashboard's settings UI.
- README: rewrite first-run flow accordingly; dashboard prompts for a
  provider on first launch.
- Bump versionName to 0.2.1, versionCode 3.

Author: CelestialCreator

README.md

@@ -6,10 +6,10 @@ A [Pi coding agent](https://pi.dev/) shipped as an Android APK. No Termux instal
 
 ## Install (team testers)
 
-1. Grab the latest APK — **v0.2.0** — from the [Releases page](https://github.com/CelestialCreator/pocket-pi/releases/latest), or directly: [pocket-pi-v0.2.0.apk](https://github.com/CelestialCreator/pocket-pi/releases/download/v0.2.0/pocket-pi-v0.2.0.apk).
-2. Sideload — tap the APK on the phone (allow install from unknown sources for your browser/file manager), or `adb install pocket-pi-v0.2.0.apk`.
+1. Grab the latest APK — **v0.2.1** — from the [Releases page](https://github.com/CelestialCreator/pocket-pi/releases/latest), or directly: [pocket-pi-v0.2.1.apk](https://github.com/CelestialCreator/pocket-pi/releases/download/v0.2.1/pocket-pi-v0.2.1.apk).
+2. Sideload — tap the APK on the phone (allow install from unknown sources for your browser/file manager), or `adb install pocket-pi-v0.2.1.apk`.
 3. Open the app. First launch runs the bootstrap (3–5 min on Wi-Fi: extracts Termux, installs Node + npm packages, registers Pi extensions).
-4. Once the dashboard loads, tap its **⚙** in the top-right of the page chrome to add provider API keys, switch models, edit AGENTS.md, etc. NVIDIA NIM is pre-seeded (free) so you can chat immediately; OpenRouter / OpenAI / Anthropic / Groq are also wired up — paste a key (or use the Claude Pro/Max OAuth Sign-In, which opens your device's default browser) and pick a model.
+4. Once the dashboard loads, tap its **⚙** in the top-right of the page chrome to add a provider. Wired up: OpenAI, Anthropic (API key or Claude Pro/Max OAuth Sign-In), Google Gemini, Groq, Mistral, NVIDIA NIM, OpenRouter, plus device-code OAuth for ChatGPT / GitHub Copilot. Paste a key (or sign in via OAuth — opens your device's default browser), pick a model, save.
 5. Chat away.
 
 If the dashboard never finishes binding, the loading screen surfaces **Restart Pi** and **Re-run setup** buttons after a 15-second stall — those re-kick the service and re-run the bootstrap installer respectively. As a last resort, force-stop the app from Android Settings and reopen; the install state on disk is preserved.
@@ -73,7 +73,7 @@ The current build uses `applicationId = com.termux` so the upstream Termux boots
 |---|---|
 | Single-APK install on aarch64 phones | ✓ |
 | pi-agent-dashboard as the WebView UI (slash commands, model switcher, session history all native) | ✓ |
-| NVIDIA NIM + OpenRouter end-to-end (chat, tool use, cost tracking) | ✓ |
+| OpenAI / Anthropic API / NVIDIA NIM / OpenRouter end-to-end (chat, tool use, cost tracking); Claude Pro/Max OAuth round-trips through the device's default browser | ✓ |
 | Recovery UI when the dashboard doesn't bind within 15s (inline Restart Pi / Re-run setup buttons) | ✓ |
 | `pi-anthropic-messages` for tool-call rendering | ✓ |
 | Shell-session feature inside the dashboard | not yet — `node-pty` has no android-arm64 prebuild and is stubbed; chat/files/tasks work, terminal tab will fail |
@@ -86,4 +86,4 @@ MIT. Third-party runtime components keep their own licenses (Termux GPL, Pi MIT)
 
 ## Status
 
-v0.2.0 — POC, shippable. The Termux-fork-inside-an-APK approach works: pi-agent-dashboard is the chat UI, single-tap APK install handles the rest. Whether to invest in productizing it (custom prefix bootstrap, real applicationId, signed release builds, Play Store, etc.) or rewrite this as a proper native Android client that talks to Pi over the network is the question this POC is meant to inform.
+v0.2.1 — POC, shippable. The Termux-fork-inside-an-APK approach works: pi-agent-dashboard is the chat UI, single-tap APK install handles the rest. Whether to invest in productizing it (custom prefix bootstrap, real applicationId, signed release builds, Play Store, etc.) or rewrite this as a proper native Android client that talks to Pi over the network is the question this POC is meant to inform.

android/app/build.gradle.kts

@@ -26,8 +26,8 @@ android {
         // legacy semantics that allow exec from app-data, which Pi (and the
         // entire Termux runtime) relies on.
         targetSdk = 28
-        versionCode = 2
-        versionName = "0.2.0"
+        versionCode = 3
+        versionName = "0.2.1"
 
         ndk { abiFilters += listOf("arm64-v8a") }
     }

bootstrap/build-bootstrap.sh

@@ -49,14 +49,15 @@ chmod +x "$WORK/prefix/etc/pocket-pi/postinstall.sh"
 chmod +x "$WORK/prefix/etc/pocket-pi/patches/"*.sh
 
 # 2. HOME skel — copied into the user's $HOME on first launch by postinstall.
+# No api-key placeholders: provider keys are user-supplied through the
+# dashboard's settings UI on first run. Pre-creating a stub file for any
+# specific provider would imply we're endorsing it.
 SKEL="$WORK/prefix/etc/pocket-pi/skel"
-mkdir -p "$SKEL/.pi/agent/skills/proposed" "$SKEL/.config/nvidia"
+mkdir -p "$SKEL/.pi/agent/skills/proposed"
 cp "$ROOT/config/AGENTS.md"          "$SKEL/.pi/agent/AGENTS.md"
 cp "$ROOT/config/claude-bridge.json" "$SKEL/.pi/agent/claude-bridge.json"
 cp "$ROOT/config/models.json"        "$SKEL/.pi/agent/models.json"
 cp -R "$ROOT/skills/."               "$SKEL/.pi/agent/skills/"
-: > "$SKEL/.config/nvidia/api-key"
-chmod 600 "$SKEL/.config/nvidia/api-key"
 
 # 3. Repack
 OUT="$DIST/bootstrap-${ARCH}.zip"

bootstrap/postinstall.sh

@@ -195,26 +195,29 @@ if [ -f "$ETC/patches/node-pty-stub.js" ] && [ -d "$NODE_PTY_PKG" ]; then
   echo "==> node-pty stub installed; src/ removed so tsx uses lib/"
 fi
 
-# --- 3b. Seed default provider/model ---------------------------------------
-# Pi reads defaultProvider/defaultModel from settings.json at boot to pick
-# the active model. Without these, the dashboard's model picker has nothing
-# selected and prompts have nowhere to go. Set NVIDIA's Qwen3 Coder 480B as
-# the default (free); only if the user hasn't already chosen.
+# --- 3b. Clean settings.json (no default provider preseed) ------------------
+# Earlier builds preseeded `defaultProvider=nvidia` so a fresh install could
+# chat immediately against free NVIDIA NIM. Pulled now: it bakes in an
+# implicit "NVIDIA is the recommended provider" without a real key behind
+# it, and the dashboard's first-run UX is better when it prompts the user
+# to pick a provider through its native settings UI. NVIDIA stays available
+# in models.json as one option among several — no preference applied.
 SETTINGS="$HOME/.pi/agent/settings.json"
-python3 - "$SETTINGS" <<'PY'
+python3 - "$SETTINGS" <<'PY' || echo "WARN: settings.json cleanup skipped"
 import json, pathlib, sys
 p = pathlib.Path(sys.argv[1])
 data = {}
 if p.exists():
     try: data = json.loads(p.read_text())
     except Exception: data = {}
-data.setdefault("defaultProvider", "nvidia")
-data.setdefault("defaultModel", "qwen/qwen3-coder-480b-a35b-instruct")
+# Strip any legacy preseeded defaults; modern flow has the dashboard prompt.
+data.pop("defaultProvider", None)
+data.pop("defaultModel", None)
 # Strip any legacy pi-webserver block — the dashboard is the UI now.
 data.pop("pi-webserver", None)
 p.parent.mkdir(parents=True, exist_ok=True)
 p.write_text(json.dumps(data, indent=2))
-print(f"merged default model into {p}")
+print(f"cleaned settings.json defaults at {p}")
 PY
 
 # --- 3c. Write dashboard tool overrides ------------------------------------