feat: consolidate course into 21 lessons

web/src/data/annotations/s15.json

@@ -2,45 +2,59 @@
   "version": "s15",
   "decisions": [
     {
-      "id": "lead-agent-owns-coordination",
-      "title": "The Lead Owns Coordination",
-      "description": "The lead agent decides when to spawn teammates, what to send them, and how to interpret replies. Teammates can work independently, but the user-facing conversation stays anchored in one lead loop.",
-      "alternatives": "A peer-to-peer team would be more flexible, but much harder to explain because no single loop owns the answer.",
+      "id": "confirm-team-before-spawn",
+      "title": "The User Confirms the Team Before It Starts",
+      "description": "The Lead may notice that a request can be split, but it first proposes a small team with clear responsibilities. Teammates start only after the user confirms the extra agents.",
+      "alternatives": "Spawning immediately saves one turn, but hides the cost and coordination choice from the user.",
       "zh": {
-        "title": "由 Lead Agent 负责协调",
-        "description": "Lead agent 决定何时创建队友、发送什么任务、如何解释回复。队友可以独立工作，但面向用户的对话始终锚定在一个 lead 循环中。"
+        "title": "启动团队前先征得用户确认",
+        "description": "Lead 可以判断一个需求适合拆分，但要先提出职责清晰的小团队。只有用户确认后，运行时才启动额外的 Agent。"
       },
       "ja": {
-        "title": "調整はリードエージェントが担う",
-        "description": "リードエージェントがチームメイトの生成、送信内容、返信の解釈を決めます。チームメイトは独立して作業できますが、ユーザー向けの会話は一つのリードループに固定されます。"
+        "title": "チームを起動する前にユーザーが確認する",
+        "description": "Lead は依頼を分割できると判断しても、まず役割が明確な小さなチームを提案する。追加 Agent はユーザーの確認後に起動する。"
       }
     },
     {
-      "id": "file-backed-mailboxes",
-      "title": "Mailboxes Make Team Communication Inspectable",
-      "description": "MessageBus writes JSONL mailboxes so every handoff is visible on disk. This avoids magical shared memory and gives learners a concrete artifact for debugging team behavior.",
-      "alternatives": "In-memory channels are faster, but they hide the communication history and disappear when the process stops.",
+      "id": "runtime-owned-delivery",
+      "title": "Message Delivery Belongs to the Runtime",
+      "description": "MessageBus stores each handoff in JSONL, while the runtime watches the Lead mailbox and injects new team events into the next turn. The model does not need an inbox polling tool.",
+      "alternatives": "A model-visible check_inbox tool is easy to add, but wastes turns and can leave completed work unnoticed.",
       "zh": {
-        "title": "邮箱文件让团队通信可检查",
-        "description": "MessageBus 使用 JSONL 邮箱记录每次交接。这样避免了神秘的共享内存，也给学习者一个能直接调试团队行为的具体文件。"
+        "title": "消息投递由运行时负责",
+        "description": "MessageBus 把每次交接写入 JSONL，运行时监听 Lead 邮箱，并把新的团队事件送入下一轮上下文。模型不需要调用邮箱轮询工具。"
       },
       "ja": {
-        "title": "メールボックスでチーム通信を検査可能にする",
-        "description": "MessageBus は JSONL メールボックスへ各ハンドオフを書き込みます。見えない共有メモリを避け、チーム動作をデバッグできる具体的な成果物を提供します。"
+        "title": "メッセージ配信はランタイムが担う",
+        "description": "MessageBus は各ハンドオフを JSONL に保存し、ランタイムが Lead のメールボックスを監視して新しい team event を次の turn に注入する。モデルに受信箱確認ツールは要らない。"
       }
     },
     {
-      "id": "scoped-teammate-tools",
-      "title": "Teammates Use Scoped Tool Sets",
-      "description": "A teammate loop receives a narrower prompt and tool set than the lead. That keeps delegation focused and prevents a helper agent from accidentally taking over orchestration.",
-      "alternatives": "Giving every teammate the full tool pool is simpler, but it blurs roles and makes failures harder to attribute.",
+      "id": "typed-request-correlation",
+      "title": "Typed Requests Carry Correlation IDs",
+      "description": "Plan and shutdown requests use explicit message types and request ids. Replies can arrive in any order and still update the correct pending request.",
+      "alternatives": "Matching the latest free-form message works only until requests overlap.",
       "zh": {
-        "title": "队友使用受限工具集",
-        "description": "队友循环拿到比 lead 更窄的提示词和工具集。这样委派更聚焦，也避免 helper agent 意外接管整体协调。"
+        "title": "类型化请求携带关联 ID",
+        "description": "计划和关机请求使用明确的消息类型与 request id。即使回复顺序不同，运行时也能更新正确的 pending request。"
       },
       "ja": {
-        "title": "チームメイトには範囲を絞ったツールセットを与える",
-        "description": "チームメイトループにはリードより狭いプロンプトとツールセットを渡します。委任を集中させ、補助エージェントが誤って全体調整を奪うことを防ぎます。"
+        "title": "型付きリクエストに対応 ID を持たせる",
+        "description": "プランと終了の要求は明示的な message type と request id を使う。返信順が変わっても、正しい pending request を更新できる。"
+      }
+    },
+    {
+      "id": "plan-approval-is-a-gate",
+      "title": "Plan Approval Is an Execution Gate",
+      "description": "When the Lead requests a plan, mutating tools remain blocked until the matching plan is approved. Rejection requires a new submission, and an idle teammate remains available for later assignments until a typed shutdown completes.",
+      "alternatives": "Treating approval as a conversational suggestion cannot prevent an early write or shell command.",
+      "zh": {
+        "title": "计划审批是执行闸门",
+        "description": "Lead 请求计划后，修改类工具会保持阻塞，直到对应计划通过。被拒绝的计划必须重新提交；空闲队友会继续保留，直到类型化关机协议完成。"
+      },
+      "ja": {
+        "title": "プラン承認を実行ゲートにする",
+        "description": "Lead がプランを要求すると、対応するプランが承認されるまで変更系ツールをブロックする。却下後は再提出が必要で、待機中のチームメイトは型付き終了プロトコルが完了するまで残る。"
       }
     }
   ]