feat(pr): hidden agent-meta marker on posted bodies (#16)

skills/land/SKILL.md

@@ -89,7 +89,8 @@ Then **end the turn**. Do not wait for anything.
 
 Each reason is one query. Nothing new: return silently, per
 `COMMON.md`. Update the state file whenever the phase or head SHA
-changes.
+changes. Every body you post ends with the metadata marker from
+`COMMON.md`.
 
 ### `reason=comments`
 
@@ -116,17 +117,23 @@ and act on what's left:
   Gitea has no reply endpoint, so that lands as a loose PR comment. To
   answer a code comment inside its own thread, post a review instead
   whose `comments[]` entry repeats the same `path` and `new_position` —
-  gitea groups code comments by position into one conversation. Record
-  the review id and its comment ids.
+  gitea groups code comments by position into one conversation
+  (`new_position: 0` for a file-level comment). Record the review id
+  and its comment ids.
 
-- **Resolve the thread** (github only — gitea has no per-thread
-  resolve, so a short confirming reply plus the pushed fix is the
-  signal):
+- **Resolve the thread** once addressed — fix pushed or reply posted:
 
   ```bash
+  # github
   gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "<tid>"}) { thread { isResolved } } }'
   ```
 
+  ```bash
+  # gitea (1.26+; on 404 fall back to a confirming reply as the signal)
+  curl -sS -X POST -H "Authorization: token $GITEA_TOKEN" \
+    "$BASE/api/v1/repos/$REPO/pulls/comments/<cid>/resolve"
+  ```
+
 Every unresolved thread gets an action — a fix or a reply. Bot
 reviewers (Copilot, CodeRabbit, crit) count. Never declare the PR ready
 over an unaddressed thread.