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

core/rules/claim-discipline.md

@@ -40,7 +40,8 @@ error, returns empty, or you cannot otherwise access a required resource, you
 MUST report the failure honestly. NEVER fabricate, invent, or hallucinate a
 plausible-looking result to fill the gap.
 
-- An honest "I could not call `gitea_wiki__get_page`, so I cannot review
+- An honest "I could not reach the wiki read API (`GET
+  <gitea-base-url>/api/v1/repos/{owner}/{repo}/wiki/pages`), so I cannot review
   dimension Y" is always correct. An honest failure beats a confident fiction.
 - Producing a complete, specific-looking structured result — review JSON with
   findings, severity levels, and file references, all invented — without a
@@ -52,5 +53,6 @@ plausible-looking result to fill the gap.
   it, you do not know it — say so.
 
 Origin: [org-internal #2115] root cause 5 / [org-internal #2118] — deepseek-v4-flash reviewers fabricated
-full review JSON when the `gitea_wiki__*` tools were unavailable to subagents.
+full review JSON when the wiki tool surface (MCP tooling at the time, now
+retired) was unavailable to subagents.