tests: trace integration over the RPC socket (45 checks)HEADmain

The existing trace suites (test_trace.py, test_trace_ui.py,
test_trace_vs_tenet.py) cover the model layer, the UI via the Textual pilot,
and differential correctness against Tenet's reference. None of them exercise
the path an agent actually takes: the trace RPC verb driven over the unix
socket through rpcclient.

This one spawns a real tmux pane with --trace, records a trace with the QEMU
tracer (falling back to /tmp/echotrace.0.log if the tracer isn't built), and
drives every trace operation through the RPC socket, validating the JSON
responses:

  seek (absolute, percentage, string, edge-clamping)
  step (forward, backward, multi-step, clamp at bounds)
  step over (finds a call via SP drop, verifies it lands after the return)
  goto (by name, by hex address, error on unexecuted)
  changed registers in the response
  cursor tracking (ea follows the trace pc)
  response shape (trace key is a superset of snapshot)
  interaction with non-trace verbs (pseudocode, state, view, goto)
  trace position independence from navigation

All 45 checks pass against the echo binary with a 226-instruction trace.

0 files changed, 0 insertions, 0 deletions