Package-scoped Bun validation and acceptance gates

For OpenCode, run bun typecheck from each affected package; never invoke tsc directly or run tests from the repository root. Run only requested commands, in exact scope and order, from owning packages; parallelize independent commands with adequate timeouts. Validation-only work must not edit or format files, install dependencies, generate artifacts, mutate VCS, start services, use recall, or add prohibited or unrequested checks. Report each command’s working directory, exit code, duration, test/file/assertion pass/fail/skip totals, diagnostics, warnings, expected fixture logs, aggregate totals, and explicit skips. When requested, prove pre/post Git SHA and porcelain status are identical. Before advancing a candidate, require substantive independent correctness/security review of the unchanged tree; empty reviews are invalid—resume or retry the existing reviewer under an evidence-or-blocker contract instead of launching duplicate or overlapping agents, including after infrastructure restarts.