# Resolved tea post-back invocation (verified via Task 2 smoke run) Gitea comment posting that survives large multi-line Markdown bodies: tea api --remote origin "/repos/{owner}/{repo}/issues//comments" -F body=@- # body via stdin [VERIFIED] # fallback: -F body=@/tmp/review-tea-body.md # body via file [VERIFIED] CRITICAL: use `-F` (typed field), NOT `-f`. `-f key=@file` posts the literal string `@file`; only `-F key=@file` / `-F key=@-` reads the file/stdin. The endpoint MUST include the `/repos/` prefix: `/repos/{owner}/{repo}/issues//comments` (without /repos/ it 404s). `tea api` already prints JSON to stdout — do NOT pass `-o json` (that writes the body to a file named `json`). Code link format (verified to render / resolve to HTTP 200 when SHA is remote-present): https://git.adlee.work/alee/vigilar/src/commit//#L-L # path segment src/commit [VERIFIED] Eligibility metadata fetch: tea pulls --remote origin --fields index,state,draft,title,mergeable,base,head,body -o json # NOTE: tea v0.14.1 returns empty `diff`/`patch` fields even when requested — do not rely on them. Diff source (preferred, local — the reliable source in this tea build): git diff origin/...origin/ # base/head come from the PR JSON's base/head fields Already-reviewed check: tea pulls review-comments --remote origin -o json # scan body for "### Code review" marker Login context: the `alee` tea login is NOT default (tea login list shows default=false). [VERIFIED: --remote origin resolves context; --login alee fallback not needed]