@yahyahammad/venastine 0.3.10 → 0.3.11

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/NOTICE CHANGED
@@ -9,6 +9,8 @@ You may obtain a copy of the License at
9
9
 
10
10
  http://www.apache.org/licenses/LICENSE-2.0
11
11
 
12
- This project does not redistribute its dependencies; they are resolved from
13
- PyPI at install time under their own licenses. See docs/THIRD_PARTY_NOTICES.md for
14
- the license assessment of each declared dependency.
12
+ The source installers resolve Python dependencies from PyPI under their own
13
+ licenses. The hosted terminal delivers third-party JavaScript and CSS to
14
+ visitors, with full browser notices in deploy/hosted/browser-NOTICES.txt and
15
+ at /venastine-static/NOTICE.txt on the hosted service. See
16
+ docs/THIRD_PARTY_NOTICES.md for dependency and distribution details.
package/README.md CHANGED
@@ -1015,7 +1015,7 @@ note that shell approval is governed solely by `shell_approval_mode` -- `tool_ap
1015
1015
  deliberately has no `shell` key, so an old file carrying one is refused at startup
1016
1016
  naming the key — see `tests/BREAKING_CHANGES.md` §24.
1017
1017
 
1018
- Run the test suite with `pytest` — 9169 tests, fully offline, no API keys needed. The suite's own packages are `requirements-test.txt`, separate from `requirements.txt` since batch 136: they used to be in the shipped dependency list, so installing the harness also installed a test runner. It runs in parallel by default (`pytest-xdist`, 70% of your cores): **1:26 on a 16-core machine, against 9:06 single-process.** `pytest -n0` forces the old serial run, which is what you want under a debugger or when something is parsing the output. Eight further tests are marked `integration` and excluded by default: three spawn a real stdio MCP server, one runs an external program through the host fallback shell, one builds the hosted bundle's Docker image, and three run the installers' uv path against a real uv (`pytest -m integration`).
1018
+ Run the test suite with `pytest` — 9193 tests, fully offline, no API keys needed. Since batch 243 the suite holds itself to that: a test that asks DNS for a name, or writes into your home folder, fails by name, and every test process runs with HOME pointing at a throwaway folder of its own. The suite's own packages are `requirements-test.txt`, separate from `requirements.txt` since batch 136: they used to be in the shipped dependency list, so installing the harness also installed a test runner. It runs in parallel by default (`pytest-xdist`, 70% of your cores): **1:26 on a 16-core machine, against 9:06 single-process.** `pytest -n0` forces the old serial run, which is what you want under a debugger or when something is parsing the output. Eight further tests are marked `integration` and excluded by default: three spawn a real stdio MCP server, one runs an external program through the host fallback shell, one builds the hosted bundle's Docker image, and three run the installers' uv path against a real uv (`pytest -m integration`).
1019
1019
 
1020
1020
  ## Documentation
1021
1021
 
@@ -1,14 +1,27 @@
1
1
  # Third-Party Notices
2
2
 
3
- This project is licensed under the **Apache License 2.0** — see [LICENSE](./LICENSE) and [NOTICE](./NOTICE) (Copyright 2026 Yahya Hammad).
4
-
5
- The dependencies listed below are **not** part of the project's own source but are required at install/runtime. All are permissive and **Apache-2.0 compatible**; the assessment was made on 2026-08-27, and re-read from each package's own metadata for batch 234's pins on 2026-11-04, when `anthropic` 2.0 moved from MIT to Apache-2.0. This file records it so a scanner or reviewer does not have to re-derive it.
6
-
7
- > **Scope.** Two things are covered here: the project's **declared direct** dependencies — the pins in `requirements.txt` and the extras in `pyproject.toml` — and, under *Non-code third-party material* below, the third-party **text** the repository reproduces.
8
- >
9
- > The transitive dependency closure is *not* enumerated: `sympy` pulls `mpmath`, `sqlmodel` pulls SQLAlchemy, and `mcp==2.3.0` brings `httpx2` (BSD-3-Clause), as `anthropic` and `openai` do since batch 234 (see the note beside the `mcp` pin in `requirements.txt`). Until batch 212 `matplotlib` was here too, pulling numpy, kiwisolver, fonttools and pillow; the confidence chart is drawn as SVG with the standard library now, and none of them is installed. For the full closure, run `pip-licenses` against a resolved environment — see *How to regenerate* below.
10
-
11
- > Versions shown are the pins from `requirements.txt` / `pyproject.toml` at the time this file was created. Where a range is used (e.g. `rich>=14.2,<16`) the exact resolved version will vary.
3
+ This project is licensed under the **Apache License 2.0** — see [LICENSE](../LICENSE) and [NOTICE](../NOTICE) (Copyright 2026 Yahya Hammad).
4
+
5
+ The tables record the declared core, test, optional, build and hosted dependencies.
6
+ Their project-level licenses are permissive; this is not a license assessment of
7
+ all transitive packages or embedded native libraries. Declarations and the
8
+ license corrections below were checked on 2026-11-07 against the manifests,
9
+ PyPI release metadata and the relevant wheel license files.
10
+
11
+ > **Distribution scope.** Git source archives, the GitHub installers and npm
12
+ > carry first-party source and notices; Python dependencies are fetched separately.
13
+ > The hosted terminal **does deliver third-party JavaScript and CSS** to browsers.
14
+ > Its notices accompany the JavaScript response and are linked from the terminal.
15
+ > A built ModelScope container contains installed dependencies and Debian packages;
16
+ > distributing that image requires a separate review of the exact image layers.
17
+
18
+ > **Transitive dependencies.** These tables are not a full resolved inventory.
19
+ > For example, HTTP clients bring certifi (MPL-2.0), hosted installs bring tqdm
20
+ > (MPL-2.0 AND MIT) and Gradio brings orjson (MPL-2.0 AND (Apache-2.0 OR MIT)).
21
+ > `httpx2` (BSD-3-Clause) and SQLAlchemy (MIT) are imported directly by the
22
+ > harness but supplied transitively by the SDKs/MCP and SQLModel, respectively.
23
+ > Versions selected by ranges can change; use the exact installed artifacts
24
+ > when reviewing a redistributed environment.
12
25
 
13
26
  ## Runtime / core dependencies
14
27
 
@@ -31,12 +44,18 @@ The dependencies listed below are **not** part of the project's own source but a
31
44
  | google-re2 | `==1.1.20251105` | BSD-3-Clause | Yes | https://pypi.org/project/google-re2/ |
32
45
  | cryptography | `>=50.0.0,<52` | Apache-2.0 OR BSD-3-Clause | Yes | https://pypi.org/project/cryptography/ |
33
46
  | PyJWT | `>=2.15.0,<3` | MIT | Yes | https://pypi.org/project/PyJWT/ |
47
+ | defusedxml | `==0.7.1` | PSF-2.0 | Yes | https://pypi.org/project/defusedxml/ |
48
+ | pypdf | `==6.21.4` | BSD-3-Clause | Yes | https://pypi.org/project/pypdf/ |
34
49
 
35
- `google-re2` (added 2026-09-15, ROADMAP_v3 §49) and `cryptography` (added 2026-09-24, ROADMAP_v3 §49 slice 5a) are the dependencies above that ship **compiled native code**. Taking `google-re2` first: its wheels carry the RE2 C++ library (BSD-3-Clause) and, as RE2 depends on it, Abseil (Apache-2.0). The paragraph under *What this means* holds for it unchanged — pip fetches the wheel onto the user's machine and this project redistributes nothing — so no inbound `NOTICE` obligation arises. Where no wheel exists (musl/Alpine, glibc older than 2.28), pip builds the source distribution locally, which is the user's build rather than a distribution by this project.
36
-
37
- `cryptography` was **already in the install closure** before it was declared — `google-genai==1.0.0` → `google-auth>=2.14.1` → `cryptography>=38.0.3`, with no extra marker (re-measured on the 2.29.0 pin in batch 172: `google-auth>=2.56.0` → `cryptography>=38.0.3`, still unmarked) — so declaring it added no package to an install and no licence surface that was not already present; it made an existing transitive dependency into a pinned direct one, because the harness-held secret store (ROADMAP_v3 §49 slice 5a, SS57) rests on it. Its wheels carry a **Rust** extension and a statically linked **OpenSSL** (Apache-2.0); the dual licence above is the project's own, and the paragraph under *What this means* holds for it unchanged — pip fetches the wheel onto the user's machine and this project redistributes nothing, so no inbound `NOTICE` obligation arises. Wheels exist for CPython 3.7+ on Windows (x64, x86), macOS (arm64, x86_64) and manylinux/musllinux (x86_64, aarch64); where none does, pip builds the sdist locally and needs a Rust toolchain, which is the user's build rather than a distribution by this project.
50
+ `google-re2` and `cryptography` ship compiled native code. RE2's wheels
51
+ include the RE2 C++ library (BSD-3-Clause) and Abseil (Apache-2.0).
52
+ Cryptography's wheels include a Rust extension and OpenSSL (Apache-2.0).
53
+ The source installers fetch these wheels onto the user's machine; a distributor
54
+ of an installed environment must inspect their bundled notices separately.
55
+ Declaring cryptography did not introduce it to the install closure: Google
56
+ Auth already required it through Google Gen AI.
38
57
 
39
- `pillow` was declared on 2026-10-28 (batch 201), as a floor under what `matplotlib` pulled in, and removed with `matplotlib` in batch 212: nothing the harness installs reaches it now. The hosted demo's Gradio bridge still installs it, in an environment of its own (`deploy/hosted/requirements.txt`).
58
+ `pillow` was declared on 2026-10-28 (batch 201), as a floor under what `matplotlib` pulled in, and removed with `matplotlib` in batch 212: the default harness install no longer reaches it; optional document/PDF dependencies can still bring it. The hosted demo's Gradio bridge still installs it, in an environment of its own (`deploy/hosted/requirements.txt`).
40
59
 
41
60
  ## Test dependencies (not used by end users during runtime, only for CI and developer testing)
42
61
 
@@ -46,24 +65,39 @@ The dependencies listed below are **not** part of the project's own source but a
46
65
  | pytest-mock | `>=3.14` | MIT | Yes |
47
66
  | pytest-asyncio | `>=1.0` | Apache-2.0 | Yes |
48
67
  | pytest-xdist | `>=3.6` | MIT | Yes |
68
+ | starlette | `>=0.40` | BSD-3-Clause | Yes |
49
69
  | execnet | transitive (via `pytest-xdist`) | MIT | Yes |
50
70
 
51
- `execnet` is listed although nothing declares it: it is `pytest-xdist`'s only dependency and the process that actually runs each worker, so a reader auditing what a `pip install -r requirements.txt` puts on the machine would otherwise have to go and find it. Both are permissive, so the no-copyleft claim under *What this means* is unchanged.
71
+ `execnet` is listed although nothing declares it: it is `pytest-xdist`'s only dependency and the process that actually runs each worker, so a reader auditing what a `pip install -r requirements-test.txt` puts on the machine would otherwise have to go and find it. It belongs to the test environment rather than the default runtime.
52
72
 
53
73
  ## Optional dependencies (`pyproject.toml` extras)
54
74
 
55
75
  | Package | Version (as pinned) | Primary License | Apache 2.0 Compatible | Notes |
56
76
  |---|---|---|---|---|
57
77
  | markitdown | `==0.1.9` (extra `documents`) | MIT | Yes | Permissive; only reachable behind `read`/`write`/`edit` (globally denied). |
58
- | protobuf | `==7.36.2` (extra `documents`) | BSD-3-Clause / Apache-2.0 | Yes | Permissive; transitive via `markitdown`→`onnxruntime`. |
78
+ | protobuf | `==7.36.2` (extra `documents`) | BSD-3-Clause | Yes | Permissive; transitive via `markitdown`→`onnxruntime`. |
59
79
  | markdown | unpinned (extra `pdf`) | BSD-3-Clause | Yes | Permissive |
60
- | weasyprint | unpinned (extra `pdf`) | BSD-3-Clause (package) | Yes (with caveats) | Package itself BSD-3-Clause; transitive deps include LGPL (e.g. `pango`/`cairo` via system libs). See weasyprint docs. |
80
+ | weasyprint | unpinned (extra `pdf`) | BSD-3-Clause (package) | Yes (with caveats) | Package itself BSD-3-Clause; Pyphen has alternative GPL/LGPL/MPL code terms and separate dictionary terms; system libraries have their own licenses. |
81
+
82
+ `weasyprint` is BSD-3-Clause itself. Its Python closure includes Pyphen with
83
+ alternative GPL/LGPL/MPL code licenses and separately licensed dictionaries.
84
+ Its native stack includes Pango (LGPL) and HarfBuzz (MIT-style); current
85
+ WeasyPrint uses pydyf for PDF output. Review exact Python and OS artifacts
86
+ before redistributing a PDF-capable environment. Windows MCP installs also
87
+ bring pywin32, whose adodbapi component has LGPL-2.1 terms.
61
88
 
62
- `weasyprint` is BSD-3-Clause itself; the caveat is its **system** dependencies (`pango`, `cairo`, `harfbuzz`), which are LGPL and are linked at runtime rather than vendored into this project. If `markdown` or `weasyprint` is later pinned, update the version column above.
89
+ ## Build backend
90
+
91
+ | Package | Declaration | Primary License | Source |
92
+ |---|---|---|---|
93
+ | setuptools | `>=77` in `pyproject.toml` | MIT, with separate vendor notices | https://pypi.org/project/setuptools/ |
63
94
 
64
95
  ## Hosted demo (`deploy/`, ROADMAP_v3 §79)
65
96
 
66
- What the bridge -- the process that serves a Space's or Studio's page and relays each session -- runs beside Gradio. None of it is installed by `pip install` or npm: `deploy/` ships in neither, and a deployment installs these from PyPI when the platform builds it, so nothing here is redistributed. Licences read from each version's PyPI metadata (2026-10-23).
97
+ The bridge runs separately from the harness's session environment. These
98
+ packages are installed by the hosting platform or generated Docker build;
99
+ `deploy/` is excluded from npm and the metadata-only Python wheel. Installing
100
+ packages on the server and sending their assets to browsers are distinct paths.
67
101
 
68
102
  | Package | Version (as pinned) | Primary License | Apache 2.0 Compatible | Where |
69
103
  |---|---|---|---|---|
@@ -73,38 +107,65 @@ What the bridge -- the process that serves a Space's or Studio's page and relays
73
107
  | gradio | `==6.30.0` | Apache-2.0 | Yes | installed by the Space at the README's `sdk_version`; in the Studio's `bridge.lock` |
74
108
  | spaces | `==0.51.3` | Apache-2.0 | Yes | installed by the Space itself; in the Studio's `bridge.lock` |
75
109
 
76
- ## Deploy tooling (CI only)
77
-
78
- Installed by `.github/workflows/deploy-demo.yml` to build, audit and upload a bundle (batch 169), and by the owner to deploy the Studio by hand. Never part of any install or bundle.
79
-
80
- | Package | Version (as pinned) | Primary License | Apache 2.0 Compatible |
81
- |---|---|---|---|
82
- | huggingface_hub | `==2.2.0` | Apache-2.0 | Yes |
83
- | pip-audit | `==2.10.1` | Apache-2.0 | Yes |
110
+ ### Browser assets
111
+
112
+ The bridge serves only `js/textual.js`, `css/xterm.css` and `NOTICE.txt` under
113
+ `/venastine-static/`. It does not expose the wheel's unused Roboto Mono fonts
114
+ or background image. The font name tables in Textual Serve 1.1.3 identify
115
+ Apache-2.0; blocking those URLs avoids delivering unneeded font copies.
116
+ The terminal's external Google Fonts stylesheet is a separate delivery by Google.
117
+
118
+ The reviewed wheel SHA-256 is
119
+ `207a472bc6604e725b1adab4ab8bf12f4c4dc25b04eea31e4d04731d8bf30f18`.
120
+ The bridge checks the original JS and CSS hashes before serving them and adds
121
+ [full browser notices](../deploy/hosted/browser-NOTICES.txt) to every JS response.
122
+ The same text is available at `/venastine-static/NOTICE.txt` and linked from the
123
+ terminal. The CSS retains its full MIT notice. Embedded components identified
124
+ in the JS include xterm.js and its addons (MIT), js-base64 3.7.7 (BSD-3-Clause),
125
+ and webpack loader/runtime code (MIT), as well as Textual Serve (MIT).
126
+ Upstream supplies no frontend lockfile, so exact versions of every embedded
127
+ component are not established. A changed asset hash requires a renewed review.
128
+
129
+ ### Installed images and native components
130
+
131
+ The ModelScope recipe installs the bridge and session packages into a
132
+ Debian-based Python image. This review did not obtain the deployed image or
133
+ establish its delivery terms. It therefore makes no claim of image compliance
134
+ or violation. Before supplying an image copy, inspect its exact wheels and OS
135
+ packages, preserve bundled LICENSE/NOTICE files, and satisfy applicable source
136
+ availability and license requirements for MPL/LGPL/GPL-covered components.
137
+ Include OpenSSL, Abseil, native libraries bundled in wheels and Debian packages
138
+ in that review. Platform-managed Hugging Face packages, including GPU wheels,
139
+ are not a fixed inventory established by the source manifests alone.
140
+
141
+ ## Development and deployment tooling
142
+
143
+ These tools run in CI or the operator's environment; they are not npm runtime
144
+ dependencies. Entries describe the primary project licenses, not every vendored
145
+ component or service agreement.
146
+
147
+ | Package | Declaration / use | Primary License |
148
+ |---|---|---|
149
+ | huggingface_hub | `==2.2.0`, deployment CI | Apache-2.0 |
150
+ | pip-audit | `==2.10.1`, dependency audit | Apache-2.0 |
151
+ | bandit | `==1.9.4`, security scan | Apache-2.0 |
152
+ | ruff | `==0.15.21`, lint | MIT |
153
+ | uv | `==0.13.4`, CI and hosted setup | MIT OR Apache-2.0 |
154
+ | modelscope | optional operator login CLI, unpinned | Apache-2.0 |
155
+ | gitleaks | `8.30.1`, secret scan | MIT |
156
+
157
+ CPython, Node.js/npm, GitHub Actions, CodeQL and optional Docker/Podman and SSH
158
+ helpers have their own project, bundled-component and, for CodeQL, service/tool
159
+ terms. They are execution tools rather than dependencies embedded in the source
160
+ package. Do not infer their complete license inventory from the Python tables.
84
161
 
85
162
  ## Non-code third-party material
86
163
 
87
- **No third-party source code is included in this repository.** Measured, not assumed: all 277 tracked
88
- Python files carry no foreign copyright header and no `SPDX-License-Identifier`; a sweep for
89
- copied or adapted code ("adapted from", "copied from", "taken from", "vendored", "borrowed from")
90
- returns only this project's own design prose; and the 45 tracked files that are neither `.py`
91
- nor `.md` are first-party without exception — the licence texts, configuration and packaging
92
- (`config.yaml`, `pyproject.toml`, the three requirements files, `package.json`, `pytest.ini`, the
93
- `.github/` workflows, issue templates and scanner configuration, the dotfiles), the two prompt
94
- texts, `bin/venastine.mjs` and `scripts/prepublish-check.mjs`, `docs/assets/research-mode-birds-eye.mermaid`,
95
- `tui/app.tcss`, the two `.example` templates, the hosted demo's four page templates in
96
- `deploy/hosted/`, one screenshot of this project's own interface, and its cover image with the
97
- page it is rendered from. **No third-party fonts, images or data files are bundled.** The
98
- cover's text is set in Cascadia Mono, Microsoft's font under the SIL Open Font License: the PNG
99
- holds rendered glyphs, and its page names the font, and neither carries a copy of it.
100
-
101
- *(Counts restated in batch 83. The figure had been 166 against 200, the enumeration named
102
- five of the thirty-four, and the closing sentence said there were no images at all while the
103
- screenshot was tracked. The claim itself held throughout; only its arithmetic had drifted.)*
104
-
105
- *(Restated again in batch 198, when the cover joined: 200 and 34 had become 277 and 43 as the
106
- project grew. Both sweeps were run again and found nothing new, and every file added since
107
- batch 83 is first-party.)*
164
+ The repository does not vendor dependency wheels, third-party fonts or browser
165
+ bundles. The hosted bridge reads the browser bundle from its installed wheel
166
+ and adds the reproduced license texts in `deploy/hosted/browser-NOTICES.txt`.
167
+ The cover image contains rendered glyphs from Cascadia Mono (SIL Open Font
168
+ License); it does not carry the font file.
108
169
 
109
170
  What the repository *does* reproduce is third-party **text**:
110
171
 
@@ -128,21 +189,33 @@ What the repository *does* reproduce is third-party **text**:
128
189
 
129
190
  ## What this means
130
191
 
131
- * All licenses **listed above** are **permissive** (MIT / BSD-3-Clause / PSF / Apache-2.0). None are copyleft (GPL/AGPL) and none impose source-disclosure on this Apache-2.0 work. This is a statement about the direct dependencies in the tables, not about the full transitive closure — see *Scope* at the top.
132
- * This project does not redistribute any of them. It is distributed as **source** — a `git` checkout or the npm package `@yahyahammad/venastine`, which is the same folder of first-party files — and `pip` fetches each dependency from PyPI, onto the user's machine, under its own license. **No inbound `NOTICE` obligation therefore arises** — nothing here carries an upstream NOTICE that this project must propagate. The trigger is **redistribution**, not source-vs-binary, and not which channel delivered the source; if a build that vendors these packages is ever distributed, ship their `LICENSE` and `NOTICE` files as received (Apache-2.0 §4(d) applies to `openai`, `google-genai` and `pytest-asyncio`). **The npm tarball must therefore never carry wheels** — that is the one change that would turn this paragraph false, and `CONTRIBUTING.md` records it as a rule.
133
- * **The npm channel adds no third-party licence surface at all.** Its launcher (`bin/venastine.mjs`) is Node standard library only, with an empty `dependencies` block, so an install of this package fetches no JavaScript code from anyone. What the tarball contains is the first-party source listed under `files` in `package.json`, plus `LICENSE`, `NOTICE` and this file. Publishing *is* distribution of the Work under Apache-2.0 §4 where running from a checkout was not, which is why those three are in the allowlist rather than left to chance: npm auto-includes `LICENSE` and does **not** auto-include `NOTICE`.
134
- * The [NOTICE](./NOTICE) file this project publishes is therefore **voluntary**, not required. Apache-2.0 §4(d) obliges you to propagate a NOTICE you *received*; it does not oblige a licensor to author one. It exists because scanners and reviewers look for it and because it gives the copyright assertion a canonical home — and it is kept minimal on purpose, since anyone who redistributes this work must carry its contents forward.
135
- * Full license texts: `pip show <package>` or `pip-licenses --format plain --with-urls`, or the PyPI links above.
192
+ * The harness's Apache-2.0 license does not replace the licenses of dependencies,
193
+ browser components, fonts or native libraries. Permissive direct dependencies
194
+ do not imply that the full installed closure contains no copyleft components.
195
+ * The source channels fetch Python packages separately. The npm launcher uses
196
+ Node built-ins and declares no npm dependencies or bundled dependencies.
197
+ Do not add wheels or installed dependency directories to the npm tarball.
198
+ * Hosted JS and CSS are copies delivered to visitors. Their notices must
199
+ accompany those copies; a LICENSE file only in server-side wheel metadata
200
+ does not accompany the browser response.
201
+ * A redistributed installed image needs its own artifact inventory, notices
202
+ and any applicable source availability arrangements. A source-only assessment
203
+ does not establish compliance for that image.
204
+ * The root [NOTICE](../NOTICE) describes these delivery paths. The first-party
205
+ copyright notice is voluntary; recipients must still retain applicable
206
+ third-party notices when redistributing their covered components.
136
207
 
137
208
  ## How to regenerate
138
209
 
139
- ```bash
140
- pip-licenses --format markdown --with-urls --with-license-file
141
- # or
142
- pip install pip-licenses && pip-licenses --format plain
143
- ```
210
+ Read `requirements.txt`, `requirements-test.txt`, the build backend and extras
211
+ in `pyproject.toml`, `deploy/hosted/requirements.txt`, and generated platform
212
+ inputs in `scripts/build_demo_bundle.py`. Inspect the exact resolved wheels
213
+ and their license files, including vendor notices; metadata alone can omit them.
214
+ `pip-licenses --format markdown --with-urls --with-license-file` can help list
215
+ an installed environment, but does not inventory browser bundles or OS layers.
144
216
 
145
- When a dependency is added or re-pinned, add a row here with its SPDX identifier and re-check the `Apache 2.0 Compatible` column. CI does not enforce this file today — it is documentation for reviewers.
217
+ When a declaration changes, update its table row and review the actual delivery
218
+ path. For a Textual Serve repin, inspect the bundle components and fonts, update
219
+ browser notices and the reviewed asset hashes, and verify the served responses.
146
220
 
147
- ---
148
- *Last updated: 2026-08-27. If any row's upstream re-licenses, this file must be updated.*
221
+ *Last checked: 2026-11-07.*
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yahyahammad/venastine",
3
- "version": "0.3.10",
3
+ "version": "0.3.11",
4
4
  "description": "A from-scratch agentic harness: tool-using chat plus a ten-pass self-critiquing research pipeline.",
5
5
  "keywords": [
6
6
  "agent",
package/pyproject.toml CHANGED
@@ -18,7 +18,7 @@ build-backend = "setuptools.build_meta"
18
18
 
19
19
  [project]
20
20
  name = "venastine-research-harness"
21
- version = "0.3.10"
21
+ version = "0.3.11"
22
22
  description = "A from-scratch agentic harness: tool-using chat plus a ten-pass self-critiquing research pipeline."
23
23
  readme = "README.md"
24
24
  requires-python = ">=3.11"