Fix iteration tracking in Sequential interpreter.
Problem
SeqConfig.seqIteration never changes, so trace events always report iteration 0.
This breaks observability and any iteration-based limits/diagnostics.
Requirements
- Increment iteration per infer cycle
- Emit correct iteration numbers in trace events
- Keep consistent with AgentState.asIteration
Acceptance
- Trace events show increasing iteration values across loops
- watch/status reflect correct iteration counts
Seq interpreter now derives iteration from state via seqGetIteration; agent CLI/op-runner set it to asIteration/csIteration. Updated README example.