Op interpreter: correct iteration numbers

t-405·WorkTask·
·
·
Created1 month ago·Updated1 month ago

Description

Edit

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

Timeline (4)

🔄[human]Open → InProgress1 month ago
🔄[human]InProgress → Done1 month ago
💬[human]1 month ago

Seq interpreter now derives iteration from state via seqGetIteration; agent CLI/op-runner set it to asIteration/csIteration. Updated README example.