docs: register the design and plan in the wiki, with what got rejected

The entity pages carry the rejected alternatives and why, so the next
reader does not have to reconstruct the argument: minimal patch cannot
fill a tier that does not exist, cherry's wire DSL buys four endpoint
protocols we do not have, and default_effort lost its only consumer the
moment enable_thinking=True became Effort.AUTO.

research-wiki/graph/edges.json

@@ -200,6 +200,16 @@
       "id": "plan:plan-issue15-telemetry-pool-lifecycle",
       "label": "实现计划: 遥测连接池的资源语义与生命周期(issue #15)",
       "type": "plan"
+    },
+    {
+      "id": "design:reasoning-effort",
+      "label": "推理档位一等化设计(issue #20 及其一般形式)",
+      "type": "design"
+    },
+    {
+      "id": "plan:reasoning-effort",
+      "label": "实现计划: 推理档位一等化",
+      "type": "plan"
     }
   ],
   "links": [
@@ -412,6 +422,13 @@
       "relation": "implements",
       "evidence": "9 个任务逐条实现设计 §4-§11",
       "added": "2026-08-26T11:28:33.469681+00:00"
+    },
+    {
+      "source": "plan:reasoning-effort",
+      "target": "design:reasoning-effort",
+      "relation": "implements",
+      "evidence": "10 个任务逐条覆盖设计 §3-§8;T10 兑现人类「能力表统一经 new-api 实测」的决定",
+      "added": "2026-09-05T04:07:17.723586+00:00"
     }
   ]
 }