@caddis/cli 0.0.0 → 0.2.0

package/bundles/antigravity-plugin-extras/skills/architecture-diagram/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: architecture-diagram
+description: Generate dark-themed technical architecture diagrams as self-contained HTML/SVG files. No external libraries or render tools needed — just a browser. Use for software system architecture, cloud infrastructure, microservice topologies, and deployment diagrams.
+source: NousResearch/hermes-agent
+---
+
+# Architecture Diagram
+
+Generate professional dark-themed architecture diagrams as standalone HTML files with embedded SVG. Browser-only — no Graphviz, no Mermaid renderer, no server required.
+
+**Not suitable for**: scientific subjects, physical objects, floor plans, hand-drawn aesthetics — use `excalidraw` or `draw-io` for those.
+
+## When to Use
+
+Load this skill when users ask for:
+- System architecture or component diagrams
+- Cloud infrastructure diagrams (AWS/Azure/GCP)
+- Microservice topology maps
+- API and database relationship diagrams
+- Deployment diagrams
+
+Complements `architecture-design` (planning/notation) — use that first, then use this skill to produce the rendered output artifact.
+
+## Semantic Color System
+
+Map every component to a type, then apply these colors consistently:
+
+| Component Type | Stroke | Fill |
+|----------------|--------|------|
+| Frontend | `#22d3ee` | `rgba(8, 51, 68, 0.4)` |
+| Backend / Service | `#34d399` | `rgba(6, 78, 59, 0.4)` |
+| Database | `#a78bfa` | `rgba(76, 29, 149, 0.4)` |
+| Cloud / AWS | `#fbbf24` | `rgba(120, 53, 15, 0.3)` |
+| Security / Auth | `#fb7185` | `rgba(136, 19, 55, 0.4)` |
+| Message Bus / Queue | `#fb923c` | `rgba(251, 146, 60, 0.3)` |
+| External / Third-party | `#94a3b8` | `rgba(30, 41, 59, 0.5)` |
+
+## Canvas & Typography
+
+- **Background**: `#020617` (slate-950) with a 40px grid pattern using `rgba(148, 163, 184, 0.05)` lines
+- **Font**: JetBrains Mono from Google Fonts (`wght@400;500;700`)
+  - Component labels: 12px weight 500
+  - Section/group titles: 14px weight 700
+  - Annotations: 7–9px weight 400
+- **Stroke width**: 1.5px on all component boxes
+
+## SVG Structure Rules
+
+### Render Order (critical)
+Render in this exact sequence to avoid transparency bleed-through:
+1. Background + grid
+2. Region/security boundary containers (dashed)
+3. **Connection arrows** ← must come before components
+4. Component boxes
+5. Component labels
+6. Legend
+
+### Double-Rect Masking (required for all component boxes)
+Prevents arrow lines from showing through filled shapes:
+```svg
+<!-- 1. opaque background rect (clips arrow lines) -->
+<rect x="X" y="Y" width="W" height="H" rx="6"
+      fill="#020617" stroke="none"/>
+<!-- 2. semi-transparent styled rect on top -->
+<rect x="X" y="Y" width="W" height="H" rx="6"
+      fill="FILL_COLOR" stroke="STROKE_COLOR" stroke-width="1.5"/>
+<!-- 3. label -->
+<text x="X+W/2" y="Y+H/2+4" text-anchor="middle"
+      font-family="JetBrains Mono" font-size="12" font-weight="500"
+      fill="STROKE_COLOR">Component Name</text>
+```
+
+### Arrowheads
+Define in `<defs>`:
+```svg
+<defs>
+  <marker id="arrow-cyan" markerWidth="8" markerHeight="6"
+          refX="7" refY="3" orient="auto">
+    <polygon points="0 0, 8 3, 0 6" fill="#22d3ee"/>
+  </marker>
+  <!-- repeat for each stroke color used -->
+</defs>
+```
+Use `marker-end="url(#arrow-cyan)"` on connection lines.
+
+### Security Boundaries & Regions
+Use dashed strokes for grouping boxes:
+```svg
+<rect x="X" y="Y" width="W" height="H" rx="8"
+      fill="rgba(251,113,133,0.05)" stroke="#fb7185"
+      stroke-width="1" stroke-dasharray="6,3"/>
+<text font-size="11" font-weight="700" fill="#fb7185" opacity="0.7">
+  Security Zone
+</text>
+```
+
+### Legend
+Always position below all boundary boxes, never overlapping content:
+```svg
+<!-- Legend box -->
+<rect x="20" y="BOTTOM+20" width="320" height="..." rx="6"
+      fill="rgba(148,163,184,0.05)" stroke="rgba(148,163,184,0.2)" stroke-width="1"/>
+<!-- Legend entries: color dot + label -->
+<circle cx="36" cy="Y" r="5" fill="#22d3ee"/>
+<text x="48" y="Y+4" fill="#94a3b8" font-size="10">Frontend</text>
+```
+
+## Output Format
+
+Single self-contained HTML file:
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <title>Architecture — [System Name]</title>
+  <link href="https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
+  <style>
+    body { margin: 0; background: #020617; display: flex; justify-content: center; padding: 24px; }
+    svg { max-width: 100%; height: auto; }
+  </style>
+</head>
+<body>
+  <svg viewBox="0 0 WIDTH HEIGHT" xmlns="http://www.w3.org/2000/svg">
+    <!-- defs: markers, grid pattern -->
+    <!-- background + grid -->
+    <!-- boundary containers -->
+    <!-- connection arrows -->
+    <!-- component boxes (double-rect) -->
+    <!-- legend -->
+  </svg>
+</body>
+</html>
+```
+
+## Sizing Guidelines
+
+| Diagram complexity | viewBox width | Component box |
+|--------------------|---------------|---------------|
+| Simple (< 8 nodes) | 900px | 140 × 50px |
+| Medium (8–20 nodes) | 1200px | 140 × 50px |
+| Large (20+ nodes) | 1600px | 120 × 45px |
+
+Minimum padding from SVG edge: 40px. Minimum gap between components: 30px.
+
+## Checklist Before Saving
+
+- [ ] All component boxes use double-rect masking
+- [ ] Arrows are drawn before component boxes in SVG order
+- [ ] Every component type uses its semantic color
+- [ ] Legend present and positioned below all content
+- [ ] Security/region boundaries use dashed strokes
+- [ ] No external JS libraries (pure SVG + CSS only)
+- [ ] JetBrains Mono loaded from Google Fonts CDN
+- [ ] File is a single self-contained HTML — open in browser to verify

package/bundles/antigravity-plugin-extras/skills/architecture-document/SKILL.md

@@ -0,0 +1,321 @@
+---
+name: architecture-document
+context: fork
+description: Generate professional enterprise-grade HLD and LLD documents from the living Architecture.md. Outputs DOCX (editable) or PPTX (executive summary) using existing document skills.
+---
+
+# Architecture Document Generator
+
+Produce formal **High-Level Design (HLD)** and **Low-Level Design (LLD)** documents from the project's living `docs/Architecture.md` and codebase.
+
+> **Project Context** — Read `project-config.md` for brand tokens, org name, tech stack, and project metadata used in document headers.
+> **Document metadata** — Any Markdown companion doc or source doc created or updated in this workflow must follow `.github/instructions/document-frontmatter.instructions.md`. For DOCX/PPTX deliverables, mirror the same author/date/model fields on the cover page or revision history.
+
+## When to Load This Skill
+
+- Stakeholder requests a formal architecture deliverable
+- Audit or compliance review requires documented HLD/LLD
+- Onboarding pack for new team members
+- Architecture review board submission
+- Project milestone that requires design documentation
+
+## Prerequisites
+
+Before generating, ensure:
+1. `docs/Architecture.md` exists and is current (the `@architect` agent maintains this)
+2. Architecture diagrams exist in `docs/architecture/*.drawio` (or `.png` exports)
+3. `project-config.md` has a profile set (for org name, tech stack, branding)
+
+## Output Formats
+
+| Format | Skill to Load | Best For |
+|--------|---------------|----------|
+| **DOCX** (recommended) | `.github/skills/document-skills/docx/SKILL.md` | Full HLD/LLD — editable, ToC, numbered sections |
+| **PPTX** | `.github/skills/document-skills/pptx/SKILL.md` | Executive summary / architecture overview deck |
+| **PDF** | `.github/skills/document-skills/pdf/SKILL.md` | Final read-only distribution (generate from DOCX) |
+
+---
+
+## HLD — High-Level Design
+
+### Document Structure
+
+```
+COVER PAGE
+    Project: <APP_TITLE>
+    Organization: <ORG_NAME>
+    Document Type: High-Level Design (HLD)
+    Version: {from Architecture.md front-matter or git tag}
+    Date: {current date}
+    Author: {architect or team}
+    Status: Draft | Under Review | Approved
+    Classification: Internal | Confidential
+
+REVISION HISTORY
+    | Version | Date | Author | Changes |
+
+APPROVAL TABLE
+    | Role | Name | Signature | Date |
+
+TABLE OF CONTENTS (auto-generated)
+
+§1  INTRODUCTION
+    §1.1  Purpose
+    §1.2  Scope
+    §1.3  Audience
+    §1.4  References & Related Documents
+    §1.5  Glossary & Abbreviations
+
+§2  EXECUTIVE SUMMARY
+    - Business context (1-2 paragraphs)
+    - Solution overview (1-2 paragraphs)
+    - Key architectural decisions summary
+
+§3  SYSTEM CONTEXT
+    §3.1  System Context Diagram (C4 Level 1)
+    §3.2  External Systems & Interfaces
+    §3.3  User Roles & Access Patterns
+    §3.4  Data Sources
+
+§4  ARCHITECTURE OVERVIEW
+    §4.1  Architecture Style & Patterns
+    §4.2  Component Architecture Diagram (C4 Level 2)
+    §4.3  Component Descriptions
+          (table: Component | Responsibility | Technology | Interfaces)
+    §4.4  Technology Stack Summary
+
+§5  DATA ARCHITECTURE
+    §5.1  Data Flow Diagram
+    §5.2  Data Sources & Stores
+    §5.3  Data Integration Patterns
+    §5.4  Data Retention & Archival
+
+§6  INTEGRATION ARCHITECTURE
+    §6.1  Integration Patterns (sync/async, push/pull)
+    §6.2  API Overview (endpoints, protocols)
+    §6.3  External System Interfaces
+    §6.4  Message Flows / Event Flows
+
+§7  DEPLOYMENT ARCHITECTURE
+    §7.1  Deployment Diagram
+    §7.2  Infrastructure Components
+    §7.3  Environment Strategy (Dev/UAT/Prod)
+    §7.4  Scaling & High Availability
+
+§8  SECURITY ARCHITECTURE
+    §8.1  Authentication & Authorization
+    §8.2  Data Protection (at rest, in transit)
+    §8.3  Network Security
+    §8.4  Compliance Requirements
+
+§9  NON-FUNCTIONAL REQUIREMENTS
+    §9.1  Performance Targets
+    §9.2  Availability & Reliability
+    §9.3  Scalability
+    §9.4  Maintainability
+    §9.5  Observability (logging, monitoring, alerting)
+
+§10  ARCHITECTURAL DECISIONS
+    §10.1  Key Decisions Log (ADR summary table)
+    §10.2  Alternatives Considered
+    §10.3  Constraints & Trade-offs
+
+§11  RISKS & MITIGATIONS
+    (table: Risk | Likelihood | Impact | Mitigation)
+
+§12  APPENDICES
+    §A  Full Diagram Index
+    §B  Glossary
+    §C  Referenced Documents
+```
+
+### Content Sourcing
+
+| HLD Section | Source |
+|-------------|--------|
+| §1 Introduction | `project-config.md` (org, tech stack) + `README.md` |
+| §2 Executive Summary | `docs/Architecture.md` introduction/overview |
+| §3 System Context | `docs/Architecture.md` context sections + `docs/architecture/system-context.drawio` |
+| §4 Architecture Overview | `docs/Architecture.md` component sections + diagrams |
+| §5 Data Architecture | `docs/Architecture.md` data sections + `project-config.md` data sources |
+| §6 Integration | `docs/Architecture.md` API/integration sections |
+| §7 Deployment | `docs/Architecture.md` deployment sections + `project-config.md` deploy env |
+| §8 Security | `docs/Architecture.md` security sections + `project-config.md` compliance |
+| §9 NFRs | `docs/Architecture.md` NFR sections |
+| §10 Decisions | `docs/architecture/` ADR files or decisions section |
+| §11 Risks | `docs/Architecture.md` risks section (or flag if missing) |
+
+---
+
+## LLD — Low-Level Design
+
+### Document Structure
+
+```
+COVER PAGE (same format as HLD, Document Type: Low-Level Design)
+REVISION HISTORY
+APPROVAL TABLE
+TABLE OF CONTENTS
+
+§1  INTRODUCTION
+    §1.1  Purpose
+    §1.2  Scope (which HLD components this LLD covers)
+    §1.3  HLD Reference (link to HLD document + version)
+
+§2  MODULE DESIGN
+    §2.1  Module Overview Diagram
+    §2.2  Module Descriptions
+          For each module:
+          - Responsibility
+          - Public interface (functions/methods/endpoints)
+          - Dependencies (internal + external)
+          - Configuration
+
+§3  DATA MODEL
+    §3.1  Entity Relationship Diagram
+    §3.2  Table Definitions
+          (table: Table | Columns | Types | Constraints | Indexes)
+    §3.3  Data Validation Rules
+    §3.4  Migration Strategy
+
+§4  API DESIGN
+    §4.1  API Endpoints
+          (table: Method | Path | Request | Response | Auth | Rate Limit)
+    §4.2  Request/Response Schemas (with examples)
+    §4.3  Error Codes & Handling
+    §4.4  Versioning Strategy
+
+§5  SEQUENCE DIAGRAMS
+    §5.1  Key User Flows
+          (one sequence diagram per critical flow)
+    §5.2  Error / Edge Case Flows
+    §5.3  Background Process Flows
+
+§6  CLASS / MODULE STRUCTURE
+    §6.1  Package/Module Hierarchy
+    §6.2  Key Classes & Responsibilities
+    §6.3  Design Patterns Used
+    §6.4  Dependency Injection / Configuration
+
+§7  CACHING & STATE MANAGEMENT
+    §7.1  Caching Strategy
+          (table: Layer | Object | Strategy | TTL | Invalidation)
+    §7.2  Session State Management
+    §7.3  Serialization Constraints
+
+§8  ERROR HANDLING & RESILIENCE
+    §8.1  Error Classification
+    §8.2  Retry Strategies
+    §8.3  Circuit Breaker Patterns
+    §8.4  Logging & Observability
+
+§9  CONFIGURATION & ENVIRONMENT
+    §9.1  Environment Variables
+    §9.2  Feature Flags
+    §9.3  Configuration Files
+    §9.4  Secrets Management
+
+§10  TESTING STRATEGY
+    §10.1  Unit Test Approach
+    §10.2  Integration Test Approach
+    §10.3  E2E Test Scenarios
+    §10.4  Performance Test Plan
+
+§11  APPENDICES
+    §A  Full Class Diagram
+    §B  Database Schema DDL
+    §C  Sample API Payloads
+```
+
+### Content Sourcing
+
+| LLD Section | Source |
+|-------------|--------|
+| §2 Module Design | Codebase scan (`src/` structure) + `docs/Architecture.md` |
+| §3 Data Model | Database schema + `project-config.md` data sources |
+| §4 API Design | FastAPI route inspection or API docs |
+| §5 Sequence Diagrams | Generate from codebase call flows |
+| §6 Class Structure | Codebase scan (imports, classes, modules) |
+| §7 Caching | `docs/Architecture.md` caching sections + codebase |
+| §8 Error Handling | Codebase patterns (try/catch, error types) |
+| §9 Configuration | `.env.example`, `config.py`, `project-config.md` |
+| §10 Testing | Test files + `docs/Architecture.md` testing strategy |
+
+---
+
+## Generation Workflow
+
+### Step 1: Gather Sources
+
+```
+1. Read docs/Architecture.md (full content)
+2. Read project-config.md (profile, tech stack, org name)
+3. List docs/architecture/*.drawio and *.png (diagram inventory)
+4. If LLD: scan src/ for module structure, key classes, API routes
+```
+
+### Step 2: Determine Scope
+
+Ask the user:
+- **HLD, LLD, or both?**
+- **Output format?** DOCX (recommended), PPTX (exec summary), or both?
+- **Which components?** Full system or specific subsystem?
+
+### Step 3: Assemble Content
+
+Map each section to its source (see Content Sourcing tables above). For each section:
+- If source content exists → extract and format
+- If source is thin → flag with `[TODO: Expand — insufficient detail in Architecture.md]`
+- If source is missing → flag with `[MISSING: No content found — update Architecture.md first]`
+
+### Step 4: Generate Document
+
+Load the appropriate document skill:
+- **DOCX**: Load `.github/skills/document-skills/docx/SKILL.md` — use OOXML for professional formatting
+- **PPTX**: Load `.github/skills/document-skills/pptx/SKILL.md` — use html2pptx workflow
+
+### Step 5: Output
+
+Save to:
+- `docs/deliverables/HLD-{project-name}-v{version}.docx`
+- `docs/deliverables/LLD-{project-name}-v{version}.docx`
+- `docs/deliverables/Architecture-Overview-{project-name}-v{version}.pptx`
+
+---
+
+## Formatting Standards
+
+### Enterprise Document Conventions
+
+- **Font**: Arial or Calibri, 11pt body, 14pt headings
+- **Section numbering**: §1, §1.1, §1.1.1 (three levels max)
+- **Tables**: Bordered, header row shaded with brand primary color
+- **Diagrams**: Captioned ("Figure N: Description"), referenced in text
+- **Page headers**: Project name + Document type + "CONFIDENTIAL" (if applicable)
+- **Page footers**: Page N of M + Version + Date
+- **Line spacing**: 1.15 for body text
+- **Margins**: 2.5cm all sides
+
+### Diagram Embedding
+
+For DOCX:
+- Embed `.png` exports of `.drawio` diagrams
+- Caption each figure: "Figure {N}: {Description}"
+- Reference in text: "See Figure {N}"
+
+For PPTX:
+- One diagram per slide (full-width)
+- Slide title = diagram caption
+- Speaker notes = brief description
+
+### Quality Checklist
+
+Before delivering:
+- [ ] Every section has content or explicit `[TODO]` marker
+- [ ] All diagrams embedded and captioned
+- [ ] Table of Contents generated and correct
+- [ ] Revision history has current entry
+- [ ] Cover page has correct project name, org, date
+- [ ] No placeholder tokens (`<ORG_NAME>` etc.) remain — all resolved from project-config.md
+- [ ] Section numbering is consistent and sequential
+- [ ] Cross-references (e.g., "See §4.2") point to correct sections

package/bundles/antigravity-plugin-extras/skills/artifacts-builder/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 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.