Insist on empirical verification and full CI closure before declaring a fix done

The user demands rigorous, adversarial correctness review of CI/infra fixes (not style-only), requiring empirical reproduction of edge cases in an isolated scratch directory (e.g. /tmp/opencode) with throwaway test data—never touching tracked files—before merging. After merging, the user follows up explicitly to confirm the actual CI run succeeded end-to-end (not just 'job passed' but that the specific mechanism, e.g. notarization, actually executed and succeeded for all variants/architectures). The user also enforces splitting unrelated changes (e.g. dependency version bumps) into separate PRs, keeping fix PRs narrowly scoped. When assistant proposes optional/secondary improvements, the user expects them raised explicitly for a yes/no decision rather than bundled in. Always verify real production behavior (log output, not just exit codes) and keep changes atomic and reviewed with skepticism.