Release v3.2.2 · 3xian/PinkCollab

PinkCollab v3.2.2: explicit host recovery and session-safe model capabilities on Android

Highlights

Android host connections now recover only when you refresh or tap Try again. Each action opens one connection; returning to the foreground, network availability, and socket failures no longer trigger automatic reconnects.
The host filter shows each host's live connection status. While syncing a selected host, the loading page names that host; an unreachable host uses the same recovery surface for an empty session list and a session without retained conversation.
Compact loading controls use orbiting dots; larger resource-loading surfaces use morphing silhouettes. Caller dimensions and indeterminate progress accessibility semantics are preserved.

Sessions on the same host share available models without sharing runtime-specific thinking-level fallbacks. Runtime replacement invalidates that session's capabilities; explicit refresh retains usable same-runtime data, and stale responses cannot overwrite newer results.
Switching to a blocked host cancels the previous session's pending detail request instead of allowing an unrelated snapshot timeout to surface later.
Retained conversations remain readable while the host is offline. Blocked hosts do not wait for session snapshots they cannot supply.

Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it. After a connection is interrupted, use refresh or Try again to reconnect.
Gateway and npm packages use the aligned version 3.2.2; this release's behavioral changes are in Android. To update the Gateway, finish active work, run npm install -g pinkcollab@3.2.2, then pinkcollab update under the existing OS user, retaining --data-dir when applicable. Restarting the Gateway ends active OMP runtimes but preserves stored sessions and pairings.