itd-2609221656373558 criterion 6 promises that on contention of any kind the second session backs off and the log names the reason and the minutes spent. Delivered: a refused claim writes a backoff line with the reason but minutes fixed at 0 (internal/core/implement/claim.go:232), and a locked run state returns ErrContention from withLock with no log line at all (internal/core/implement/run.go:182-186), so lock contention is never counted in the derived comparison and the verb measures no backed-off minutes; queue contention is logged only when the session hand-writes implement log backoff. Found by the fidelity audit; not fixed here.

itd-2609221656373558 criterion 6 promises that on contention of any kind the second session backs off and the log names the reason and the minutes spent. Delivered: a refused claim writes a backoff line with the reason but minutes fixed at 0 (internal/core/implement/claim.go:232), and a locked run state returns ErrContention from withLock with no log line at all (internal/core/implement/run.go:182-186), so lock contention is never counted in the derived comparison and the verb measures no backed-off minutes; queue contention is logged only when the session hand-writes implement log backoff. Found by the fidelity audit; not fixed here.

Grounds

• pursued: contention of any kind the second session meets leaves a backoff line naming reason and minutes; shown wrong if a lock or claim contention returns exit 3 with no backoff line, or a backoff line lacks either field