.gitignore

# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
/.pnp
.pnp.js
.yarn/install-state.gz

# testing
/coverage
/.test-binary
/.test-npx

# next.js
/.next/
/out/

# production
/build
/dist

# misc
.DS_Store
*.pem

# debug
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# local env files
.env
.env.*

# vercel
.vercel

# typescript
*.tsbuildinfo
next-env.d.ts

# claude
.claude/*
!.claude/settings.json

# cursor
.cursor/*
!.cursor/hooks.json

# opencode
.opencode/*
!.opencode/opencode.json
!.opencode/plugins
.opencode/plugins/*
!.opencode/plugins/failproofai.mjs

# pi
.pi/*
!.pi/settings.json

# custom hooks loader temp files
*.__failproofai_tmp__.*

# package manager lockfiles (bun.lock is tracked; bun.lockb is binary).
# This rule exists to stop an `npm install` in the ROOT project producing a
# second, divergent lockfile beside bun.lock. `sdk/typescript` is a separate npm
# package that is installed with npm and nothing else, so its lockfile is real:
# its CI job runs `npm ci`, which refuses to run without one, and the release
# workflow's whole point is installing exactly what CI installed.
package-lock.json
!sdk/typescript/package-lock.json

# translation cache
.translation-cache.json

# build artifacts from test scripts
*.tgz
/failproofai-local
packages/*/bin/
packages/*/assets/
.gstack/

# closed-source platform (cloned separately)
/platform

# FailproofAI Cloud reference source (cloned separately for docs research)
/agenteye

# rust
/target

# WSL/Windows alternate data streams
*:Zone.Identifier
.dev.log

# Local monitoring scratch files (CI run watchers etc.)
.monitor-*.sh
.monitor-*.log

# Local Mintlify dev server log (transient)
mint-dev.log

# superpowers brainstorm session scratch
.superpowers/

# transient commit-message scratch files
COMMIT_MSG.tmp

# integration-suite: decoded credentials during a local/CI run (the suite
# deletes both on exit, but a crashed run could leave them stageable)
/tokens/
/canary.env
/integration-suite-state.json
/cli-integration-state.json

# Compressed failproofaid binaries — produced by
# .github/workflows/build-daemon.yml (or a local `cargo build --release` +
# gzip for manual Docker verification), uploaded as release assets, never
# committed. Same for npm-pack tarballs produced anywhere in the repo during
# local packaging tests.
/failproofaid-*.gz
*.tgz

# Release-pipeline scratch. The publish workflow keeps both of these in
# RUNNER_TEMP — a build sweeps anything at the project root into
# .next/standalone — but a manual run (`gh release download --dir
# release-assets`, `build-daemon-packages.mjs --staging .daemon-packages`)
# lands them here.
/.daemon-packages/
/release-assets/

# Sandbox HOME directories from local/Docker smoke tests (see CLAUDE.md's
# testing protocol) leak into the repo when HOME points at a relative path
# instead of a real temp directory. A real one holds bun's install cache and
# this CLI's own runtime state, never source — and the parent directory name
# is random each time it happens (587d0567's committed ino.ujh3/ was one),
# so match the tell-tale contents anywhere in the tree rather than a name.
# The repo's own dogfood `/.failproofai/` (policies-config.json, policies/)
# has none of these subpaths, so it is unaffected.
**/.bun/install/cache/
**/.failproofai/bin/
**/.failproofai/run/
**/.failproofai/state/

# The dogfood enable/disable set is now local to each contributor. It was
# committed, which meant every local change to which policies run on YOUR
# machine — turning a noisy one off while you work on it, or switching the
# Stop gates off to get a long-running task finished — showed up as a staged
# change to everyone else's enforcement. The policies themselves stay tracked
# in `.failproofai/policies/`; only which of them are enabled here is yours.
# Untrack it once with: git rm --cached .failproofai/policies-config.json
/.failproofai/policies-config.json

# The dogfood custom policies, for the same reason: they are the ones that gate
# a turn (a Stop gate cannot tell "a subagent owns the working tree right now"
# from "you forgot to commit"), so switching one off while you work should not
# be a change to anybody else's repo. Same caveat as above — these are tracked,
# so this rule only takes effect after:
#   git rm --cached .failproofai/policies/review-policies.mjs .failproofai/policies/workflow-policies.mjs
/.failproofai/policies/*.mjs

# Python build and test artefacts from fp-cloud-cli/. `/dist` above is the Next.js one at
# the repo root; fp-cloud-cli builds into its own nested dist/, which that rule does not
# match, so it needs naming separately.
fp-cloud-cli/dist/
fp-cloud-cli/.venv/
fp-cloud-cli/.pytest_cache/
.ruff_cache/
sdk/python/dist/
sdk/python/.venv/
sdk/python/.pytest_cache/
**/__pycache__/
*.py[cod]
*.egg-info/

# blog drafts (local, not for commit yet)
/blog/

# Generated by `bun run build:pack` — the builtins emitted as a policy pack.
policy-pack/

# `failproofai publish` writes its three release assets here by default.
# They are uploaded, not source — and a publisher running the command inside
# their own repo should not find them staged.
dist-pack/