scovant-core 0.1.0__tar.gz

scovant_core-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.pyc
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+npm/node_modules/

scovant_core-0.1.0/CHANGELOG.md

@@ -0,0 +1,275 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+Keep a Changelog; versions follow semver. `ruleset_version` changes are called
+out explicitly because scores are only comparable within one ruleset version.
+
+## [0.1.0] - 2026-09-12
+
+### Added
+- Package skeleton, security layer (SSRF guard), parsers for robots.txt,
+  Content-Signal, llms.txt, MCP discovery, UCP profile, HTML
+  metadata/structured data, and the AI crawler registry.
+- 45 deterministic checks (`ruleset_version` `2026.09`) across 5 categories
+  — 5 of the 45 are `experimental` (marked below): evaluated and reported
+  on every scan, but excluded from the Static Signal Score until
+  calibrated against real-world traffic and promoted:
+  - Access & Discovery (10) — `CORE-ACCESS-001` HTTPS reachability,
+    `CORE-ACCESS-002` robots.txt availability and syntax,
+    `CORE-ACCESS-003` AI search crawler policy,
+    `CORE-ACCESS-004` training vs. search crawler separation,
+    `CORE-ACCESS-005` sitemap availability,
+    `CORE-ACCESS-006` sitemap freshness,
+    `CORE-ACCESS-007` canonical URL integrity,
+    `CORE-ACCESS-008` indexability,
+    `CORE-ACCESS-009` llms.txt presence and integrity,
+    `CORE-ACCESS-010` Content-Signal declaration
+  - Machine Understanding (12) — `CORE-MACHINE-001` JSON-LD parseability,
+    `CORE-MACHINE-002` Organization entity,
+    `CORE-MACHINE-003` WebSite/WebPage entity,
+    `CORE-MACHINE-004` Product structured data,
+    `CORE-MACHINE-005` Offer price/currency/availability,
+    `CORE-MACHINE-006` product identifier count,
+    `CORE-MACHINE-007` breadcrumbs,
+    `CORE-MACHINE-008` metadata quality,
+    `CORE-MACHINE-009` heading structure,
+    `CORE-MACHINE-010` language declaration,
+    `CORE-MACHINE-011` image alt coverage,
+    `CORE-MACHINE-012` visible vs. structured price (experimental)
+  - Agent Interfaces (9) — `CORE-INTERFACE-001` MCP discovery presence,
+    `CORE-INTERFACE-002` MCP server declaration quality,
+    `CORE-INTERFACE-003` WebMCP static presence,
+    `CORE-INTERFACE-004` WebMCP tool declaration quality (experimental),
+    `CORE-INTERFACE-005` OpenAPI discovery,
+    `CORE-INTERFACE-006` OAuth authorization-server metadata,
+    `CORE-INTERFACE-007` OAuth protected-resource metadata,
+    `CORE-INTERFACE-008` UCP profile validity (experimental),
+    `CORE-INTERFACE-009` agent discovery surface presence — A2A cards,
+    AI-plugin manifests, agents.json, Agent Skills (experimental)
+  - Trust & Commerce (7) — `CORE-TRUST-001` contact/support
+    discoverability, `CORE-TRUST-002` shipping policy discoverability,
+    `CORE-TRUST-003` returns/refund policy discoverability,
+    `CORE-TRUST-004` privacy policy discoverability,
+    `CORE-TRUST-005` terms/conditions discoverability,
+    `CORE-TRUST-006` security.txt discoverability,
+    `CORE-TRUST-007` pricing discoverability
+  - Operability & Efficiency (7) — `CORE-OPERABILITY-001`
+    server-rendered core content, `CORE-OPERABILITY-002` redirect chain
+    complexity, `CORE-OPERABILITY-003` cache validators,
+    `CORE-OPERABILITY-004` broken machine-consumable endpoints,
+    `CORE-OPERABILITY-005` agent parse cost, `CORE-OPERABILITY-006`
+    form/control labels, `CORE-OPERABILITY-007` machine reference
+    integrity (experimental; its gatherer runs only under `--experimental`
+    — the only gatherer whose requests leave the target's own origin)
+- `scovant scan` CLI (`scovant`/`scovant check`) with `--profile`,
+  `--format text|json`, `--min-score`, `--fail-on`, `--timeout`,
+  `--max-pages`, `--user-agent`, `--include`/`--exclude`, `--experimental`,
+  `--token-chars-ratio` (characters-per-token estimate for
+  `CORE-OPERABILITY-005`'s page-cost evidence, default 4), `--quiet`,
+  `--no-color`, `--verbose`, and a stable exit-code contract (0 ok, 1
+  threshold, 2 invalid input, 3 network, 4 security block, 5 internal
+  error).
+- Human-readable text report and a versioned JSON report
+  (`schema_version` `1.0`), both driven off one `Report` model.
+- Network safety model: scheme allow-list, DNS/literal-IP SSRF guard
+  re-checked on every redirect hop, a driven (not automatic) redirect loop
+  capped at 5 hops, per-kind response size caps, connect/request/total-budget
+  timeouts — see `docs/security.md`.
+- Deterministic profile resolution (`content`/`commerce`/`saas`/`api`) —
+  see `docs/profiles.md`.
+- Golden-report regression tests for four canonical fixture sites —
+  `commerce-good` (100, A), `commerce-bad` (35, F), `api-good` (89, B),
+  `saas-mixed` (80, B) — plus unit tests for every parser, gatherer, and
+  check.
+- Evidence-honesty rules applied uniformly across the checks:
+  - A reference the scanner could not fetch (`status: null`) is reported as
+    `unresolved`, never as a broken link — whatever declared it. When
+    nothing could be read at all, the check is `ERROR`, not `PASS`.
+  - A declared MCP endpoint is recorded but never judged: it speaks
+    JSON-RPC over POST and Core never performs the handshake, so whatever it
+    answers to a GET is `inconclusive`.
+  - A 200 response carrying an HTML page where a machine document was
+    requested (a catch-all router / soft-404 template) is treated as the
+    document being ABSENT — for `robots.txt`, sitemaps, `llms.txt` and
+    OpenAPI specs alike — and recorded as `served_as_html`. OpenAPI
+    discovery keeps probing the remaining candidates instead of locking
+    onto such a response.
+  - An unresolvable hostname is a network failure (CLI exit 3), not a
+    security block (exit 4): nothing was blocked, the name does not exist.
+  - A report whose entry URL never answered carries `final_url: null`.
+- Sitemap and MCP server-card probes follow redirects through the guarded
+  client, so a document declared behind a 301 is found rather than reported
+  as absent.
+- The text report prints `(evaluated/applicable)` check counts beside each
+  category score, and an `Experimental (not scored)` block listing any
+  experimental check that evaluated to something other than `N/A` (or a
+  one-line notice when none did); `docs/methodology.md` documents the
+  per-category check/weight distribution.
+- Documented, capped request budget per scan beyond the entry-page fetch
+  and always-on discovery documents: policy pages ≤5, `security.txt` ≤2,
+  OAuth metadata 2, UCP profile 1, agent discovery surfaces ≤10 (≤11 when
+  the OpenAPI document was found at a path other than `/openapi.json` —
+  three of the thirteen conventional paths, the OpenAPI root document and
+  the two OAuth discovery documents, are shared documents another gatherer
+  already fetched this scan, so a DEFINITIVE earlier answer (a real 200 +
+  real JSON, a genuine 404/410, or a soft-200 HTML catch-all) is recorded
+  from that read instead of being probed a second time; an inconclusive
+  earlier read is never guessed into an answer and is probed directly),
+  machine reference integrity ≤20 (`--experimental` only — the only
+  gatherer gated on the flag, zero requests without it) — see
+  `docs/security.md`.
+- The machine reference integrity probe (`analysis/integrity_probe.py`) is
+  routed through the same guarded `SecureClient` every other gatherer
+  uses for its package-registry lookups (SSRF guard, size cap, and a
+  refusal of any redirect that would leave the requested registry host —
+  no cross-host hop is followed even when the hop itself is a safe public
+  address); DNS lookups for domain references remain their own, separate,
+  HTTP-free resolution. It only ever runs under `--experimental` and is
+  bounded by the ≤20-lookup budget above.
+- `--format markdown` — the same `Report` rendered as GitHub-flavored
+  Markdown (score table, per-category breakdown, findings grouped by
+  status with collapsible evidence) for pasting into a PR or issue.
+- `--format html` — the same `Report` rendered as one self-contained HTML
+  document (inline CSS, no external resources, no JavaScript) suitable to
+  open directly in a browser or attach as a CI artifact. Both new
+  renderers are plain Python over the existing `Report` model
+  (`html.escape` for HTML) — no template-engine dependency added.
+- `--allow-private-networks` — an explicit, off-by-default opt-in that
+  lifts the SSRF address block for the scan's target host only (every
+  other protection — scheme allow-list, redirect re-check, size caps,
+  request budget — stays in force); the CLI and the GitHub Action's
+  `allow-private-networks` input both map to the same
+  `SecurityPolicy.allow_private_networks` flag, and every report format
+  prints a one-line notice when it was used. See `docs/security.md` §
+  Private-network targets (opt-in) — the match is on the exact hostname
+  string you typed (`localhost` does not cover `127.0.0.1`).
+- Composite GitHub Action (`action.yml` at the package root, so
+  `uses: Scovant/scovant-core@v1` runs it): installs itself from the
+  checked-out ref (`pip install "$GITHUB_ACTION_PATH"`, no PyPI
+  round-trip, no version skew between the pinned tag and the code that
+  runs), scans one URL, writes a Markdown Step Summary, uploads the full
+  report as a workflow artifact, and fails the step per its
+  `min-core-score`/`fail-on` gate. Inputs: `url`, `profile`,
+  `min-core-score`, `fail-on`, `experimental`, `timeout`, `report-format`,
+  `allow-private-networks`. Outputs: `score`, `grade`, `pass_count`,
+  `warn_count`, `fail_count`, `report_path`. One URL, one run, no state,
+  no comparison across runs — see the README's "Free boundary" note for
+  where Scovant Monitor picks up.
+- `scovant mcp` — a stdio MCP server behind the optional `[mcp]` extra
+  (`mcp>=1.28,<2`), exposing five read-only tools (`scan_site`,
+  `get_core_score`, `list_checks`, `explain_check`, `get_finding`) so an
+  agent host can run a passive scan as a tool call instead of a shell
+  command. Single-flight (one scan at a time) and keeps only the last 8
+  reports in memory for `get_finding` to read back; never opens a browser,
+  never performs an MCP `initialize`/`tools/call` against the *scanned*
+  site, never authenticates.
+- One shared `document_status()` rule backs every one of the nine checks
+  that classify a single well-known document fetch (robots.txt, sitemaps,
+  llms.txt, MCP/OpenAPI/OAuth/UCP/`security.txt` discovery) — see
+  `docs/methodology.md` § The status model for the exact ERROR/N/A/PASS
+  boundary it enforces.
+- Discovery-surface probe budget: ≤13 candidate requests per scan, ≤10
+  when all three shared documents (OpenAPI at `/openapi.json`, both OAuth
+  well-knowns) gave a definitive earlier answer — an inconclusive earlier
+  read (5xx/401/403/error/a different path) is re-probed directly instead
+  of being guessed. See the request-budget bullet above.
+- Documentation: `docs/methodology.md`, `docs/checks.md` (generated),
+  `docs/core-vs-cloud.md`, `docs/security.md`, `docs/profiles.md`,
+  `docs/releasing.md`.
+- Published, generated JSON schema for the report (`docs/report.schema.json`,
+  JSON Schema draft 2020-12) — `scovant_core.schema.report_schema()` derives
+  it from the `Report` pydantic model, `python -m scovant_core.schema`
+  writes it, and a test pins the committed file to the generator and
+  validates every golden fixture and every MCP tool's `inputSchema` against
+  it. Adding a report field never bumps `schema_version`; removing or
+  retyping one does — see `docs/methodology.md` § Report schema.
+- `--contribute` — opt-in, off by default: after a scan completes, sends
+  one HTTPS POST to a single fixed URL with an aggregate-only measurement
+  (`domain`, `timestamp`, `core_version`, `ruleset_version`,
+  `ruleset_digest`, `profile`, `experimental`, `check_statuses`, `score`)
+  for the community index at scovant.com/research. No page content, no
+  evidence, no IP address is ever sent. Never blocks or changes the exit
+  code; refused (exit 2) together with `--allow-private-networks`. See the
+  README's "Community contributions" section and `docs/security.md` §
+  Outbound requests.
+- `@scovant/core` — a thin npm launcher (`npm/`) that runs the Python
+  engine rather than reimplementing any of it: it resolves a runner in
+  order (`uvx`, then `pipx`, then `python3 -m scovant_core`), each pinned
+  to the exact npm package version, and exits 9 when none is usable. The
+  package's own `src/scovant_core/__main__.py` was added so the third
+  fallback (`python3 -m scovant_core`) actually works. Published to npm
+  from a tag-triggered `publish_npm` job that runs only after the PyPI
+  `release` job succeeds, behind its own reviewer-gated environment; it
+  does not use `--provenance` — npm cannot attest provenance from a
+  private source repository — and that limitation is documented in the
+  runbook and the npm README. The `python3 -m scovant_core` fallback is the
+  one path that cannot pin the version, so the launcher compares the
+  version that interpreter reports with its own and warns on stderr,
+  naming both, before running it — it never substitutes an engine version
+  silently. A probe killed by its own timeout is reported as a timeout
+  (with `SCOVANT_NPM_PROBE_TIMEOUT_MS` to raise the budget), never as a
+  missing tool, and the published tarball carries the Apache-2.0 licence
+  text.
+- `docs/example-report.md` — a full example report rendered from the
+  `commerce-good` golden fixture via `python -m scovant_core.docs
+  --example`, generated rather than hand-written, and pinned by a test
+  so it can never drift from the renderer or the fixture.
+
+### Changed
+- A verdict drawn from a document the fetch layer cut off at its per-kind
+  byte cap now declares that partial read wherever it happens, not only on
+  the four robots.txt-derived checks (`CORE-ACCESS-002`, `-003`, `-004`,
+  `-010`) that used to be the whole contract. The truncation flag travels
+  from the fetch layer through every body-reading gatherer to the checks:
+  such a finding records `"truncated": true` in its evidence, caps its
+  confidence at `medium`, and says so in its summary — on every branch,
+  including a `FAIL`, since a partial read can invert a verdict in either
+  direction. 41 of the 45 checks participate; the remaining four
+  (`CORE-ACCESS-001`, `CORE-OPERABILITY-002`, `-003`, `-004`) are audited
+  exemptions whose verdict is drawn from status codes, response headers, or
+  the redirect chain — data a byte cap cannot affect. Truncation does not
+  change a verdict: the same site scans to the same statuses and the same
+  score whether a document was read in full or cut off, which a parity test
+  asserts directly, and the set of checks carrying the flag is pinned so the
+  coverage cannot shrink unnoticed. (The one status change on this release
+  is separate and deliberate — see the JSON-probe entry below.) Three
+  further tests make the contract structural rather than a convention — one
+  enumerates the gatherers, one enumerates the checks, and one walks every
+  individual verdict branch of every participating check, so a check that
+  declares on one branch and stays silent on another fails rather than
+  passing on the strength of its other branches.
+  `docs/methodology.md` and `docs/security.md` describe the wider
+  contract; reports produced before it are identified by
+  `provenance.core_version` / `core_version`.
+- The shared JSON probe used to answer "truncated" and "not valid JSON"
+  identically, so an oversized document was reported as ABSENT. It now
+  distinguishes the two, and `CORE-INTERFACE-001` (MCP discovery presence)
+  reports `ERROR` for an MCP server card it could not read in full instead
+  of claiming the card is not there. **This is the one status change in this
+  release, and it can move a report's outcome.** An `ERROR` counts toward a
+  category's applicable weight, so a site whose only unreadable document is
+  an oversized server card can now fall below the evidence-coverage floor
+  and be reported as `INSUFFICIENT_EVIDENCE` rather than scored. That is the
+  intended trade: a document we could not read is not a document that is
+  absent, and reporting "no MCP discovery file is published" about a file we
+  never finished reading is the over-claim this release exists to remove.
+  It cannot fire on a genuinely absent document — a real 404 still yields a
+  confirmed absence, which a test pins alongside the `ERROR` case.
+- `CORE-OPERABILITY-005` states a token estimate taken from a truncated
+  page as a floor ("at least N tokens"), so a partial read can no longer
+  read as a measurement that came in under the threshold. The cost band
+  follows the sentence: on a partial read the finding's evidence reports
+  `level: null` with `level_at_least` naming the band, instead of asserting
+  a below-threshold classification the floor cannot support.
+
+### Fixed
+- Every report format (Markdown, HTML, and text) now accounts for every
+  check it counts: the header/summary line counts all 45 checks, but
+  experimental `N/A` findings appeared in no section of the body, so the
+  arithmetic did not reconcile (37 PASS + 8 N/A with only 5 N/A listed).
+  They are now listed as bare ids — in the "Experimental (not scored)"
+  section for Markdown and HTML, and on the same compact "N/A: ..." line
+  for text. Statuses, scoring and applicability are unchanged — this is a
+  rendering fix.
+- `cli.py`'s `_PROFILES` is now imported from `scovant_core.profiles`
+  instead of a second, hand-duplicated tuple.

scovant_core-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at security@scovant.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

scovant_core-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing
+
+Thank you for helping make AI-agent readiness measurable.
+
+## How changes land
+
+This repository is a mirror. Pull requests are welcome and are reviewed here,
+but they are merged in Scovant's development monorepo and appear here in the
+next sync commit with your authorship preserved as a co-author trailer.
+Please do not be surprised when your PR is closed with a reference to the
+sync commit that contains it.
+
+## What we accept
+
+New deterministic checks, parser improvements, support for new public
+standards, test fixtures, output formats, documentation.
+
+A new check must satisfy at least four of: machine-verifiable, deterministic,
+reproducible, useful across many sites, linked to an authoritative standard,
+meaningful to agent access/understanding/action, low operational cost, safe
+to evaluate passively. Checks that need a real agent or a browser session
+belong to Scovant Cloud, not here.
+
+## Requirements for every PR
+
+- tests for every parser or check touched (fixtures must be synthetic — see
+  `fixtures/PROVENANCE.md`);
+- no network access in unit tests;
+- no new runtime dependency without discussion;
+- `ruff check` and `pytest` green.
+- `mypy src` clean.
+- A ruleset change must update the golden reports explicitly
+  (`SCOVANT_CORE_UPDATE_GOLDENS=1 pytest tests/test_golden.py`) and the diff
+  must be reviewed.

scovant_core-0.1.0/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 Scovant
+
+   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.