kandev/docs/plans/native-code-review-status-atomicity/plan.md

created, status, requirements, system_design, legacy_specs

created	status	requirements	system_design	legacy_specs
2026-09-14	completed	REQ-AGENTS-NATIVE-CODE-REVIEW-001	../../specs/agents/system-design/native-code-review-status-atomicity.md

Implementation plan: Native review finding status atomicity

Review finding status changes must be safe when more than one client updates the same finding at the same time. The repository owns one atomic transition that reads the stored status, derives resolved_at, and returns the stored finding. The service keeps validation and publishes the existing update event after the transition succeeds.

Work order

• Make review finding status transitions atomic

Scope

• Keep the existing review finding and WebSocket contracts.
• Use one repository transition for status and timestamp updates.
• Cover concurrent SQLite writers and an environment-gated PostgreSQL multi-connection path.