fix(gmail): make body truncation hints discoverable

[clawsweeper]

Summary

• Align gmail thread get --full help with the existing gmail messages search --full wording.
• Make default text truncation markers for gmail thread get and gmail messages search --include-body point users to --full or JSON output.
• Preserve existing full-output behavior for --full and JSON, and refresh the generated Gmail command docs that change.

Closes #807

Reported by @privatenumber in #807.

Testing

• make fmt
• make docs-commands
• go test ./internal/cmd -run 'TestExecute_GmailThread_Text_FullFlag|TestExecute_GmailMessagesSearch_Text_IncludeBodyTruncationDiscoverable|TestSanitizeMessageBody_TruncateUTF8|TestSanitizeMessageBody_FullSkipsTruncation|TestGmailPresentationSchemas|TestExecute_Schema_GmailTruncationHelp'
• make ci

Release note

Gmail read-body text output now makes truncation discoverable and points users at full-output modes.

ClawSweeper 🐠 replacement reef notes:

• Cluster: issue-openclaw-gogcli-807
• Source PRs: none
• Credit: Issue reported by @privatenumber in gmail: make read-body truncation discoverable (align --full help; point truncation markers at --full) #807; credit the report in the PR body.; Release-note context for PR body: Gmail text output now tells users how to get full message bodies when body previews are truncated.
• Validation: make fmt; make docs-commands; go test ./internal/cmd -run 'TestExecute_GmailThread_Text_FullFlag|TestExecute_GmailMessagesSearch_Text_IncludeBodyTruncationDiscoverable|TestSanitizeMessageBody_TruncateUTF8|TestSanitizeMessageBody_FullSkipsTruncation|TestGmailPresentationSchemas|TestExecute_Schema_GmailTruncationHelp'; make ci
• Replacement reason: ClawSweeper could not update the source PR branch directly, so it opened a writable replacement PR instead.

fish notes: reasoning high; reviewed against dfa1615.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed June 15, 2026, 1:45 AM ET / 05:45 UTC.

Summary
Review failed before ClawSweeper could summarize the requested change.

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Review metrics: none identified.

Merge readiness
Overall: 🌊 off-meta tidepool
Proof: 🌊 off-meta tidepool
Patch quality: 🌊 off-meta tidepool
Result: rating does not apply to this item.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Risk before merge

• [P1] No close action taken because the review did not complete.

Maintainer options:

1. Decide the mitigation before merge
   Retry the Codex review after fixing the execution failure.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

• Review did not complete, so no work-lane recommendation was made.

Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

Do we have a high-confidence way to reproduce the issue?

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Codex review notes: model internal, reasoning high; reviewed against 23b847ca53cf.

Label changes

Label changes:

• add rating: 🌊 off-meta tidepool: Overall readiness is 🌊 off-meta tidepool; proof is 🌊 off-meta tidepool and patch quality is 🌊 off-meta tidepool.
• remove P3: Current review triage priority is none.
• remove rating: 🐚 platinum hermit: Current PR rating is rating: 🌊 off-meta tidepool, so this older rating label is no longer current.
• remove status: 👀 ready for maintainer look: Current PR status no longer selects a status label.

Label justifications:

• rating: 🌊 off-meta tidepool: Overall readiness is 🌊 off-meta tidepool; proof is 🌊 off-meta tidepool and patch quality is 🌊 off-meta tidepool.

Evidence reviewed

What I checked:

• failure reason: timeout.
• codex failure detail: Codex review failed for this PR: spawnSync /opt/hostedtoolcache/node/24.16.0/x64/bin/node ETIMEDOUT.
• codex stderr: No stderr captured.
• codex stdout: {"type":"thread.started","thread_id":"019ec9bd-9915-7b70-ab57-5d410e683a2d"}.
• process error code: ETIMEDOUT.

Likely related people:

• unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[clawsweeper]

🦞👀
ClawSweeper saw the passing review, but did not merge yet.

Source: clawsweeper[bot]
Feedback: structured ClawSweeper verdict: pass (sha=dfa16156249f10ee2fe110feda1e5128218210b7)
Merge status: PR is in ClawSweeper autofix mode; merge is disabled

I left the PR open for the remaining gate instead of bypassing it.

Automerge progress:

• 2026-06-15 04:42:27 UTC review passed dfa16156249f (structured ClawSweeper verdict: pass (sha=dfa16156249f10ee2fe110feda1e512821821...)

[steipete]

@clawsweeper stop

[clawsweeper]

🦞✅
Got it. ClawSweeper will leave this item for human review.

I added clawsweeper:human-review and paused the automation trail until a maintainer asks again.