.vercelignore

# Vercel deploy upload exclusions.
#
# Mirrors vercel.json's ignoreCommand path list (the dirs whose changes
# don't trigger a deploy) so they're also excluded from the upload when
# a deploy IS triggered. ignoreCommand alone only gates deploy
# triggering — it does not filter the build context. Without this file,
# every deploy uploads ~hundreds of MB of Python venvs, Playwright +
# Chromium binaries, and ML plots that no Vercel function can use.
#
# IMPORTANT: All top-level directory patterns are anchored with a
# leading "/" so they match the repo root only. Without anchoring,
# gitignore-style globs like "ml/" match at any depth — which would
# also exclude api/ml/ (a real Vercel endpoint folder) and break the
# build. "/ml/" matches the root ml/ directory only.
#
# When adding a new top-level directory that Vercel shouldn't touch,
# add it here (with a leading "/") AND to vercel.json's ignoreCommand
# path list to keep the two aligned.

# Railway-deployed services — never run on Vercel
/sidecar/
/uw-stream/
/periscope-scraper/
/daemon/

# Python ML pipeline + research — local + GH Actions only.
# Anchored — api/ml/ contains real Vercel endpoint handlers and must
# NOT be excluded.
/ml/

# Pine Script (TradingView) — not deployed anywhere
/pine/

# Operational scripts (backfills, probes, audits) — local-only.
# write-build-info.mjs is the one exception: it runs during Vercel's
# build to inject the commit SHA into api/_lib/build-info.ts, so it
# MUST be uploaded. Exclude everything else in scripts/.
/scripts/*
!/scripts/write-build-info.mjs

# Documentation — not needed at runtime
/docs/
/*.md

# E2E + Playwright artifacts — local + CI only
/e2e/
/playwright-report/
/test-results/

# Python build artifacts that may exist anywhere in the repo
**/__pycache__/
**/.venv/
**/.pytest_cache/

# Claude Code plugin installs — ~800 MB of locally-installed skills,
# resources, and references that don't belong on Vercel. Mirrors the
# pattern in .gitignore so `vercel deploy` from the CLI ships only
# what git would ship: the 4 committed SKILL.md files plus the
# periscope/references/** tree (loaded via `includeFiles` for the
# api/periscope-auto-playbook.ts function).
#
# Git-triggered deploys never saw this bloat — Vercel clones the
# tracked git tree directly. CLI deploys upload the local working
# tree and need this filter explicitly.
/.claude/*
!/.claude/skills/
/.claude/skills/*
!/.claude/skills/charm-pressure/
!/.claude/skills/delta-pressure/
!/.claude/skills/gamma/
!/.claude/skills/periscope/
/.claude/skills/charm-pressure/*
/.claude/skills/delta-pressure/*
/.claude/skills/gamma/*
/.claude/skills/periscope/*
!/.claude/skills/charm-pressure/SKILL.md
!/.claude/skills/delta-pressure/SKILL.md
!/.claude/skills/gamma/SKILL.md
!/.claude/skills/periscope/SKILL.md
!/.claude/skills/periscope/references/
!/.claude/skills/periscope/references/**

# Test coverage reports — local + CI only
/coverage/

# Local frontend build output — Vercel generates this fresh from src/
/dist/