minimal-agent 0.9.0 → 0.10.0

package/workflows/youtube-shorts.yaml

@@ -7,32 +7,40 @@ description: |
   去做任意视频流水线（横屏长视频、广告片、教程片都行）。
 version: "0.1"
 
+# 声明产物：new-task 启动清理残留 / completed 报实际产物 / 同任务 resume 重写不被
+# 内核「覆盖前先 Read」守卫挡（见 CLAUDE.md 任务身份语义）
+artifacts:
+  - "./assets/script.json"
+  - "./out/shorts.mp4"
+
 inputs:
   - name: topic
     type: string
     required: true
-    description: "视频主题（中文）"
+    greedy: true
+    description: "视频主题（中文，可一句话自然语言；命令行整句进 topic，不被空格拆碎）"
   - name: openrouter_key
     type: string
     required: false
-    description: "OpenRouter API key；不填则用 OPENROUTER_API_KEY 环境变量"
+    description: "【高级·用 --input openrouter_key=...】OpenRouter API key；不填则用 OPENROUTER_API_KEY 环境变量"
   - name: aspect
     type: enum
     values: ["9:16", "16:9", "1:1", "4:5"]
     default: "9:16"
-    description: "图片与视频宽高比"
+    description: "【高级·用 --input aspect=...】图片与视频宽高比"
   - name: width
     type: number
     default: 1080
-    description: "视频输出宽度"
+    description: "【高级·用 --input width=N】视频输出宽度"
   - name: height
     type: number
     default: 1920
-    description: "视频输出高度"
+    description: "【高级·用 --input height=N】视频输出高度"
 
 steps:
   # ---------- 1. 用 LLM 写 5 幕脚本（强制 5 幕以便后续 loop 用静态数组） ----------
   - id: write_script
+    title: "1/11·写五幕脚本"
     llm: |
       你是短视频文案策划。请为主题"${inputs.topic}"写一个 **正好 5 幕** 的竖屏短视频。
       每一幕包含：
@@ -48,13 +56,17 @@ steps:
 
   # ---------- 2. 把 LLM 输出落盘为 script.json ----------
   - id: write_script_json
+    title: "2/11·脚本落盘 script.json"
     tool: Write
+    artifacts:
+      - "./assets/script.json"
     args:
       file_path: "./assets/script.json"
       content: "${script_json_text}"
 
   # ---------- 3. 解析 script.json，拆出 prompts.txt / narrations.txt（每行一个） ----------
   - id: parse_script
+    title: "3/11·解析脚本拆分文案"
     tool: Bash
     args:
       command: |
@@ -69,6 +81,7 @@ steps:
       content: parse_log
 
   - id: assert_script_parsed
+    title: "4/11·校验脚本拆分产物"
     type: verify
     checks:
       - 'file_exists:./assets/prompts.txt'
@@ -76,39 +89,49 @@ steps:
     onFail: "脚本解析失败：./assets/prompts.txt 或 ./assets/narrations.txt 不存在"
 
   # ---------- 4. 生成 5 张配图（loop 静态数组 + 每轮先读对应一行 prompt） ----------
+  # ⚠️ Bash 引号 footgun：${i} 是引擎插值（shell 之前发生）。曾写 1 基算术
+  # `sed -n '$((${i}+1))p'`——shell 单引号内不做算术展开，sed 收到字面 $((0+1))p
+  # 直接报错。正解：loop 直接用 1 基序号，sed 行号即 ${i}。
   - id: gen_images
+    title: "5/11·生成五张配图"
     type: loop
-    over: "[0, 1, 2, 3, 4]"
+    over: "[1, 2, 3, 4, 5]"
     as: i
     do:
       - id: read_prompt
+        title: "读第 ${i} 行画面提示词"
         tool: Bash
         args:
-          command: "sed -n '$((${i}+1))p' ./assets/prompts.txt"
+          command: 'sed -n "${i}p" ./assets/prompts.txt'
         capture:
           content: prompt_text
       - id: gen_one_image
+        title: "生成第 ${i} 张配图"
         skill: image-gen-openrouter
         input: 'prompt=${prompt_text} output=./assets/img_${i}.png aspect=${inputs.aspect} key=${inputs.openrouter_key}'
 
-  # ---------- 5. 生成 5 段 TTS 音频 ----------
+  # ---------- 5. 生成 5 段 TTS 音频（1 基序号，理由同 gen_images） ----------
   - id: gen_audio
+    title: "6/11·生成五段配音"
     type: loop
-    over: "[0, 1, 2, 3, 4]"
+    over: "[1, 2, 3, 4, 5]"
     as: i
     do:
       - id: read_narration
+        title: "读第 ${i} 句旁白"
         tool: Bash
         args:
-          command: "sed -n '$((${i}+1))p' ./assets/narrations.txt"
+          command: 'sed -n "${i}p" ./assets/narrations.txt'
         capture:
           content: narration_text
       - id: gen_one_tts
+        title: "合成第 ${i} 段语音"
         skill: tts-zh
         input: 'text=${narration_text} output=./assets/audio_${i}.mp3'
 
   # ---------- 6. 探测各段音频时长，逗号串联 ----------
   - id: probe_durations
+    title: "7/11·探测音频时长"
     tool: Bash
     args:
       command: |
@@ -121,6 +144,7 @@ steps:
 
   # ---------- 7. 合并所有 TTS 段成一条音轨 ----------
   - id: merge_audio
+    title: "8/11·合并音轨"
     tool: Bash
     args:
       command: |
@@ -135,6 +159,7 @@ steps:
 
   # ---------- 8. 读 narrations_json（前面 parse_script 已写好），作 SRT 文本输入 ----------
   - id: read_narrations_json
+    title: "9/11·读取旁白清单"
     tool: Read
     args:
       file_path: "./assets/narrations_json.txt"
@@ -143,16 +168,19 @@ steps:
 
   # ---------- 9. 生成 SRT 字幕 ----------
   - id: make_srt
+    title: "10/11·生成字幕"
     skill: subtitle-srt
     input: 'texts=${narrations_json} durations=${durations} output=./assets/subs.srt'
 
   # ---------- 10. 合成最终 mp4 ----------
   - id: compose_video
+    title: "11/11·合成最终视频"
     skill: video-compose
     input: 'images_glob=./assets/img_*.png audio=./assets/audio.mp3 srt=./assets/subs.srt output=./out/shorts.mp4 width=${inputs.width} height=${inputs.height}'
 
   # ---------- 11. 守门 verify（升级自 assert） ----------
   - id: verify_output
+    title: "完成·守门校验"
     type: verify
     checks:
       - 'file_exists:./out/shorts.mp4'

package/MINIMAL-TRACE.md

@@ -1,77 +0,0 @@
-# MINIMAL-TRACE —— 用最短路径读懂 agent 主循环
-
-> 教学导读。本项目首要目标是「讲透一个 agent 从输入 → 工具循环 → 落盘」。
-> 但 `src/loop.ts` 已含不少**生产硬化**（4 种压缩 / 反应式自救 / 并行事件队列 / 截断警告…），
-> 初学者直接读会被淹没。这篇带你**第一遍只看主干**，把硬化层全部圈出来跳过。
-
-## 一句话本质
-
-```
-用户输入 → 调 LLM → LLM 想调工具就执行 → 结果喂回 → 再调 LLM → … → 不调工具了，输出最终回答
-```
-
-整个 agent 就是这个循环。它写在 `src/loop.ts::runQuery`（一个 `async function*`，逐步 `yield` 事件给 UI）。
-
-## 最小可读路径（第一遍只看这 6 步）
-
-打开 `src/loop.ts`，找到 `runQuery`，顺着看这几段——**只看主干，遇到下面「进阶层」列出的东西先跳过**：
-
-1. **用户消息入栈**：把 `{ role:'user', content: userInput }` push 进 `history`，`yield` 一个 `user_message_committed` 让 UI 先把它显示出来。`history` 是一个会被原地 mutate 的数组（调用方和 loop 共享同一引用）。
-
-2. **进入 `while (turn < maxTurns)`**：每一轮 = 一次「调 LLM（可能带工具）」。`maxTurns`（默认 50）是失控保护。
-
-3. **调 LLM、把流式响应拼成一条 assistant 消息**：`for await (const ev of chat({...}))` 逐块消费——`text_delta` 累积成答案文本并 `yield {type:'text'}`；`tool_call_delta` 累积成工具调用（OpenAI 协议下工具调用也是分片返回的，用 `mergeToolCallDelta` 合并）。循环结束后组装出 `assistantMsg` 推入 `history`、`yield assistant_message`。
-
-4. **没有工具调用 → 这一轮就是最终回答，结束**：`if (toolCallsByIndex.length === 0)` → `yield {type:'turn_done'}` 然后 `return`。这是循环的正常出口。
-
-5. **有工具调用 → 逐个执行、把结果按顺序回填 `history`**：对每个工具调用，`yield tool_start` → 调 `executeToolFn(name, argsJson, signal)` → `yield tool_end`，再把结果作为 `{ role:'tool', tool_call_id }` 消息 push 回 `history`。**关键**：tool 消息必须严格按 assistant 的 `tool_calls` 顺序回填（OpenAI 协议要求一一对应）。
-
-6. **回到 `while` 顶部继续下一轮**：模型这次能看到上一轮的工具结果，于是接着推理——要么再调工具，要么给出最终答案（回到第 4 步出口）。
-
-读完这 6 步，你就掌握了 agent 的全部本质。下面的都是「让它在生产环境不出岔子」的加固，第一遍可以完全不看。
-
-## 进阶层（第一遍请跳过）
-
-这些都是 `runQuery` 里为了**健壮/体验**加的料，每个解决一个具体问题，但都不影响你理解主循环：
-
-| 你会看到 | 它解决什么 | 第一遍 |
-|---|---|---|
-| `autoCompactIfNeeded`（每轮开头） | 上下文快撑爆时，把旧对话压成摘要，防止超 contextWindow | 跳过 |
-| `reactiveCompactIfApplicable`（catch 里） | 真撞上 prompt-too-long 时，压缩历史后**同轮重发**自救 | 跳过 |
-| `snipCompactIfNeeded`（压缩失败兜底） | 连压缩都失败时，硬砍最老消息释放空间再继续 | 跳过 |
-| `microCompact`（回填 tool 结果时） | 把单个超长工具输出就地压短，省 token | 跳过 |
-| `allConcurrencySafe` 分支 + 事件队列 | 本轮工具**全是只读**才并行执行，否则串行（杜绝并行写同一文件） | 跳过 |
-| `lastFinishReason === 'length'` 警告 | 模型答案被 max_tokens 截断时提醒用户「这是半截」 | 跳过 |
-| `reasoningContent / reasoning / reasoning_details` | 累积思维链（DeepSeek-R1 / MiniMax 等），下一轮原样回传防「失忆」 | 跳过 |
-| `error` 事件的 `code`（llm_error / max_turns / …） | 让 `-p --output-format json` 把终结原因映射成稳定的 stop_reason（给宿主 spawn 用） | 跳过 |
-| `options.chat` / `options.executeTool` | 依赖注入：测试时传 stub，零进程污染；生产走真实模块单例 | 跳过 |
-
-## 时序图（主干）
-
-```
-用户输入
-   │
-   ▼
-runQuery  ──push user 消息──►  history
-   │
-   ├─◄─────────────────────────┐  （每轮 turn）
-   ▼                           │
- chat(LLM)  ──流式 text / tool_call──►  拼成 assistant 消息 → history
-   │                           │
-   ├── 无 tool_calls ──► turn_done ──► return（最终回答）
-   │                           │
-   └── 有 tool_calls           │
-        │                      │
-        ▼                      │
-   executeTool ×N ──► tool 结果 → history ──┘（回到下一轮，模型看到结果再推理）
-```
-
-## 延伸阅读（按需，第几步用到再看）
-
-- **`src/types.ts`** —— 类型字典。先看 `Message`（4 种 role）、`ToolCall`、`LlmStreamEvent`（LLM 流式块）、`LoopEvent`（loop 给 UI 的事件）。读主循环前先扫一遍这四个就够。
-- **`src/llm/client.ts`** —— `chat()` 的实现：把 provider 的 SSE 流解析成 `LlmStreamEvent`。对应主干第 3 步。
-- **`src/tools/index.ts`** —— `ALL_TOOLS`（工具清单）+ `executeTool()`：参数防线（JSON.parse → Zod 校验 → 调 `tool.call()`，**工具失败不抛异常**，把 error 喂回 LLM 让它重试）。对应主干第 5 步。
-- **`src/context/compact.ts`** —— 自动压缩入口（进阶层）。想搞懂「上下文怎么不撑爆」再看。
-- **`src/loop.ts`** —— 主角本身。读完本文按上面 6 步对照源码，再回头看进阶层。
-
-> 一句话给初学者：**先把 6 步主干跑通，把进阶层当黑盒**；等你能复述「输入怎么变成最终回答」了，再一个个揭开硬化层——每揭开一个，你就多懂一点「为什么生产级 agent 不只是一个 while 循环」。

package/plugins/workflow-runner/src/voteHelpers.js

@@ -1,110 +0,0 @@
-/**
- * ============================================================
- *  voteHelpers.ts —— vote 节点的 voter 调用辅助
- * ------------------------------------------------------------
- *  对抗式审查：N 个 voter 跑同一 prompt + refuted: boolean 反向投票。
- *  策略上倾向 refuted=true（找漏洞），所以阈值算的是"驳回票数"。
- *  详见 ADR-05。
- * ============================================================
- */
-import { execLlmStep } from './stepExecutors/llm.js';
-/** voter 输出 schema（内置，不接受用户自定义） */
-export const VERDICT_SCHEMA = {
-    type: 'object',
-    additionalProperties: false,
-    required: ['refuted', 'reasoning'],
-    properties: {
-        refuted: { type: 'boolean', description: '是否驳回此 finding' },
-        reasoning: { type: 'string', description: '核心论证（≤200 字）' },
-    },
-};
-export function buildVoterPrompt(rules, item) {
-    const itemStr = typeof item === 'string' ? item : JSON.stringify(item, null, 2);
-    return `你是一个对抗式审查者，你的核心任务是积极找出下面这个 finding 的逻辑漏洞、证据不足、或论证它是伪命题。
-
-**被审查的 finding**：
-${itemStr}
-
-**审查规则**：
-${rules}
-
-**重要心理学定位**：你应当倾向于 refuted=true。只在你**找不到任何合理的反驳角度**且这个 finding 论证扎实时，才输出 refuted=false。"老好人式赞同"是错误的。
-
-输出 JSON，refuted=true 表示你成功找到反驳理由，false 表示你认为它确实成立。reasoning 字段写明你的核心论证（≤200 字）。`;
-}
-/** 单个 voter 调用。包装 execLlmStep，强制 VERDICT_SCHEMA + 对抗式 prompt。
- *  解析失败时默认 refuted=false（保守保留 item，避免 LLM 失误导致正确 finding 被误删）。 */
-export async function runVoter(rules, item, vars, ctx) {
-    const virtualStep = {
-        id: 'vote_voter', // 仅 ID，不影响事件流
-        llm: buildVoterPrompt(rules, item),
-        output_schema: VERDICT_SCHEMA,
-    };
-    try {
-        // execLlmStep 现为 AsyncGenerator：手动 drain 取 return 值。voter 必须静默——
-        // N 个 voter 在 Promise.all 里并行，若把它们的 text 事件向上转发会在 UI 互相打架。
-        const gen = execLlmStep(virtualStep, vars, ctx);
-        let res = await gen.next();
-        while (!res.done)
-            res = await gen.next();
-        const result = res.value;
-        const verdict = extractVerdict(result.raw);
-        if (verdict)
-            return verdict;
-        return { refuted: false, reasoning: '(voter 输出格式异常，保守保留)' };
-    }
-    catch (e) {
-        return {
-            refuted: false,
-            reasoning: `(voter 调用失败: ${e.message}，保守保留)`,
-        };
-    }
-}
-/**
- * 从 execLlmStep 的 raw 提取 { refuted, reasoning }：
- *   1. raw 直接含字段（B 改完 llm.ts 串通 output_schema 后的形态）
- *   2. raw.text / raw.result 是 JSON 字符串，parse 后含字段（B 未改完时的 fallback）
- *   3. raw.text / raw.result 含 ```json fenced block，剥壳后含字段
- *   4. 其余 → null
- */
-function extractVerdict(raw) {
-    if (typeof raw.refuted === 'boolean' &&
-        typeof raw.reasoning === 'string') {
-        return { refuted: raw.refuted, reasoning: raw.reasoning };
-    }
-    for (const k of ['text', 'result']) {
-        const v = raw[k];
-        if (typeof v !== 'string' || v.length === 0)
-            continue;
-        const parsed = tryParseJsonLike(v);
-        if (parsed &&
-            typeof parsed === 'object' &&
-            typeof parsed.refuted === 'boolean' &&
-            typeof parsed.reasoning === 'string') {
-            return {
-                refuted: parsed.refuted,
-                reasoning: parsed.reasoning,
-            };
-        }
-    }
-    return null;
-}
-function tryParseJsonLike(s) {
-    // 1. 直接 JSON
-    try {
-        return JSON.parse(s);
-    }
-    catch {
-        // 2. 剥 ```json ... ``` 围栏
-        const fence = s.match(/```(?:json)?\s*([\s\S]*?)```/);
-        if (fence) {
-            try {
-                return JSON.parse(fence[1].trim());
-            }
-            catch {
-                return null;
-            }
-        }
-        return null;
-    }
-}

package/skills/config/SKILL.md

@@ -1,123 +0,0 @@
----
-name: config
-description: 配置向导技能。当用户输入 "/config" 且没有任何其他内容时触发。用于重新配置 LLM provider（BASE_URL / API_KEY / MODEL）。
----
-
-# Config Skill
-
-当用户**只输入 `/config`** 时（不带任何其他内容）触发，引导用户重新配置 LLM provider。
-
-使用 Read 读现有配置（如有），逐项询问用户新值（允许保留旧值），最后用 Write 工具写入 `~/.minimal-agent/config.json`，并提示用户重启 minimal-agent 使新配置生效。
-
-⚠️ 重要：本技能仅在用户**精确输入 `/config`**（前后无任何其他文字）时触发。如果用户的消息里包含其他内容（例如 "/config 帮我看下"、"我想 /config 一下"），不要触发，按普通对话回应。
-
----
-
-## 执行步骤
-
-### Step 1: 读取现有配置
-
-调用 Read 工具：
-
-```
-Read({ file_path: "~/.minimal-agent/config.json" })
-```
-
-- 文件存在 → 解析 JSON，记住当前的 `baseURL` / `apiKey` / `model` / `provider` / `contextWindow` 字段
-- 文件不存在 → 这是首次手动配置，所有字段都是空
-
-⚠️ 注意：用户的 home 目录路径需要展开（`~` → 实际路径）。Read 工具会自动处理，但若失败，尝试用 `process.env.HOME` 或 `process.env.USERPROFILE`（Windows）拼路径。
-
-### Step 2: 逐项询问用户
-
-依次询问以下字段，每项展示当前值（若有），并明确说明可以"直接回车保留当前值"：
-
-| 字段 | 必需 | 说明 |
-|---|---|---|
-| `baseURL` | ✅ | OpenAI 兼容 API 的 base URL，如 `https://api.minimax.chat/v1` |
-| `apiKey` | ✅ | API key（敏感信息） |
-| `model` | ✅ | 模型 id，如 `MiniMax-M2.7` |
-| `provider` | ⬜ | 显示名（仅用于状态栏），默认 `env` |
-| `contextWindow` | ⬜ | 模型上下文窗口（token 数），**推荐值见下方速查表**（按 provider+model 推断） |
-| `tavilyApiKey` | ⬜ | Tavily key（WebSearch 工具用）；可留空跳过，免费 key 申请见 https://tavily.com/ |
-
-### Provider 默认值速查表（contextWindow）
-
-权威值见 `src/cli/configWizard.tsx::PRESETS`；本表是它的镜像，发现不一致以代码为准。
-
-| Provider | Model | 推荐 contextWindow |
-|---|---|---|
-| minimax | MiniMax-M2.7 / MiniMax-M1 / abab6.5s-chat | 204800 |
-| deepseek | deepseek-chat / deepseek-reasoner | 128000 |
-| openai | gpt-4o / gpt-4o-mini | 128000 |
-| moonshot | moonshot-v1-8k | 8000 |
-| moonshot | moonshot-v1-32k | 32000 |
-| moonshot | moonshot-v1-128k | 128000 |
-| volces | doubao-seed-2.0-pro / glm-5.1 / kimi-k2.6 / deepseek-v3.2 / minimax-latest | 204800 |
-| 其它 / custom | — | 128000 |
-
-⚠️ 火山方舟 ARK Coding Plan：一个 endpoint (`https://ark.cn-beijing.volces.com/api/coding/v3`) 后挂多个 model，**model 字段大小写严格匹配**（`glm-5.1` 而非 `GLM-5.1`）。常见 model id 见 `src/cli/configWizard.tsx::PRESETS` 的 `volces` 项；部分 model（如 `glm-5.1`）走 draft-2020-12 严校验，由 `src/utils/zodToJson.ts::modernizeExclusiveBounds` 透明兼容。
-
-⚠️ 询问 `contextWindow` 时，**先按上表给出推荐值并明确告诉用户**（例：「按你选的 `MiniMax-M2.7`，推荐 `contextWindow = 204800`，直接回车采纳」）。**不要让用户裸填 token 数**；用户主要关心 `baseURL` / `apiKey` / `model`，contextWindow 应优先按 provider+model 推断。
-
-如果用户改了 model 但没改 contextWindow，**主动重新计算推荐值**并提示；用户旧 contextWindow 与新 model 不匹配时（如把 model 从 `moonshot-v1-8k` 改成 `moonshot-v1-128k`），明确建议同步更新。
-
-**对话格式示例**（每次只问一个字段，等用户答完再问下一个）：
-
-```
-当前 baseURL: https://api.minimax.chat/v1
-请输入新的 baseURL（直接回车保留当前值）：
-```
-
-如果用户回车直接发空消息，保留旧值。
-
-### Step 3: 写入配置
-
-收齐所有字段后，构造完整 JSON 对象并用 Write 工具写入：
-
-```
-Write({
-  file_path: "~/.minimal-agent/config.json",
-  content: JSON.stringify({
-    baseURL: <...>,
-    apiKey: <...>,
-    model: <...>,
-    provider: <...>,
-    contextWindow: <...>,
-    tavilyApiKey: <... or 省略字段>,
-    savedAt: Date.now()
-  }, null, 2)
-})
-```
-
-字段 `savedAt` 必须是当前的 unix 毫秒时间戳。
-
-`tavilyApiKey` 字段策略：
-- 用户没有 Tavily key → **从写入的 JSON 里删掉这个字段**（不要写空串，readSavedConfig 会拒空串）。
-- 用户提供了 key → 写入字符串。
-- 用户没主动改这个字段 → **保留旧值**（不要为了"格式整洁"删除）。
-- 写入后启动注入：下次启动 minimal-agent 时 `applyToolKeysToEnv()`（`src/config.ts`）会把它注入 `process.env.TAVILY_API_KEY`，WebSearch 工具就能用了。
-
-### Step 4: 提示重启
-
-写入成功后，输出（中文）：
-
-```
-✅ 配置已更新到 ~/.minimal-agent/config.json
-
-⚠️ 当前会话仍在使用旧配置。请按以下步骤让新配置生效：
-  1. 按 Ctrl+C 退出 minimal-agent
-  2. 重新运行（bun run start / minimal-agent / bun run src/main.tsx）
-
-如果不想等重启，也可以临时 `export MINIMAL_AGENT_BASE_URL=... API_KEY=... MODEL=...`
-再重新运行 —— 环境变量始终优先于配置文件。
-```
-
----
-
-## 不做的事
-
-- ❌ 不要主动调用 LLM API 测试新配置 —— 这可能用旧配置去打新地址，混乱
-- ❌ 不要修改 `.env` 文件 —— 那是用户的私有文件，由用户自己管
-- ❌ 不要在用户输入 `/config 帮我...` 等带其他内容的消息时触发本技能
-- ❌ 不要试图"热重启"或重新加载 provider —— 重启进程是最可靠的方式

package/skills/frontend-design/LICENSE.txt

@@ -1,177 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS