# Binaries
*.exe
*.exe~
*.dll
*.so
*.dylib

# Test binary, built with `go test -c`
*.test

# Output of the go coverage tool
*.out

# Go workspace file. Deliberately NOT committed: a workspace would put
# test/proto-validate into the product's MVS build list, so the shipped binary's
# dependency set could be moved by a bump to a live-test helper's manifest. The
# module is reached by `cd`-ing into it instead (see AGENTS.md).
go.work
go.work.sum

# Dependency directories
vendor/

# Build output
bin/
dist/

# IDE
.idea/
.vscode/
*.swp
*.swo
*~

# OS
.DS_Store
Thumbs.db

# Environment
.env
.env.local

# .claude
.claude/

# Capability development workflow artifacts (agent outputs, process records)
.capability-development/

# Live test artifacts
test/.live-test-config
test/.results/
test/.*.pid
test/.*.pids
test/.*.log
test/rest-api/rest-api
test/soap-service/soap-service
test/grpc-server/grpc-server
test/concat-spa/concat-spa
test/forms-target/forms-target
# Unlike the entries above, no script builds this one: test/proto-validate's only
# consumer is `go run`, which writes to the build cache. It is listed because
# proto-validate is its own module, so `cd test/proto-validate && go build` is a
# natural thing to do by hand — not because a build step produces it.
test/proto-validate/proto-validate
test/graphql-server/node_modules/
test/spec-validators/node_modules/

# go build artifacts when run at repo root
/vespasian
/proto-validate
