software-validationlisted

# Software Validation Establish what the repository already treats as valid, run the smallest applicable check surface safely, and report both evidence and gaps. A green command proves only what that command observes. ## Core Contract - Discover commands from repository evidence; never substitute ecosystem habit for an established command. - Do not silently install or upgrade a runtime, SDK, compiler, dependency, linter, formatter, test runner, documentation generator, or package manager. - Preserve unrelated working state. Treat every check as potentially write-producing and report validation-generated files or diffs. - Execute each planned command once. A single transparent sequential recovery attempt is allowed only after a parallel workspace race is stopped and cleanup is confirmed; report both attempts. - Give every applicable category an explicit terminal state only after its process tree has ended; keep skipped, still-running, or missing evidence visible. ## Workflow 1. Read scoped `AGENTS.md`, `CLAUDE.md`, repository instructions, and the user's requested validation boundary. Resolve the canonical repository root, relevant package or workspace, changed contract, and current dirty and staged state before running anything. 2. Read [Command discovery](references/command-discovery.md). Build a deduplicated plan from instructions, CI, task runners, manifests, contributor docs, package conventions, and recent successful CI usage, in that or