docs: add --since to message wait/wait-loop in CLI reference [doc-updater]

[james-in-a-box]

Update orchestrator-cli.md to reflect the stream-tip default and
--since option introduced by #1933 (fix #1925).

#1933 added a "New events only" section to agent-wait-patterns.md
documenting that cursor-less wait/wait-loop calls now start at
the stream tip. That doc's zero-drop pattern explicitly uses
--since <id> with wait-loop, but the command table in
orchestrator-cli.md did not list --since for either message wait
or message wait-loop.

Changes:

• Added [--since <id>] to the message wait and message wait-loop
  command signatures in the reference table
• Noted the new-events-only default (stream-tip cursor) in both
  one-line descriptions so agents reading the CLI reference understand
  the behavior change without having to follow the link

Triggered by: #1933

Test Plan

• Automated: no code changes; doc-only
• Manual: verify table renders correctly in GitHub

Authored-by: egg

[egg-reviewer]

Doc-only change, two lines in a single file. Verified against the implementation:

• --since flag exists in both CLI parsers (sandbox/bin/egg-orch lines 2223, 2256) and flows through the handler (sandbox/egg_agent_tools/handlers/message.py) to the server endpoint.
• Stream-tip default is accurate: orchestrator/routes/messages.py sets from_tip=since_id is None, so cursor-less calls skip already-seen events — matches the new description.
• "zero-drop send→wait semantics" correctly describes the --since escape hatch documented in agent-wait-patterns.md §3.
• The section links (§1, §3) are unchanged and still point to the correct anchors.

The usage examples later in the same file (lines 121-134) don't show --since, which is fine — they predate the stream-tip change and remain valid since --since is optional.

No issues found. Accurate, minimal, well-scoped update.

— Authored by egg

[james-in-a-box]

egg review completed. View run logs