itsol-qa-handoff

name	itsol-qa-handoff
description	QA handoff: test notes, acceptance evidence, bug reports, release readiness.

ITSOL QA Handoff

Make QA testable: provide scope, data, environments, risks, scenarios, and a clear pass/fail outcome.

Process

1. Confirm QA has the story, acceptance criteria, PR, tech notes, environment, data, roles, accounts, config, and known limitations.
2. Build scenarios from risk: happy path, negative path, edge cases, regression, permissions, data boundaries, integrations, retries, and security smoke.
3. Use test-design techniques where useful: equivalence classes, boundary values, decision tables, state transitions, and exploratory testing.
4. For bugs, require environment, reproducible steps, actual versus expected result, data, attachments, impact, severity, priority, and release-blocking status.
5. Select the real interaction surface: agent-browser for web UI, supported CDP/browser automation for Electron, interactive command execution for CLI, contract/integration/security tests for API/backend, device/runtime checks for mobile, integrity/migration/rollback for data, and readiness/observability/rollback for infrastructure.
6. In Initiative Delivery, use the harness-native QA plan/verdict capability. Execute every required packet, bind the verdict to the implementation fingerprint, and never infer PASS from a planned check or agent completion label.
7. Route failed QA to implementation-fix, plan-revision, or user-decision. After remediation, rerun applicable plan review and code review and then fresh QA. Do not close the phase until QA passes.
8. For release readiness, check QA result, regression, support notes, monitoring, feature flags, rollback, and production verification needs.

Execution Policy

After resolving itsol-workflow-mode, load itsol-execution-policy, resolve the complete sibling execution state and observable done_when, and preserve both contracts through plans, task context, compaction, delegation, continuation, review, and handoff. Resource policy never changes workflow authority. Do not set maxTurns; do not accept agent termination or a completed label without validating evidence.

Read references/guide.md first; it is a routing index for focused reference files. Then read only the sector files relevant to the current situation.