v0.1.1: Gitea transport surface de-MCP — REST+swagger sole canon (adapter recipes, terminology map, review probes)

core/skills/review-code/SKILL.md

@@ -974,7 +974,8 @@ After the Developer completes revision:
       `question` tool, passing `stage: "review-code"`:
 
       > **Gitea approval timing (mandatory when the PR needs a human approval
-      > gate)**: register the reviewer FIRST via `gitea_pull__add_reviewer`,
+      > gate)**: register the reviewer FIRST via
+      > `POST <gitea-base-url>/api/v1/repos/{owner}/{repo}/pulls/{index}/requested_reviewers`,
       > wait for the `REQUEST_REVIEW` registration to be recorded, and only
       > THEN ask the human to approve. Approving before the reviewer is
       > registered produces `official: false` on the approval — the gate
@@ -987,7 +988,7 @@ After the Developer completes revision:
       Final verdict: {PASS | WARN | FAIL}
        Converged: {true | false}
 
-      See full report: wiki page `{slug}/reviews/code/final/report` （DAG task mode: `{epic-slug}/reviews/code/final/report-task-{node-id}`）（via `gitea_wiki__get_page`，`_shared/gitea-read-patterns.md` Pattern 1）
+      See full report: wiki page `{slug}/reviews/code/final/report` （DAG task mode: `{epic-slug}/reviews/code/final/report-task-{node-id}`）（via `GET <gitea-base-url>/api/v1/repos/{owner}/{repo}/wiki/page/{mangled-name}` — `sub_url` resolved from `GET .../wiki/pages` first, `_shared/gitea-read-patterns.md` Pattern 1）
       All review artifacts: ticket #{issue_number} comments + wiki pages under `{slug}/reviews/code/`（DAG task mode: under `{epic-slug}/reviews/code/`, Tier 1 round artifacts under `<runs-root>/{epic-slug}-task-{node-id}/reviews/code/`）
       Inline comments（only when step 2.56 ran；omit for no-PR flows）: `inline: X posted / Y file-level / Z fallback / W failed`