# Logs

logs

*.log

npm-debug.log*

yarn-debug.log*

yarn-error.log*

lerna-debug.log*

# database

*.sqlite

# package-json

package-json.lock

# bun deploy file

node_modules.bun

# Diagnostic reports (https://nodejs.org/api/report.html)

report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json

# Runtime data

pids

*.pid

*.seed

*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover

lib-cov

# Coverage directory used by tools like istanbul

coverage

*.lcov

# nyc test coverage

.nyc_output

# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)

.grunt

# Bower dependency directory (https://bower.io/)

bower_components

# node-waf configuration

.lock-wscript

# Compiled binary addons (https://nodejs.org/api/addons.html)

build/Release

# Dependency directories

node_modules/

jspm_packages/

# TypeScript v1 declaration files

typings/

# TypeScript cache

*.tsbuildinfo

# Optional npm cache directory

.npm

# Optional eslint cache

.eslintcache

# Microbundle cache

.rpt2_cache/

.rts2_cache_cjs/

.rts2_cache_es/

.rts2_cache_umd/

# Optional REPL history

.node_repl_history

# Output of 'npm pack'

*.tgz

# Yarn Integrity file

.yarn-integrity

# dotenv environment variables file

.env

.env.*

!.env.example

# Credential / key material — kept in lockstep with the secret-hygiene gate's KEY_EXTENSIONS +

# SECRET_BASENAMES (tooling/repo-checks) so the working-tree defense matches what CI enforces.

*.pem

*.p12

*.key

*.pfx

*.jks

*.keystore

id_rsa

id_dsa

id_ecdsa

id_ed25519

credentials.json

# parcel-bundler cache (https://parceljs.org/)

.cache

# Next.js build output

.next

# Nuxt.js build / generate output

.nuxt

dist

# Gatsby files

.cache/

# Comment in the public line in if your project uses Gatsby and *not* Next.js

# https://nextjs.org/blog/next-9-1#public-directory-support

# public

# vuepress build output

.vuepress/dist

# Serverless directories

.serverless/

# FuseBox cache

.fusebox/

# DynamoDB Local files

.dynamodb/

# TernJS port file

.tern-port

# Claude Code agent/harness state (skills, workflows, settings) — machine-local, not repo source.

.claude/

# Vercel CLI link state. `vercel link` / `vercel pull` write project.json (the team_*/prj_* API IDs)

# here; CI passes those as secrets instead, so a checked-in copy would only ever be one developer's.

# The pulled env file already matches the .env.* rule above.

.vercel/

# Local benchmark outputs are transient (per-run raw trees + the local run index). The PUBLISHED

# dataset lives under data/dataset/ and is committed by the promote step, so it is NOT ignored.

data/raw/

data/runs/

# The local run index that bench-suite maintains beside them. It sits at the root of the data/ tree

# (a Run index always does — see packages/schema runDocumentPath), so it needs its own entry rather

# than riding the data/runs/ line above.

data/index.json

# Where the in-sandbox producer writes (results_dir in lib/bench.sh): running any

# `mise run benchmark:**` leaf on a dev machine leaves artifacts here. They belong to the sandbox

# that produced them — the harness collects them out of the sandbox and the promote step publishes

# the normalized result — so a local copy is never the thing to commit.

benchmark-results/

# Generated from packages/templates/src/pins.ts by build.sh / the publish workflow (the

# e2b CLI requires this file on disk; the TypeScript config is its single source of truth).

packages/templates/images/e2b/e2b.toml

# Generated per-bake by `bake` (apps/cli/src/lib/bake/e2b.ts): the committed e2b/Dockerfile with its

# base pinned to the candidate/version registry ref, since e2b CLI 2.x can't inject a build-arg.

packages/templates/images/e2b/Dockerfile.generated

# macOS Finder litter - never content, and the artifact gate compares docs/figures exactly.

.DS_Store