# `.dockerignore` is generated from `.gitignore` by `mise run gen:dockerignore`.
# After editing `.gitignore`, regenerate it and commit both, or the dockerignore-check task fails on drift.
.claude/
*.wasm
*.onnx
target/
.DS_Store
services/ws-wasm-agent/pkg/
services/ws-modules/pywasm1/pkg/
services/ws-modules/rdata1/pkg/webr/
services/ws-modules/rcomm1/pkg/webr/
services/ws-modules/rmath1/pkg/webr/
services/ws-modules/js-data1/pkg/et_ws_js_data1.js
services/ws-server/static/models/
.zig-cache/
zig-out/
*.o
*.pem
mprocs.log
__pycache__/
.pytest_cache/
.python-version
node_modules/
.venv/
# .NET build output.
# `obj/` is safe globally (nothing tracked is named obj/), but `bin/` is scoped to the module so it never
# matches a Rust crate's `src/bin/` (e.g. utilities/int-gen/src/bin/).
obj/
services/ws-modules/dotnet-data1/bin/
# Gradle project caches and build output plus the Kotlin session dir, all regenerated by any Gradle run.
.gradle/
.kotlin/
services/ws-modules/kotlin-data1/build/
services/ws-modules/kotlin-math1/build/
# Coverage-report artifacts produced by the coverage workflow, uploaded to Codecov and never committed.
# Covers cargo-llvm-cov's lcov, pytest-cov's Cobertura xml, and pytest-cov's .coverage data file.
/lcov.info
coverage-python.xml
.coverage
# minicov/llvm raw profiles dropped by instrumented binaries run during coverage builds.
*.profraw
# Editor dir, tool caches, and the ws-server's runtime file storage.
# The .vscode dir is ignored except its shared recommended-extensions list (negated below).
.vscode/*
!.vscode/extensions.json
.ruff_cache/
.ryl_cache/
.lycheecache
# Dart pub tool dir, regenerated by `dart pub get`; one global rule for the whole workspace (root + members).
**/.dart_tool/
services/ws-server/storage/
# One-off Markdown an agent writes on request, such as an email draft or notes, which is never committed.
*.local.md
# Lock files a generated scenario leaves behind when it is run.
# `lockfile = true` makes mise write one beside whichever config it resolved tools for, so running a scenario
# drops `mise.lock` into that scenario's output directory. It is a by-product of running the deployment rather
# than part of it: `regen-verification` never writes one, the drift check never reads one, and what it pins is
# whatever the machine that ran it happened to resolve. One rule here rather than a `.gitignore` generated into
# each scenario, so a scenario added later is covered without anything having to be written into it.
verification/**/*.lock
# The npm dependency graphs `mise lock` records beside that lockfile, a by-product for the same reason.
verification/**/.mise/locks/
# No rule for the per-scenario credential file, deliberately.
# Under verification/ it is committed like every other generated artifact: the password is derived from an
# input this repository already carries, so the file reproduces from public material rather than keeping a
# secret, and the drift check has to be able to read it. A deployment generated anywhere else gets its own
# `.gitignore` written beside it by `et-cli`, which is what keeps a real credential out of a real repository.