observe-kit 0.1.1__tar.gz

observe_kit-0.1.1/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,18 @@
+name: Bug report
+description: observed did something it should not have
+labels: [bug]
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened
+      description: A minimal decorated function and how you called it, what you expected, what you got.
+    validations:
+      required: true
+  - type: input
+    id: versions
+    attributes:
+      label: Versions
+      placeholder: observe-kit 0.1.0, structlog 25.1, Python 3.13
+    validations:
+      required: true

observe_kit-0.1.1/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/MdaaaaO/observe-kit/security/advisories/new
+    about: Report privately, not in a public issue.

observe_kit-0.1.1/.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,15 @@
+name: Feature request
+description: Propose a change to the decorator
+labels: [enhancement]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What you are trying to observe, and why the decorator does not cover it today.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal

observe_kit-0.1.1/.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: monthly
+    commit-message:
+      prefix: ci
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: monthly
+    commit-message:
+      prefix: build

observe_kit-0.1.1/.github/pull_request_template.md

@@ -0,0 +1,8 @@
+<!-- Title: a conventional commit, e.g. "feat: async support". It becomes the changelog line. -->
+
+## What and why
+
+## How it was tested
+
+<!-- For a breaking change, add a footer:
+BREAKING CHANGE: what users must do differently -->

observe_kit-0.1.1/.github/workflows/ci.yml

@@ -0,0 +1,56 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
+      - run: make lint typecheck
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
+        with:
+          python-version: ${{ matrix.python }}
+      - run: make tests
+
+  coverage:
+    # Coverage comment on PRs, badge on the data branch for main. Advisory, not a required check.
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
+        with:
+          python-version: "3.13"
+      - run: make tests
+      - uses: py-cov-action/python-coverage-comment-action@v4.5
+        with:
+          GITHUB_TOKEN: ${{ github.token }}
+          MINIMUM_GREEN: 95
+          MINIMUM_ORANGE: 85
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
+      - run: uv build
+      - run: uvx twine check --strict dist/*

observe_kit-0.1.1/.github/workflows/claude-review.yml

@@ -0,0 +1,179 @@
+name: claude-review
+
+# Two jobs, one action:
+#   review  — every non-draft PR gets an automatic review, posted as inline comments plus one
+#             sticky summary.
+#   mention — "@claude <question>" (or "@claude review" after a fix push) in a PR/issue comment
+#             gets an answer. Maintainers only: see the `if` on that job.
+#
+# Authenticated with a Claude subscription OAuth token (CLAUDE_CODE_OAUTH_TOKEN, from
+# `claude setup-token`). Until that secret exists the jobs skip with a notice instead of failing:
+# a missing reviewer must not turn a PR red.
+#
+# Public-repo safety:
+# - PRs from forks get no secrets on `pull_request`, so they are skipped with the same notice.
+#   Never switch this to `pull_request_target`: that hands the token to code from a stranger's fork.
+# - `issue_comment` runs WITH secrets on any PR, forks included, so the mention job only answers
+#   comments from the repo owner, members and collaborators.
+# - The reviewer is read-only on the repo (contents: read). It can comment; it can never push.
+#
+# The action refuses to run a workflow file that differs from the copy on the default branch
+# (anti-tamper), so a change to THIS file must be merged on its own before a PR carrying the
+# same change can be reviewed.
+
+on:
+  pull_request:
+    # Not on every push, because each round uses the plan's quota. After fixes, ask again with
+    # "@claude review".
+    types: [opened, reopened, ready_for_review]
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+
+permissions:
+  contents: read
+  pull-requests: write
+  issues: write
+  id-token: write
+  actions: read
+
+# Keyed on event, number and actor. Without the event, the reviewer's own first inline comment
+# (a pull_request_review_comment) cancels the review that is still running. Without the actor,
+# the mention job's progress comment cancels the run that posted it.
+concurrency:
+  group: claude-${{ github.event_name }}-${{ github.event.pull_request.number || github.event.issue.number }}-${{ github.actor }}
+  cancel-in-progress: true
+
+jobs:
+  review:
+    name: claude-review
+    if: >
+      github.event_name == 'pull_request' &&
+      github.event.pull_request.draft == false &&
+      !startsWith(github.event.pull_request.title, 'chore(release):') &&
+      github.actor != 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - id: token
+        name: Is the reviewer configured?
+        env:
+          TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+        run: |
+          if [ -n "$TOKEN" ]; then
+            echo "enabled=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "enabled=false" >> "$GITHUB_OUTPUT"
+            echo "::notice title=claude-review skipped::CLAUDE_CODE_OAUTH_TOKEN is not available (not set, or a PR from a fork)."
+          fi
+
+      - if: steps.token.outputs.enabled == 'true'
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0  # the review needs the base branch to diff against
+
+      - if: steps.token.outputs.enabled == 'true'
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          use_sticky_comment: true
+          prompt: |
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ github.event.pull_request.number }}
+
+            You are reviewing a pull request for observe-kit, a small Python library whose one job
+            is the `@observed` decorator: it times a call, classifies how it ended (finished,
+            expected, swallowed, raised), writes a structlog line, emits an ObservedEvent to a
+            sink, and tells a notifier on `raised`. Applications put it on hot paths and on error
+            paths, so a regression silently changes what they log, alert on or return.
+
+            Read the README and CONTRIBUTING.md first. They define the contract:
+            - The four outcomes and their rules are public API: `expected` is warned and
+              re-raised; `swallow` is logged at debug and returns `default`; any other Exception
+              is RAISED (error with traceback, notifier, re-raise); a type in both tuples counts as
+              expected; BaseExceptions that are not Exceptions pass through untouched unless
+              listed. The re-raise must be a bare `raise`, so tracebacks gain no frame.
+            - The decorator never changes the wrapped function's return value, signature
+              metadata (functools.wraps) or sync/async nature, and refuses generators.
+            - Event names (`<name>.<outcome>`), the ObservedEvent fields, the log line's keys
+              (duration_ms, error, the bound context) and the EventSink / Notifier protocols are
+              public API: sinks and dashboards downstream depend on them.
+            - NotifyPolicy is a privacy boundary. By default no context field reaches a notifier;
+              only allow-listed fields, only the first line of the error, and never a URL.
+              Anything that lets more through is a security finding, not a style note.
+            - structlog is the only runtime dependency. A new one needs a strong reason.
+
+            Look for, in this order:
+            1. Correctness bugs: outcome classification, the sync and async wrappers drifting
+               apart, timing that does not cover the await, `fields` / `detail` resolution
+               against the signature (positional, keyword, defaults, malformed calls), Provider
+               fallbacks when an attribute is missing or the wrong shape.
+            2. Anything that widens what a notification can carry (see NotifyPolicy above).
+            3. Breaking changes to the public API above that the title does not mark with `!`
+               and a BREAKING CHANGE footer.
+            4. Workflow security: secrets reaching fork PRs, `pull_request_target`, untrusted
+               GitHub expressions (PR titles, comment bodies) interpolated straight into `run:`
+               instead of passed through `env:`, permissions wider than the job needs, or
+               publishing without trusted publishing.
+            5. New behaviour without a test, for sync and async alike. MemorySink collects
+               events, so most tests need nothing else.
+            6. README drift: a changed argument, outcome rule or protocol that the README still
+               documents the old way.
+
+            Do NOT comment on formatting, import order or line length. ruff, mypy --strict and
+            actionlint already gate those in CI. Do not restate the PR description back.
+
+            Use `gh pr diff` and `gh pr view` to see the change. Post specific findings as inline
+            comments on the exact lines (mcp__github_inline_comment__create_inline_comment).
+            Then post ONE summary comment via `gh pr comment`: a short verdict, the findings
+            ranked by severity, and anything you could not verify. If there is nothing
+            significant, say so in two sentences. A short honest review beats a long padded one.
+
+            Budget: you have a hard cap of 60 tool calls, and the run fails if you exceed it. Start
+            from `gh pr diff --name-only` and `gh pr diff`. Read a file in full only when the diff
+            alone cannot answer the question. Post the summary comment no later than your 45th
+            call, and say what you did not get to. An unposted review is worth nothing.
+          claude_args: |
+            --max-turns 60
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Read,Grep,Glob"
+
+  mention:
+    name: claude-mention
+    # Maintainers only: issue_comment runs with secrets even on fork PRs, so anyone else could
+    # spend the plan's quota. Never react to the bot's own comments, or it talks to itself forever.
+    if: >
+      (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment') &&
+      contains(github.event.comment.body, '@claude') &&
+      contains(fromJSON('["OWNER","MEMBER","COLLABORATOR"]'), github.event.comment.author_association) &&
+      github.actor != 'claude[bot]'
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - id: token
+        name: Is the reviewer configured?
+        env:
+          TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+        run: |
+          if [ -n "$TOKEN" ]; then
+            echo "enabled=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "enabled=false" >> "$GITHUB_OUTPUT"
+            echo "::notice title=claude-mention skipped::CLAUDE_CODE_OAUTH_TOKEN is not set."
+          fi
+
+      - if: steps.token.outputs.enabled == 'true'
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+
+      - if: steps.token.outputs.enabled == 'true'
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          # No prompt means tag mode: it answers the @claude comment in context. "@claude review"
+          # is a full review of the head, so it gets the review job's budget. A question gets 20.
+          claude_args: |
+            --max-turns ${{ contains(github.event.comment.body, '@claude review') && '60' || '20' }}
+            --append-system-prompt "You have a hard cap on tool calls (--max-turns) and the run FAILS the moment you exceed it. Work from `gh pr diff --name-only` and `gh pr diff`; read a file in full only when the diff cannot answer the question. Post your answer (for a review request, one summary comment via `gh pr comment`) by three quarters of that budget at the latest, saying plainly what you did not get to."
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh issue view:*),Read,Grep,Glob"

observe_kit-0.1.1/.github/workflows/pr.yml

@@ -0,0 +1,12 @@
+name: pr
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+
+permissions:
+  contents: read
+
+jobs:
+  pr-title:
+    uses: MdaaaaO/conventional-release/.github/workflows/pr-title.yml@v0

observe_kit-0.1.1/.github/workflows/release.yml

@@ -0,0 +1,60 @@
+name: release
+
+# `make release` opens the release PR; squash-merging it lands here, tags vX.Y.Z and publishes.
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  tag:
+    uses: MdaaaaO/conventional-release/.github/workflows/tag.yml@v0
+    permissions:
+      contents: write
+
+  build:
+    needs: tag
+    if: needs.tag.outputs.released == 'true'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ needs.tag.outputs.tag }}
+      - uses: astral-sh/setup-uv@v10.2.0
+      - run: uv build
+      - run: uvx twine check --strict dist/*
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  testpypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write  # trusted publishing, no token stored anywhere
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  pypi:
+    needs: testpypi
+    runs-on: ubuntu-latest
+    environment: pypi  # required reviewer: the maintainer
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

observe_kit-0.1.1/.gitignore

@@ -0,0 +1,11 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.coverage
+coverage.xml
+htmlcov/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/

observe_kit-0.1.1/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
+
+## 0.1.1 (2026-09-25)
+
+
+### Documentation
+
+* contribution model, coverage report and badges ([#3](https://github.com/MdaaaaO/observe-kit/issues/3)) ([29cd95e](https://github.com/MdaaaaO/observe-kit/commit/29cd95ec318474eb71f9e3d1fc6b048d481a2cb5))
+
+
+### CI
+
+* claude review on pull requests ([#2](https://github.com/MdaaaaO/observe-kit/issues/2)) ([998b9b9](https://github.com/MdaaaaO/observe-kit/commit/998b9b9e76edea8bc7dcf95e258069ed715997b7))
+
+## 0.1.0 (2026-09-25)
+
+
+### Features
+
+* observed decorator with sinks, notifier and notify policy ([4116dab](https://github.com/MdaaaaO/observe-kit/commit/4116dab7d4de6808fd7c62d48a2d4256c03bf56b))

observe_kit-0.1.1/CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing
+
+Thanks for helping. The short version:
+
+- **Open an issue first** for anything bigger than a typo, so we agree on the change before you write it.
+- **PR titles are [Conventional Commits](https://www.conventionalcommits.org).** PRs are
+  squash-merged, the title becomes the commit, and the commit becomes the changelog line. The
+  `pr-title` check enforces this (`feat: async support`, `fix: …`, `docs: …`). Put `!` after
+  the type or scope for a breaking change, and explain it in a `BREAKING CHANGE:` footer in the
+  PR description.
+- **`make ci` passes locally** before you push. It runs ruff, `mypy --strict`, pytest with branch
+  coverage, and actionlint. You need [uv](https://docs.astral.sh/uv/). Run `make install` once.
+- Maintainer PRs start from an issue and say so: `Closes #N` or `Refs #N` in the description.
+  Release PRs and Dependabot are exempt.
+- New behaviour comes with a test, for sync and `async def` alike. `MemorySink` collects events,
+  so most tests need nothing else.
+- The scope is the decorator. Integrations (a Prometheus sink, a Slack notifier) belong in your
+  application or in a separate package; the protocols in `observe_kit.sinks` are the extension points.
+
+## Code review
+
+An automated Claude review comments on each PR from this repo's branches, as inline threads plus
+one summary comment. Maintainers can ask it again after a fix push with `@claude review`. Release
+PRs and Dependabot are not reviewed. The `coverage` job adds a comment with the coverage of the
+lines the PR changes; PRs from forks get a read-only token, so there the job runs but cannot comment.
+
+The review is advisory, but its threads are not optional: a PR is merged only when every thread is
+answered and resolved (the `main` ruleset requires it). An answer is one of:
+
+1. **A fix on the branch** — the default, even if it costs another review cycle. Reply with the
+   commit SHA.
+2. **A follow-up issue**, only for what is genuinely outside the PR's scope, labelled
+   `review-followup` and cited in the reply. It is picked up first, right after the merge.
+3. **A disagreement, with the reason**, citing the commit or issue that makes it checkable.
+
+A finding is never parked without an issue number. PRs are squash-merged only, and the branch is
+deleted on merge.
+
+## Releasing (maintainers)
+
+Releases use [conventional-release](https://github.com/MdaaaaO/conventional-release).
+`make release` (or `make release ARGS=minor`) opens the `chore(release): X.Y.Z` PR. Squash-merge
+it with the title unchanged. `release.yml` then tags the merge commit, publishes the GitHub
+Release, publishes to TestPyPI and then to PyPI (the `pypi` environment waits for approval).
+`make release-dry` shows what would ship.

observe_kit-0.1.1/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Georg Kasper
+
+   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.
+