One issue, both halves
An issue of the wire is one email that says the same thing twice, once for each reader.
The half you read
A short list of what moved, grouped by tool. One line per change, with the old value and the new one side by side and a link to the vendor page it came from.
The half your agent reads
The same changes as JSON, between two ---
lines at the top of the plain-text part. Field by field it's specified
in the
machine contract
and
wire.schema.json.
A real past issue goes here next, printed both ways so you can see one change land in both halves. Hand the wire to your agent has the JSON fields in the meantime.