@robmclarty/volley 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md ADDED
@@ -0,0 +1,123 @@
1
+ # Changelog
2
+
3
+ ## v0.5.1 — 2026-09-16
4
+
5
+ ### Changed
6
+ - **Published as `@robmclarty/volley`** — the bare `volley` name on npm belongs to an unrelated project. The binary is still `volley`; config files import `VolleyConfig` from the scoped name.
7
+ - **License is Apache-2.0**, with the license file now in the tree, matching fascicle, checkride, plumbbob, and ridgeline; the manifest had said MIT and shipped no license text.
8
+ - **README corrections.** Anthropic paused its programmatic-billing change on 2026-06-15 rather than shipping it, so the cost-cap section no longer claims subscription runs are metered; the trajectory viewer is named by the bin fascicle actually ships; ridgeline is linked.
9
+
10
+ ### Added
11
+ - A README **Status** section saying what this is — a personal research harness at v0.x with pinned substrates and no support commitment — and where the design record lives.
12
+ - **GitHub Actions CI**: the full checkride gate plus a build on every push to `main` and every pull request.
13
+
14
+ ### Internal
15
+ - Public-facing docs, code comments, and test names no longer cite spec decisions by their internal ids. The specs under `research/` and the build logs under `.plumbbob/` remain the decision record, ids included.
16
+ - The `/version` release skill no longer claims volley has no remote. It still marks a release with a bare `vX.Y.Z` commit and leaves pushing to the operator, and its verify note names the current checkride slots.
17
+
18
+ ## v0.5.0 — 2026-09-16
19
+
20
+ ### Changed
21
+ - **`volley matrix` row and run-state shapes.** A row is now a seat aggregated over its attempts (`runs`, `converged`, `mean_iterations`, `mean_wall_clock_ms`, `mean_cost_usd`, `reason`, plus every `attempt`) rather than one run's fields, and per-attempt state moved from `.volley-matrix/<builder>__<critic>/summary.json` to `…/run-NN/summary.json`. Both `--json` consumers and on-disk readers of the v0.4.1 layout need updating.
22
+
23
+ ### Added
24
+ - **volley sees what the builder changed, and says so.** Every iteration now diffs the build root against a baseline captured before the first iteration, and hands the result to the two places that were flying blind. The **critic prompt** carries the changed-path list, so a critic reviews a change instead of re-reading a tree the deterministic check already blessed (paths and statuses only — never diff hunks, so a 32k-context local critic's prompt stays bounded). The **run summary** gains `comparison.gate_edits`, and each iteration archive carries its own change set.
25
+ - **`volley matrix --repeat N`.** Each seat now runs N times (default 1) and the row reports a pass *rate* over those attempts, because one run is the only thing n=1 can honestly report on: local runs are stochastic, so a single sample supports a hard failure and nothing else — not iterations-to-converge, not wall clock. Each aggregate names the population it is over: `iters` averages the converged attempts only, `wall` and `cost` average every attempt that reported one, and salvage is a ratio of totals rather than a mean of ratios. Every attempt's run state is kept (`.volley-matrix/<builder>__<critic>/run-NN/summary.json`), and the whole sweep is written to `.volley-matrix/matrix.json`.
26
+ - **The matrix table says *why* a seat fell off.** `budget_exhausted` is a status, not a diagnosis. A row's new `why` column names the failing check slots, the criteria the critic still judged unmet, a cost cap, a gate edit, or the error that broke the run; `flags` separates what qualifies a pass (`deg` for a degraded critic, `gate` for a builder that edited the gate) from what explains a failure. Mean cost per run joins the table, and every attempt's full detail — status, verdict, failing slots, unmet criteria, gate edits — is in the `--json` aggregate.
27
+ - **`comparison.unmet_criteria` in the run summary**: what the critic still judged unmet when the run stopped, verbatim, so a non-converged run says what it was missing rather than only that it stopped. Archived per iteration too.
28
+ - **Gate-edit detection.** Changed paths matching the *gate* — the tests, fixtures, and check configuration that decide whether the work passes — are called out to the critic, warned about on stderr, and recorded in the summary. This mechanizes the by-hand verification `research/reckon-local-run-finding.md` recommends making routine: a green check plus an empty `gate_edits` is worth more than a green check alone, because a builder can also pass by editing the test. Reported, not refused, by default (plenty of tasks are legitimately about the tests); `--fail-on-gate-edit` halts the run with the new **exit 8** instead, and beats success rather than losing to it. `--gate-paths` / `gate_paths` replaces the built-in pattern list, and `--dry-run` predicts the posture — including a warning that the refusal cannot fire outside a git repository.
29
+
30
+ ### Fixed
31
+ - **`volley --version` reports the real version.** It was a literal in `src/cli.ts`, frozen at `0.2.0` since v0.2 while `pnpm version` bumped only `package.json`; it now reads the manifest at startup, so it cannot drift from a release again. The fixing commit filed this under v0.4.1 below, but it landed after that release; v0.5.0 is the first version that ships it.
32
+
33
+ ### Internal
34
+ - `research/reckon-local-run-finding.md`: the first multi-module, all-local run finding — four modules with a real dependency order and a `node --test` gate — and the by-hand verification that gate-edit detection now automates.
35
+ - Change-detection tests pin the `--worktree` seam (the diff runs against the worktree, not the workspace) and the exact promise the gate-edit warning makes; preflight tests cover the `--dry-run` gate-edit posture line.
36
+
37
+ ## v0.4.1 — 2026-07-24
38
+
39
+ ### Added
40
+ - **`volley matrix`**: sweep builder×critic model combos serially over one otherwise-fixed config and aggregate every run's `comparison` block into a single table (per-combo state under `.volley-matrix/<builder>__<critic>/summary.json`; `--json` for the aggregate). Serial by design — the local providers share one GPU, so parallel combos would thrash the model loader. A combo that runs without converging is a *result* row; the sweep exits nonzero only when a combo yields no summary at all.
41
+ - **Critic-seat canary in `--dry-run`**: for a local critic, one tiny $0 generate through the real critic tool wiring before any builder spend. A degradable death warns and predicts `critic_degraded`; only a would-fail-even-degraded combo exits 5, named model×seat. The `claude_cli` critic path never runs it.
42
+ - **`--discard-worktree`**: throw a `--worktree` run's effects away at teardown instead of keeping them on the run branch — "isolate the effects, I only want the verdicts". `volley matrix` forces it for every seat, so a sweep leaves neither a branch nor a squash commit per combo. Refused without `--worktree`; `--git` still wins, so `--worktree --git` integrates exactly as before.
43
+ - **Two example families for probing a local model's real ceiling**: `examples/essayist` (a non-code task with a custom critic prompt, rubric, and JS check gate) and `examples/ladder` (seven capability rungs from greenfield through brownfield bugfix and cross-file refactor, plus an online-only dependency-wrangling run recipe).
44
+ - An upstream-ready write-up of the Ollama qwen tool-call parser failure that kills `qwen3.6` in the critic seat (`research/ollama-qwen-parser-issue.md`).
45
+
46
+ ### Changed
47
+ - **A local critic now degrades instead of dying.** A provider stream error is retried once (recorded on the critic record as `retries` / `retry_cause_kind`), and a critique that keeps dying with tools attached falls back to a tool-less verdict grounded in the criteria, the raw check artifacts, and a workspace file inventory. A fallback verdict is *always* marked `critic_degraded` — in the iteration summary, the run's `comparison` block, and the matrix table — so a shallower critique never passes silently as a full one.
48
+
49
+ ### Fixed
50
+ - **`volley --version` reports the real version.** It was a literal in `src/cli.ts`, frozen at `0.2.0` since v0.2 while `pnpm version` bumped only `package.json`; it now reads the manifest at startup (from `src/` under tsx and from `dist/` in the published package alike), so it cannot drift from a release again.
51
+ - **`--worktree` without `--git` no longer destroys a successful run's work.** With `worktree: true` and git checkpoints off (the default), a fully green run — check passed, critic approved — ended in `git branch -D` plus a forced worktree removal: the builder's uncommitted work deleted, the workspace untouched, nothing said before or after. Teardown now *salvages* that case instead — it commits the worktree's state onto the run branch (`volley/<run id>`), keeps the branch, removes only the checkout, and reports the branch as `salvaged_branch` in `.volley/summary.json` and `--json` output, so the work is recoverable with `git switch` / `git cherry-pick`. If the salvage commit itself cannot land (no git identity, a stale index lock), the checkout is left standing rather than deleted. Runs that did not converge, and `--worktree --git` runs whose work was squash-merged, still discard wholesale; the documented integrate path is unchanged.
52
+ - **A `--worktree` run's fate is now predicted before any model spend.** `--dry-run` and run start each print one line saying what a successful run will do with its effects — squash-merge onto the workspace branch (`--git`), leave them on the run branch (`--worktree` alone; a warning, since nothing is integrated), or throw them away (`--discard-worktree`) — alongside the existing critic-seat canary and `num_ctx` predictions.
53
+
54
+ ### Internal
55
+ - README refreshed to v0.4.0 truth, and the matrix example's `--config` path corrected.
56
+
57
+ ## v0.4.0 — 2026-07-17
58
+
59
+ ### Added
60
+ - **Sandboxed local builds.** A local-model builder now runs as the whole volley process inside one hardened Docker container that volley *detects* it is inside (the `VOLLEY_CONTAINED=1` marker its image bakes in — volley does not start the container itself) over a per-run git worktree (`--worktree`) — its effects land on a throwaway phase branch and squash-merge onto the workspace only on a successful `--worktree --git` run. Ships a default image and `Dockerfile` (`--sandbox-image` / `VOLLEY_SANDBOX_IMAGE` to override), default-deny network egress with a host-gateway allowlist, and a `--dry-run` preflight that verifies the toolchain, worktree, and host LLM endpoint before any model spend (exit 5 on failure). `claude_cli` builds stay on the host, Docker-free.
61
+ - **v3 comparison examples.** `examples/all-claude` and `examples/all-local` run an identical task, criteria, check gate, and caps so their `.volley/summary.json` `comparison` block (iterations-to-converge, wall-clock, cost, verdict, check trajectory, local salvage rate, transport) isolates model-vs-transport; the finding is written up under `research/`.
62
+
63
+ ### Changed
64
+ - **Upgraded to fascicle 0.9.5 on AI SDK v7** (`ai@^7`, `ai-sdk-ollama@^4`), moving the local-provider peer set forward together on the `ai_sdk` transport (the native Ollama transport is documented as a one-line future flip). Resolves the v0.3.1 local-builder peer-major mismatch by construction.
65
+ - **A require-containment gate for local builders:** a local builder is admitted only when volley detects it is running inside its container (`VOLLEY_CONTAINED=1`) or `--allow-unsandboxed-builder` (`VOLLEY_ALLOW_UNSANDBOXED_BUILDER=1`) is set; `claude_cli` is exempt. A *contained* `claude_cli` role must use API-key auth (`VOLLEY_AUTH_MODE=api_key`) — its subscription/OAuth token does not survive containerization.
66
+ - Upgraded checkride 0.2.1 → 0.4.1 (atomic summary writes, stale-artifact clearing, and a `checks_run` vacuous-green signal).
67
+
68
+ ### Fixed
69
+ - `checkride --json` parsing now tolerates pnpm 11's dep-verify line printed ahead of the JSON, with a `.check/summary.json` fallback — the check no longer dies with "unparseable stdout."
70
+
71
+ ### Internal
72
+ - oxlint-tsgolint bumped to 0.22.1 to satisfy oxlint's peer floor.
73
+
74
+ ## v0.3.1 — 2026-07-10
75
+
76
+ ### Fixed
77
+ - The default Ollama base URL is now the server root (`http://localhost:11434`):
78
+ the previous `…/api` default made `ai-sdk-ollama` (which appends `/api/…`
79
+ itself) request `/api/api/chat` and 404 on every call, breaking both local
80
+ roles out of the box. A trailing `/api` on `VOLLEY_OLLAMA_URL` is stripped
81
+ for compatibility with the old documented value.
82
+ - Pre-load an Ollama model at builder start (and before a local critic's first
83
+ verdict): a cold multi-GB model load could exceed the provider's in-request
84
+ first-byte timeout and kill the run minutes in with an opaque
85
+ `stream interrupted: fetch failed`.
86
+ - Document that the `ai-sdk-ollama` peer must match fascicle's declared major
87
+ (`^3` today — a bare `pnpm add ai-sdk-ollama` pulls v4, which targets a newer
88
+ AI SDK spec and hard-fails at the first call), and ship it as a devDependency
89
+ so the local live smoke test runs from a fresh checkout.
90
+
91
+ ### Internal
92
+ - Name every checkride slot that actually runs (`types`, `lint`, `struct`,
93
+ `dead`, `links`) in `checkride.config.json`, not just the three that were
94
+ previously listed — the config file now matches the pipeline reality
95
+ instead of relying on silent tool detection.
96
+
97
+ ## v0.3.0 — 2026-07-10
98
+
99
+ ### Added
100
+ - Run the builder on a local model (Ollama or LM Studio) with `--builder-provider ollama|lmstudio`. A local builder brings no built-in tools, so volley supplies its own workspace tool loop — read/search/list, `write_file`, `edit_file` (exact-match-or-fail), a stateless `bash`, a readability-based `fetch` with SSRF protection, and an explicit `finish` — bounded by `--builder-max-steps` (default 50) per iteration. The produced workspace goes to check + critic exactly like a Claude Code CLI build.
101
+ - Refuse a local builder by default: it runs a real host `bash` with no sandbox yet, so volley stops before any model spend unless you opt in with `--allow-unsandboxed-builder` (or `VOLLEY_ALLOW_UNSANDBOXED_BUILDER=1`), which prints a one-time warning.
102
+ - Warn at builder start when an Ollama model's context window is detectably too small (`num_ctx` below ~16k) — the most common cause of a local model silently ignoring its tools.
103
+ - Record local-builder health per iteration: a `max_steps` cutoff is surfaced as a warning rather than an error, and the run summary carries the loop's `finish_reason` and the rate of tool calls salvaged from unstructured model output.
104
+ - README `Local builder` guide and a `VOLLEY_LIVE`-gated live smoke test for the local path.
105
+
106
+ ### Internal
107
+ - Enforce the spec's architecture decisions as ast-grep rules (create-engine confinement, no deep-sibling imports, no classes).
108
+ - Pin dependencies to exact versions; upgrade checkride to 0.2.1 and flesh out its config for the v3-s1 build.
109
+
110
+ ## v0.2.1 — initial release
111
+
112
+ ### Added
113
+ - Builder/critic loop CLI: runs a full agentic Claude Code CLI session as the builder, gates on a deterministic check pipeline (checkride auto-detected, a custom command, or none), then requires a schema-validated critic verdict before converging.
114
+ - Local critic support — point `--critic-provider` at Ollama or LM Studio to run the read-only critic on a free local model (workspace-scoped read/search/list tools, `$0` cost reporting) while the builder stays on Claude.
115
+ - Cost and iteration caps (`--max-cost-usd`, `--max-iterations`), a stable exit-code contract, and `volley resume <run-id>` to continue an interrupted run.
116
+ - Pluggable critic personas (`reviewer`, `optimizer`, `researcher`, or a custom prompt file) and a TypeScript config-file surface (`VolleyConfig`).
117
+ - `--git` flag to commit after each phase; `.volley/` run artifacts (config, summary, trajectory, per-iteration archives) for every run.
118
+ - `--json`, `--verbose`, and `--quiet` output modes for composing volley under other harnesses.
119
+
120
+ ### Internal
121
+ - Built on fascicle (loop primitive, usage/cost accounting, trajectory logging) and checkride (deterministic check pipeline); both pinned to fascicle 0.8.16 / checkride 0.2.0.
122
+ - Config, CLI, and engine plumbing landed for a future local *builder* provider (`ollama`/`lmstudio`); not yet wired into execution.
123
+ - Unit and integration test suite, with opt-in live smoke tests (`VOLLEY_LIVE=1`) against the real Claude CLI and checkride.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for describing the origin of the Work and
141
+ reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may accept and charge a
167
+ fee for acceptance of support, warranty, indemnity, or other liability
168
+ obligations and/or rights consistent with this License. However, in
169
+ accepting such obligations, You may act only on Your own behalf
170
+ and on Your sole responsibility, not on behalf of any other
171
+ Contributor, and only if You agree to indemnify, defend, and hold
172
+ each Contributor harmless for any liability incurred by, or claims
173
+ asserted against, such Contributor by reason of your accepting any
174
+ such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Rob McLarty
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
200
+ implied. See the License for the specific language governing
201
+ permissions and limitations under the License.