Validation

TraceMap is meant to be checked, not trusted on vibes.

The project uses unit tests, sample repositories, pinned smoke checks, generated-output guards, and artifact acceptance criteria to keep static evidence deterministic.

Local checks

Run the relevant language checks before finishing analyzer work.

Site-only changes usually need the site build and browser preview checks.

dotnet test src/dotnet/TraceMap.sln
cd src/typescript && npm run check
JAVA_HOME=/opt/homebrew/opt/openjdk@21/libexec/openjdk.jdk/Contents/Home gradle -p src/jvm test
python3 -m pytest src/python/tests

cd site && npm run validate

Acceptance

Validation includes outputs, not just exit codes.

Artifacts existScans produce manifest, facts, SQLite, report, and logs.

Coverage is labeledReduced analysis stays visible in reports and reducer outcomes.

No raw snippets by defaultOutputs store spans and hashes unless explicitly configured otherwise.

Deterministic rowsJSON, Markdown, and SQLite outputs should remain stable for repeatable inputs.

Swift real-world smokeThe Swift smoke proof explains pinned public API-client samples and sanitized summaries for static evidence discovery.

Deploy auditThe static deploy audit checks public routes, sitemap, robots, and discovery files before publish.

Public demo sharing has its own checklist.

The public demo runbook uses this validation page as a gate before public demo summaries are shared; it does not replace validation or generated-output guards.

Legacy validation has stricter publication rules.

The legacy validation concept keeps local sample paths, private repository names, raw remotes, source snippets, SQL, config values, and raw generated artifacts hidden until a redacted summary passes pre-publish checks.