Bug
When af send delivers a message longer than 3 lines to a terminal, the terminal (likely xterm.js or the shell) classifies it as a paste rather than typed input. This causes the final Enter/newline to be swallowed — the message appears in the terminal but doesn't get submitted.
Steps to Reproduce
af send 0042 "a message that spans more than three lines"
- Observe that the message appears in the builder's terminal but the trailing Enter doesn't fire
- Short messages (1-3 lines) work fine
Expected Behavior
The message should be fully delivered AND submitted (Enter processed), regardless of length.
Suggested Fix
Pace the output for messages longer than 3 lines — introduce a small delay between chunks or between the message body and the final newline, so the terminal doesn't classify it as a bracketed paste.