@tyroneross/navgator 0.2.2 → 0.9.0

package/.agents/plugins/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "navgator-local-workspace",
+  "interface": {
+    "displayName": "NavGator Workspace Plugins"
+  },
+  "plugins": [
+    {
+      "name": "navgator",
+      "source": {
+        "source": "local",
+        "path": "./"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Coding"
+    }
+  ]
+}

package/.claude-plugin/marketplace.json

@@ -1,23 +1,37 @@
 {
   "name": "navgator",
-  "owner": { "name": "Tyrone Ross", "url": "https://github.com/tyroneross" },
+  "owner": {
+    "name": "Tyrone Ross",
+    "url": "https://github.com/tyroneross"
+  },
   "metadata": {
     "description": "Architecture connection tracker — know your stack before you change it",
-    "version": "1.0.0"
+    "version": "0.9.0"
   },
   "plugins": [
     {
       "name": "gator",
       "source": "./",
       "description": "Architecture connection tracker for Claude Code — know your stack before you change it",
-      "version": "0.2.2",
-      "author": { "name": "Tyrone Ross" },
+      "version": "0.9.0",
+      "author": {
+        "name": "Tyrone Ross"
+      },
       "homepage": "https://github.com/tyroneross/navgator#readme",
       "repository": "https://github.com/tyroneross/navgator",
-      "license": "MIT",
-      "keywords": ["architecture", "connections", "dependencies", "impact-analysis"],
+      "license": "Apache-2.0",
+      "keywords": [
+        "architecture",
+        "connections",
+        "dependencies",
+        "impact-analysis"
+      ],
       "category": "development",
-      "tags": ["architecture", "dependency-tracking", "impact-analysis"]
+      "tags": [
+        "architecture",
+        "dependency-tracking",
+        "impact-analysis"
+      ]
     }
   ]
 }

package/.claude-plugin/plugin.json

@@ -1,13 +1,18 @@
 {
-  "name": "gator",
-  "version": "0.2.2",
-  "description": "Architecture connection tracker — know your stack before you change it",
-  "author": { "name": "Tyrone Ross" },
-  "homepage": "https://github.com/tyroneross/navgator",
-  "repository": "https://github.com/tyroneross/navgator",
-  "license": "MIT",
-  "keywords": ["architecture", "connections", "context", "dependencies", "impact-analysis"],
-  "hooks": "../hooks/hooks.json",
-  "skills": "../skills/",
-  "agents": "../agents/"
+  "name": "navgator",
+  "version": "0.9.0",
+  "description": "Map dependencies and analyze blast radius before changing code",
+  "author": {
+    "name": "Tyrone Ross"
+  },
+  "homepage": "https://github.com/tyroneross/NavGator",
+  "repository": "https://github.com/tyroneross/NavGator",
+  "license": "Apache-2.0",
+  "keywords": [
+    "architecture",
+    "connections",
+    "context",
+    "dependencies",
+    "impact-analysis"
+  ]
 }

package/.codex-plugin/plugin.json

@@ -0,0 +1,31 @@
+{
+  "name": "navgator",
+  "version": "0.9.0",
+  "description": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
+  "author": {
+    "name": "Tyrone Ross"
+  },
+  "homepage": "https://github.com/tyroneross/navgator",
+  "repository": "https://github.com/tyroneross/navgator",
+  "license": "Apache-2.0",
+  "keywords": [
+    "architecture",
+    "connections",
+    "context",
+    "dependencies",
+    "impact-analysis"
+  ],
+  "skills": "./skills",
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "NavGator",
+    "shortDescription": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
+    "longDescription": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
+    "developerName": "Ross Labs",
+    "category": "Coding",
+    "capabilities": [
+      "Read",
+      "Write"
+    ]
+  }
+}

package/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "navgator": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/dist/mcp/server.js"]
+    }
+  }
+}

package/CLAUDE.md

@@ -1,3 +1,6 @@
+<!-- Plugin: navgator · Version: 0.6.1 · Source of truth: local (~/dev/git-folder/NavGator) -->
+<!-- Before any commit, version bump, or major change, read ./VERSIONING.md. Update it on version bumps. -->
+
 # NavGator — Architecture Context for Claude
 
 ## What NavGator Does
@@ -6,7 +9,7 @@ NavGator externalizes architecture knowledge so you never lose track of file pat
 
 ## Context Model (Three Tiers)
 
-**Tier 1 — Hot Context** (`SUMMARY.md`)
+**Tier 1 — Hot Context** (`NAVSUMMARY.md`)
 Read this first. It's a concise overview (~40-150 lines) with:
 - Components by layer (frontend, backend, database, queue, infra, external)
 - AI/LLM routing table (provider, file, line, purpose)
@@ -14,7 +17,7 @@ Read this first. It's a concise overview (~40-150 lines) with:
 - Delta from last scan (what changed)
 - Pointers to detail files for drill-down
 
-If `SUMMARY.md` was compressed (large projects), the full version is at `SUMMARY_FULL.md`.
+If `NAVSUMMARY.md` was compressed (large projects), the full version is at `NAVSUMMARY_FULL.md`.
 
 **Tier 2 — Structured Index** (`index.json`, `graph.json`, `file_map.json`, `prompts.json`)
 Use for programmatic lookups:
@@ -23,50 +26,221 @@ Use for programmatic lookups:
 - `file_map.json` — maps file paths to component IDs (O(1) lookup)
 - `prompts.json` — full prompt content with LLM provider associations (scan with `--prompts`)
 
-**Tier 3 — Detail Files** (`components/COMP_*.json`, `connections/CONN_*.json`)
-Load on demand when you need full detail about a specific component or connection. Each entry in SUMMARY.md points to its detail file.
+**Tier 3 — Detail Files** (`components/COMP_*.json`, `connections/CONN_*.json`) *(opt-in since v0.9.0)*
+Off by default to keep the on-disk footprint small (~70MB → ~1MB on atomize-ai-scale projects). The consolidated `graph.json`, `index.json`, `file_map.json`, `connections.jsonl`, and `reverse-deps.json` carry the same information. Enable per-entity files when you need stable per-record paths (Obsidian linking, external indexers): run `navgator scan --per-entity-files` or set `NAVGATOR_PER_ENTITY_FILES=true`. When disabled, each scan idempotently removes any legacy per-entity files left over from earlier versions.
 
 ## When to Read Architecture Context
 
-**Always read `SUMMARY.md` at the start of a session.** It's located at:
+**Always read `NAVSUMMARY.md` at the start of a session.** It's located at:
 ```
-<project-root>/.claude/architecture/SUMMARY.md
+<project-root>/.navgator/architecture/NAVSUMMARY.md
 ```
 
 **Before editing tracked files:** If you're about to edit a file that belongs to a tracked component, read the component's detail file first. The architecture-check hook will remind you.
 
-**After dependency changes:** If you ran `npm install`, `pip install`, etc., architecture data may be stale. Run `/gator:scan` to update.
+**After dependency changes:** If you ran `npm install`, `pip install`, etc., architecture data may be stale. Run `/navgator:scan` to update.
+
+## Investigation Protocol — Consult Before Fixing
+
+**Before fixing a bug, debugging an issue, or making any change that touches multiple files:**
+
+1. **Understand the component:** Run `navgator explore <component>` or the `explore` MCP tool to see what the component connects to, its runtime identity, impact severity, and data flow paths.
+
+2. **Check blast radius:** Run `navgator impact <component>` to see what breaks downstream. A "simple fix" in a high-fan-out component can cascade.
+
+3. **Trace the data flow:** Run `navgator trace <component>` to follow how data moves through the system. This reveals the full chain: User → Frontend → API → Service → Database → Response.
+
+4. **Check for patterns:** Run `navgator rules` to identify any existing architectural violations that might be related to the issue.
+
+**Why this matters:** Code fixes that don't consider architecture cause cascading failures. NavGator's graph shows connections that aren't obvious from reading a single file. A queue worker change might affect 5 API routes and 3 cron jobs — NavGator tells you which ones.
+
+**Quick reference for common investigation tasks:**
+
+| I need to... | Use |
+|-------------|-----|
+| Understand a component before changing it | `explore <component>` |
+| Know what breaks if I change X | `impact <component>` |
+| Follow data through the system | `trace <component>` |
+| Check architecture health | `rules` or `/navgator:review` |
+| Find where a function/file is used | `connections <component>` |
+| See the full architecture overview | `status` |
+
+## Retrieving Stored Context
+
+NavGator stores architecture data in `.navgator/architecture/`. Key files for retrieval:
+
+| File | What it contains | When to read |
+|------|-----------------|-------------|
+| `NAVSUMMARY.md` | Hot context — component overview, AI routing, top connections | Session start, quick orientation |
+| `index.json` | Stats, component/connection counts by type | Programmatic lookups |
+| `file_map.json` | File path → component ID mapping | "What component owns this file?" |
+| `graph.json` | Full connection graph | Impact analysis, traversal |
+| `prompts.json` | AI prompt content + provider associations | LLM debugging, prompt review |
+| `components/COMP_*.json` | Full detail for one component *(opt-in: `--per-entity-files`)* | Deep dive on specific component |
+| `connections/CONN_*.json` | Full detail for one connection *(opt-in: `--per-entity-files`)* | Understanding a specific relationship |
+
+**For agents building on NavGator:** Use the MCP tools (`scan`, `status`, `explore`, `review`, `trace`, `rules`) rather than reading JSON files directly. The tools return pre-analyzed, compact text output optimized for LLM consumption.
 
 ## Available Commands
 
+### Slash Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/navgator:map` | Map full architecture — components, connections, topology, LLM use cases |
+| `/navgator:scan` | Quick scan — refresh tracking data |
+| `/navgator:trace <component>` | Trace data flow through the system (cron → route → service → DB → queue → LLM) |
+| `/navgator:impact <component>` | What breaks if you change this? Blast radius analysis |
+| `/navgator:test [instructions]` | End-to-end architecture test with optional custom focus |
+| `/navgator:review` | Architectural integrity review (connections, drift, lessons) |
+| `/navgator:review learn "..."` | Record a manual architectural lesson |
+| `/navgator:llm-map` | Map all LLM use cases by purpose (search, summarization, extraction, etc.) |
+| `/navgator:schema [model]` | Show readers vs writers per database model |
+| `/navgator:dead` | Find orphaned components — unused packages, models, queues, infra |
+
+### CLI Commands
+
+| Command | Purpose |
+|---------|---------|
+| `navgator status` | Architecture summary with runtime topology and anomaly warnings |
+| `navgator connections <component>` | Show all connections with `[test]`/`[dev-only]` badges |
+| `navgator diagram` | Generate visual architecture diagram |
+| `navgator trace <component>` | Trace with `--production`, `--max-paths N`, `--direction` |
+| `navgator rules` | Check architecture rules (orphans, layer violations, cycles, hotspots) |
+| `navgator llm-map` | LLM use case map with `--provider`, `--category`, `--classify` |
+| `navgator schema [model]` | Database model read/write analysis |
+| `navgator dead` | List orphaned components by type |
+| `navgator history` | Architecture change timeline |
+| `navgator diff [id]` | Detailed architecture diff |
+| `navgator subgraph <component>` | Extract focused subgraph |
+| `navgator coverage --fields` | Prisma field usage analysis |
+| `navgator coverage --typespec` | Prisma vs TypeScript type validation |
+| `navgator coverage --fields` | Analyze DB field usage (unused, read-only, write-only) |
+| `navgator coverage --typespec` | Validate Prisma types against TypeScript interfaces |
+
+## Agent/Machine Output
+
+All commands that support `--json` also support `--agent`, which wraps output in a stable envelope:
+
+```json
+{
+  "command": "scan",
+  "data": { ... },
+  "schema_version": "1.0.0",
+  "timestamp": 1234567890
+}
+```
+
+### Infrastructure Scanning
+
+NavGator detects infrastructure beyond packages:
+- **Prisma models**: schema parsing, relations, indexes (`--field-usage` for usage analysis)
+- **Environment variables**: `.env` files + `process.env` references in source
+- **Queues**: BullMQ/Bull producers and consumers
+- **Cron jobs**: vercel.json, railway.json, node-cron patterns
+- **Deploy configs**: Vercel, Railway, Heroku service definitions
+- **TypeSpec validation**: Prisma model vs TypeScript interface comparison (`--typespec`)
+
+These are detected automatically during `navgator scan`. Use `navgator coverage --fields` or `--typespec` for detailed analysis.
+
+### Runtime Topology
+
+NavGator annotates components with runtime identity — service names, connection endpoints, and deployment targets extracted from code and config. This enables backward tracing from runtime failures to code: "which code produces to this BullMQ queue?" or "what database engine does this Prisma schema connect to?"
+
+The `navgator status` command shows a RUNTIME TOPOLOGY section with all detected bindings.
+
+### LLM Use Case Tracking
+
+NavGator tracks distinct LLM use cases, not raw import counts. Instead of "154 service calls," it shows "8 use cases across 3 providers." Deduplication uses a priority cascade: prompt-based grouping (strongest), function name grouping, callType+model grouping, file-based (fallback). Test and dev-only connections are filtered automatically.
+
+The `navgator status` command shows an AI/LLM section with use case count, providers, and a table of distinct use cases.
+
+### Lessons System
+
+NavGator accumulates architectural lessons in `.navgator/lessons/lessons.json`. Lessons are patterns that caused issues — they're matched against future changes during `/navgator:review`. Categories: api-contract, data-flow, component-communication, llm-architecture, infrastructure, typespec, database-structure.
+
+Record lessons manually with `/navgator:review learn "description"`. Lessons are validated periodically against current documentation via `/navgator:review --validate`.
+
+### Lessons: Per-Project vs Global (Three-Tier Data Model)
+
+NavGator uses a three-tier data model so architecture details stay local to each
+repo while transferable patterns become shareable across projects.
+
+**Tier 1 — Per-project architecture** (`<project>/.navgator/architecture/`)
+Full scan output: `index.json`, `graph.json`, `file_map.json`, `prompts.json`,
+`connections.jsonl`, `reverse-deps.json`, `NAVSUMMARY.md`. With
+`--per-entity-files`, also `components/` and `connections/`. Project-specific.
+Never shared.
+
+**Tier 2 — Per-project lessons** (`<project>/.navgator/lessons/lessons.json`)
+Patterns discovered in *this* project. Recorded via `/navgator:review learn` or
+surfaced by `/navgator:review`. Scoped to this repo by default.
+
+**Tier 3 — Global lessons** (`~/.navgator/lessons/global-lessons.json`)
+Cross-project patterns — approaches, architectural connections, config insights
+that apply across your work. Each entry includes `source_project`, `applies_to`
+tags, and `promoted_at` so you can trace provenance.
+
+**Promotion is opt-in and non-destructive.** When you promote a local lesson to
+global, the local lesson stays in place but gets marked `promoted: true`. The
+global lesson gets a full copy plus traceability fields. There is no automatic
+cross-project application — global lessons are for recall and reference.
+
+**CLI**:
+
 | Command | Purpose |
 |---------|---------|
-| `/gator:scan` | Scan project architecture |
-| `/gator:status` | Show architecture summary |
-| `/gator:impact` | Analyze what's affected by a change |
-| `/gator:connections` | Show all connections for a component |
-| `/gator:diagram` | Generate visual architecture diagram |
-| `/gator:export` | Export architecture to markdown or JSON |
-| `/gator:check` | Run health checks (outdated packages, vulnerabilities) |
-| `/gator:ui` | Launch the web dashboard |
-| `/gator:update` | Update NavGator to the latest version |
+| `navgator lessons list` | List lessons in current project |
+| `navgator lessons list --global` | List global lessons across all projects |
+| `navgator lessons list --all` | Combined view |
+| `navgator lessons show <id>` | Show full detail for one lesson |
+| `navgator lessons search <query>` | Regex-search across lessons |
+| `navgator lessons search <q> --tag <t>` | Filter by applies_to tag (global only) |
+| `navgator lessons search <q> --category <c>` | Filter by lesson category |
+| `navgator lessons promote <id> --tag <t>` | Promote local → global with tags |
+| `navgator lessons demote <id>` | Remove from global (local untouched) |
+
+All `lessons` subcommands support `--json` and the `--agent` envelope.
+
+### Scan Flags
+
+| Flag | Purpose |
+|------|---------|
+| `--track-branch` | Capture git branch/commit in scan output (opt-in) |
+| `--json` | Output scan results as JSON (stats, changes, git info) |
+| `--agent` | Wrap output in agent envelope (implies `--json`) |
+
+### Schema Version
+
+All JSON files (`index.json`, `graph.json`, `file_map.json`, `prompts.json`) include a `schema_version` field (currently `1.0.0`). The `file_map.json` is wrapped as `{ schema_version, generated_at, files: { ... } }`.
+
+### Branch Tracking
+
+When `--track-branch` is used during scan:
+- `timeline.json` entries include a `git` field with `{ branch, commit }`
+- `NAVSUMMARY.md` header shows `> Branch: **main** @ \`abc1234\``
+- `navgator history` shows `[branch@commit]` tags on entries
+- `navgator projects` shows the last tracked branch
 
 ## Architecture Data Location
 
-All data lives in `<project-root>/.claude/architecture/`:
+All data lives in `<project-root>/.navgator/architecture/`:
 ```
-.claude/architecture/
-├── SUMMARY.md          ← Read this first (hot context)
-├── SUMMARY_FULL.md     ← Full version if compressed
+.navgator/architecture/
+├── NAVSUMMARY.md          ← Read this first (hot context)
+├── NAVSUMMARY_FULL.md     ← Full version if compressed
 ├── index.json          ← Master index
 ├── graph.json          ← Connection graph
 ├── file_map.json       ← File path → component ID lookup
 ├── prompts.json        ← Full prompt content + LLM associations
 ├── hashes.json         ← File change detection
-├── components/         ← One JSON per component
-└── connections/        ← One JSON per connection
+├── timeline.json       ← Architecture change history (diffs between scans)
+├── connections.jsonl   ← All connections (one JSON object per line)
+├── reverse-deps.json   ← Derived: file → importers index (fast incremental walk)
+├── components/         ← One JSON per component (opt-in: --per-entity-files)
+└── connections/        ← One JSON per connection (opt-in: --per-entity-files)
 ```
 
 ## Key Principle
 
-Instead of trying to "remember" architecture details, reload the externalized source of truth. SUMMARY.md is cheap to read and gives you the full picture. Drill into detail files only when needed.
+Instead of trying to "remember" architecture details, reload the externalized source of truth. NAVSUMMARY.md is cheap to read and gives you the full picture. Drill into detail files only when needed.

package/LICENSE

@@ -1,21 +1,202 @@
-MIT License
-
-Copyright (c) 2025 Tyrone Ross
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                                 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.