/target
# Cargo.lock IS tracked: melange-cli ships a binary, so the lockfile is committed
# for reproducible builds and a stable MSRV floor. (A library would gitignore it.)
# The nightly-only fuzz crate is workspace-excluded; its separate lock stays local.
crates/melange-solver/fuzz/Cargo.lock
*.swp
*.swo
*~
.DS_Store
.venv/
__pycache__/
*.pyc
.claude/
test.rs
test_output.txt
out

# Audio files
*.wav

# DAW peak cache (Reaper)
peaks/

# ngspice source distribution
ngspice*/
ngspice_*
# ...but keep the checked-in ngspice golden-reference regen kit (the ngspice_*
# rule above would otherwise eat this directory and break golden reproducibility).
!crates/melange-solver/tests/golden/ngspice_ref/

# Package archives
*.tar.gz
*.tar.xz
*.dsc

# Generated reports
*.html

# Archived/disabled files (git history preserves them)
*.archived
*.disabled
golden-baselines/
# `golden-harness compare` writes its report to the CWD by default, which is
# the repo root — an untracked build artifact one `git add -A` away from being
# committed.
golden-compare-report*.json

# Local, machine-specific melange context (ecosystem, inter-agent mail) — not public
CLAUDE.local.md

# Local, untracked working docs (design notes, briefs, research) — not public
local-docs/

# Agent scratch that must NOT reach a public repo.
# AGENTS.md is DERIVED from the maintainer's account-level ~/.claude/CLAUDE.md —
# personal working preferences, not project documentation. It was untracked but
# un-ignored, so a single `git add -A` during release prep would have published
# it. If a public agent guide is ever wanted, write one deliberately rather than
# committing this file.
AGENTS.md
# Chart/scratch output from another agent session.
tools/viz/
