#!/usr/bin/env bash
# token-tracker installer. Usage:
#   curl -fsSL <app>/install.sh | TT_TOKEN=<device-token> bash
set -eo pipefail

ORIGIN="https://www.tokken.site"
DIR="$HOME/.token-tracker"
CONFIG="$DIR/config.env"
COLLECTOR="$DIR/collect.sh"

if [ -z "$TT_TOKEN" ]; then
  echo "TT_TOKEN env var is required — copy the command from your Devices page." >&2
  exit 1
fi

mkdir -p "$DIR"

cat > "$CONFIG" <<EOF
TT_TOKEN=$TT_TOKEN
TT_INGEST_URL=$ORIGIN/api/ingest
TT_TOOLS="claude:claude-code"
TT_CCUSAGE_SPEC="ccusage@20.0.17"
TT_INTERVAL=300
EOF
chmod 600 "$CONFIG"

echo "token-tracker: downloading collector..."
curl -fsSL "$ORIGIN/collect.sh" -o "$COLLECTOR"
chmod +x "$COLLECTOR"

# Source the collector to reuse its tt_apply_schedule — one definition of the
# launchd/cron schedule, shared by the installer and by the collector's own
# server-driven re-scheduling, so the two can never drift apart. Sourcing does not
# run a sync (the collector guards its main body on BASH_SOURCE).
export TT_CONFIG="$CONFIG"
. "$COLLECTOR"
tt_apply_schedule 300 "$CONFIG"
echo "token-tracker: scheduled every 300s (+ on login/reboot)."

echo "token-tracker: running first sync..."
TT_CONFIG="$CONFIG" /bin/bash "$COLLECTOR" || true
echo "token-tracker: installed. Your data will appear on the dashboard shortly."