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

core/skills/_shared/review-pipeline-phases.md

@@ -68,12 +68,13 @@ in `_shared/gitea-write-patterns.md`.
    in the Orchestrator instead of letting {DIMENSION_COUNT} parallel subagents
    each rediscover the gap:
 
-   - **Primary path**: confirm `gitea_wiki__*` tools are registered (the
-     Orchestrator checks its own tool catalog; these tools are forwarded to
-     reviewer subagents when registered — [org-internal #2116] raised the tool cap 50→100 so
-     they are present in normal runs). If available → continue to step 2.
-   - **Fallback path** (when `gitea_wiki__*` is NOT registered, e.g. a
-     cross-repo scenario [org-internal #2115]): verify the **local wiki clone** at
+   - **Primary path**: confirm the Gitea REST API is reachable — probe
+      `GET <gitea-base-url>/api/v1/repos/{owner}/{repo}/wiki/pages` with
+      `-H "Authorization: token <token>"` (a 200 or 403 response means
+      reachable; anything else — timeout, connection refused, 5xx — is
+      unreachable). If reachable → continue to step 2.
+    - **Fallback path** (when REST is unreachable, e.g. a
+      cross-repo scenario [org-internal #2115]): verify the **local wiki clone** at
      `<wiki-clone-root>/{repo}-wiki/` is readable —
      `glob(pattern="*.md", path="<wiki-clone-root>/{repo}-wiki/")`. If the clone
      is readable → continue to step 2; reviewers use the local clone (see
@@ -82,13 +83,14 @@ in `_shared/gitea-write-patterns.md`.
    - **Both unavailable → FAIL FAST**: post a `failure` commit status (state
      `"failure"`, context `pipeline/{REVIEW_TYPE}`, description naming the
      missing capability) and abort — do NOT enter parallel dispatch. Report the
-     gap so the environment can be fixed (register the wiki MCP server, or
-     populate `<wiki-clone-root>/{repo}-wiki/`).
+      gap so the environment can be fixed (restore Gitea REST reachability —
+      token validity, network route — or
+      populate `<wiki-clone-root>/{repo}-wiki/`).
 
-   This probe is belt-and-suspenders: RC1 (tool cap, [org-internal #2116]) already fixed the
-   primary cause of missing `gitea_wiki__*` in subagents. It exists so a future
-   environment regression fails gracefully with one clear message instead of N
-   silent subagent aborts.
+    This probe is belt-and-suspenders: it exists so a future
+    environment regression (REST unreachable, stale token) fails gracefully
+    with one clear message instead of N
+    silent subagent aborts.
 
 2. Post an initial pending commit status via REST:
 
@@ -471,8 +473,10 @@ not the round-1 full set.
 
 3.5. **Gitea approval timing (mandatory when the PR needs a human approval
    gate)**: if the flow requests approval from a human reviewer on Gitea,
-   register the reviewer FIRST via `gitea_pull__add_reviewer`, wait for the
-   `REQUEST_REVIEW` registration to be recorded, and only THEN ask the human
+    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 treats the PR as unapproved
    and the approval must be re-done. ([org-internal #1931]: audit R2→R3 re-loop + re-approve,