fix(remote): correct fill recording recovery guidance

Merged
NI
2d ago
+50-3

Summary

When fill --record-as lacks an armed recording, the daemon tags the error with a typed reason. Remote clients now explain that recording must start in a fresh session on a local daemon, instead of suggesting a command the remote transport rejects. Local recovery guidance and the intentional remote refusal remain unchanged. Adds focused daemon and client coverage. Four files changed; scope stays within fill validation and client error adaptation. Closes #4345.

Validation

  • Head: abdf3fa705b14f20fe6a1fd9014837f9cfffa0c9.
  • Build passed on the original implementation commit; focused Vitest passed on this head (2 files, 6 tests); oxlint passed on this head.
  • The affected gate on this head could not acquire its validation lock (EROFS at ~/.cache/agent-device/validation.reclaim.lock). On the previous commit it reached 76 Vitest files: 73 passed, 3 failed (333 passed, 6 failed), mostly because the environment could not create ~/.agent-device/apple-runner/leases; one proxy parity assertion also failed. Earlier gate receipt: .tmp/validation/run-7f69Hp/receipt.json.
  • GitHub checks remain required. Not merge-ready until the affected gate and remaining CI obligations are resolved. No device behavior changed.