Evidence-driven repository, testing, and review workflow

Use the established branch/PR workflow and review code before committing. For every bug fix, add a deterministic regression that exercises the real production precondition, prove it fails on the base, passes with the fix, and fails when the guard is removed. For nontrivial changes, perform separate correctness and security reviews with exact current file:line evidence. Freeze the candidate identity and hashes before exhaustive validation; review it read-only without network, services, formatting, or VCS mutation. Run focused checks, the exact aggregate gate, fresh bundle verification, and required lint/typecheck/format checks with recorded exit codes; shard only if the aggregate result is inconclusive. In .jj repositories use noninteractive jj mutations, verify jj st/log, and treat conflicts as recorded state. Resolve findings in a new child and refreeze.