Summary

Default text output truncates message bodies, but the remedy (--full) is under-advertised and the
two read paths are inconsistent, so users/agents routinely don't realize output was cut.

Details (v0.22.0, 197992a)

• gmail thread get truncates each body at 500 chars and appends ... [truncated]
  (internal/cmd/gmail_thread.go:165-166) but doesn't say how to get the full body; its --full
  help is just "Show full message bodies".
• gmail messages search --include-body truncates at 200 chars with a bare ...
  (internal/cmd/gmail_messages.go:339,341, truncateRunes), with no [truncated] marker at all.
  Its --full help is better: "Show full message bodies without truncation (implies --include-body)".
• Same --full flag, weaker help on thread get; the markers differ and neither names the fix.

Suggested fix

• Align thread get --full help with the messages search wording ("...without truncation").
• Make both truncation markers actionable, e.g. ... [truncated; use --full or --json].
• Optionally note in thread get/get help that default text truncates while --json is complete.

Environment

gog v0.22.0 (confirmed by reading source at 197992a).