zozul-cli 0.1.0

package/.env.example

@@ -0,0 +1,44 @@
+# ─── zozul-cli configuration ───
+
+# Port the zozul server listens on (hooks, OTEL receiver, API, dashboard)
+ZOZUL_PORT=7890
+
+# Path to the SQLite database (default: ~/.zozul/zozul.db)
+# ZOZUL_DB_PATH=~/.zozul/zozul.db
+
+# Enable verbose logging of hook/OTEL events to stderr (default: false)
+ZOZUL_VERBOSE=false
+
+# ─── Claude Code OTEL configuration ───
+# These are written to ~/.claude/settings.json by `zozul install`.
+# Claude Code sends OTEL data directly to zozul (no external collector needed).
+
+# OTLP endpoint (points at zozul itself)
+OTEL_ENDPOINT=http://localhost:7890
+
+# OTLP protocol (must be http/json for zozul's built-in receiver)
+OTEL_PROTOCOL=http/json
+
+# Log full user prompt text in OTEL events (default: true)
+OTEL_LOG_USER_PROMPTS=1
+
+# Log MCP server/tool names in OTEL events (default: true)
+OTEL_LOG_TOOL_DETAILS=1
+
+# Metrics export interval in ms (default: 60000)
+# OTEL_METRIC_EXPORT_INTERVAL=60000
+
+# Logs export interval in ms (default: 5000)
+# OTEL_LOGS_EXPORT_INTERVAL=5000
+
+# Optional OTLP auth header (e.g. Authorization=Bearer your-token)
+# OTEL_AUTH_HEADER=
+
+# ─── Remote sync configuration ───
+# Required for 'zozul sync'. Set these to push local data to a remote backend.
+
+# Base URL of the zozul backend API
+# ZOZUL_API_URL=https://api.zozul.dev
+
+# API key for authenticating with the backend (sent as X-API-Key header)
+# ZOZUL_API_KEY=your-api-key-here

package/.github/workflows/publish.yml

@@ -0,0 +1,26 @@
+name: Publish to npm
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://registry.npmjs.org
+
+      - run: npm ci
+
+      - run: npm run build
+
+      - run: npm test
+
+      - run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/DEVELOPMENT.md

@@ -0,0 +1,288 @@
+# Development & Agent Context
+
+This document is the running reference for anyone (human or agent) picking up work on this codebase. It captures non-obvious design decisions, current state, known issues, and how to orient yourself quickly.
+
+---
+
+## Project overview
+
+zozul-cli is a local observability sidecar for Claude Code. It ingests data from three sources (OTEL, hooks, JSONL), stores everything in SQLite, and serves a dashboard + JSON API. Single process, no external services.
+
+---
+
+## Source layout
+
+```
+src/
+  index.ts              Entry point — loads .env, runs CLI
+  cli/
+    commands.ts         All CLI commands (serve, install, ingest, etc.)
+    format.ts           Terminal output formatters
+  storage/
+    db.ts               SQLite setup, schema migration, row types
+    repo.ts             All DB queries — SessionRepo class
+  hooks/
+    server.ts           HTTP server: hook handler, API routes, OTEL receiver dispatch
+    config.ts           Read/write ~/.claude/settings.json for hooks
+  otel/
+    receiver.ts         Parse OTLP JSON payloads → DB + session accumulation
+    config.ts           Read/write ~/.claude/settings.json for OTEL env vars
+  parser/
+    jsonl.ts            Discover and parse Claude Code session JSONL files
+    ingest.ts           Persist parsed sessions/turns/tool_uses to DB
+    watcher.ts          fs.watch on ~/.claude/projects, debounced ingest
+    types.ts            JSONL type definitions
+  dashboard/
+    index.html          Dashboard SPA (vanilla JS, Chart.js from CDN)
+    html.ts             Reads and serves index.html (thin wrapper)
+  service/
+    index.ts            Install/uninstall as launchd (macOS) or systemd (Linux) service
+```
+
+Build output goes to `dist/`. The build script also copies `src/dashboard/index.html` → `dist/dashboard/index.html`.
+
+---
+
+## Data flow
+
+### OTEL (metrics + logs)
+
+Claude Code sends OTLP JSON to `POST /v1/metrics` and `POST /v1/logs` on a configurable interval (default: 60s metrics, 5s logs).
+
+**Important**: values are **deltas per export window**, not cumulative totals. Each batch represents tokens/cost/time accrued since the last export.
+
+Flow:
+1. `hooks/server.ts` receives POST, reads body (50MB cap)
+2. Calls `handleOtlpMetrics` / `handleOtlpLogs` in `otel/receiver.ts`
+3. Receiver builds a flat batch, inserts into `otel_metrics` / `otel_events`
+4. Receiver also aggregates per-session deltas from the batch and calls `repo.updateSessionFromOtel()` for each session seen
+5. `updateSessionFromOtel` does an accumulating UPSERT: `total_cost_usd += delta`, `total_*_tokens += delta`, `total_duration_ms += delta`, `ended_at = MAX(...)`
+
+Key metric names from Claude Code:
+- `claude_code.token.usage` — attribute `type` is `input` / `output` / `cacheRead` / `cacheCreation`
+- `claude_code.cost.usage` — USD, no type attribute
+- `claude_code.active_time.total` — seconds of active use
+- `claude_code.session.count`, `claude_code.lines_of_code.count`, etc.
+
+### Hooks
+
+Claude Code POSTs to `/hook/<event>` synchronously as events happen. The hook handler:
+1. Parses JSON body
+2. Deduplicates `SessionEnd` events within 60s for the same session (Claude Code sometimes fires two)
+3. Inserts into `hook_events`
+4. On `SessionEnd`: decodes project path from `transcript_path`, calls `ingestSessionFile`
+
+Hook event names: `SessionStart`, `SessionEnd`, `Stop`, `UserPromptSubmit`, `PostToolUse`, `PreToolUse`, `Notification`
+
+### JSONL
+
+Claude Code writes session transcripts to:
+```
+~/.claude/projects/<encoded-project-path>/<session-uuid>.jsonl
+```
+
+The encoded path replaces `/` with `-` (lossy — hyphens in directory names become `/` when decoded). Session UUID is used as the session ID everywhere.
+
+Each line in the file is one JSON entry. Entries have `message.role`, `message.content`, `message.usage`, `costUSD`, `durationMs`. Note: `costUSD` is often `0` in practice — OTEL is the reliable cost source.
+
+**Discovery**: `discoverSessionFiles()` in `parser/jsonl.ts` scans `~/.claude/projects/*/` for UUID-named `.jsonl` files (regex: `/^[0-9a-f]{8}-...-[0-9a-f]{12}\.jsonl$/i`). It does NOT look in `sessions/` subdirectories — the directory structure changed in Claude Code 2.x.
+
+**Watcher**: `watchSessionFiles()` in `parser/watcher.ts` runs on `zozul serve`. It does a catch-up ingest of all files on startup, then watches for changes using `fs.watch({ recursive: true })`. Each file change is debounced 500ms before calling `ingestSessionFile`.
+
+---
+
+## Database schema
+
+Six tables, all in `~/.zozul/zozul.db` (WAL mode, foreign keys ON).
+
+### `sessions`
+One row per Claude Code session. Updated from both JSONL and OTEL.
+
+```sql
+id TEXT PRIMARY KEY           -- session UUID (from JSONL filename)
+project_path TEXT             -- decoded from transcript path
+started_at TEXT NOT NULL      -- ISO timestamp, from JSONL
+ended_at TEXT                 -- kept current by OTEL batches
+total_input_tokens INTEGER    -- OTEL-accumulated (MAX with JSONL)
+total_output_tokens INTEGER
+total_cache_read_tokens INTEGER
+total_cache_creation_tokens INTEGER
+total_cost_usd REAL           -- OTEL only (JSONL always 0)
+total_turns INTEGER           -- from JSONL (count of parsed turns)
+total_duration_ms INTEGER     -- OTEL active_time accumulated
+model TEXT                    -- last model seen
+```
+
+Upsert semantics: `MIN(started_at)`, `MAX()` for all metric fields, `COALESCE` for nullable strings. This means re-ingesting from JSONL never destroys OTEL-accumulated cost/duration.
+
+### `turns`
+One row per message turn. Unique on `(session_id, turn_index)`.
+
+```sql
+id INTEGER PRIMARY KEY AUTOINCREMENT
+session_id TEXT → sessions(id)
+turn_index INTEGER
+role TEXT                     -- 'user' or 'assistant'
+timestamp TEXT
+input_tokens / output_tokens / cache_* INTEGER
+cost_usd REAL                 -- often 0, from JSONL
+duration_ms INTEGER
+model TEXT
+content_text TEXT             -- full message text
+tool_calls TEXT               -- JSON array of {toolName, toolInput, toolResult}
+```
+
+### `tool_uses`
+Extracted tool calls, one row per tool invocation.
+
+```sql
+id INTEGER PRIMARY KEY AUTOINCREMENT
+session_id TEXT → sessions(id)
+turn_id INTEGER → turns(id)   -- nullable
+tool_name TEXT
+tool_input TEXT               -- JSON
+tool_result TEXT
+success INTEGER               -- null (not yet populated)
+duration_ms INTEGER           -- 0 (not yet populated)
+timestamp TEXT
+```
+
+Re-ingest is safe: `persistSession` calls `replaceToolUsesForTurn(turnId, ...)` which deletes existing rows for the turn before inserting — no duplication.
+
+### `hook_events`
+Raw hook payloads, append-only.
+
+```sql
+id INTEGER PRIMARY KEY AUTOINCREMENT
+session_id TEXT               -- nullable (some hooks lack it)
+event_name TEXT
+timestamp TEXT
+payload TEXT                  -- full JSON body
+```
+
+### `otel_metrics`
+Raw OTEL metric data points, append-only.
+
+```sql
+id INTEGER PRIMARY KEY AUTOINCREMENT
+name TEXT                     -- e.g. 'claude_code.token.usage'
+value REAL
+attributes TEXT               -- full JSON of flattened OTLP attributes
+session_id TEXT               -- extracted from attributes
+model TEXT                    -- extracted from attributes
+timestamp TEXT
+```
+
+Dashboard charts query this table directly (not `sessions`) for time-series data.
+
+### `otel_events`
+Raw OTEL log records, append-only.
+
+```sql
+id INTEGER PRIMARY KEY AUTOINCREMENT
+event_name TEXT
+attributes TEXT               -- full JSON
+session_id TEXT
+prompt_id TEXT
+timestamp TEXT
+```
+
+---
+
+## Key design decisions
+
+**OTEL is the authoritative source for cost and duration.** JSONL transcripts do not reliably contain `costUSD` (it's often 0 in practice). `total_cost_usd` in `sessions` is always populated by OTEL accumulation.
+
+**JSONL is the only source for full conversation text.** OTEL events can include prompt text when `OTEL_LOG_USER_PROMPTS=1`, but the assistant's full response is only in the JSONL transcript.
+
+**Sessions table uses MAX() semantics on upsert.** This means the highest value seen from any source wins. OTEL running totals always exceed JSONL partial values, so OTEL naturally wins for metrics without any special logic.
+
+**OTEL deltas are accumulated, not replaced.** `updateSessionFromOtel` does `total_cost_usd = total_cost_usd + @cost`. This is correct because OTEL sends deltas per window. Do not change this to an assignment.
+
+**Tool uses are replaced, not appended, on re-ingest.** `replaceToolUsesForTurn` deletes then re-inserts. This prevents duplication when the watcher re-ingests a live session file on every new turn.
+
+**`insertTurn` uses `RETURNING id`.** On `ON CONFLICT DO UPDATE`, `lastInsertRowid` returns 0. Using `RETURNING id` gives the correct turn ID for the FK on `tool_uses`.
+
+**JSONL file paths use lossy encoding.** Claude Code replaces `/` with `-` in project directory names. `decodeProjectPath` reverses this, but hyphens in original paths become `/`. This is unavoidable with Claude Code's current encoding scheme.
+
+---
+
+## Session lifecycle
+
+```
+Claude Code starts
+  → SessionStart hook fires → hook_events INSERT
+  → OTEL export #1 arrives (within 60s) → otel_metrics INSERT + sessions UPSERT (stub or update)
+  → turns happen → JSONL file grows → watcher fires → ingestSessionFile → sessions/turns/tool_uses UPSERT
+  → OTEL exports keep arriving every 60s → cost/duration accumulate in sessions
+  → User stops Claude → Stop hook fires
+  → SessionEnd hook fires → ingestSessionFile called with transcript_path → final JSONL state ingested
+  → OTEL export continues until session ID stops appearing in batches
+```
+
+**Late-start behaviour**: if zozul wasn't running when Claude started, the watcher's catch-up pass immediately ingests all existing JSONL files. OTEL data from before zozul started is lost (no replay). The first OTEL batch after zozul starts will include cumulative cost for that window, partially recovering missed cost data.
+
+---
+
+## API routes
+
+All served by `hooks/server.ts` on port 7890.
+
+| Method | Path | Description |
+|---|---|---|
+| GET | `/dashboard` | Dashboard HTML |
+| GET | `/api/stats` | Aggregate stats — sessions, tokens, cost, user prompts, interruptions |
+| GET | `/api/sessions` | Paginated session list — returns `{ sessions, total, limit, offset }` |
+| GET | `/api/sessions/:id` | Single session row |
+| GET | `/api/sessions/:id/turns` | Turns for a session |
+| GET | `/api/metrics/tokens` | Token time-series from `otel_metrics` |
+| GET | `/api/metrics/cost` | Cost time-series from `otel_metrics` |
+| GET | `/api/metrics/tools` | Tool usage breakdown from `tool_uses` |
+| GET | `/api/metrics/models` | Per-model cost/token breakdown from `otel_metrics` |
+| POST | `/v1/metrics` | OTLP metrics receiver |
+| POST | `/v1/logs` | OTLP logs receiver |
+| POST | `/hook/:event` | Claude Code hook receiver |
+
+`/api/sessions` accepts `?limit=N` (default 50, max 500) and `?offset=N`. The response envelope `{ sessions, total, limit, offset }` lets the dashboard implement Load More without a separate count query.
+
+Time-series endpoints accept `?range=7d`, `?range=24h`, or `?from=ISO&to=ISO&step=5m`. Step auto-selects based on range if omitted.
+
+---
+
+## Background service
+
+`zozul install --service` writes a platform service file and loads it immediately:
+
+- **macOS**: `~/Library/LaunchAgents/com.zozul.serve.plist` — loaded with `launchctl bootstrap gui/<uid>`
+- **Linux**: `~/.config/systemd/user/zozul.service` — enabled with `systemctl --user enable --now`
+
+The service file bakes in the absolute paths to the node binary (`process.execPath`) and the script (`process.argv[1]` resolved). This makes it nvm-safe but means you need to re-run `zozul install --service` if you upgrade node or move the project.
+
+`zozul restart` kills and immediately relaunches the running service (`launchctl kickstart -k` on macOS, `systemctl --user restart` on Linux). Use this after `npm run build` to pick up code changes without reinstalling.
+
+Logs: `~/.zozul/zozul.log`
+
+---
+
+## Known limitations
+
+- **No schema migrations**: `db.ts` uses `CREATE TABLE IF NOT EXISTS`. Adding columns to existing tables requires manual SQL or a proper migration system.
+- **JSONL path decoding is lossy**: hyphens in project directory names decode incorrectly. No fix without changes to Claude Code.
+- **OTEL cost history is unrecoverable**: if zozul wasn't running during a session, cost data for that period is permanently lost.
+- **`tool_uses.success` and `tool_uses.duration_ms` are never populated**: the schema has these columns but nothing writes to them yet.
+- **Session filter is client-side only**: the filter input searches loaded sessions; Load More fetches additional pages.
+
+---
+
+## Dev workflow
+
+```bash
+npm install          # Install dependencies
+npm run dev          # Run via tsx (no build step needed)
+npm run build        # Compile TypeScript + copy index.html to dist/
+npm test             # Run vitest
+```
+
+When the service is installed, it runs `dist/index.js` directly. After code changes: `npm run build && zozul restart`.
+
+The DB is at `~/.zozul/zozul.db`. Use `sqlite3 ~/.zozul/zozul.db` for ad-hoc inspection. Use `zozul db-clean` to remove rows with invalid timestamps.

package/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.