clawdex-mobile 5.0.1 → 5.0.2

package/docs/privacy-policy.md

@@ -1,54 +0,0 @@
-# Privacy Policy
-
-Last updated: March 6, 2026
-
-## Overview
-
-Clawdex Mobile is a companion app for connecting to a bridge service that you run on your own machine. The app is designed for trusted private networking, such as LAN, VPN, or Tailscale. It is not a public multi-tenant shell service.
-
-## Information Processed
-
-Clawdex Mobile can process:
-
-- Chat prompts and assistant responses
-- Bridge connection details you enter in the app
-- Terminal command text and command output returned by your bridge
-- Git repository status, diffs, commit messages, and related metadata
-- File or image attachments you choose to send
-- Voice input audio used for speech-to-text features
-
-## How Information Is Used
-
-The app uses this information to:
-
-- connect your phone to your self-hosted bridge
-- display and continue assistant threads
-- execute approved terminal and Git workflows on infrastructure you control
-- upload user-selected files and images to your own workflow
-- support optional voice-to-text input
-
-## Storage and Retention
-
-Clawdex Mobile does not define a separate cloud retention layer for your project data. Data is generally stored by services and infrastructure you control, including your local bridge, repository, logs, caches, and any model providers or integrations that you configure.
-
-## Sharing
-
-Clawdex Mobile does not include advertising SDKs. Data may be transmitted to third-party model or infrastructure providers only when you configure and use those services as part of your own setup.
-
-## Security
-
-Security depends on how you configure your bridge and network. The app is intended for trusted-network use. You are responsible for protecting bridge tokens, provider credentials, repository access, and device access.
-
-## Your Responsibility
-
-You are responsible for:
-
-- operating the bridge only on systems you own or are authorized to control
-- securing your network path and credentials
-- reviewing commands, approvals, and repository actions before execution
-
-## Contact
-
-For support, use the project support channel:
-
-https://github.com/Mohit-Patil/clawdex-mobile/issues

package/docs/realtime-streaming-limitations.md

@@ -1,161 +0,0 @@
-# Realtime Streaming Limitations And Mitigations
-
-Date: February 22, 2026
-
-## Context
-
-This project has three relevant runtime paths:
-
-1. Mobile app connects to bridge WebSocket (`/rpc`).
-2. Rust bridge spawns `codex app-server --listen stdio://` as a child process.
-3. Codex CLI interactive (`codex` TUI) can run independently from the bridge path.
-
-Because of this, shared history and shared live stream are not the same thing.
-
-## Current Architecture Facts
-
-1. Bridge -> app-server transport is `stdio://` (process pipes), not network WebSocket.
-2. Mobile receives events that the bridge app-server instance emits.
-3. CLI interactive runs can happen in a separate process/session pipeline.
-4. Persisted thread data is written under the same `CODEX_HOME` (default `~/.codex` when unset).
-
-## Why Main Messages Appear But Some Live Details Do Not
-
-When a turn is started outside the bridge pipeline (for example from standalone Codex CLI), mobile can still show the final/main message because it periodically reads persisted thread history:
-
-1. Mobile calls `thread/read` (with `includeTurns`) through API client.
-2. Persisted `agentMessage` / `userMessage` items are mapped into chat messages.
-3. So the main output appears after persistence.
-
-However, item-level realtime notifications (reasoning deltas, tool call progress, activity transitions, approval prompts) are stream-bound and may not be available unless that turn is on the same live app-server stream the mobile bridge is subscribed to.
-
-## Limitation (Known)
-
-For CLI-originated turns outside the bridge-owned live stream:
-
-1. Main conversation output is usually visible (via persisted history read).
-2. Full realtime telemetry is not guaranteed:
-   - activity bar transitions
-   - reasoning deltas
-   - tool call begin/progress/completion events
-   - approval/user-input request timing parity
-
-This is an architectural boundary, not just a UI rendering bug.
-
-## How We Are Overcoming It Today
-
-Current mitigation strategy is hybrid: live events when available + snapshot sync fallback.
-
-1. Live forwarding
-   - Bridge forwards app-server notifications to all WebSocket clients.
-2. Event replay
-   - Bridge stores replayable notifications with `eventId`.
-   - Mobile can request missed events (`bridge/events/replay`) after reconnect.
-3. Running-state hints
-   - `thread/status/changed` is used as a lightweight signal for externally-observed activity.
-4. Fast/idle polling fallback
-   - Active chat sync interval and idle sync interval keep UI consistent even when deltas are missed.
-5. Debounced full sync on external status changes
-   - Prevents noisy expensive reload loops while still converging to latest persisted state.
-6. Read-only open behavior for past chats
-   - Opening history uses read/snapshot flow and avoids accidentally starting/resuming old sessions.
-
-## Practical Guidance
-
-1. If full realtime detail is required, start turns through mobile/bridge flow.
-2. For standalone CLI-originated turns, expect eventual consistency in mobile (main output first-class, detailed live telemetry best-effort).
-3. Keep all clients on the same user + same `CODEX_HOME` to preserve shared persisted history continuity.
-4. Use `bridge/events/replay` for reconnect gaps.
-
-## Future Improvement Direction
-
-To get strict realtime parity across CLI and mobile, move to a single live event authority:
-
-1. Route all turn execution through one shared bridge/app-server pipeline, or
-2. Make clients attach to the exact same running app-server stream/session boundary.
-
-Without this architectural change, the hybrid model remains the pragmatic and low-risk approach.
-
-## Incident Note: February 28, 2026 Live-Sync Regression
-
-### Symptom
-Mobile chat showed persisted messages, but did not show live activity/reasoning updates (`codex/event/*`, `thread/status/changed`) for CLI-origin turns.
-
-### Root Cause
-Rust bridge rollout discovery scheduler used a modulo condition that could never become true when the discovery interval was `1`.
-
-- Previous behavior: discovery did not run for that interval value.
-- Effect: rollout files were not tracked, so no CLI live-tail notifications were emitted.
-
-### Fix Applied
-Live-sync discovery scheduling was hardened so it is valid for all interval values and always runs on first tick.
-
-Operational result:
-
-1. Rollout files are discovered consistently.
-2. CLI-origin event lines are tailed and converted into bridge notifications.
-3. Mobile receives activity/reasoning status in realtime again.
-
-## Optimization Backlog (Live-Sync Observability + Reliability)
-
-### 1) Add `bridge/liveSync/status` RPC (recommended next)
-
-Goal: make rollout tailing state visible from mobile/Postman without guessing.
-
-Suggested response payload:
-
-1. Sessions root currently in use (`CODEX_HOME` resolved path).
-2. Discovery config (`pollIntervalMs`, `discoveryIntervalTicks`, `maxTrackedFiles`).
-3. Tracked files list:
-   - file path
-   - thread id
-   - originator
-   - include/exclude flag
-   - include/exclude reason
-   - current offset
-   - last seen timestamp
-4. Summary counters:
-   - files discovered
-   - files included
-   - lines parsed
-   - lines dropped (invalid JSON / filtered / duplicate)
-   - notifications emitted by method bucket
-5. Last error (if any) in discovery/poll loop.
-
-Why this helps:
-
-1. Explains "why no live updates" immediately.
-2. Reduces debugging time for CLI vs mobile parity issues.
-3. Enables lightweight health checks and QA verification.
-
-### 2) Add discovery/poll loop metrics
-
-Expose counters for:
-
-1. discovery runs
-2. poll runs
-3. per-file parse errors
-4. event mapping misses
-5. replay buffer writes/drops
-
-These can be returned by the status RPC and optionally logged to stderr in dev mode.
-
-### 3) Add dedup + mapping diagnostics for dropped events
-
-Track bounded recent reasons for dropped lines:
-
-1. duplicate hash
-2. unsupported rollout record type
-3. missing thread id
-4. originator filtered
-
-This will clarify whether events are not emitted due to filtering or malformed source lines.
-
-### 4) Add a short runbook for operators
-
-When live updates are missing, check in this order:
-
-1. `bridge/events/replay` contains recent `codex/event/*` or not.
-2. `bridge/liveSync/status` include/exclude reason for newest rollout file.
-3. newest rollout file `session_meta.originator` and resolved thread id fields.
-4. mobile selected thread id matches emitted thread id.

package/docs/terms-of-service.md

@@ -1,33 +0,0 @@
-# Terms of Service
-
-Last updated: March 6, 2026
-
-## Overview
-
-Clawdex Mobile is a companion client for interacting with a bridge service and repository environment that you control. By using the app, you agree to use it only with systems, repositories, and infrastructure that you own or are explicitly authorized to access.
-
-## Acceptable Use
-
-You may not use Clawdex Mobile to access, control, or modify machines, repositories, or services without authorization. You are responsible for all actions initiated through the app, including approvals, terminal commands, Git actions, and file transfers.
-
-## Credentials and Access
-
-You must keep bridge tokens, provider credentials, repository credentials, and device access secure. If you believe credentials have been exposed, you should rotate them immediately and stop using the affected bridge until it is secured.
-
-## Operational Risk
-
-Clawdex Mobile can initiate workflows that change files, repositories, and machine state on your host environment. You are responsible for reviewing and approving actions before execution and for maintaining backups or recovery procedures appropriate to your environment.
-
-## Availability
-
-The app depends on your bridge, network, repositories, model providers, and related services. Functionality may be unavailable if those dependencies are unavailable or misconfigured.
-
-## No Warranty
-
-The software is provided on an as-is basis. You assume responsibility for how it is configured and used in your environment.
-
-## Contact
-
-For support, use the project support channel:
-
-https://github.com/Mohit-Patil/clawdex-mobile/issues

package/docs/voice-transcription.md

@@ -1,87 +0,0 @@
-# Push-to-Talk Voice Transcription
-
-Voice-to-text input for the mobile composer. Tap the mic button to record, tap again to stop — the audio is sent to the Rust bridge which calls OpenAI's transcription API and returns the text into the composer.
-
-## Architecture
-
-```
-Phone (expo-audio)        Rust Bridge              OpenAI
-  record 16kHz mono       --> base64 over WebSocket --> POST /v1/audio/transcriptions
-  (iOS WAV, Android M4A)
-  insert text in composer <-- { text: "..." }    <-- gpt-4o-transcribe response
-```
-
-The flow mirrors Codex CLI 0.105.0's TUI push-to-talk feature — same API, same model (`gpt-4o-transcribe`), same auth. The bridge acts as the HTTP proxy since the phone doesn't hold API keys directly.
-
-## Auth Resolution
-
-The bridge resolves transcription credentials in order:
-
-1. `OPENAI_API_KEY` env var → `https://api.openai.com/v1/audio/transcriptions` (model: `gpt-4o-transcribe`)
-2. `BRIDGE_CHATGPT_ACCESS_TOKEN` env var → `https://chatgpt.com/backend-api/transcribe` (no model param)
-3. `~/.codex/auth.json` fallback:
-   - `OPENAI_API_KEY` field present → same as path 1
-   - `auth_mode: "chatgpt"` with `tokens.access_token` → same as path 2
-
-## Files
-
-### Rust Bridge
-
-| File | What |
-|------|------|
-| `services/rust-bridge/Cargo.toml` | Added `reqwest` (multipart, json, rustls-tls) |
-| `services/rust-bridge/src/main.rs` | `bridge/voice/transcribe` JSON-RPC method, `transcribe_voice()`, `resolve_transcription_auth()`, `resolve_codex_auth_json_path()` |
-
-### Mobile
-
-| File | What |
-|------|------|
-| `apps/mobile/app.json` | `NSMicrophoneUsageDescription` (iOS), `RECORD_AUDIO` permission (Android), `expo-audio` plugin |
-| `apps/mobile/src/api/types.ts` | `VoiceTranscribeRequest`, `VoiceTranscribeResponse` |
-| `apps/mobile/src/api/client.ts` | `transcribeVoice()` method on `HostBridgeApiClient` |
-| `apps/mobile/src/hooks/useVoiceRecorder.ts` | Recording state machine hook using `expo-audio` |
-| `apps/mobile/src/components/ChatInput.tsx` | Mic button UI with three visual states |
-| `apps/mobile/src/screens/MainScreen.tsx` | Wires hook to ChatInput |
-
-## Recording Config
-
-- Sample rate: 16,000 Hz
-- Channels: 1 (mono)
-- Format:
-  - iOS: LINEARPCM 16-bit (`audio/wav`)
-  - Android: MPEG-4 AAC (`audio/mp4`, `.m4a`)
-- Minimum duration:
-  - Mobile guard: 1 second
-  - Bridge raw payload guard: ~0.5 seconds (16KB minimum)
-- Maximum payload size:
-  - Mobile guard: 20MB
-  - Bridge guard: 100MB by default (override with `BRIDGE_MAX_VOICE_TRANSCRIPTION_BYTES`)
-
-## UI States
-
-The mic button occupies the send button slot when the composer is empty and no turn is running:
-
-| State | Icon | Style |
-|-------|------|-------|
-| Idle | `mic-outline` | Muted color |
-| Recording | `mic` | Red icon, red border |
-| Transcribing | `ActivityIndicator` | Spinner |
-
-Interaction: tap to start recording, tap again to stop and transcribe. The transcribed text is appended to the current draft.
-
-Voice input is enabled on iOS and Android. The mic button is hidden on web.
-
-## Dependencies
-
-- **`expo-audio`** — Recording via `useAudioRecorder` hook. Works in Expo Go (unlike `expo-av` which requires a dev build in SDK 55).
-- **`reqwest`** (Rust) — HTTP client for the multipart POST to OpenAI. Uses `rustls-tls` to avoid native-tls linking issues on macOS.
-
-## Error Handling
-
-- Mic permission denied → error message, stays idle
-- Recording < 1 second → "Recording too short" error, discarded
-- Audio payload < 16KB → bridge rejects with `invalid_params`
-- Audio payload > 20MB → mobile rejects before upload
-- Audio payload > bridge max bytes (default 100MB) → bridge rejects with `invalid_params`
-- No credentials found → bridge returns error code `-32002`
-- Transcription API HTTP error → bridge returns status + body in error data

package/scripts/codex-live-demo.sh

@@ -1,69 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# Demo launcher for a patched Codex TUI build that live-syncs rollout updates.
-# It replaces the old tmux restart workaround.
-
-DEFAULT_CODEX_SRC="/tmp/openai-codex-latest/codex-rs"
-CODEX_SRC="${CODEX_SRC:-$DEFAULT_CODEX_SRC}"
-PATCHED_APP_RS="${PATCHED_APP_RS:-$CODEX_SRC/tui/src/app.rs}"
-PATCHED_TUI_BIN="${PATCHED_TUI_BIN:-$CODEX_SRC/target/debug/codex-tui}"
-
-usage() {
-  cat <<'EOF'
-Usage:
-  scripts/codex-live-demo.sh [codex-tui args...]
-
-Environment overrides:
-  CODEX_SRC                  (default: /tmp/openai-codex-latest/codex-rs)
-  PATCHED_APP_RS             (default: $CODEX_SRC/tui/src/app.rs)
-  PATCHED_TUI_BIN            (default: $CODEX_SRC/target/debug/codex-tui)
-
-Notes:
-  - This starts the patched TUI binary directly.
-  - Bridge/app-server can continue using stock codex:
-      CODEX_CLI_BIN=/opt/homebrew/bin/codex
-  - If PATCHED_TUI_BIN is missing, the script will build it via:
-      cargo test -p codex-tui
-EOF
-}
-
-if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then
-  usage
-  exit 0
-fi
-
-if ! command -v cargo >/dev/null 2>&1; then
-  echo "cargo is required" >&2
-  exit 1
-fi
-
-if [[ ! -f "$PATCHED_APP_RS" ]]; then
-  echo "patched source file not found: $PATCHED_APP_RS" >&2
-  echo "set CODEX_SRC or PATCHED_APP_RS to your patched codex-rs checkout" >&2
-  exit 1
-fi
-
-if ! command -v rg >/dev/null 2>&1 || ! rg -q 'ROLLOUT_LIVE_SYNC_INTERVAL' "$PATCHED_APP_RS"; then
-  echo "warning: patch marker not found in $PATCHED_APP_RS" >&2
-  echo "continuing anyway; verify your checkout includes rollout live sync changes" >&2
-fi
-
-if [[ ! -x "$PATCHED_TUI_BIN" ]]; then
-  echo "building patched codex-tui at: $CODEX_SRC"
-  (cd "$CODEX_SRC" && cargo test -p codex-tui >/dev/null)
-fi
-
-if [[ ! -x "$PATCHED_TUI_BIN" ]]; then
-  echo "patched codex-tui binary not found after build: $PATCHED_TUI_BIN" >&2
-  exit 1
-fi
-
-echo "launching patched Codex TUI:"
-echo "  $PATCHED_TUI_BIN $*"
-echo
-echo "for bridge/app-server, keep stock codex binary configured:"
-echo "  CODEX_CLI_BIN=/opt/homebrew/bin/codex"
-echo
-
-exec "$PATCHED_TUI_BIN" "$@"

package/scripts/start-bridge-secure.sh

@@ -1,5 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd -L)"
-exec node "$SCRIPT_DIR/start-bridge-secure.js" "$@"

package/scripts/start-expo.sh

@@ -1,176 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd -L)"
-ROOT_DIR="${INIT_CWD:-$(cd "$SCRIPT_DIR/.." && pwd -L)}"
-if [[ ! -f "$ROOT_DIR/package.json" ]]; then
-  ROOT_DIR="$(cd "$SCRIPT_DIR/.." && pwd -L)"
-fi
-
-MODE="${1:-mobile}"
-SECURE_ENV_FILE="$ROOT_DIR/.env.secure"
-MOBILE_WORKSPACE="apps/mobile"
-AUTO_REPAIR="${EXPO_AUTO_REPAIR:-true}"
-CLEAR_CACHE="${EXPO_CLEAR_CACHE:-false}"
-RUNTIME_REPAIRED="false"
-EXPO_SETUP_VERBOSE="${CLAWDEX_SETUP_VERBOSE:-false}"
-
-info() { echo "info: $*"; }
-warn() { echo "warn: $*" >&2; }
-fail() { echo "error: $*" >&2; }
-
-run_quiet_command() {
-  local label="$1"
-  shift
-  local log_file=""
-
-  if [[ "$EXPO_SETUP_VERBOSE" == "true" ]]; then
-    "$@"
-    return $?
-  fi
-
-  log_file="$(mktemp "${TMPDIR:-/tmp}/clawdex-expo-setup.XXXXXX.log")"
-  if "$@" >"$log_file" 2>&1; then
-    rm -f "$log_file"
-    return 0
-  fi
-
-  fail "$label failed."
-  warn "Last 40 lines from installer output:"
-  tail -n 40 "$log_file" >&2 || true
-  warn "Full installer log: $log_file"
-  return 1
-}
-
-extract_env_value() {
-  local file="$1"
-  local key="$2"
-
-  if [[ ! -f "$file" ]]; then
-    return 0
-  fi
-
-  awk -F= -v key="$key" '$1 == key { print substr($0, index($0, "=")+1); exit }' "$file"
-}
-
-resolve_expo_host() {
-  local host=""
-
-  if [[ -f "$SECURE_ENV_FILE" ]]; then
-    host="$(extract_env_value "$SECURE_ENV_FILE" "BRIDGE_HOST" | tr -d '[:space:]')"
-    if [[ -n "$host" ]]; then
-      printf '%s' "$host"
-      return 0
-    fi
-  fi
-
-  if command -v tailscale >/dev/null 2>&1; then
-    host="$(tailscale ip -4 2>/dev/null | head -n1 | tr -d '[:space:]' || true)"
-    if [[ -n "$host" ]]; then
-      printf '%s' "$host"
-      return 0
-    fi
-  fi
-
-  echo "error: cannot resolve Expo host IP for QR." >&2
-  echo "Run: npm run setup:wizard  (or npm run secure:setup) first." >&2
-  return 1
-}
-
-has_expo_dependency() {
-  [[ -d "$ROOT_DIR/node_modules/expo" ]] || [[ -d "$ROOT_DIR/$MOBILE_WORKSPACE/node_modules/expo" ]]
-}
-
-has_typescript_dependency() {
-  node -e "require.resolve('typescript/package.json', { paths: ['$ROOT_DIR/$MOBILE_WORKSPACE', '$ROOT_DIR'] })" >/dev/null 2>&1
-}
-
-has_mobile_react_native_runtime() {
-  local root_touchable="$ROOT_DIR/node_modules/react-native/Libraries/Components/Touchable/BoundingDimensions.js"
-  local workspace_touchable="$ROOT_DIR/$MOBILE_WORKSPACE/node_modules/react-native/Libraries/Components/Touchable/BoundingDimensions.js"
-  local root_devtools="$ROOT_DIR/node_modules/react-native/src/private/devsupport/rndevtools/specs/NativeReactDevToolsRuntimeSettingsModule.js"
-  local workspace_devtools="$ROOT_DIR/$MOBILE_WORKSPACE/node_modules/react-native/src/private/devsupport/rndevtools/specs/NativeReactDevToolsRuntimeSettingsModule.js"
-
-  local touchable_ok="false"
-  local devtools_ok="false"
-
-  if [[ -f "$root_touchable" ]] || [[ -f "$workspace_touchable" ]]; then
-    touchable_ok="true"
-  fi
-
-  if [[ -f "$root_devtools" ]] || [[ -f "$workspace_devtools" ]]; then
-    devtools_ok="true"
-  fi
-
-  [[ "$touchable_ok" == "true" ]] && [[ "$devtools_ok" == "true" ]]
-}
-
-install_mobile_dependencies() {
-  info "Installing project dependencies (one-time setup for Expo runtime)..."
-  run_quiet_command "Project dependency install" bash -lc "cd \"$ROOT_DIR\" && npm install --include=dev && npm dedupe"
-}
-
-repair_mobile_runtime_dependencies() {
-  warn "Detected incomplete React Native runtime. Running dependency repair..."
-  run_quiet_command "React Native dependency repair" bash -lc "cd \"$ROOT_DIR\" && npm install --include=dev --force && npm install --include=dev --force -w \"$MOBILE_WORKSPACE\" && npm dedupe"
-  RUNTIME_REPAIRED="true"
-}
-
-ensure_mobile_runtime() {
-  if has_expo_dependency && has_typescript_dependency && has_mobile_react_native_runtime; then
-    return 0
-  fi
-
-  install_mobile_dependencies
-
-  if has_expo_dependency && has_typescript_dependency && has_mobile_react_native_runtime; then
-    return 0
-  fi
-
-  if [[ "$AUTO_REPAIR" != "true" ]]; then
-    fail "mobile runtime is incomplete. Re-run with EXPO_AUTO_REPAIR=true or run npm install --include=dev --force"
-    return 1
-  fi
-
-  repair_mobile_runtime_dependencies
-
-  if ! has_expo_dependency || ! has_typescript_dependency || ! has_mobile_react_native_runtime; then
-    fail "mobile runtime is still incomplete after repair."
-    fail "Try: npm install --include=dev --force && npm install --include=dev --force -w $MOBILE_WORKSPACE"
-    return 1
-  fi
-}
-
-run_expo() {
-  local -a cmd
-  local -a extra_args=(--host lan)
-
-  if [[ "$CLEAR_CACHE" == "true" ]] || [[ "$RUNTIME_REPAIRED" == "true" ]]; then
-    extra_args+=(--clear)
-  fi
-
-  case "$MODE" in
-    mobile)
-      cmd=(npm run -w "$MOBILE_WORKSPACE" start -- "${extra_args[@]}")
-      ;;
-    ios)
-      cmd=(npm run -w "$MOBILE_WORKSPACE" ios -- "${extra_args[@]}")
-      ;;
-    android)
-      cmd=(npm run -w "$MOBILE_WORKSPACE" android -- "${extra_args[@]}")
-      ;;
-    *)
-      echo "error: unknown mode '$MODE' (expected: mobile|ios|android)" >&2
-      exit 1
-      ;;
-  esac
-
-  "${cmd[@]}"
-}
-
-cd "$ROOT_DIR"
-ensure_mobile_runtime
-EXPO_HOST="$(resolve_expo_host)"
-export REACT_NATIVE_PACKAGER_HOSTNAME="$EXPO_HOST"
-echo "Starting Expo with host: $EXPO_HOST (QR will use this IP)"
-run_expo

package/scripts/sync-versions.js

@@ -1,63 +0,0 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const path = require('path');
-
-const rootDir = path.resolve(__dirname, '..');
-
-function readJson(relativePath) {
-  const fullPath = path.join(rootDir, relativePath);
-  return JSON.parse(fs.readFileSync(fullPath, 'utf8'));
-}
-
-function writeJson(relativePath, value) {
-  const fullPath = path.join(rootDir, relativePath);
-  fs.writeFileSync(fullPath, `${JSON.stringify(value, null, 2)}\n`);
-}
-
-function updateCargoTomlVersion(relativePath, version) {
-  const fullPath = path.join(rootDir, relativePath);
-  const current = fs.readFileSync(fullPath, 'utf8');
-  const next = current.replace(/^version\s*=\s*".*"$/m, `version = "${version}"`);
-  if (next === current) {
-    throw new Error(`Could not find Cargo.toml version field in ${relativePath}`);
-  }
-  fs.writeFileSync(fullPath, next);
-}
-
-function syncVersions() {
-  const rootPkg = readJson('package.json');
-  const version = rootPkg.version;
-  if (typeof version !== 'string' || version.trim().length === 0) {
-    throw new Error('Root package.json version is empty.');
-  }
-
-  const mobilePkgPath = 'apps/mobile/package.json';
-  const mobilePkg = readJson(mobilePkgPath);
-  mobilePkg.version = version;
-  writeJson(mobilePkgPath, mobilePkg);
-
-  const bridgePkgPath = 'services/rust-bridge/package.json';
-  const bridgePkg = readJson(bridgePkgPath);
-  bridgePkg.version = version;
-  writeJson(bridgePkgPath, bridgePkg);
-
-  updateCargoTomlVersion('services/rust-bridge/Cargo.toml', version);
-
-  const appJsonPath = 'apps/mobile/app.json';
-  const appConfig = readJson(appJsonPath);
-  if (!appConfig.expo || typeof appConfig.expo !== 'object') {
-    throw new Error('apps/mobile/app.json is missing expo config.');
-  }
-  appConfig.expo.version = version;
-  writeJson(appJsonPath, appConfig);
-
-  console.log(`Synchronized app and bridge versions to ${version}`);
-}
-
-try {
-  syncVersions();
-} catch (error) {
-  console.error(String(error instanceof Error ? error.message : error));
-  process.exit(1);
-}