coding-proxy 0.1.0__tar.gz

coding_proxy-0.1.0/.github/workflows/promote.yml

@@ -0,0 +1,163 @@
+# =============================================================================
+# coding-proxy: Prerelease → Stable Promotion Workflow
+# =============================================================================
+# Trigger: Manual workflow_dispatch with tag_name input
+# Purpose: Promote a validated TestPyPI prerelease to PyPI production
+#
+# Flow:
+#   Job 1 (validate): Verify target release exists AND is a prerelease
+#   Job 2 (promote):  Update GitHub Release metadata + build/publish to PyPI
+#
+# Safety Guarantees:
+#   - Refuses to promote non-prerelease releases (idempotency guard)
+#   - Uses environment: pypi for deployment approval gate (human gate)
+#   - Concurrency group prevents simultaneous promotions of same tag
+#   - Rebuilds from git tag for deterministic, reproducible artifacts
+#
+# Paired with: release.yml (initial release creation)
+#
+# Pre-requisites (same auth options as release.yml):
+#   Option A — OIDC Trusted Publishing:
+#     1. Create GitHub Environment: "pypi" with required reviewers
+#     2. Configure Trusted Publisher on PyPI admin panel
+#   Option B — API Token Fallback:
+#     1. Set repository secret: PYPI_API_TOKEN
+#     2. (Optional) Create "pypi" environment for deployment guards
+#
+# References:
+#   [1] https://docs.github.com/en/rest/releases/releases#update-a-release
+#   [2] https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
+# =============================================================================
+
+name: Promote Prerelease to PyPI
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag_name:
+        description: '待提升的 prerelease tag（如 v0.2.0a1）'
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+concurrency:
+  group: promote-${{ inputs.tag_name }}
+  cancel-in-progress: false
+
+jobs:
+  # ===========================================================================
+  # Job 1: VALIDATE -- Confirm release exists and is a prerelease
+  # ===========================================================================
+  validate:
+    name: Validate prerelease status
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+
+    steps:
+      - name: Check release exists and is a prerelease
+        uses: actions/github-script@v7
+        id: check-release
+        with:
+          script: |
+            const tag = context.payload.inputs.tag_name;
+            const { owner, repo } = context.repo;
+
+            const release = await github.rest.releases.getReleaseByTag({
+              owner,
+              repo,
+              tag,
+            });
+
+            const isPrerelease = release.data.prerelease;
+            const releaseId = release.data.id;
+            const tagName = release.data.tag_name;
+
+            if (!isPrerelease) {
+              core.setFailed(
+                `Release ${tagName} is NOT a prerelease. ` +
+                `Only prereleases can be promoted to stable.`
+              );
+            }
+
+            core.setOutput('release_id', releaseId);
+            core.setOutput('tag_name', tagName);
+            core.info(`✅ Validated: release #${releaseId} (${tagName}) is a prerelease`);
+
+  # ===========================================================================
+  # Job 2: PROMOTE -- Update release + publish to PyPI Production
+  # ===========================================================================
+  promote:
+    name: Promote to PyPI Production
+    runs-on: ubuntu-latest
+    needs: validate
+    timeout-minutes: 15
+    environment:
+      name: pypi
+      url: https://pypi.org/p/coding-proxy
+    permissions:
+      contents: write   # 更新 Release 元数据所需
+      id-token: write   # OIDC Trusted Publishing 所需
+
+    steps:
+      # -----------------------------------------------------------------------
+      # Step 1: 检出精确的 git tag 用于确定性重建
+      # -----------------------------------------------------------------------
+      - name: Checkout repository at release tag
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ needs.validate.outputs.tag_name }}
+          persist-credentials: false
+
+      # -----------------------------------------------------------------------
+      # Step 2: 更新 GitHub Release: prerelease=false, make_latest=true
+      # -----------------------------------------------------------------------
+      - name: Promote release to stable
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const releaseId = ${{ needs.validate.outputs.release_id }};
+            const { owner, repo } = context.repo;
+
+            await github.rest.releases.update({
+              owner,
+              repo,
+              release_id: releaseId,
+              prerelease: false,
+              make_latest: true,
+            });
+
+            core.notice(
+              `✅ Release #${releaseId} promoted to stable (make_latest=true)`
+            );
+
+      # -----------------------------------------------------------------------
+      # Step 3: 从 tagged source 构建分发包
+      # -----------------------------------------------------------------------
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+
+      - name: Install build dependencies
+        run: uv pip install --system build twine
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      - name: Check package metadata
+        run: twine check dist/*
+
+      # -----------------------------------------------------------------------
+      # Step 4: 发布到 PyPI Production
+      # -----------------------------------------------------------------------
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

coding_proxy-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,151 @@
+# =============================================================================
+# coding-proxy: PyPI Publishing Workflow (Initial Release)
+# =============================================================================
+# Trigger: GitHub Release publication event
+# Architecture: Build-Publish Separation (PyPA security best practice)
+#   Paired with: promote.yml (prerelease → stable promotion gate)
+#   - Job 1 (build): Low privileges, produces sdist+wheel artifacts
+#   - Job 2 (publish-testpypi): Publish to TestPyPI (prereleases only)
+#   - Job 3 (publish-pypi): Publish to PyPI (stable releases / hotfixes)
+#
+# Routing Logic:
+#   - prerelease == true  --> TestPyPI (with skip-existing tolerance)
+#                          --> THEN use promote.yml to promote to PyPI after validation
+#   - prerelease == false --> PyPI production (direct stable release, e.g. hotfixes)
+#
+# Promotion Flow (see promote.yml):
+#   1. Create release with prerelease: true  --> builds + publishes to TestPyPI
+#   2. Human validates package on TestPyPI
+#   3. Run promote.yml (workflow_dispatch)  --> promotes to PyPI production
+#
+# Pre-requisites (choose ONE authentication method):
+#
+#   Option A — OIDC Trusted Publishing (recommended, no secrets needed):
+#     1. Create GitHub Environments: "pypi" and "testpypi"
+#     2. Configure Trusted Publishers on PyPI/TestPyPI admin panels
+#     3. (Recommended) Set "Required reviewers" on "pypi" environment
+#
+#   Option B — API Token Fallback (simpler initial setup):
+#     1. Set repository secrets: PYPI_API_TOKEN and/or TEST_PYPI_API_TOKEN
+#     2. (Optional) Create "pypi"/"testpypi" environments for deployment guards
+#        If environments are not created, remove the `environment:` blocks below.
+#
+# References:
+#   [1] https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
+#   [2] https://github.com/pypa/gh-action-pypi-publish
+#   [3] https://docs.pypi.org/trusted-publishers/using-a-publisher/
+# =============================================================================
+
+name: Release / Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  # ===========================================================================
+  # Job 1: BUILD -- Produce distribution artifacts (low privilege isolation)
+  # ===========================================================================
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+
+      - name: Install build dependencies
+        run: uv pip install --system build twine
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      - name: Check package metadata
+        run: twine check dist/*
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          retention-days: 14
+
+  # ===========================================================================
+  # Job 2: PUBLISH TO TESTPYPI -- Prerelease / staging releases only
+  # ===========================================================================
+  publish-testpypi:
+    name: Publish to TestPyPI
+    runs-on: ubuntu-latest
+    needs: build
+    if: github.event.release.prerelease == true
+    timeout-minutes: 10
+    environment:
+      name: testpypi
+      url: https://test.pypi.org/p/coding-proxy
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.TEST_PYPI_API_TOKEN }}
+          repository-url: https://test.pypi.org/legacy/
+          skip-existing: true
+          attestations: false    # TestPyPI 不支持 attestations，必须显式禁用
+          verbose: true         # 启用详细日志以获取 400 错误响应体
+
+  # ===========================================================================
+  # Job 3: PUBLISH TO PYPI -- Production releases only
+  # ===========================================================================
+  publish-pypi:
+    name: Publish to PyPI
+    runs-on: ubuntu-latest
+    needs: build
+    if: github.event.release.prerelease == false
+    timeout-minutes: 10
+    environment:
+      name: pypi
+      url: https://pypi.org/p/coding-proxy
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

coding_proxy-0.1.0/.gitignore

@@ -0,0 +1,17 @@
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+*.db
+*.sqlite
+*.egg-info/
+dist/
+build/
+*.whl
+.uv/
+
+# Custom
+.idea/
+.temp/
+config.yaml
+.claude/.prompts.md

coding_proxy-0.1.0/AGENTS.md

@@ -0,0 +1,82 @@
+# AGENTS.md
+
+## Collaboration Protocol (协作协议)
+
+本文件旨在规范 AI Agent（Claude Code、Antigravity 等）在本项目中的代码与文档协作行为。
+
+- **Core Language**: Output MUST be in **Chinese (Simplified)** unless serving code/technical constraints.
+- **Tone**: Professional, precise, and evidence-based.
+
+## Project Positioning (项目定位)
+
+参考 README.md
+
+## Engineering Code of Conduct (工程行为准则)
+
+**Core Philosophy**: **Entropy Reduction (熵减)**. 通过上下文锚定、复用驱动与标准化流水线，对抗软件系统的无序熵增。
+
+### 道 (Mindset - 认知心法)
+
+- **Context-Driven (上下文驱动)**: 上下文是第一性要素 (Context Quality First)。任何变更需建立在深度理解之上（CDD），拒绝基于关键字匹配的机械式修改。
+- **Minimal Intervention (最小干预)**: 遵循奥卡姆剃刀与 YAGNI 原则，仅实施必要的变更，推崇演进式设计 (Evolutionary Design) 而非过度设计。
+- **Evidence-Based (循证工程)**: 杜绝主观臆断，核心决策需以权威文献（IEEE 格式）为佐证，构建 Feedback Loops 以验证假设。
+- **Systemic Integrity (系统完整性)**: 具备全局视角与二阶思维 (Second-Order Thinking)，评估变更对上下游依赖及整个生态（Engine, Adapter, Agent, UI）的“涟漪效应”，优先保障整体稳定性与逻辑自洽。
+
+### 法 (Strategy - 架构原则)
+
+- **Plan Node Default (默认规划模式)**: 面对任何非琐碎任务（预估步骤 > 3 或涉及架构级决策），**必须**率先进入 Plan 模式。规划产物需明确界定：功能边界、边缘 Case 应对策略、与现有逻辑的交互锚点以及预计改动的爆炸半径。
+- **Subagent Strategy (子代理并发策略)**: 面对高复杂度命题，严禁主 Agent 单点统揽。应贯彻“算力换空间”思路，果断编排 Subagent 进行任务拆解与并行攻坚，主 Agent 的职责需严格收敛于上下文协同与最终成果的组装整合。
+- **Verification Before Done (交付前验证定式)**: 严禁在缺乏确凿运行证据的情况下标记任务为“已完成”。交付阶段**强制要求**提供客观自证材料：Diff 变更分析、测试用例覆盖、实施日志截图及核心链路边缘 Case 验证结果，并时刻以“方案是否能通过 Staff Engineer 严格审查”的视角自检。
+- **Reuse-Driven (复用驱动)**: Composition over Construction。系统变更**必须**主动参考业界经典设计模式与最佳实践。在进入实质性编码前，需率先对相关领域的成熟范式进行深度调研，并结合当前项目上下文输出充分的关联分析与方案梳理。坚决贯彻“拿来主义”，优先通过组合与集成来构建系统，防范闭门造车与重复造轮子。
+- **Boundary Management (边界管理)**: 严控模块/Agent 间的职责边界与契约，确保高内聚低耦合，防范隐式依赖穿透。
+- **Orthogonal Decomposition (正交分解)**: 坚持“正交地提取概念主体”。识别系统中独立变化的维度并进行解耦（如机制与策略分离），确保单一概念主体的变更具备局部性，避免逻辑纠缠。
+- **Feedback Loops (反馈闭环)**：构建“设计-实现-验证”的完整闭环，确保每一项工程行动都能产生可观测的反馈信号（测试、日志、监控），以验证假设并指导迭代。
+- **Evolutionary Design (演进式设计)**: 将系统视为有机体，通过将 AI 错误转化为经验约束 (Negative Prompts) 和持久化知识，实现系统的自我进化与熵减。
+- **Second-Order Thinking (二阶思维)**：不只关注变更的直接结果，更要预测“结果的结果”（如引入缓存导致的陈旧数据、重试机制引发的雪崩），未雨绸缪防范隐性风险。
+- **Single Source of Truth (单一事实源)**：严格维护唯一的权威定义源。引用时**必须**使用轻量级指针 (Link/ID) 而非数据副本 (Copy-Paste)，从根源消除断裂 (Split-Brain) 风险。
+- **Proactive Navigation (主动导航)**: 智能体不应止步于被动响应，需即时转化为“领航者”。在交付任务结果的同时，**必须**基于上下文预判并提出**下一步最佳行动建议 (Next Best Action)**。不仅交付“答案”，更要交付“路径”，消除用户决策的认知摩擦，确保持续的熵减动量。
+
+### 术 (Tactics - 执行规范)
+
+- **Vibe Coding Pipeline**: 遵循 **Specification-Driven (规划驱动)** + **Context-Anchored (上下文锚定)** + **AI-Pair (AI 结对)** 模式，将开发固化为可审计的流水线，避免代码腐化为无法维护的“大泥球 (Big Ball of Mud)”。
+- **Visual Documentation (图文并茂)**: 对于复杂逻辑，优先使用 Mermaid 图表（Sequence/Flowchart/Class）辅助说明，构建“图文并茂”的直观文档。
+- **Direct Hyperlinking (直接跳转)**: 在文档中提及 Repo 内其他资源（文档/代码）时，**必须**构建可跳转的相对路径链接（如 `[Doc Name](./path.md)`），严禁使用“死文本”引用，以降低信息检索熵。
+- **Operational Excellence (卓越运营)**:
+  1. **Git Hygiene**: 如非显性要求，严禁调用 git commit；
+  2. **Temp Management**: 临时产物（执行计划等）一律收敛至 `.temp/` 并及时清理；
+  3. **Link Validity**: 确保所有引用的 URL 可访问且具备明确的上下文价值；
+  4. **Git Commit**: 在需要提交变更到 Git 时，一律使用 Shell 调用 Claude Code 的自定义 Slash Command: `/commit` 进行 git commit 操作（若环境中未安装 Claude Code，则直接读取 `~/.claude/commands/commit.md`，按照其中的规则进行 git commit 操作）。不要执行 Rebase。
+- **Package Management Standardization (包管理规范)**:
+  1. **Python**: 严禁使用 pip/poetry，**必须**统一使用 `uv` 进行包管理与脚本执行（如 `uv run`）；
+  2. **JavaScript/TypeScript**: 严禁使用 npm/yarn，**必须**统一使用 `pnpm` 进行包管理与脚本执行。
+- **Database Management**: 谨慎操作，数据迁移、测试等操作严禁将现有数据删除。
+
+## Documentation Standards (文档规范)
+
+### Mermaid Visualization Norms (Mermaid 可视化规范)
+
+- **色彩语义与兼容性**：为图表节点配置具备语义辨识度的色彩，并确保在深色模式（Dark Mode）下具有极高的对比度与清晰度。
+- **逻辑模块化解构**：针对业务跨度较大的架构流程，强制采用 `subgraph` 容器进行层级解构与边界划分，以增强图表的自解说（Self-explaining）能力。
+
+### Reference Specifications (IEEE)
+
+为保障工程决策的可追溯性与学术严谨性，核心引用需遵循 **IEEE 标准引用格式**。
+
+> **模版准则**：[编号] 作者缩写. 姓, "文章标题," _刊名/会议名缩写 (斜体)_, 卷号, 期数, 页码, 年份.
+
+```latex
+[1] A. Author, B. Author, and C. Author, "Title of paper," *Abbrev. Title of Journal*, vol. X, no. Y, pp. XX–XX, Year.
+```
+
+**引用实践**
+
+- **文内锚定**：采用标准上标链接形式：`描述内容<sup>[[1]](#ref1)</sup>`。
+- **文献索引**：底层采用 HTML 锚点 `id` 实现跳转稳定性。
+
+```latex
+<a id="ref1"></a>[1] A. Vaswani et al., "Attention is all you need," Adv. Neural Inf. Process. Syst., vol. 30, pp. 5998–6008, 2017.
+```
+
+## Knowledge Map (知识索引)
+
+(WIP)

coding_proxy-0.1.0/CHANGELOG.md

@@ -0,0 +1,34 @@
+# Changelog
+
+本文件基于 [Keep a Changelog](https://keepachangelog.com/zh-CN/) 规范维护，版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
+
+## [Unreleased]
+
+## [v0.1.0] — 2026-04-05
+
+### ✨ 亮点特性
+
+> **coding-proxy MVP 版本发布！** 一行环境变量，让 Claude Code 拥有永不宕机的多后端智能代理——主服务故障时毫秒级自动切换至备用通道，编码心流零中断。
+
+| 特性                   | 价值                                                                                                     |
+| :--------------------- | :------------------------------------------------------------------------------------------------------- |
+| **N-tiers 故障转移**   | 灵活编排的供应商优先级与降级链路；<br/>默认 Claude → GitHub Copilot → Antigravity → GLM 全链路自动降级； |
+| **智能熔断器**         | 状态机防护雪崩，指数退避自动恢复；                                                                       |
+| **Token 用量成本看板** | SQLite 本地存储，CLI 多维统计（按天/供应商/模型）；                                                      |
+| **OAuth2 内置集成**    | GitHub Device Flow / Google OAuth 开箱即用，令牌自动轮转；                                               |
+| **协议双向转换**       | Anthropic ↔ OpenAI/Gemini 双向无缝翻译；                                                                 |
+| **模型名自助映射**     | 自定义模型转发规则，`claude-*` → `glm-*` 一键切；                                                        |
+| **零侵入轻量透明代理** | 开箱即用，配置 `ANTHROPIC_BASE_URL` 即接入，FastAPI 异步架构，交互全透明；                               |
+| **SSE 流式全链路**     | 流式请求完整透传，跨协议 SSE 转换零感知；                                                                |
+| **双窗口配额守卫**     | 5h 滑动窗口 + 周配额双重护盾，超额前主动预警；                                                           |
+
+### 🔧 更多特性
+
+- 模型定价表支持，按供应商/模型细粒度成本追踪；
+- 指数退避重试机制，可配置最大重试次数与退避策略；
+- Vendor 自动兼容性降级决策；
+- 速率限制头解析与智能等待，精确计算恢复时间；
+- Copilot 421 Misdirection 自动重试；
+- 优雅停机与资源清理，进程退出无残留；
+
+[0.1.0]: https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.1.0

coding_proxy-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

coding_proxy-0.1.0/LICENSE

@@ -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.