Loop-lane convention: record the fresh-context review boundary as an explicit decision

[kyle-sexton]

Context

Independent fresh-context review fires on the C3 exception path and non-trivial conflict resolutions; there is no routine per-cycle independent review of ordinary loop output — the common path relies on deterministic gates. Defensible and probably correct, but it reads as an unexamined boundary. Companion blog corroborates the principle ("a reviewer with fresh context is less biased"). One paragraph in docs/conventions/loop-lane/README.md §3 making it an explicit decision. (Item 11, Tier 3, CORROBORATED. Source: action-items.md item 11)

Acceptance criteria

• The boundary is recorded as a decision with its rationale in the loop-lane convention