@journeeze/sdk 0.0.0-stage → 0.1.0-rc.2

package/AGENTS.md

@@ -0,0 +1,67 @@
+# Integrating Journeeze — guide for coding agents
+
+Rules for an agent adding `@journeeze/sdk` to a host app. The Journeeze contracts are the source
+of truth: SDK (C0a), transport (C0b), journeys (C0c) and signals (C0d), with the integration guide.
+The public types in this package (`dist/types`) follow them.
+
+## Install
+- Public on npm: `npm install @journeeze/sdk@<exact version>`. No registry config or token.
+- Pin an exact version. `-rc.N` = release candidates (`rc` dist-tag), plain = stable (`latest`).
+
+## Configuration
+- `siteKey` (`pk_` + 32 hex, `SITE_KEY_PATTERN`) is **public** runtime config per site. It is not a secret.
+- Direct mode is the default (browser → `app.journeeze.dev`, CORS for the site's allowlisted
+  origins). Set `apiHost`/`apiPath` **only** when the host runs a same-origin proxy
+  (docs/collector-proxy.md); `http:` is accepted only for `localhost`/`127.0.0.1`.
+- CSP, if the host sends one: `script-src 'self' https://app.journeeze.dev` (+ `'wasm-unsafe-eval'`
+  only with signals), `connect-src 'self' https://app.journeeze.dev`, `img-src 'self' blob:
+  https://app.journeeze.dev`, `media-src 'self' https://app.journeeze.dev`, and pass your `nonce`.
+  Use `app.staging.journeeze.dev` for staging.
+
+## Identity
+- `userId` is optional. It must be `HMAC-SHA256(per-environment secret, internal user id)` computed
+  **on the server**, as 64 lowercase hex or 43 base64url characters (`USER_ID_PATTERN` from
+  `@journeeze/sdk/contract`). Never an email, name or raw id; never hashed in the browser.
+- Deliver it only in an authenticated `Cache-Control: no-store` response for the signed-in user,
+  never in public runtime config.
+- **Sign it (v1.3, sdk-v1.md §14).** In the same response, return `userIdExp` (Unix seconds, at
+  most 24 h ahead) and `userIdSig = base64url_nopad(HMAC-SHA256(site identity secret,
+  "jz-id-v1\n" + siteKey + "\n" + userId + "\n" + userIdExp))`, and pass both to the SDK
+  (`userIdSig`/`userIdExp` config or provider props, or `setUser(userId, { sig, exp })`). New sites
+  ignore unsigned ids: that feedback is anonymous and carries no screenshot. Check your
+  implementation against the published test vectors. The identity secret is a server secret, like
+  the HMAC secret above; re-issue the signature before it expires (the SDK never refreshes it).
+
+## React
+- `<JourneezeProvider siteKey={…} userId={…} context={…}>` at the app root. While `siteKey` is
+  `undefined` the provider renders with an **inert handle** (no-ops, nothing sent); the first
+  defined key creates the real handle. `useJourneeze()` never throws inside the provider.
+- Logout is the provider's lifecycle: `userId` changing away from an id, or the provider
+  unmounting, calls `reset()`. Do **not** call `reset()` yourself inside the provider. Script-tag
+  hosts call `window.Journeeze.reset()` on every logout path.
+- `onHelpStatus(status)` (handle option or provider prop) reports `{ available: true }` or
+  `{ available: false, reason: "disabled" | "audience" }`; hide the host's own Help control on
+  `available: false`.
+
+## Context and privacy
+- `context`: `persona`, `journeyId`, `journeyStep`, `device`, `businessType`, `state`.
+  `journeyId` is the journey's candidate id (C0c); `journeyStep` is a stable `stepRef` id such as
+  `route.projects.hub` — **never a URL, path or record id**. With route ids, set `pagePath: "none"`.
+- Put `data-jz-mask` on every element showing customer content and `data-jz-block` on regions to
+  leave out of screenshots entirely. `maskSelectors` fail closed: one invalid selector disables
+  screenshots for that handle.
+- The SDK asks for consent before any capture. Global Privacy Control is honoured
+  (`respectGlobalPrivacyControl`, default on); Do Not Track is ignored (deprecated).
+- Give guided elements a stable `data-tflow-id`; guides fall back to test id, role + name, CSS.
+
+## Signals (optional)
+- `signals: { enabled: true, tflo: () => import("tflo-browser-events") }`. If the host already uses
+  `tflo-browser-events` (`>=0.1.0 <1`, optional peer dependency), **inject it** so the page has
+  one tflo runtime; otherwise the SDK lazy-loads its own copy after consent.
+- Signals start only after the same consent as feedback, and stop when the site's kill switch is off.
+
+## Never
+- Put a secret in the bundle (the HMAC secret, tokens, gateway keys).
+- Send raw user ids, emails, names, URLs or record ids anywhere (context, steps, rules, params).
+- Load a second tflo runtime next to the host's.
+- Disable masking or skip the consent step.

package/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+## Unreleased
+
+- **Public on npm:** published to the npm registry as `@journeeze/sdk` (no registry config or token), starting with 0.1.0-rc.2. GitHub Packages (`@matt-cochran-products/journeeze-sdk`) is no longer published. The package is licensed for use with the Journeeze service (`LICENSE.md`); it is not open source.
+- **Signed host identity (contract C0a §4, v1.3):** `userIdSig` / `userIdExp` config fields and provider props, and `setUser(userId, { sig, exp })`. The signature is sent with feedback and end-user screenshot uploads while it is unexpired; the same id with a new signature only refreshes it. Sites that require signed identity treat an unsigned id as anonymous.
+- The SDK's own lazy tflo copy (used only when the host injects none) is `tflo-browser-events@0.3.0`: no element text, no `document.title` and path-only URLs by default. Hosts that inject their own tflo are unaffected; the 0.1.0 capability floor is still tested.
+
+## 0.1.0-rc.1
+
+First release candidate of the v1 SDK (epic #75). Published to GitHub Packages as
+`@matt-cochran-products/journeeze-sdk`; install it as `@journeeze/sdk` (see `docs/integrating.md`).
+
+- **Contracts:** implements SDK contract v1 (C0a v1.1-r3 + v1.2), direct-mode transport (C0b v1.1-r3 +
+  v1.2), journey import (C0c v1.1-r3) and signals (C0d v1.1-r3 + v1.2), all signed off by Allumata.
+- **Direct mode by default:** the browser talks to Journeeze directly (CORS for allowlisted origins,
+  `text/plain`, no preflight); `apiHost`/`apiPath` keep a same-origin proxy working. One 32 KiB
+  page-end budget, keepalive `fetch` first, retries honouring `Retry-After`, idempotent
+  `submissionId`.
+- **Handle, identity and context:** `setContext`, opaque host-computed `userId` (HMAC digest only,
+  sent on feedback), `reset()` on logout, per-owner outbox and consent, React provider lifecycle
+  with an inert handle until `siteKey` is known, `pagePath: "redacted" | "none"`.
+- **Feedback:** masked screenshots with preview before send; fail-closed `maskSelectors`;
+  `data-jz-block`; signed-in end users can attach screenshots (anonymous visitors never do).
+- **Help:** in-app guides with fallback target resolution (tflo id → test id → role + name → CSS)
+  in its own lazy chunk; public or reviewers-only audience; `onHelpStatus` reports availability.
+- **Signals:** opt-in, consent-gated derived signals via `tflo-browser-events` (host-injected or the
+  SDK's own lazy 0.2.0 copy); platform rules `jz-platform@1` plus registered site rules; no
+  session id, no sampling; the site kill switch is honoured.
+- **Size:** entry ≤ 2 KiB gzipped; everything else loads lazily.

package/LICENSE.md

@@ -0,0 +1,27 @@
+# Journeeze SDK License
+
+Copyright (c) 2026 Matt Cochran Products. All rights reserved.
+
+This package (`@journeeze/sdk`) is proprietary software. It is not open source.
+
+You may install this package and include it, unmodified, in websites and applications
+(including bundled and minified builds) solely to connect them to the Journeeze service, under
+the terms of your agreement for that service.
+
+You may not:
+
+- modify, adapt or create derivative works of this package, other than the bundling and
+  minification your build tools perform;
+- distribute this package on its own, or as part of anything other than a website or
+  application that uses the Journeeze service;
+- decompile, reverse engineer or otherwise attempt to derive source code from this package,
+  except to the extent applicable law expressly permits it;
+- use this package to build or operate a product or service that competes with Journeeze.
+
+Third-party components included in this package are licensed under their own terms; see
+`dist/THIRD_PARTY_LICENSES.txt`.
+
+THIS PACKAGE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
+BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR
+OTHER LIABILITY ARISING FROM, OUT OF OR IN CONNECTION WITH THIS PACKAGE OR ITS USE.

package/README.md

@@ -1,3 +1,165 @@
-# Temporary Holding Version
+# @journeeze/sdk
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Opt-in "suggest an improvement" mode for any website or app. A tiny loader (≤ 2 KB gz) holds
+your options and context; the widget is lazy-loaded only when the mode is switched on.
+Nothing observes the page while the mode is off. Inputs and editable regions are always masked,
+and the widget asks for consent before anything is captured.
+
+## Install and transport
+
+Install from npm, or use the script tag served by Journeeze at `/sdk/`. The Journeeze
+integration guide covers the full path (provisioning, CSP block, identity, help, signals,
+checklist).
+
+```sh
+npm install @journeeze/sdk@<version>
+```
+
+**Direct mode (default since v1):** the SDK calls the Journeeze collector that issued your site
+key (`https://app.journeeze.dev`) with CORS for your site's allowlisted origins
+(`docs/contract/direct-mode-v1.md`). Requests never carry cookies or other credentials and are
+never cached.
+
+**Proxy mode (optional):** set `apiHost` to your own origin (`data-journeeze-api-host` on the
+script tag; `apiPath` / `data-journeeze-api-path` for a sub-path) and proxy the collector paths
+per `docs/collector-proxy.md`. A v0 host that relied on the old same-origin default must set
+`apiHost: location.origin` before upgrading. `endpoint` / `data-journeeze-endpoint` still work
+and are deprecated.
+
+```html
+<script type="module" src="https://app.journeeze.dev/sdk/script.js" data-journeeze-site-key="pk_..."></script>
+<script>/* later, from your own control: */ window.Journeeze?.enable();</script>
+```
+
+```tsx
+import { JourneezeProvider, useJourneeze } from "@journeeze/sdk/react";
+
+<JourneezeProvider siteKey="pk_..." context={{ persona: "owner", journeyId: "r1-j09", journeyStep: "pay" }}>
+  <App />
+</JourneezeProvider>;
+
+const jz = useJourneeze(); jz.enable(); jz.setContext({ journeyStep: "confirm" });
+```
+
+- Keep `context` in sync with your router: the provider sets it on every change and clears values
+  a route no longer provides. The widget asks "Did this step make sense?" about the step the
+  reviewer just finished when `journeyStep` changes.
+- Invited reviewers arrive with `?jz_invite=<token>`: the script tag and the provider read it once,
+  remove it from the URL and keep it for the tab's session (`takeReviewerToken`), unless you pass
+  `reviewerToken` yourself.
+- `onModeChange(enabled)` tells you when the mode switches on or off, including from inside the
+  widget (Esc, Exit, "Not now").
+
+## Signed-in users, logout and privacy options (contract v1.1)
+
+The full contract is `docs/contract/sdk-v1.md`. The parts a host touches most:
+
+```tsx
+<JourneezeProvider
+  siteKey="pk_..."
+  apiHost="https://www.example.com" // proxy mode only; omit for direct mode (the default)
+  userId={user ? user.journeezeHash : undefined} // HMAC from YOUR server, never an email or raw id
+  pagePath="none" // you pass route ids (e.g. route.projects.hub) as journeyStep
+  maskSelectors={[".customer-name"]}
+  context={{ persona, journeyId, journeyStep: routeTemplate }}
+>
+```
+
+- **`userId`** is `HMAC-SHA256(server_secret, internal_user_id)` as 64 hex or 43 base64url
+  characters, delivered in an authenticated `no-store` response. Anything else is ignored with a
+  warning; the SDK never hashes. `USER_ID_PATTERN` and the other patterns are exported from
+  `@journeeze/sdk/contract` for your server's tests.
+- **Logout:** the provider handles it. `userId` changing away from an id, or the provider
+  unmounting, calls `reset()`. Script-tag hosts call `window.Journeeze.reset()` on every logout
+  path. `setUser(otherId)` resets first. `reset()` sends the user's unsent feedback once and
+  removes it from the device, clears context, consent and the reviewer token, and keeps help
+  available (empty) if it was on.
+- **Masking:** inputs, editable regions, `[data-jz-mask]`, media and frames are always masked.
+  `maskSelectors` and `maskAllText` widen it; an invalid selector switches screenshots off (fails
+  closed). `[data-jz-block]` leaves an empty box and cannot be picked. Users can always send
+  without the screenshot, after seeing it full size.
+- **Who sends a screenshot:** reviewers, and signed-in end users the host attributes with
+  `userId` on a site that accepts non-reviewer feedback; the upload is bound to that user. A fully
+  anonymous visitor never captures or sends one, and the consent copy says so (ADR 0013 §4).
+- **`pagePath`:** `"redacted"` (default) replaces id-like path segments with `:id`; `"none"` sends
+  no path.
+- **`nonce`** is set on the SDK's `<style>` elements for strict CSPs; Global Privacy Control turns
+  help telemetry off (`respectGlobalPrivacyControl`, default `true`).
+
+## In-app help
+
+Help is independent of the feedback mode. It shows a launcher that opens guides built from the
+site's published journeys, with search, step-by-step guidance that outlines each step's element,
+and an optional "Did this step make sense?" check-in. Reading guides needs no consent; nothing
+of the help chunk loads or listens on the page until you switch it on.
+
+```html
+<script type="module" src="https://<cdn>/journeeze/script.js" data-journeeze-site-key="pk_..." data-journeeze-help></script>
+```
+
+```tsx
+const jz = useJourneeze();
+await jz.enableHelp();   // lazy-loads the help chunk and shows the launcher
+jz.isHelpEnabled();      // true
+jz.disableHelp();        // removes the launcher and panel
+```
+
+To hide your own Help control when help isn't for this user, pass `onHelpStatus` (or the React
+provider's `onHelpStatus` prop). After `enableHelp()` checks the site it is called with
+`{ available: true }`, or `{ available: false, reason: "disabled" }` (the site has help off) or
+`{ available: false, reason: "audience" }` (reviewers-only help and no reviewer token), and again
+if that changes.
+
+- `data-journeeze-help` on the script tag calls `enableHelp()` for you; a failed chunk load never
+  surfaces as an unhandled rejection.
+- Help reads guides with the collector RPCs `GetHelpIndex` and `GetGuide`, and loads step
+  screenshots, the guide video and its captions from `GET /journeeze.collector.v1/guide-assets/*`
+  (short-lived signed links). Your proxy must forward that prefix and `GET /sdk/*` (the chunks)
+  in addition to the feedback paths; see `docs/collector-proxy.md`.
+- Steps are anchored to `data-tflow-id` names. A step whose element isn't on the current page
+  shows its text without an outline.
+- If help is switched off for the site (the site's help settings on the board's **Settings** screen), the launcher renders nothing.
+
+**Publishing guides.** Guides come from Jevitate journeys. An operator imports them into the
+project with `journeeze import-journeys --project <id> <.jevitate/journeys dir>`; each journey
+arrives as a draft. A triager reviews it on the board's **Journeys** screen (light edits to step
+text are allowed) and publishes it. Only published guides appear in help; a guide whose source
+journey changed goes stale until the new import is adopted.
+
+Mark elements with `data-tflow-id="area.element"` to anchor feedback to stable names, and
+`data-jz-mask` to mask extra regions (form fields and `contenteditable` regions are always masked).
+
+License: undecided (`UNLICENSED`); packaged so it can be open-sourced later.
+
+## Signals (signal contract C0d)
+
+Aggregate-only behaviour signals (`docs/contract/signals-v1.md`): rage clicks, dead clicks,
+hesitation, abandoned journey steps, and your own registered site signals. Raw events never
+leave the page; only derived signals are sent, through a closed allowlist, with no URL, text,
+user id or session id.
+
+```ts
+createJourneeze({
+  siteKey,
+  signals: {
+    enabled: true,
+    // Pass your own tflo module so the page runs one tflo runtime (recommended if you use tflo):
+    tflo: () => import("tflo-browser-events"),
+    // Optional site rules; each name must be registered for the site in Journeeze first.
+    rules: [{ name: "export_clicked", when: 'event.kind == "click" && event.fields.target == "export.button"' }],
+  },
+});
+```
+
+- **When they run:** only after the visitor's consent, while help or feedback mode is on, with
+  `signals.enabled: true` and the site's signals switch on in Journeeze. Global Privacy Control
+  turns them off. Before that, no signals or tflo code is loaded.
+- **What is tracked:** elements with a `data-tflow-id` (`[a-z0-9._:-]`, up to 96 characters)
+  outside `data-jz-mask` / `data-jz-block` regions and form fields. The SDK listens to `click`,
+  `pointerover`/`pointerout`, `focusin`/`focusout` and `change` only: never keys, input or pointer
+  moves, and it never patches `fetch` or XHR.
+- **tflo:** without `signals.tflo` the SDK loads its own copy as a separate lazy chunk with the
+  WASM inlined. Under a Content-Security-Policy that needs `script-src 'wasm-unsafe-eval'` and
+  `connect-src data:`; injecting your own module avoids the second.
+- **Journeys:** set `journeyId` and `journeyStep` with `setContext`; `journeyStep` must equal the
+  published journey's step ids (its `stepRef`s) for `abandoned_step` to apply.

package/dist/THIRD_PARTY_LICENSES.txt

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