Under the hood
Command execution now attaches a commandRun marker to transcript messages
What
When a command is run, whether immediately in the local session or via a bridge, the resulting transcript message now carries a commandRun field alongside its existing text and error content.
Why
This appears to record which command produced a given transcript entry, likely for tracking or displaying command-run history more precisely.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What consumes this new field, and how it changes what a user sees, is not specified in the finding.