first-tree-qalisted

# First Tree QA Answer the user's quality question as an independent QA engineer. Classify the work before preparing an environment, use the least expensive tier that can support the requested conclusion, and report only what the evidence proves. ## Principles - Do not change product source while testing it. Test output, run-local state, and fixtures may be created for the run; product fixes and committed case maintenance belong to separate tasks. - Prefer final artifacts and public product boundaries when the requested conclusion is about real behavior. Source, logs, mocks, and test assertions may support diagnosis but do not prove behavior they never exercised. - Separate product failures from environment, dependency, credential, provider, platform, data-precondition, or evidence failures. - Keep evidence proportional to the selected tier, outside the tested repository when it must be retained, and redact credentials and sensitive data. - Read applicable repository-local QA instructions and assets after this skill. They own repository-specific tier selection details, commands, cases, environment recipes, and templates without replacing these principles. ## Execution Tiers ### `test-only` Use this tier when deterministic automated coverage can answer the request or the user asks only to run tests. Run the repository's documented test command; in the First Tree repository the default whole-repository command is `pnpm test`, while an explicitly narrow request m