tycho-cli 0.0.1__tar.gz

tycho_cli-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,70 @@
+# CI for Tycho (TYCHO-9). Tycho gates other people's work, so its own gate has to be real:
+# every job here fails loudly rather than degrading to a pass.
+#
+# Note the commands are NOT piped. Piping a runner through `tail`/`head` discards its exit
+# code (a POSIX pipeline exits with its *last* command's status), which is exactly the
+# false-green Tycho exists to catch — see TYCHO-31. Keep it that way.
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  # uv.lock is checked in to pin the dev toolchain, but nothing installs from it (the
+  # matrix below uses pip), so drift is invisible until someone runs `uv sync` and gets an
+  # environment matching neither CI nor pyproject.toml. It had already silently drifted
+  # once (TYCHO-42). This job is the enforcement that makes tracking it mean something.
+  # uv comes from pip rather than an action: one less third-party version to pin.
+  lock:
+    name: uv.lock is current
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"  # the floor in requires-python — resolve against the oldest
+      - run: python -m pip install uv
+      - name: Check lockfile
+        run: uv lock --check  # fails if uv.lock disagrees with pyproject.toml
+
+  test:
+    name: py${{ matrix.python-version }} (${{ matrix.os }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      # Report every version's result: "does it break on 3.11?" is the question this
+      # matrix exists to answer, and fail-fast would cancel the answer.
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+        os: [ubuntu-latest]
+        # Windows is a first-class target (TYCHO-28): one job proves the suite, the wheel
+        # build/install, and the console-script hook all work under cp1252/backslash/`.exe`.
+        # One version keeps it cheap — the version matrix is the Linux axis's job.
+        include:
+          - python-version: "3.12"
+            os: windows-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: python -m pip install -e ".[dev]"
+
+      - name: Lint
+        run: ruff check tycho tests
+
+      # Includes tests/test_e2e_install.py, which builds the wheel *and* the sdist and
+      # installs each into a clean venv on this exact interpreter — so the matrix covers
+      # both artifacts users get, not just the in-tree package.
+      - name: Test
+        run: pytest -q --cov=tycho --cov-fail-under=80

tycho_cli-0.0.1/.github/workflows/release.yml

@@ -0,0 +1,109 @@
+# Release for Tycho (TYCHO-10). Tag `vX.Y.Z` → build sdist+wheel, smoke-test the artifact,
+# publish to PyPI. Scaffold: it does nothing until you (a) push a version tag and (b) set up
+# publishing on PyPI (see the `publish` job). Nothing here is triggered automatically.
+#
+# The tag must match tycho/__init__.py:__version__ (Hatchling reads it). The build job asserts
+# that, so a mistagged release fails loudly instead of shipping the wrong number.
+#
+# Not piped, deliberately — a piped runner discards its exit code (TYCHO-31). Keep it that way.
+#
+# The `binaries` job (TYCHO-69) freezes a standalone one-file binary per target and asserts
+# `tycho --version`. It is BUILD-ONLY: it does not sign, notarize, or attach to a release —
+# those need operator-provisioned secrets. See docs/bundler-spike.md and docs/tycho-69-remaining.md.
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    name: build + smoke-test the artifact
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"  # build on the floor from requires-python
+
+      - name: Tag matches the package version
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          pkg="$(python -c 'import tycho; print(tycho.__version__)')"
+          test "$tag" = "$pkg" || { echo "tag $tag != package $pkg"; exit 1; }
+
+      - name: Build sdist + wheel
+        run: |
+          python -m pip install build
+          python -m build  # -> dist/*.tar.gz, dist/*.whl
+
+      - name: Smoke-test the built wheel
+        run: |
+          python -m venv /tmp/smoke
+          # Install by the *distribution* name (tycho-cli); the console script it drops is `tycho`.
+          /tmp/smoke/bin/pip install --no-index --find-links dist tycho-cli
+          got="$(/tmp/smoke/bin/tycho --version)"
+          test "$got" = "tycho ${GITHUB_REF_NAME#v}" || { echo "smoke: got '$got'"; exit 1; }
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  binaries:
+    name: standalone binary — ${{ matrix.target }}
+    # Freeze a one-file binary per target with PyInstaller and assert `tycho --version` (TYCHO-69).
+    # Build-only: no signing/notarization, no release upload — those need operator secrets. Native
+    # runner per target because PyInstaller does not cross-compile.
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - { target: macos-arm64, runs-on: macos-14 }
+          - { target: macos-x86_64, runs-on: macos-13 }
+          - { target: linux-x86_64, runs-on: ubuntu-latest }
+          - { target: windows-x86_64, runs-on: windows-latest }
+    runs-on: ${{ matrix.runs-on }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"  # build on the floor from requires-python
+
+      - name: Freeze a one-file binary
+        run: |
+          python -m pip install pyinstaller .
+          pyinstaller --onefile --clean --noconfirm --name tycho --console --collect-submodules tycho tycho/__main__.py
+
+      - name: Smoke-test the binary (tycho --version)
+        shell: bash  # bash is present on the Windows runner; keeps the assert one shell
+        run: |
+          bin="dist/tycho"; [ -f "dist/tycho.exe" ] && bin="dist/tycho.exe"
+          got="$("$bin" --version)"
+          test "$got" = "tycho ${GITHUB_REF_NAME#v}" || { echo "smoke: got '$got'"; exit 1; }
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: tycho-${{ matrix.target }}
+          path: dist/tycho*
+
+  publish:
+    name: publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    # Trusted Publishing (OIDC) — no stored token. TO ENABLE: on PyPI, add this repo +
+    # workflow as a "trusted publisher" for the `tycho-cli` project (Project → Publishing).
+    # Prefer a GitHub Environment named `pypi` with required reviewers so a human approves
+    # each publish. Alternatively, drop OIDC and pass `password: ${{ secrets.PYPI_API_TOKEN }}`.
+    environment:
+      name: pypi
+      url: https://pypi.org/project/tycho-cli/
+    permissions:
+      id-token: write  # OIDC token for Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

tycho_cli-0.0.1/.gitignore

@@ -0,0 +1,236 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# macOS
+.DS_Store
+
+# Local AI / editor tooling
+.claude/
+.cursor/
+.codex/
+.opencode/
+
+# Tycho's own repo-local state (install stamp + hook heartbeat)
+.tycho/
+
+# Local-only: internal planning/strategy docs + agent instruction files. Kept on disk
+# (CLAUDE.md/AGENTS.md still drive local agents) but never committed to the public repo.
+.private/
+/CLAUDE.md
+/AGENTS.md

tycho_cli-0.0.1/.tycho.toml

@@ -0,0 +1,25 @@
+# .tycho.toml — Tycho configuration. Managed by `tycho scope` / `tycho relay`; also safe
+# to hand-edit. Tycho never assumes this file exists: with an empty `include` below,
+# `scope_drift` stays UNSUPPORTED and every other check runs as it does with no file.
+
+[scope]
+# Directories/files the agent is allowed to edit, as globs with POSIX separators
+# (e.g. "src/**", "tests/**"). An edit outside these FAILs scope_drift. This is an
+# explicit, deterministic bound — never inferred from the prompt.
+# Manage with: tycho scope add|remove|set <glob>...  (or /tycho-scope-* in Claude Code)
+include = ["**"]
+# Paths to carve back OUT of `include`, same glob syntax. An edit matching any of these
+# FAILs scope_drift even if it also matches `include` — exclude wins (e.g. include "**",
+# exclude "LICENSE" allows the whole tree but that one file). Empty = pure allowlist.
+# Manage with: tycho scope add|remove|set --exclude <glob>...
+exclude = ["LICENSE"]
+
+[checks]
+# Check names to disable entirely (rarely needed), e.g. "command_execution".
+disable = []
+
+[relay]
+# Feed a non-VERIFIED verdict back to the agent so it keeps working until VERIFIED
+# (Claude Code only, bounded by TYCHO_RELAY_MAX). Off by default — verdicts stay
+# human-only. Toggle: tycho relay --on|--off  (or /tycho-relay-on / -off in Claude Code).
+enabled = true

tycho_cli-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to Tycho
+
+Thanks for helping out. Tycho is an offline, stdlib-only verifier (Python ≥ 3.11, zero
+runtime dependencies) that proves an agent did what it claimed — from git, the filesystem,
+exit codes, and the harness event stream.
+
+## Setup
+
+```sh
+python -m venv .venv
+. .venv/bin/activate          # Windows: .venv\Scripts\activate
+pip install -e ".[dev]"       # or: uv pip install -e ".[dev]"
+```
+
+## Before you push
+
+- **Tests:** `python -m pytest -q`
+- **Lint:** `ruff check tycho tests`
+
+Both run in CI (Linux, Python 3.11 / 3.12 / 3.13) on every pull request.
+
+## Design invariants (don't break these)
+
+- **Never blocks.** The Stop hook (`hook.py`) always exits 0 and fails open (returns `None`)
+  on any error. Only `tycho verify` exits 1 (on FAILED), so CI can gate on it.
+- **Harness-agnostic engine.** Checks run on a frozen, normalized `Session` and never learn
+  which harness produced it. All harness-specific code lives in `harness.py` (the adapter)
+  plus one `parse_*` reader in `events.py`.
+- **Immutable.** `Session` / `Event` / `FileEdit` are frozen; `verify.gather()` is the only
+  inbound I/O — everything downstream is pure.
+
+## Adding support for a new harness
+
+One adapter + one reader + one fixture, no engine change:
+
+1. Add an adapter in `harness.py` (detect, repo root, transcript location, output format).
+2. Add a `parse_*` reader in `events.py`, pinned to a real fixture in `tests/fixtures/`.
+3. That's it — the engine and the checks stay untouched.
+
+See [`docs/hooks.md`](docs/hooks.md) for the multi-harness design and
+[`docs/harness-support.md`](docs/harness-support.md) for the contracts each adapter depends on.
+
+## Commits
+
+- **No AI-agent attribution.** Do not add `Co-authored-by` trailers or list any agent
+  (Claude, Codex, Copilot, …) as author or co-author, regardless of which tool produced the
+  change.
+- Keep commits focused, and write *why*, not just *what*.
+
+## Pull requests
+
+Open a PR against `main`. CI (tests + `ruff`) must be green before merge.

tycho_cli-0.0.1/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 [2026] [Arnav Bonigala]
+
+   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.