# Cargo.lock is deliberately NOT ignored here. This is its own cargo workspace
# (the root manifest excludes `fuzz`), so no Dependabot entry reaches it;
# tracking the lockfile is what makes divergence from the workspace detectable
# at all, and what gives `.clusterfuzzlite/build.sh` something to assert
# `cargo metadata --locked` against. `just check-fuzz-lock-parity` gates it on
# every PR — see README.md and
# docs/ADR/0011-fuzz-lockfile-workspace-parity.md.
target/
artifacts/
coverage/

# libfuzzer-generated mutation files inside corpus subdirectories.
# Mutations are SHA-1-named (40 lowercase hex chars, no extension).
# Identify them by name shape rather than by extension whitelist so
# that human-curated seeds with arbitrary names (e.g. Task 6's
# 'utf8-ascii') are tracked correctly. The pattern below repeats
# [0-9a-f] forty times because gitignore has no count quantifier.
corpus/*/[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]
