writedock-mcp 0.4.2 → 0.4.6

package/README.md

@@ -1,102 +1,126 @@
 # WriteDock MCP
 
-连接用户自己的 agent 与 WriteDock 浏览器扩展。agent 写稿并准备图片或视频，本服务负责素材读取、任务转发与结果查询。平台 Cookie 留在浏览器中。
+连接你自己的 agent 与 WriteDock 浏览器扩展：agent 写稿并准备图片或视频，一次调用发布到多个平台，并按平台查询结果。
 
-## 通过 npx 连接
+MCP 运行在你自己的电脑上，只监听 `127.0.0.1`。平台 Cookie 留在浏览器里，稿件和媒体不经过 npm。
 
-电脑需要 Node.js 22+（包含 npm/npx），首次获取及更新需要能访问 npm。无需手动下载解压安装包，无需全局安装。本包运行的是本机 stdio MCP，不是远程托管服务。
+## 安装
+
+需要 Node.js 22+ 和 Chrome 或 Edge。运行：
+
+```bash
+npx -y writedock-mcp@latest setup
+```
+
+它会做两件事，并在最后告诉用户下一步：
+
+- 给本机已有的 Codex、Claude Code、Cursor、Claude Desktop 添加 MCP 配置，原文件留一份 `.writedock-backup`。已有的 WriteDock 配置不会改动。
+- 把内置的扩展放到本机固定目录。
+
+然后重启 agent，在扩展管理页打开开发者模式，加载提示中的文件夹，打开扩展点「连接」。
+
+其他客户端手动添加：
 
 ```json
 {
   "mcpServers": {
     "writedock": {
       "command": "npx",
-      "args": ["-y", "--prefer-online", "writedock-mcp@latest"],
-      "env": { "WRITEDOCK_PORT": "9647" }
+      "args": ["-y", "--prefer-online", "writedock-mcp@latest"]
     }
   }
 }
 ```
 
-Codex 的配置示例（格式依据 [OpenAI 官方 MCP 文档](https://developers.openai.com/codex/mcp/)）：
-
-```toml
-[mcp_servers.writedock]
-command = "npx"
-args = ["-y", "--prefer-online", "writedock-mcp@latest"]
-startup_timeout_sec = 120
-tool_timeout_sec = 60
-
-[mcp_servers.writedock.env]
-WRITEDOCK_PORT = "9647"
-```
-
-不同客户端按各自支持的配置格式添加。首次下载需预留启动时间；Windows 的 npx 启动命令按客户端要求处理。
-
-启动 MCP 后调用 `get_connection_status`；尚未配对时调用 `begin_pairing`，将一次性配对码粘贴到扩展的「MCP 连接」。配对码 3 分钟有效、使用一次失效。连接配置和配对阶段不提交文章；连通后按用户指定的平台和内容调用发布工具。
-
-## 更新与旧版迁移
-
-`--prefer-online` 在每次新启动时检查 npm 包的更新，相同版本可复用缓存；`latest` 指向维护者发布的版本。正在运行的进程不会自动替换，发布新版后重新加载 MCP 连接或重启相关 agent。新建聊天、刷新扩展不一定重启 MCP。
-
-从旧的 `node /安装目录/index.cjs` 迁移时，修改已有 writedock 服务的 command/args，保留原端口、`WRITEDOCK_DATA_DIR`、已有 `WRITEDOCK_TOKEN` 和其他客户端配置，停掉仍运行旧程序的 WriteDock MCP，再重新加载连接。无需删除旧程序目录或配对资料。
+首次下载较慢，请把启动超时设为 120 秒。启动后调用 `get_connection_status`；未连接时，让用户打开扩展点「连接」。
 
-身份与配对保存在用户数据目录的 `identity-端口.json`，不在程序目录或 npm 缓存里：
+## 发布
 
-- macOS：`~/Library/Application Support/WriteDock/mcp/`
-- Windows：`%LOCALAPPDATA%/WriteDock/mcp/`
-- Linux：`${XDG_DATA_HOME:-~/.local/share}/writedock/mcp/`
-
-保留同一系统用户、端口和数据目录时，npx 更新继续复用身份。旧 `WRITEDOCK_TOKEN` 仅在首次建立持久身份时迁移，资料已存在时不会覆盖。扩展更新保留浏览器配对；卸载重装扩展后用 `begin_pairing` 恢复，不需要重装 MCP。配对资料不备份浏览器稿件或 Cookie。
+优先使用 `publish`，一次调用即可：
 
-服务默认只监听 `127.0.0.1:9647`，可通过 `WRITEDOCK_PORT` 调整。Cookie、稿件与媒体不经过 npm 注册表。MCP 桥接主进程重启后，未完成的本机素材授权需要重新准备，已提交的任务先查询原 request_id，不自动重发。
-
-`npx -y --prefer-online writedock-mcp@latest --version` 只显示版本，不启动服务或读取配对资料。
+```json
+{
+  "platforms": ["zhihu", "baijiahao", "weibo", "xiaohongshu", "douyin"],
+  "article": { "file_path": "/absolute/path/article.md" },
+  "post": { "kind": "image", "title": "标题", "content": "正文", "image_paths": ["/absolute/path/1.png"] },
+  "request_id": "my_post_20261105_01"
+}
+```
 
-## 版本提示
+扩展按平台选择内容：
 
-自 v0.4.2 起，MCP 在启动后异步检查 npm latest，随后每 6 小时检查，失败后至少等待 10 分钟再试。查询只访问公开版本信息，不传送配对凭据或稿件，也不会阻塞配对、工具调用或发布任务。
+| 平台 ID | 默认发送 | 说明 |
+|---|---|---|
+| `zhihu` | 文章 | 标题最多 100 字，可内嵌本地 MP4 |
+| `baijiahao` | 文章 | 标题最多 64 字；没有 `cover` 时使用正文第一张图 |
+| `bilibili` | 文章 | 不接独立封面；LV1–3 账号每天只能发 1 篇，删除不退额度 |
+| `weibo` | 有 `post` 发图文或视频，否则发长文章 | 长文章标题最多 32 字；视频必须明确 `weibo_video_creation` |
+| `xiaohongshu` | 有 `post` 发图文或视频，否则发长文 | 长文标题最多 64 字、正文最多 10000 字 |
+| `douyin` | 图文或视频 | 不接文章 |
+| `weixin`、`sohu` | 只保存文章草稿 | 不公开发布 |
 
-`get_connection_status` 返回 `mcp_version`、可用时的 `latest_version`、`update_available`、`update_checked_at`、`update_checking` 及可选 `update_check_error`。运行版本指与扩展实际连接的本机桥接进程；多个 agent 共用端口时，不把新启动客户端的版本误当成仍占用端口的旧服务版本。
+- 用 `modes` 可为微博、小红书指定内容类型，如 `{"weibo": "article"}`。
+- 某个平台未登录、不能接收这份内容或失败时，只跳过该平台，其他平台继续。
+- 不支持的 `cover` 会被忽略，并写入该平台的 `warnings`。标题超长不会被截断，该平台直接失败。
+- 平台依次执行，全部完成通常需要几分钟。同一时间只运行一个任务。
+- 只有用户明确要求发布并指定平台时，才调用发布工具。
 
-现有 ready/ping 消息附带相同信息，扩展显示版本和更新提示。只有确定 npm 版本更新时才提醒用户重新启动 WriteDock MCP。发布任务进行中只提示，不自动重启、改配置或重新提交。旧扩展忽略新增字段；旧 MCP 未提供版本字段时显示未知。npm 查询失败不影响当前连接。
+`rehearse_publish` 参数相同，但会在点击发布之前停下，也不需要 `request_id`。可能上传图片并留下草稿，结果 `rehearsed` 不代表已发布。
 
-工具包括：`get_connection_status`、`begin_pairing`、`list_platforms`、`check_auth`、`prepare_article`、`publish_article`、`sync_article`、`prepare_post`、`publish_post`、`get_sync_task`、`list_sync_history`。
+## 查询结果
 
-小红书的三种发布方式共用 `platforms: ["xiaohongshu"]`：
+`publish` 立即返回 `task_id`，随后用 `get_sync_task` 查询，直到 `finished: true`。任务结束后，按 `summary` 逐平台告诉用户结果：
 
-| 模式 | 调用 | 说明 |
+| `summary` 分类 | 含义 | agent 应该怎么做 |
 |---|---|---|
-| 写长文 | `publish_article` | Markdown/HTML/稿件文件，支持正文图片，原生自动排版后发布；标题最多 64 字、正文最多 10000 字，不接独立 `cover`、内嵌视频或长文话题 |
-| 普通图文 | `publish_post`，`kind: "image"` | `image_paths`、标题和正文；首图作封面 |
-| 独立视频 | `publish_post`，`kind: "video"` | `video_path`、标题和简介；不传 `cover_path` 时使用平台自动生成的第一帧封面 |
-
-Agent 先看 `list_platforms` 返回的 `publishModes`、`tools`、`modeOptions` 再选入口；直接传内容即可，不要求先准备本机预览。沿用已有工具名称、参数及桥接协议，已有通用 `publish_article` / `publish_post` 的 MCP 无需因小红书增加长文而重装。工具说明源码同步更新，未改用户安装。普通图文/视频的标题、数量、格式和正文长度还受原生控件限制，不能截断或丢图后继续提交。
-
-小红书仅在匹配本任务的 `POST /web_api/sns/v2/note` 返回 HTTP 成功、`success: true`、`result: 0` 和有效笔记 ID 时确认 `submitted`。长文需先核对排版前的完整正文与插图，再核对生成图片的上传及最终长文标记。验证码、协议、封面或设置需人工处理时，Agent 把 `user_actions` 的原因和原稿件链接交给用户，在已打开的同一页处理并手动发布；不重发、不换请求 ID。本次仅完成源码接入，未运行测试、构建、打包或实际投稿。
+| `submitted` | 平台已接受提交，可能还在审核 | 汇报结果和链接 |
+| `draft_saved` | 已保存草稿 | 汇报，说明未公开发布 |
+| `rehearsed` | 演练结束，未发布 | 不得说已发布 |
+| `not_logged_in` | 未登录，未执行 | 请用户登录后，用新 `request_id` 只重发这些平台 |
+| `login_unconfirmed` | 无法确认登录状态，未执行 | 请用户检查后再提交 |
+| `waiting_verification` | 正在等用户完成验证码 | 立即转告 `user_actions` 的提示和链接，继续查询 |
+| `needs_user_action` | 需要用户在页面上处理 | 转告原因和链接，不重发 |
+| `unknown` | 结果未确认，可能已经发布 | 让用户核对，**不要重发** |
+| `failed` | 未能完成 | 汇报 `error`，必要时提供 `diagnostics` |
 
-知乎用 `publish_article` 直接发布 Agent 写好的 Markdown/HTML，参数为 file_path/markdown/html 三选一（或已准备的 draft_id）、platforms: ["zhihu"] 和稳定 request_id。可直接提交，无需在扩展编写，也无需先调用 prepare_article。支持本地 PNG/JPEG/GIF/WebP 正文图片；稿件中的 `<video src="./demo.mp4"></video>` 可插入本地 MP4，路径按稿件目录或 base_directory 解析。每篇最多 5 个视频、总量 512 MB；标题最多 100 字，独立封面和话题暂未接入。视频是文章内嵌，不是独立视频投稿。
+验证码由用户手动完成，agent 和扩展都不代做。用户完成后任务会自动更新，不需要重新提交。
 
-扩展自动完成知乎内部草稿准备，再触发页面原生发布，让平台生成动态签名；仅在发布接口返回 code=0 且文章 ID 匹配时确认 submitted。未知结果返回 unknown，不自动重发。返回 task_id 后调用 get_sync_task 查询。源码接入尚未运行测试或真实投稿。
+相同 `request_id` 和相同内容不会重复提交；内容变化必须换新 ID。部分平台失败时，只针对失败的平台用新 ID 重发，`unknown` 的平台不要重发。
 
-百家号同样使用 `publish_article`，必须提供 cover 封面（本地图片、HTTP(S) 地址或 data URI），当前接收 64 字以内标题，暂不接文章内视频。平台要求旋转验证码、其他验证码或调整封面时，任务返回 needs_user_action，顶层 requires_user_action 和 user_actions 给出原因、原稿件链接。Agent 必须把它们告诉用户，优先让用户在扩展已打开的页面完成验证并手动发布，不解验证码、不重发、不换 ID。人工接管不会被标记为提交成功，原任务也不会自动确认用户之后的操作。
+## 工具
 
-微博长文章同样用 `publish_article`，platforms: ["weibo"]；当前接收 32 字以内标题，正文支持图片、封面可选。无独立封面时使用本篇第一张正文图片，没有正文图片则需显式提供 cover。视频 URL 尚未接入。验证码、原创协议或发布设置无法核对时转人工处理；不自动关注官方账号、声明原创或同步新浪新闻。
+| 工具 | 用途 |
+|---|---|
+| `get_connection_status` | 连接状态、运行版本和更新提示 |
+| `begin_pairing` | 仅在一键连接不可用时使用：生成一次性配对码 |
+| `list_platforms`、`check_auth` | 平台能力和登录状态 |
+| `publish`、`rehearse_publish` | 一次调用发多平台，以及演练 |
+| `get_sync_task`、`list_sync_history` | 任务结果和最近 25 次记录 |
+| `prepare_article`、`prepare_post` | 可选：把稿件存到扩展里预览 |
+| `publish_article`、`publish_post`、`sync_article` | 旧版按类型发布，继续可用 |
+| `rehearse_article`、`rehearse_post` | 旧版按类型演练 |
 
-微信公众号、搜狐号暂用 `sync_article` 保存草稿。B站专栏改用 `publish_article`，平台 ID 为 `bilibili`，`platforms: ["bilibili"]` 接收 Agent 的 Markdown/HTML/文件，支持正文图片。扩展使用新版原生编辑器生成实时签名、上传图片并直接提交；不经过旧版专栏草稿接口。B站暂不接视频、视频卡片、音频或独立 cover，标题按页面实际限制校验。`code=-352` 或验证码请求返回 needs_user_action 和当前原稿件页链接，让用户在已打开的标签页验证并手动发布，Agent 不重新提交。只有匹配的 create/opus 返回 code=0 及有效字符串 dyn_id_str 才报告 submitted。B站接入沿用现有工具和平台字符串参数，不增加 MCP 工具、参数或协议，无需因此重装 MCP。微博长文章保留并接入直发。知乎、百家号、微博长文章、B站专栏旧草稿请求不会自动公开发布，需显式使用 publish_article。实际能力以 list_platforms 的 action、publishModes、capabilities、coverRequired 为准，publish_article 的平台入参不固定枚举。
+文章来源支持 `file_path`、`markdown`、`html` 三选一，图片支持 PNG/JPEG/GIF/WebP，单张 8 MB，整篇 24 MB。图文图片单张 20 MB、总量 100 MB；视频支持 MP4/MOV/WebM，最大 512 MB。实际限制还以平台页面为准。
 
-小红书、抖音、微博普通图文/独立视频用 `prepare_post` / `publish_post`。字段包括 kind（image/video）、title、content、image_paths、video_path、cover_path、tags、base_directory。路径由 agent 自动准备。图片单张 20 MB、总量 100 MB；视频最大 512 MB，支持 MP4/MOV/WebM，具体格式和数量以平台上传控件为准。视频封面可选，图文封面使用第一张图片。普通微博标题放在正文首行，最多 18 张图片；微博视频封面最多 5 MB、标题最多 30 个汉字或 60 个半角字符。
+## 已知限制
 
-抖音 `platforms: ["douyin"]` 直接复用 MultiPost-Extension 的公开页面流程，用户不需要先操作发布或抓 HAR。图文用 `kind: "image"`，独立视频用 `kind: "video"`，可选 `cover_path`。当前图文话题最多 4 个、视频最多 5 个；标题、全文和话题写入后会完整核对。仅接即时投稿，工具未提供定时发布或横竖两套封面参数。抖音以本次操作新增的原生成功提示确认 `submitted`，`list_platforms.confirmation` 为 `native_page_message`；未核对最终 HTTP 业务回执，跳转本身不算成功，没有明确提示则返回 `unknown`。验证码、声明、协议和封面问题返回 `needs_user_action`，Agent 交出原投稿页和原因，让用户在同一页处理并手动发布，不重发。本次沿用现有 `publish_post` 及桥接协议，已有此工具的 MCP 无需因此重装；仅改源码，未运行测试、构建、打包或修改用户安装。
+- 发布依赖平台页面，平台改版可能导致失败。失败结果的 `diagnostics` 含阶段、页面结构和请求路径，不含 Cookie、输入内容和 URL 查询参数。
+- 抖音只能通过页面提示确认结果，没有接口回执，遇到验证码时直接交给用户。
+- 除 B站外，其他平台的验证码流程尚未在真实验证码上验证过。
+- 视频发布已走到发布前，但尚未真实发布验证。
+- `submitted` 不跟踪之后的审核结果。
 
-微博视频必须明确 `weibo_video_creation: original | secondary | repost`（原创/二创/转载），不得默认声明原创。此参数会保存到本机稿件并参与请求去重。若需补充来源、原视频关联、内容声明、分类、封面或验证码，返回 needs_user_action 及原投稿页链接，Agent 告诉用户在已打开的页面手动处理并发布，不重新提交。只有匹配本任务的 statuses/update 成功回执才确认微博 submitted；视频回执可能不带帖子 ID，不因此编造 ID。微博长文章继续用 publish_article，三种格式共用 weibo 这个平台 ID。
+## 更新
 
-先用 `prepare_post` 存本机预览，返回 draft_id；再向 `publish_post` 传 draft_id、request_id 和 platforms（xiaohongshu/douyin/weibo）。也可直接向 publish_post 提供全部内容与素材。该工具会打开平台原生页面并点击发布，必须以用户明确的发布要求和目标平台为依据。publish_post 的平台参数改为由扩展实际能力校验，不在 MCP 中固定枚举。
+- **MCP：** `--prefer-online` 在每次启动时检查新版，运行中的进程不会自动替换，重启 agent 即可。发布任务进行中不要重启。
+- **扩展：** 新版 MCP 内置更新的扩展时，扩展的「连接 agent」页会出现「更新扩展」。用户点一下，MCP 覆盖扩展目录，扩展自行重新加载；发布任务进行中不能更新。
 
-所有提交都需要稳定的 `request_id`，返回 `task_id` 后用 `get_sync_task` 跟进。同 ID 的相同请求复用原任务，不能用同 ID 发布不同内容。Agent 只使用 WriteDock MCP，不依赖浏览器或 Playwright 工具。打开平台原生投稿页及操作由扩展完成。任务返回 finished、next_action、results、agent_instructions；poll_task 按原 ID 继续查询，report_result 汇报逐平台结果和链接。submitted/published 后不再打开网站验证；验证码、图形验证、unknown 或 interrupted 时，把 user_actions 中的原因和链接交给用户自行点击处理，不自动换 ID 重试。submitted 表示平台接受提交，是否公开展示以平台审核为准。
+连接资料保存在用户数据目录的 `identity-端口.json`：
 
-本地视频不嵌入 MCP 消息，而是通过随机授权、绑定具体文件的本机 HTTP 范围请求分块传输。授权两小时有效，MCP 桥接主进程重启后重新准备素材；文件变更会拒绝读取。从旧版使用新增 publish_article 或 prepare_post/publish_post 工具时，原位升级本 MCP 一次并重启，保留 agent 配置和已有配对资料。
+- macOS：`~/Library/Application Support/WriteDock/mcp/`
+- Windows：`%LOCALAPPDATA%/WriteDock/mcp/`
+- Linux：`${XDG_DATA_HOME:-~/.local/share}/writedock/mcp/`
 
-本次微博接入新增创作类型参数，并放开 publish_post 的固定平台枚举，启用新版时需原位更新 MCP 程序一次。后续同类平台增删由扩展校验，避免每次改平台枚举；保留安装位置、启动配置和配对资料，无需卸载重装。本版本提供可通过 npx 启动的构建包，未进行真实平台投稿验证。
+卸载重装扩展后，在扩展里再点一次「连接」即可，不需要重装 MCP。`npx -y writedock-mcp@latest --version` 只显示版本。
 
-对应源码位于 npm 包内 `source/`，可在该目录安装开发依赖并运行构建命令。第三方依赖许可见 `THIRD_PARTY_NOTICES.txt`，本服务遵循 GPL-3.0-only，见 `LICENSE` 与 `NOTICE.md`。
+对应源码位于包内 `source/`。本服务遵循 GPL-3.0-only，见 `LICENSE`、`NOTICE.md` 和 `THIRD_PARTY_NOTICES.txt`。

package/extension/LICENSE-MULTIPOST.txt

@@ -0,0 +1,201 @@
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.