> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oynk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Operations runbook

> Commands for migrations, synchronization, audits, targeted repairs, and validation.

## Routine commands

```bash theme={"dark"}
docker compose up -d postgres
pnpm db:migrate
pnpm dev
pnpm sync
pnpm audit:bsc
pnpm audit:solana
```

The API syncs on startup when `SYNC_ON_START=true` and schedules later runs. `pnpm sync` performs a one-time run and closes the database pool.

## Targeted repair

Inspect before changing a cursor:

```bash theme={"dark"}
pnpm sync:contract -- --chain BSC --wallet <wallet> --contract <address> --dry-run
pnpm sync:contract -- --chain SOLANA --wallet <wallet> --contract <mint> --source-account <address> --dry-run
```

Only add `--reset` after verifying the chain, network, wallet, asset identity, replay boundary, and database backup. Resetting checkpoints can be expensive and can expose RPC limitations, although deterministic identities should prevent duplicate records.

## API health and failures

```bash theme={"dark"}
curl http://localhost:4000/health/live
curl http://localhost:4000/health/ready
curl http://localhost:4000/api/sync/status
curl http://localhost:4000/api/sync/failures
```

Run/failure endpoints reveal operational state and must be restricted at the deployment boundary. A production failure reprocessor is not implemented; never delete unresolved records to make monitoring appear healthy.

## Manual sync

```bash theme={"dark"}
curl -X POST http://localhost:4000/api/dashboard/sync \
  -H "x-admin-api-key: $OYNK_ADMIN_API_KEY"
```

The endpoint returns `202` with a run ID, `409` if work is already running, and `429` after excessive requests. Keep the admin key out of shell history and logs; the example variable name is intentionally not a repository configuration variable.

## Release validation

```bash theme={"dark"}
pnpm typecheck
pnpm test
pnpm build
git diff --check
```