l0ng-ai db275b7770 docs(cli): say that a newline inside send's TEXT presses Enter ...

$ tty7 send %1 "$(printf 'echo ONE\necho TWO')"
    ... echo ONE
    ONE
    ... echo TWO          <- typed, waiting

Correct for a verb whose first line is "types TEXT into the pane exactly
as a keyboard would" -- typing a newline is pressing Enter. But `--enter`
is documented right next to it as the way to submit, which reads as
though TEXT alone cannot, and an orchestrator passing along text it did
not write runs it a line at a time.

So `--help` and the reference now say it, with the shape it takes: the
text before the newline runs, and what follows is left typed at the
prompt it asked for. A test pins the bytes -- neither stripped nor split
into two writes -- so the pages and the behaviour cannot drift apart.

Found while feeding a pane input it does not expect. Three neighbours
came through that unchanged and are worth recording: invalid UTF-8 in
output becomes U+FFFD with correct recovery (`\xc3\x28` is one
replacement and a literal `(`), `capture --json` stays valid JSON over
it, and an OSC title carrying bad bytes is folded before storage so
`machine.json` stays parseable and the tab table stays aligned.

2026-08-16 13:33:46 +08:00

..

agent-skill.mdx

docs(skill): show how to update an installed tty7 skill

2026-08-12 17:09:55 +08:00

overview.mdx

docs: correct claims that no longer match the code

2026-08-11 14:35:54 +08:00

reference.mdx

docs(cli): say that a newline inside send's TEXT presses Enter

2026-08-16 13:33:46 +08:00