vardoger 0.1.0__tar.gz

vardoger-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,58 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v8.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: pyproject.toml
+
+      - name: Install dependencies
+        run: uv sync --python ${{ matrix.python-version }}
+
+      - name: Lint
+        run: uv run ruff check src/ tests/ scripts/
+
+      - name: Format check
+        run: uv run ruff format --check src/ tests/ scripts/
+
+      - name: Type check
+        run: uv run mypy src/
+
+      - name: Check rendered plugin skills are in sync
+        run: uv run scripts/render-skills.py --check
+
+      - name: Test
+        run: uv run pytest tests/ --tb=short -q --cov=vardoger --cov-fail-under=80
+
+  security:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v8.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: pyproject.toml
+
+      - name: Install dependencies
+        run: uv sync
+
+      - name: Static security scan (bandit)
+        run: uv run --with bandit bandit -r src/ -q
+
+      - name: Dependency CVE scan (pip-audit)
+        run: uv run --with pip-audit pip-audit --skip-editable

vardoger-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,39 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v8.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: pyproject.toml
+
+      - name: Build package
+        run: uv build
+
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

vardoger-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# OS files
+.DS_Store
+Thumbs.db
+
+# IDE files
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+
+# Environment and secrets
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+credentials.json
+
+# Build artifacts
+build/
+dist/
+out/
+target/
+
+# Dependencies
+node_modules/
+vendor/
+__pycache__/
+*.pyc
+
+# Logs
+*.log
+logs/
+
+# Coverage
+coverage/
+.coverage
+.nyc_output/
+
+# Pytest
+.pytest_cache/
+
+# Python / uv
+.venv/
+*.egg-info/
+uv.lock
+
+# vardoger generated output (don't commit personalization)
+.cursor/rules/vardoger.md

vardoger-0.1.0/AGENTS.md

@@ -0,0 +1,141 @@
+# Engineering Rules (for AI Assistants)
+
+Authoritative coding instructions for this repository. Linked from:
+- `.cursor/rules/` (Cursor)
+- `.github/copilot-instructions.md` (Copilot)
+- `CLAUDE.md` (Claude Code)
+- `AGENTS.md` (OpenAI Codex)
+
+---
+
+## Project Structure & Naming
+
+```
+src/vardoger/          # shared core — history reading, analysis, prompt generation
+plugins/cursor/        # Cursor MCP server config, install script
+plugins/claude-code/   # Claude Code plugin manifest, skills
+plugins/codex/         # Codex plugin manifest, skills
+plugins/openclaw/      # OpenClaw skill
+tests/                 # all tests, mirroring src/ structure
+```
+
+| Kind | Path pattern |
+|---|---|
+| History adapters | `src/vardoger/history/<platform>.py` |
+| Prompt writers | `src/vardoger/writers/<platform>.py` |
+| AI prompts | `src/vardoger/prompts/*.md` (or `plugins/<platform>/prompts/` if platform-specific) |
+| Plugin manifests | `plugins/<platform>/.<tool>-plugin/plugin.json` |
+| Skills | `plugins/<platform>/skills/<name>/SKILL.md` |
+| Tests | `tests/` directory mirroring `src/vardoger/` (e.g., `tests/history/test_cursor.py`) |
+
+---
+
+## Before You Code
+
+- **Find the module boundary**: locate the nearest `pyproject.toml` and treat it as the unit of build, test, and dependency rules.
+- **Preserve layering**: shared core lives in `src/vardoger/`, platform-specific code in `plugins/<platform>/`. Don't mix them.
+- **Prefer configuration over ad-hoc constants**: use a config class and env vars rather than scattering `os.getenv` calls.
+- **Avoid duplication**: if you see near-identical blocks, centralize them.
+
+---
+
+## Code Review Priorities
+
+These are the patterns reviewers consistently flag:
+
+- **Module boundaries & dependency direction**
+  - Shared types belong in `src/vardoger/`, not inside a plugin.
+  - Plugin modules should not import from other plugins; dependencies flow inward to the shared core.
+
+- **Config & safety**
+  - Put env/config interpretation in a config class, not sprinkled across code.
+  - Add explicit enablement flags for destructive or side-effectful operations.
+
+- **Code clarity**
+  - Keep method/variable names aligned with actual behavior.
+  - Keep private helper functions at the bottom of the file.
+  - PR titles/descriptions must match the actual scope.
+
+- **Testing**
+  - Prefer simple, readable tests over elaborate fixtures.
+  - Add unit tests for new non-trivial logic.
+  - Assert whole expected objects in a single comparison, not field-by-field.
+
+- **Serialization & data**
+  - Don't build JSON by string concatenation or manual dict construction; use Pydantic models and `model_dump_json()`.
+  - Parse incoming JSON with `model_validate_json()`, not raw `json.loads()` + `.get()` chains.
+  - Keep templates centralized and reusable.
+
+- **Performance**
+  - Don't recreate immutable instances on every call; reuse a single instance when safe.
+  - Prefer `orjson` for heavy JSON workloads.
+
+---
+
+## Git Workflow
+
+### Commits
+- **Subject**: imperative summary, one line. Never mention AI assistants (no `Co-Authored-By`).
+- **Dependency bumps**: `bump <package> to <version>` (commit both `pyproject.toml` and `uv.lock`).
+
+### Pull Requests
+- **Title**: short imperative summary.
+- **Description**: say what and why. Don't list changed files. Don't mention AI assistants.
+- **Merge**: rebase and merge to `main`, delete branch after merge.
+
+---
+
+## Python
+
+### Runtime & Dependencies
+- **Python version**: ≥3.11 (follow `pyproject.toml`).
+- **Package manager**: [uv](https://docs.astral.sh/uv/)
+  - Install: `uv sync`
+  - Add runtime dep: `uv add <pkg>`
+  - Add dev dep: `uv add --group dev <pkg>`
+  - Lock update: `uv lock`
+
+### Quality Checks
+
+Run these before pushing — all must pass:
+
+```bash
+uv run ruff check .                  # lint
+uv run ruff format --check .         # format check
+uv run mypy src/                     # type check
+uv run pytest                        # tests
+uv run pytest --cov=vardoger         # coverage
+```
+
+Quick-fix formatting and auto-fixable lint issues:
+
+```bash
+uv run ruff format .                 # auto-format
+uv run ruff check --fix .            # auto-fix lints
+```
+
+### Code Standards
+- **Data structures**:
+  - Use `pydantic.BaseModel` for all JSON I/O shapes (parsing, validation, serialization). All Pydantic models live in `src/vardoger/models.py`.
+  - Use `model_validate_json(raw)` to parse, `model_dump_json()` to serialize. Avoid manual `json.loads` / `json.dumps` for typed data.
+  - Set `extra="ignore"` on models that parse external/third-party JSON with unpredictable fields.
+  - Plain `dataclasses` are fine for pure domain objects that are never serialized (e.g., `Message`, `Conversation` in `history/models.py`).
+  - Do not scatter model definitions across modules; add new models to `models.py`.
+- **Typing**:
+  - Add `from __future__ import annotations` in every module.
+  - MyPy strict mode: `disallow_untyped_defs`, `check_untyped_defs`.
+  - Prefer precise types and immutable collections (`frozenset`, `tuple`).
+- **Formatting**: enforced by ruff (replaces black + isort + autoflake). See `[tool.ruff]` in `pyproject.toml`.
+
+### Testing
+- Framework: pytest. Tests live in `tests/`, mirroring the `src/vardoger/` structure.
+- Target coverage: ≥90% for core modules.
+- All tests must pass before commit/push.
+
+### Architecture Patterns
+- **Configuration**: centralize env access (e.g., `Config.from_env()`), avoid scattered `os.getenv`.
+- **Error handling**: raise clear exceptions with actionable messages.
+- **Logging**: `getLogger(__name__)`, structured and context-rich, never log PII or secrets.
+- **Imports**: absolute imports within the `vardoger` package namespace.
+- **Immutability**: immutable DTOs, avoid mutating inputs.
+- **Prompts**: store as standalone `.md` files under `src/vardoger/prompts/`, never as inline strings. Python code loads them at runtime.

vardoger-0.1.0/CHANGELOG.md

@@ -0,0 +1,69 @@
+# Changelog
+
+All notable changes to this project are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres
+to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] — 2026-04-20
+
+### Added
+
+- Phase 4 marketplace-ready release.
+- Plugin manifests for all four platforms carry consistent metadata (`name`,
+  `version`, `description`, `author`, `homepage`, `repository`, `license`,
+  `keywords`).
+- Cursor native plugin layout: `.cursor-plugin/plugin.json` and a self-bootstrapping
+  `mcp.json` that launches the CLI via `uvx` with a `pipx run` fallback.
+- OpenClaw SKILL frontmatter now matches the ClawHub schema
+  (`version`, `metadata.openclaw.requires.bins`, `homepage`).
+- Shared analyze-skill template under `plugins/_shared/` with `scripts/render-skills.py`
+  to keep the three per-platform `SKILL.md` files in sync.
+- Repo-level `SECURITY.md`, `CHANGELOG.md`, and committed `assets/logo.svg`.
+- Public `plugins/codex/marketplace.json` so users can install via Codex's
+  custom-marketplace flow without cloning the repo.
+
+### Changed
+
+- `Development Status` classifier bumped from `3 - Alpha` to `4 - Beta`.
+- README install instructions default to the stable `pipx install vardoger` path;
+  the `--pre` / `uvx vardoger@...` flow is kept under "Previous pre-releases."
+- PRD Phase 1 checkboxes for OpenClaw history adapter and local skill install
+  flipped to match reality.
+
+### Removed
+
+- Stale pre-release wheel and sdist artifacts from `dist/`.
+
+## [0.1.0b3] — 2026-04-17
+
+### Fixed
+
+- Codex plugin registration path and sandbox-aware CLI invocation (#3).
+- `prepare` now only checkpoints after the final batch to avoid premature commits.
+
+### Added
+
+- YAML frontmatter emitted in generated `SKILL.md` outputs.
+
+## [0.1.0b2] — 2026-04-17
+
+### Changed
+
+- Pinned `astral-sh/setup-uv` to `v8.1.0` for reproducible CI installs.
+- Documented the beta install path (`pipx install --pre vardoger`).
+- Bumped CI action versions.
+
+## [0.1.0b1] — 2026-04-17
+
+### Added
+
+- First public beta on PyPI via trusted-publisher release workflow.
+- Cross-platform core: Cursor, Claude Code, OpenAI Codex, and OpenClaw.
+- Phase 1 — history readers, platform-native prompt writers, `vardoger setup`.
+- Phase 2 — skill-driven analysis pipeline (`prepare`/`synthesize`/`write`).
+- Phase 3 — staleness detection, feedback accept/reject with auto-revert,
+  confidence scoring, and A/B comparison.
+- 80% combined test-coverage floor enforced in CI plus `bandit` + `pip-audit`
+  security job.

vardoger-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,137 @@
+# Contributing to vardoger
+
+Thanks for taking the time to contribute! This document walks through the full
+workflow for submitting a pull request. For a one-paragraph version, see the
+[Contributing section in the README](README.md#contributing).
+
+Coding standards, project layout, and per-module expectations live in
+[AGENTS.md](AGENTS.md) — please skim it before your first change.
+
+## Prerequisites
+
+- Python 3.11 or newer (CI tests 3.11, 3.12, 3.13).
+- [uv](https://docs.astral.sh/uv/getting-started/installation/) for dependency
+  management.
+- A GitHub account for forking the repository.
+
+## 1. Fork and clone
+
+1. Click **Fork** on [github.com/dstrupl/vardoger](https://github.com/dstrupl/vardoger)
+   to create your own copy.
+2. Clone your fork and add the upstream remote so you can keep it in sync:
+
+   ```bash
+   git clone https://github.com/<your-username>/vardoger.git
+   cd vardoger
+   git remote add upstream https://github.com/dstrupl/vardoger.git
+   ```
+
+3. Install dependencies:
+
+   ```bash
+   uv sync
+   ```
+
+## 2. Create a topic branch
+
+Base your work on an up-to-date `main`:
+
+```bash
+git fetch upstream
+git checkout -b my-change upstream/main
+```
+
+Use a short, descriptive branch name (e.g. `fix-cursor-timestamp-parsing`,
+`add-openclaw-staleness-check`).
+
+## 3. Make your change
+
+- Follow the conventions in [AGENTS.md](AGENTS.md): Pydantic for JSON I/O,
+  `from __future__ import annotations` in every module, absolute imports within
+  the `vardoger` package, prompts as `.md` files (not inline strings).
+- Add or update tests under `tests/` to cover new behavior. Coverage must stay
+  at or above 80% overall.
+- Keep commits focused and use imperative-mood subjects (e.g. `fix cursor
+  transcript edge case`, not `Fixed a bug`). Do **not** add AI co-author
+  trailers.
+
+## 4. Run the quality gates locally
+
+CI will run the same checks on your PR; running them locally first avoids the
+back-and-forth. The one-liner:
+
+```bash
+uv run ruff check . \
+  && uv run ruff format --check . \
+  && uv run mypy src/ \
+  && uv run pytest --cov=vardoger --cov-fail-under=80
+```
+
+Individual commands, if you want to iterate on one at a time:
+
+| Check | Command |
+| --- | --- |
+| Lint | `uv run ruff check .` |
+| Auto-fix lint | `uv run ruff check --fix .` |
+| Format | `uv run ruff format .` |
+| Format check | `uv run ruff format --check .` |
+| Type check | `uv run mypy src/` |
+| Tests + coverage | `uv run pytest --cov=vardoger --cov-fail-under=80` |
+
+The security job in CI additionally runs:
+
+```bash
+uv run --with bandit bandit -r src/ -q
+uv run --with pip-audit pip-audit --skip-editable
+```
+
+You can run these locally too, but they rarely fail on feature PRs.
+
+## 5. Push and open a PR
+
+```bash
+git push -u origin my-change
+```
+
+Then open a pull request against `dstrupl/vardoger:main`. In the PR
+description:
+
+- Say **what** the change does and **why** (not the list of touched files).
+- Link any related issue.
+- Mention anything reviewers should pay extra attention to (risk, migrations,
+  follow-ups).
+
+## 6. What happens on your PR
+
+- GitHub runs the `CI` workflow automatically:
+  - `test` job: lint, format check, mypy, and pytest with an 80% coverage
+    floor on Python 3.11, 3.12, and 3.13.
+  - `security` job: `bandit` plus `pip-audit`.
+- If you are a first-time contributor, a maintainer may need to click
+  **Approve and run** before the first workflow execution. Subsequent pushes
+  to the same PR run automatically.
+- The `publish.yml` workflow does **not** run on PRs; it only fires on tagged
+  releases from `main`.
+- Maintainer will rebase and merge once the review is green and CI passes;
+  the branch is deleted after merge.
+
+## Keeping your fork up to date
+
+Rebase rather than merge to keep history linear:
+
+```bash
+git fetch upstream
+git rebase upstream/main
+git push --force-with-lease
+```
+
+## Reporting bugs and proposing features
+
+Open a GitHub issue before starting on large changes so we can discuss scope.
+For security issues, please avoid filing a public issue — contact the
+maintainer directly.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the
+[Apache License, Version 2.0](LICENSE) that covers the project.

vardoger-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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 the 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 the 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 any 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
+
+   Copyright 2026 David Strupl
+
+   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.