July 2026

A focused day on telemetry robustness and community extension maintenance.

Rusty addressed a critical issue across multiple Query-farm extensions where telemetry was blocking the load process. Fixes were applied to openprompt, redis, rapidfuzz, webmacro, a5, httpclient, query-farm-telemetry-client, and cronjob. This systematic fix ensures that telemetry failures no longer cascade into extension initialization failures—a significant reliability improvement for the extension ecosystem.

On the DuckDB community-extensions front, he opened 19 PRs updating various extensions to their latest commits. The batch includes airport, a5, adbc_scanner, bitfilters, crypto, datasketches, evalexpr_rhai, hashfuncs, inflector, json_schema, jsonata, lindel, marisa, minijinja, quickjs, shellfs, stochastic, tera, textplot, and tsid. This reflects active stewardship of the community extension ecosystem, keeping dependencies and implementations current.

Rusty also provided community support by replying to issue #12 on shellfs, helping diagnose a performance problem where extension loading took 120 seconds when behind a proxy server without proper HTTP proxy configuration. This kind of targeted troubleshooting helps users understand environment-specific configuration requirements.

Private repository activity included 3 commits across 3 separate projects.

Rusty spent the day reinforcing integration testing infrastructure across multiple vgi language implementations and pushing out a release for the Python RPC layer.

Across vgi-java, vgi-rust, and vgi-go, he implemented consistency improvements to CI integration testing. These changes enforce a skip contract and establish an executed-case floor — mechanisms to detect and handle edge cases in test collapse detection. The Rust implementation added a collapse detector floor specifically, while the Java and Go versions added the broader skip contract enforcement alongside the floor threshold.

The vgi-rpc-python repository received significant attention with a 0.27.0 release. The update includes support for extra_metadata passthrough and improved empty-buffer tolerance. Related commits show Rusty refactored write_request to carry extra batch metadata across re-frame boundaries, and applied code formatting via ruff to test utilities.

A minor 0.1.2 release went out on vgi-color, rounding out the release activity.

Rusty also engaged in open-source stewardship, replying to a DuckDB community issue (PR #22715) regarding Arrow export support for the VARIANT type, and provided feedback on a radio repository issue tracking version 1.5.1.

Behind the scenes, he maintained momentum across 6 private repositories with 11 additional commits, keeping internal projects current alongside the public work.

A busy day across the VGI ecosystem, focused on protocol evolution and schema-aware function resolution. The work spans multiple language implementations and introduces breaking changes to improve dispatch correctness.

vgi-java saw substantial protocol refinement with 10 commits advancing from version 0.20.0 to 0.21.0. Key changes include a breaking shift to resolve functions by (schema, name) tuple rather than name alone (protocol 1.1.0), carrying the owning schema on unary aggregate and buffering RPCs (protocol 1.2.0), and refactoring dispatch to enforce exactly one declared home per function with no fallback logic. Test fixtures were expanded to validate cached same-name-in-two-schemas scenarios and a new cached_explode per-value fan-out fixture. The HTTP layer was hardened to finish COPY-FROM operations in a single tick and make substream_partial_sum state portable. CI improvements addressed macOS bash 3.2 compatibility for empty array expansion.

vgi-rust kept pace with matching protocol changes across 8 commits, reaching version 0.25.0. The dispatch refactor mirrors Java—every function now has exactly one home with exact resolution. Protocol 1.1.0 introduced (catalog, schema, name) resolution tuples, with protocol 1.2.0 adding schema to by-name RPCs. Backward compatibility was maintained by backfilling schema_name on unary requests from older peers. Test coverage expanded with same-name collision probes across schemas and the new cached_explode fixture, replacing cache_interleaved. Documentation fixes clarified wasm_worker intra-doc links, and CI was aligned with Java on bash 3.2.

vgi-rpc-typescript went through a rapid release cycle—0.15.2 through 0.15.4—to address Arrow/Flechette serialization. Version 0.15.3 added per-batch custom metadata preservation during Arrow serialization, but the streaming guard introduced there was reverted in 0.15.4 after further testing.

vgi-go received 6 commits to align with the Java and Rust protocol work. Function resolution now uses (catalog, schema, name) tuples (protocol 1.1.0) and carries schema on by-name unary RPCs (protocol 1.2.0). Test fixtures expanded to cover same-name collisions across schemas and catalogs, plus exchange-mode and aggregate schema probes. CI integration improvements moved shared memory onto the launch lane for full suite runs.

cupola was updated to pull in vgi-typescript 0.23.0 and fix vgi-rpc root barrel resolution.

haybarn-community-extensions tracked the main branch changes across three dependency bumps, including a substantial update capturing months of VGI improvements: result-cache schema-ownership fixes, protocol 1.2.0 binding changes, per-value cache arena columnarization and SQLite disk backend, worker function attachment via ATTACH, and the removal of vgi_table_function().

Private repositories also received attention with 23 commits across 4 repos.

A prolific day spanning 60 repositories with 134 commits, driven by three major themes: linting infrastructure updates, WebAssembly browser worker standardization, and dependency and feature refinements.

Linting and Lint-Check Infrastructure

The most substantial work landed in vgi-lint-check, where Rusty shipped two releases alongside significant architectural improvements. Version 0.79.0 introduced the simulate discovery contract, fixing self-contradictions in how the standalone command handles configuration. Version 0.76.0 focused on sweep accuracy fixes, including improved waiver auditing so that quiet execution rules no longer falsely prove waivers are dead. Additional refinements addressed JVM worker discovery via shaded jar location, timing-sensitive findings measured serially to avoid false positives, and credential refusal handling (VGI911/VGI906) to distinguish scan failures from authentication rejections. A new assurance levels framework was introduced alongside structured waivers with audit trails and the vgi-lint fleet command.

Across the broader ecosystem, Rusty systematized lint configuration by declaring waiver kinds and reasons explicitly in config files across ~25 repositories including vgi-bgp, vgi-lightgbm, vgi-tika, vgi-etf-schwab, vgi-compress, vgi-netflow, vgi-iso20022, vgi-cbor, vgi-mft, vgi-pprof, vgi-x12, and vgi-scikit-learn. Several projects dropped hardcoded lint-check version pins to track the latest release: vgi-yara, vgi-causal, vgi-xslt, vgi-trading-calendar, vgi-vision, vgi-useragent, and vgi-units. Cold-start timing was addressed in vgi-statsmodels by sizing the lint execution window appropriately.

WebAssembly Browser Worker Standardization

A coordinated rollout of wasm32 browser builds and the new vgi::wasm_worker! macro landed across ~20 repositories. The core enabler, vgi-rust 0.24.0, shipped the wasm_worker! macro for canonical browser worker entry points. Consumer repos including vgi-bgp, vgi-mask, vgi-image, vgi-ioc, vgi-compress, vgi-netflow, vgi-tiktoken, vgi-cbor, vgi-mft, vgi-code, vgi-pprof, vgi-sourcemap, vgi-useragent, and vgi-units added build.sh scripts to produce wasm32 builds. vgi-fixedformat went further, refactoring its WASM layer to adopt the macro and canonical ABI, then sourcing the browser runtime from @query-farm/vgi-worker-runtime, resulting in version 0.9.3.

Dependency Updates and Feature Work

Dependency bumps were applied strategically: vgi-lightgbm resolved an ATTACH RPC schema staleness issue by bumping vgi-python to 0.17.0, and the same upgrade was rolled out to vgi-libpostal and vgi-survival. vgi-fixedformat dropped its interim git dependency in favor of vgi 0.24.0 from crates.io.

Feature work included cache control enhancements: vgi-java and vgi-rust both added perValue / with_per_value() opt-ins to CacheControl. In vgi-fhir, streaming was improved so Bundle page scans answer on the first round-trip rather than requiring multiple network calls.

Minor housekeeping included removing a dead VGI146 waiver from vgi-tika and adding .gitignore entries for WASM build output in vgi-useragent.

Beyond public repos, Rusty also logged 37 commits across 16 private repositories.

A prolific day across the VGI ecosystem, with Rusty systematically rolling out Docker image publishing infrastructure and release workflows across dozens of repositories. The work represents a major infrastructure push to containerize and automate distribution for the query-farm suite.

Docker & CI/CD Infrastructure

Across vgi-chart, vgi-jolt, vgi-bgp, vgi-elasticsearch, vgi-mask, vgi-tika, vgi-image, vgi-ioc, vgi-compress, vgi-yara, vgi-netflow, vgi-secretscan, vgi-tiktoken, vgi-iso20022, vgi-cbor, and others, Rusty added multi-architecture Docker images with ghcr.io publishing CI. Several repositories also received release workflows to streamline versioning and GitHub Release creation. Notable additions included granting checks:write permissions to CI jobs in vgi-bgp and vgi-compress to unblock release automation, and refactoring Python workers into importable wheel packages in vgi-sigma, vgi-xslt, vgi-scholar, and vgi-libpostal for better composability.

RPC Infrastructure Updates

vgi-rpc-rust received significant enhancements: client-authoritative codec negotiation and compression enabled by default in the HTTP layer, along with a fix to disable axum's DefaultBodyLimit so the configured max_body_size is respected. The MSRV (Minimum Supported Rust Version) was raised from 1.90 to 1.97, and a compression-disabled worker was added to the shared conformance test suite. Two releases shipped: 0.15.0 and 0.16.0. Similar codec negotiation and compression changes landed in vgi-rpc-go. The vgi-rpc-typescript repository also began receiving multi-arch Docker builds.

Core Rust & Java Updates

vgi-rust released 0.23.0 following updates to support vgi-rpc 0.15's HTTP codec negotiation; the MSRV bump to 1.97 was applied here as well, with clippy lint fixes following. vgi-java bumped to 0.20.0, migrating to vgirpc 0.17.0 and introducing per-partition result-cache fixtures via the new vgi.cache.partition_scope configuration. Build dependencies were updated accordingly.

Code Quality & Standards

Multiple repositories achieved or maintained vgi-lint score of 100/100: vgi-bgp reached the milestone after dropping the bgp_version() scalar, vgi-netflow cleared all findings (68→100) and removed netflow_version(), and vgi-compress lifted to perfect score under vgi-lint-check 0.73.0. vgi-etf-schwab also hit 100 and bumped vgi-python to 0.16.1. vgi-azure-signins upgraded to vgi 0.19 / vgi-rpc 0.14 and cleared vgi-lint findings with new filter/until examples.

Workflow Improvements

vgi-trading-calendar made its CI workflow reusable via workflow_call so docker-publish can gate on it—a pattern likely used across other repositories. Several projects added ci/check-version.sh guards (e.g., vgi-scholar) to enforce consistency between git tags and pyproject versions. Conformance test suites in both vgi-rpc-rust and vgi-rpc-go now include compression-disabled workers to validate behavior across configurations.

Private Repository Activity

An additional 43 commits were made across 8 private repositories, continuing parallel development efforts.

A substantial push across the VGI extension ecosystem, focused on standardizing metadata quality and SDK version alignment. The work spans 79 repositories with 117 commits, demonstrating a coordinated effort to upgrade catalogs and achieve consistent linting conformance.

Metadata and Linting Standardization

Rusty undertook a systematic pass across dozens of extensions to drive vgi-lint conformance to 100/100. This involved clearing findings in vgi-chart, vgi-jolt, vgi-mask, vgi-conform, vgi-ioc, vgi-yara, vgi-secretscan, vgi-sigma, vgi-causal, vgi-iso20022, vgi-tiktoken, vgi-xslt, vgi-scholar, vgi-docgen, vgi-libpostal, vgi-trading-calendar, vgi-statsmodels, vgi-mft, vgi-code, vgi-x12, vgi-audio, vgi-feed, vgi-geocode, vgi-cve, vgi-anomaly, vgi-survival, vgi-vision, vgi-sympy, vgi-quant, vgi-match, vgi-pdf, vgi-useragent, vgi-units, vgi-fhir, vgi-odata, vgi-tantivy, vgi-news, vgi-poi, and vgi-saml. The work included standardizing catalog descriptions, removing version scalars in favor of catalog-level implementation_version, and ensuring type backticking in documentation.

SDK Upgrades

Across the ecosystem, SDK versions were bumped consistently—primarily to vgi-python 0.16.x, vgi-go 0.16, and vgi-rpc-go 0.16. Notable extensions receiving this treatment include vgi-elasticsearch, vgi-lint-check (which added new rule VGI106 for substantive catalog descriptions), vgi-sigma, vgi-causal, vgi-libpostal, vgi-statsmodels, vgi-feed, vgi-geocode, vgi-cve, vgi-fhir, vgi-odata, and vgi-news.

Feature Releases and Enhancements

Several extensions reached stable release status. vgi-tika shipped v0.1.0 as the first tagged jar release (dropping -SNAPSHOT). vgi-image, vgi-ioc, vgi-yara, vgi-mft, vgi-code, vgi-x12, and vgi-tantivy all bumped to v0.1.1. vgi-fixedformat released 0.9.2 with a new wasm32 browser build alongside native support, splitting SDK features appropriately for each target.

Enhancements to extension functionality included adding supported_postal_countries discovery table in vgi-conform, thumbnail_fit ergonomics and dropping image_version in vgi-image, introducing yara_modules browsable table in vgi-yara, and adding transaction_sets reference view in vgi-x12. The vgi-trading-calendar extension gained a trading_sessions column ergonomics pass. vgi-causal exposed random_state argument, and vgi-anomaly added zscore default overload.

Build and CI Improvements

vgi-x12 received CI hardening with grants for release workflow checks and secrets inheritance fixes. vgi-fixedformat integrated VGI_WORKER_PRE environment variable into the wasm build pipeline. vgi-java and vgi-rust benefited from benchmark fixture additions, and vgi-rust enabled sha2-asm and fast hex optimizations.

Community Infrastructure

haybarn-wasm was bumped to 1.5.4-rc2, and work continued on haybarn-community-extensions with 19 commits across private repositories.

Additional refinements across the suite included SQL ergonomics passes (vgi-xslt), richer example documentation (vgi-geocode, vgi-quant, vgi-survival, vgi-pdf), and gate hardening in vgi-news.

A major coordination day across the VGI extension ecosystem, with 101 commits focused on aligning the entire suite to the latest platform releases.

Core Platform Updates

Rusty pushed vgi-rust to version 0.21.0, introducing a per-partition result-cache opt-in feature alongside dependency refreshes. The update brings in vgi-rpc 0.14.2, ureq 3, bincode 2, and axum 0.8.

Work on vgi-rpc-rust was particularly focused on performance and quality. He cut per-request and per-tick allocations across dispatch, wire, and HTTP layers, released version 0.14.2 with rustdoc link fixes, and resolved all 15 intra-doc-link warnings. Additional improvements included gating build_log_metadata on the http feature and pruning trybuild scratch before rust-cache saves.

vgi-rpc-go saw parallel optimization efforts: memoizing per-type reflection and pooling codec writers while fixing two concurrency bugs. Documentation was overhauled to replace the circular badge with the VGI shield mark, and the conformance pipeline now drives from the released PyPI package rather than a hardcoded venv. Dependencies were refreshed across the board, including arrow-go v18.6.0 and migrating to the sentry-go v0.48 API.

Lint Rule Expansion

vgi-lint-check saw active development with three new rules and two releases. Rusty added VGI182 (description-type-formatting), VGI181 (description-boilerplate), and VGI328 (no-diagnostic-function), released as 0.71.0 and 0.70.0 respectively. He also escalated VGI509 from a warning to a hard error, requiring executable examples in extension metadata—this went out as version 0.72.0.

Extension Ecosystem Alignment

The bulk of today's work was a coordinated update across 25+ extension repositories. Each repo received two primary changes:

• Float vgi/vgi-rpc to the latest 0.x and refresh lockfiles to vgi 0.21.0
• Add the new ProcessParams/InitRequest fields introduced by vgi 0.21

Affected repos include vgi-bgp, vgi-mask, vgi-image, vgi-ioc, vgi-compress, vgi-yara, vgi-netflow, vgi-tiktoken, vgi-iso20022, vgi-cbor, vgi-mft, vgi-code, vgi-x12, vgi-pprof, vgi-sourcemap, vgi-useragent, vgi-units, and vgi-tantivy.

Special Focus: Fixed Format Extension

vgi-fixedformat received targeted attention across three releases (0.9.0, 0.9.1, and subsequent work). He removed the deprecated fixedformat_version() function, conformed catalog metadata to VGI515, bumped dependencies to vgi 0.21 and vgi-rpc 0.14.2, dropped fixed quick-xml audit ignores, and resolved vgi-lint metadata gates for VGI515 and VGI509 compliance.

Community & Private Work

One issue/PR comment reply provided community support or feedback. Additionally, 18 commits across 9 private repositories indicate ongoing internal work.

Work today focused on maintaining and upgrading the vgi-tika project. Rusty bumped the VGI SDK dependencies to versions 0.19.0 and 0.16.0, then addressed linting issues flagged by vgi-lint-check. This kind of dependency housekeeping ensures the project stays current with upstream SDK improvements and maintains code quality standards.

A new issue was also opened, though details about its scope remain to be seen.

Rusty had a prolific day across the VGI ecosystem, coordinating a major version bump cycle to align the Java, Rust, Go, and TypeScript implementations with Python 0.16 delta features.

vgi-java saw the most extensive work. The release bumped from 0.18.0 to 0.19.0, bringing blended table operators, provenance tracking, and result caching into the Java runtime. Key commits include exchange-mode result-cache support with scalar CACHE_CONTROL opt-in, blended RowTransformFunction support across Phase A and Phase B, and substream_id routing with parallel per-substream finalization. A critical fix ensured named exchange states survive HTTP token roundtrips, preventing initialization-baked arguments from being lost during serialization.

vgi-rpc-rust received coordinated updates for HTTP exchange parity and shared-memory (SHM) request routing. The workspace bumped to 0.13.0, introducing continuation-only stream resume via new client methods (resume_stream, next_with_token, seek_to_token). SHM routing was hardened with proper batch resolution and per-connection segment caching, plus a fix to compile on targets lacking both POSIX and Win32 SHM support. HTTP delivery was corrected to pass the init request's metadata to a producer's first tick, ensuring consistent state.

vgi-rpc-go merged HTTP metadata handling improvements. The init request's continuation token now rolls forward with emit metadata, and InputMetadata from exchanges is properly surfaced. Support for capability discovery through HEAD /health was regression-tested, and public wire contracts were exposed: __upload_url__ for upload routing, DecodeContentEncoding for intermediary body decoding, and helper functions (WriteRequest, FindStateToken, FindProtocolVersion, unary-result rewrap).

vgi-rust underwent the heaviest feature lift. The 0.20.0 release integrated blended operators, per-output-row provenance for LATERAL joins, and result caching. Scalar functions gained opt-in caching with CACHE_CONTROL, table-in-out blended support added worker routing with arity/varargs overload resolution, and substream_id routing enabled parallel finalization. Conditional-revalidation validators were surfaced for cache control in buffered-finalize emits. A one-to-zero edge case in BlendedDropFunction was added to fixtures for regression prevention. The workspace now consumes vgi-rpc 0.13.0 from crates.io rather than a local patch.

vgi-rpc-typescript aligned with Rust and Go. Version 0.14.0 added client stream resume methods (nextWithToken, seekToToken, resumeStream), fixed HTTP metadata preservation on zero-row exchange data batches, and hardened wire error handling by defaulting buildErrorStream to an empty schema. Integration tests were updated to expect DESCRIBE_VERSION 4 from CLI describe, and Biome linting issues were resolved.

vgi-llm was updated for Python 0.16.0 compatibility and VGI515 example descriptions using vgi-lint 0.69.0.

Across all public activity, 54 commits shipped coordinated feature work and fixes. An additional 21 commits were made to private repositories. The day reflects a major version synchronization effort spanning six language bindings and RPC transports.

A productive day focused on linting rules, metadata enhancements, and WebAssembly worker improvements across the Query-farm ecosystem.

Linting & Code Quality

Two new linting rules shipped in vgi-lint-check. The VGI515 rule now requires every example to carry a description, released in version 0.68.0. Following closely, VGI327 flags hand-rolled function registries in favor of proper abstractions, landing in 0.69.0. These additions tighten the codebase's quality gates and enforce better documentation practices.

Rust Metadata Layer

The vgi-rust repository gained a new metadata field: FunctionMetadata.max_workers, which controls parallel scan fan-out. This enables more granular tuning of concurrent execution within function pipelines.

WebAssembly Worker Transport

Substantial work landed in haybarn-wasm to mature the SAB (SharedArrayBuffer) transport for the VGI worker. Key improvements include:

• Cancellation-aware ring buffer reads with improved build hygiene
• Integration of navigator.geolocation into the SAB worker context
• Fixed ring stub reads to use live wasmMemory.buffer references and unique claim IDs to prevent races
• Claim-ID token semantics updated to fix a Stream header EOF slot-reuse race condition
• Replaced the geolocation handler with a generic onVgiWorkerMessage hook for broader extensibility

These changes solidify the worker's ability to operate concurrently with proper resource cleanup and message routing.

TypeScript RPC & LLM

The vgi-rpc-typescript package now exports ByteSink from index.core and accepts browser ByteSink instances as the serve writable target, improving interoperability with browser-based sinks. Meanwhile, vgi-llm reached version 0.1.2 with OCI image publication to ghcr.io on release, streamlining deployment workflows.

26 additional commits landed across private repositories.

Rusty maintained focus across several interconnected projects today, with 17 commits across open-source repositories and additional private work.

In vgi-rust, he fixed a schema consistency issue in the catalog module, ensuring that input_from_args is properly included in the FunctionInfo schema to match the behavior of both the C++ and Python implementations. This type of cross-language alignment is critical for maintaining feature parity across the VGI ecosystem.

Over in haybarn-wasm, two commits addressed worker coordination and transport concerns. First, a fix to the process-global worker deduplication logic eliminated race conditions when handling concurrent worker scans. This was followed by a more substantial feature addition: integration of a SharedArrayBuffer (SAB) transport engine with main-thread bridge glue code. This work improves how the WASM runtime communicates with worker threads, laying groundwork for higher-concurrency workload handling.

Rusty also engaged in community stewardship across the DuckDB ecosystem. He replied to issue #2234 on community-extensions, clarifying support expectations for versioned community extension releases. On the main duckdb repository, he provided feedback on PR #23731, which introduces an external resource type registry and SQL-level create_external_resource functionality — a significant feature for extending DuckDB's resource management capabilities.

Beyond the visible activity, 14 commits across private repositories suggest ongoing work on related infrastructure or internal tooling.

Cross-platform compilation and WebAssembly focus dominated today's work, with significant progress on making RPC and worker infrastructure compile cleanly for wasm32 targets.

In vgi-rpc-rust, Rusty tackled platform-specific gating to unblock WebAssembly builds. A fix targeted windows-sys to Windows only so the shared-memory module won't break on wasm32, and another corrected macro feature gating to separate stream-codec from http dependencies, allowing more granular compilation paths.

Similar cross-platform work landed in vgi-rust, where the ctrlc handler was gated off for wasm32 environments. More notably, he exposed a public serve_reader_writer method, enabling arbitrary byte-stream transports beyond the built-in HTTP stack—a valuable abstraction for specialized transport layers.

haybarn-wasm saw major progress on the worker transport layer. Two commits introduced JavaScript library slot stubs for SAB (SharedArrayBuffer) transport and an ABI-exact SAB duplex-ring core with Node.js testing, laying groundwork for high-performance bidirectional byte-stream communication in the browser and Node.js environments.

In vgi-llm, the work shifted toward CI reliability and feature development. He hardened the deterministic tooling installation, refactored test storage to use process-local in-memory backends compatible with pytest-xdist parallelization, and isolated pydoclint to avoid namespace collisions. The project also received a comprehensive initial commit introducing vgi-aisql—Cortex-style AI functions for DuckDB—which was later renamed to vgi-llm. Secrets handling was hardened with improved aggregate secret reads, and a version bump to 0.1.1 was published.

On the open-source front, Rusty opened two PRs on duckdb/community-extensions (PR #2237 and PR #2236) updating the adbc_scanner extension to the latest commits, continuing active stewardship of the DuckDB ecosystem.

Throughout the day, 41 commits across the active repos and 28 additional commits on private infrastructure demonstrate sustained momentum on transport abstraction, WebAssembly compatibility, and AI-native database features.

A focused day of infrastructure updates and linter conformance across the Query-farm ecosystem. The work centered on propagating breaking changes from the core vgi-rust SDK and ensuring all dependent worker projects conform to the latest linting standards.

Core SDK and Linter Updates

In vgi-rust, Rusty released version 0.19.0 with a significant wire-format change: renaming required_field_filter_paths to required_filters using Conjunctive Normal Form (CNF). This change was reflected in vgi-java with breaking updates to the TableInfo catalog structure and corresponding test fixes. The vgi-lint-check linter was enhanced with a new VGI415 rule validating the vgi_required_filters tag, triggering a 0.67.0 release. A separate quality improvement scoped VGI316 to table functions only, released as v0.66.0.

Worker and Extension Conformance

Following the SDK updates, Rusty systematically updated 16+ worker extensions to track the latest vgi-lint-check scoring rules and dependency versions. Python-based workers (vgi-sigma, vgi-scholar, vgi-statsmodels, vgi-sympy, vgi-quant, vgi-pdf, vgi-search, vgi-survival) were upgraded to vgi-python 0.15.0 and brought into full linter conformance. Rust-based workers (vgi-netflow, vgi-tiktoken, vgi-mft, vgi-pprof, vgi-sourcemap, vgi-saml, vgi-tantivy) were bumped to vgi 0.17–0.19 and vgi-rpc 0.11, with several reaching perfect lint scores (e.g., vgi-tantivy at 100/100). Additional updates included transitive dependency bumps in vgi-mask (cc 1.2.67, rand 0.8.7) and CI workflow improvements across the suite.

Community Review and Maintenance

Beyond direct commits, Rusty reviewed and approved 43 pull requests across the ecosystem—dependency upgrades, security patches (ed25519-dalek 2.2→3.0, p256 0.13→0.14, ecdsa 0.16→0.17, p384 0.13→0.14), and CI tool updates (actions/checkout, dtolnay/rust-toolchain, sccache-action). This systematic review and approval workflow ensured consistent standards and timely integration of updates across all projects.

VGI linting refinement. Rusty opened PR #10 on vgi-lint-check to scope the VGI316 rule — which flags array arguments that could be table functions — to table functions only. The rule was previously firing on scalar and aggregate functions as false positives, since those function types cannot structurally be refactored into table functions that accept relation inputs. This tightens the rule's applicability and reduces noise for users.

Dependency maintenance across the ecosystem. He provided feedback on two dependency-related PRs on vgi-mask: one bumping the vgi linter from 0.11.0 to 0.14.0 (PR #14) and another updating the mozilla-actions/sccache-action CI action from 0.0.9 to 0.0.10 (PR #12). Additionally, he replied to an open issue on shellfs (#11) regarding a missing release for v1.4.5, helping coordinate the release pipeline.

Private work. One commit landed on a private repository.

A high-velocity coordination day across the VGI ecosystem. Rusty drove releases and conformance updates across 30+ repositories, touching both infrastructure libraries and domain-specific extensions.

Core SDK releases: vgi-rust bumped to 0.18.0 with result-cache worker support—new fixtures and example code added to demonstrate the pattern. The Java SDK (vgi-java) reached 0.17.0, also adding result-cache workers plus a fix pinning the RPC reference to resolve HTTP metadata initialization. TypeScript RPC (vgi-rpc-typescript) and Java RPC (vgi-rpc-java) both released 0.13.0 and 0.16.0 respectively, introducing intermediary wire helpers for framing and HTTP first-tick metadata delivery, with Go RPC (vgi-rpc-go) receiving the same metadata fix. Rust RPC (vgi-rpc-rust) advanced to 0.12.0 with intermediary wire helpers, public __upload_url__ contract, and gzip decoding support.

Lint conformance wave: vgi-lint-check released 0.65.0 after merging PR #9, which excludes COPY-format handlers from corpus coverage to address false positives (VGI511/VGI520). Across the ecosystem, 15+ repositories—including vgi-mask, vgi-etf-schwab, vgi-image, vgi-ioc, vgi-secretscan, vgi-iso20022, vgi-fixedformat, vgi-odata, vgi-news, vgi-poi, and others—were updated to conform to vgi-lint 0.63.1–0.64.0, with most achieving 100% static compliance or near-perfect scores.

Feature & bug fixes: cupola addressed two editor usability issues—preventing comment-only segments from being treated as runnable statements, and preserving shared SQL across sign-in redirects. The vgi-secretscan detector registry is now browsable. vgi-rust unblocked six silently-gated tests and guarded CI against fatal-signal reports. vgi-fixedformat added an audit exemption for unfixable quick-xml DoS advisories.

Dependency stewardship: Rusty provided approvals and feedback across 28 dependency upgrade PRs spanning minor-version SDK bumps, CI action updates (checkout, setup-uv, rust-toolchain), and direct dependency refreshes (object_store, quick-xml, bgpkit-parser) across extensions like vgi-cbor, vgi-compress, vgi-bson, vgi-bgp, vgi-disasm, vgi-charset, vgi-asn1, vgi-evtx, vgi-barcode, and more.

Activity also included 10 commits across 8 private repositories.

A day of systematic conformance work across the VGI ecosystem. Rusty released vgi-lint-check 0.63.1, which included a significant performance optimization that strips Claude Code agent context from the claude -p command — reducing token usage by 13× — along with fixes for batch byte parsing and new hang/batch shape probing (VGI911/VGI912). He then brought 20+ worker repositories into alignment with this latest lint standard, bumping SDK versions across Go, Python, and JavaScript implementations.

vgi-lint-check itself saw two releases this cycle. The 0.63.0 release introduced execution diagnostics to probe every scan for hangs and batch shape anomalies. Version 0.63.1 followed with the token optimization and a critical fix to parse Batch Bytes exactly rather than via float conversion.

Across the broader ecosystem:

• vgi-jolt, vgi-chart, vgi-bgp, vgi-elasticsearch, vgi-tika, vgi-conform, vgi-docgen, vgi-cbor, vgi-code, vgi-audio, vgi-feed, vgi-cve, vgi-anomaly, vgi-fhir, vgi-azure-directory, vgi-azure-defender, vgi-azure-loganalytics, vgi-ical, and vgi-hl7 all received conformance updates to meet the 0.63.1 standard, with SDK dependency bumps across vgi-go (0.14–0.16), vgi-python (0.14–0.16), and vgi-rpc variants (0.11–0.15).

• vgi-etf-schwab, a new Python VGI worker for streaming fund data via BoundStorage queue and parallel workers, received its initial commit and containerization setup (Dockerfile, docker-publish CI, ghcr.io image tagging).

• vgi-azure-signins, vgi-azure-risk, vgi-causal, and vgi-compress added metadata-quality CI gates alongside their conformance upgrades.

• vgi-anomaly received special attention for linter timeout tuning to accommodate cold numba JIT startup.

cupola (the query editor) gained shareable links via #sql= and #sql_z= hash parameters, and fixes for OAuth redirect flashing and history pollution. Share links now point to /latest/ for version stability.

Rusty also replied to issue #50 on httpserver regarding a DuckDB 1.5 release.

Beyond the public repos, 19 commits landed across 7 private repositories.

A productive day across the VGI ecosystem, with significant feature work in linting and documentation tooling, plus coordinated version bumps across multiple language bindings.

In vgi-lint-check, the focus was on expanding validation coverage with three new checks: flagging bare SELECT * in example queries (VGI514) as low-effort, detecting documentation headings that duplicate short descriptions (VGI178), and warning when workers define table functions but lack browsable tables or views (VGI146). Additionally, support for structured and validated table-function result schemas was implemented. These changes shipped in v0.61.0.

vgi-java and vgi-rust received coordinated version updates, surfacing catalog macros in describe.json (0.15.0/0.16.0) and adding per-schema documentation support (0.16.0/0.17.0). The Rust bindings also saw CI fixes to pin the vgi-rpc dependency and apply rustfmt formatting to macro-generated code.

The most substantial work landed in cupola, where the landing page received a comprehensive overhaul: markdown rendering now supports DuckDB types and macros with expand-only descriptions, tables are properly formatted, and per-argument documentation with constraints is surfaced in the Arguments section. A two-tier Cupola call-to-action and footer were also added. On the attachment side, cupola now honors the ?data_version_spec= query parameter to pin catalog data versions at ATTACH time.

Language binding releases were synchronized across vgi-rpc-rust, vgi-rpc-typescript, and vgi-rpc-java to refresh vendored landing.html assets, with workspace versions bumped from 0.9.0 to 0.11.0 across the stack. vgi-rust CI also kept pace, updating doc-example pins accordingly.

Private repository work involved 9 additional commits across 5 repos.

Rusty had a highly productive day across the VGI ecosystem, shipping 52 commits across nine repositories while maintaining active development on five private projects.

Landing Pages & Identity: A major theme emerged around standardizing worker landing pages across the platform. The vgi-rpc-rust, vgi-rpc-go, vgi-rpc-typescript, and vgi-rpc-java repositories all received updates to serve a shared, standardized landing surface with VGI logo headers and _vgi_identity cookie support. Similar landing page implementations landed in vgi-java and vgi-rust. This coordinated effort appears designed to provide a consistent user experience across language-specific RPC implementations.

Linting & Validation (vgi-lint-check): Several lint rule improvements shipped, including fixes for VGI317 range regex, VGI313 ambiguous types, and a target-scoping leak. New validation rules were added: VGI014/VGI015 now validate vgi.icon_url image assets, and VGI145 ensures views wrapping parameterless table functions are classified as tables. Parse-based example and test coverage tracking landed via json_serialize_sql (VGI511-513, 520-521), and worker subprocess pools now warm up proactively with warnings on slow relaunches. A significant tutorial linting system shipped—VGI1327 validates that tutorials feature DuckDB/SQL for search intent, while executable worker tutorials can now be linted, verified, built, and LLM-planned (VGI13xx). Version 0.59.0 was released.

Frontend & Editor (cupola): The web editor received multiple UX enhancements: results grid cells/rows/columns are now copyable with selection support, EXPLAIN output renders as a formatted plan tree, and users can now maximize or pop out the results grid as a snapshot. A split button for "Create SELECT query" was added to the catalog table page. Landing page updates brought the VGI logo header, and metadata tags now adopt the vgi-lint-check standard. Dependency updates pinned @haybarn/haybarn-wasm to 1.5.4-rc1 for the updated catalog_attach schema, and the vendored VGI extension mirror bumped to v1.5.4. A fix resolved vgi/client bundling issues, and shell initialization now syncs timezone before ATTACH to avoid timeout warnings. Version 0.4.94 shipped with maximize/pop-out and timezone fixes.

Trading Calendar (vgi-trading-calendar): A new VGI worker for trading calendars launched with initial commits. Module filenames were refactored to drop redundant trading_ prefixes, and metadata was updated to satisfy vgi-lint rules VGI509 and VGI804.

Dependency Management (vgi-rpc-rust, vgi-java): Internal workspace dependencies were bumped from 0.8.0 to 0.9.0 across the Rust RPC implementation, and vgi-java pinned VGI_RPC_JAVA_REF to v0.13.0 to pick up the new DescribeProvider feature. Test examples were advanced to 1.5.4-rc1.

Beyond the public repositories, Rusty maintained active development across five private projects with 15 commits, suggesting ongoing infrastructure or client work.

VGI Linting Improvements

Rusty continued enhancing the validation ruleset in vgi-lint-check, promoting an existing diagnostic to error status (VGI317) and introducing a new rule requiring language declarations on code fences within descriptions (VGI177). These changes tighten the constraints on documentation quality and code block formatting.

DataSketches Integration & Community Support

A PR was opened on the DuckDB community extensions to update datasketches to the latest upstream commits, keeping the extension synchronized with the parent library's improvements.

On the datasketches repository itself, Rusty engaged with two active issues. He investigated a segmentation fault occurring during parallel aggregation when merging KLL sketches—specifically an unguarded null pointer in DSQuantilesMergeOperation::Combine (issue #8). He also reviewed a feature request to add approximate mode and frequent items support leveraging DataSketches' FrequentItemsSketch (issue #3), providing feedback on the proposed enhancement.

Background Activity

Substantial work continued across five private repositories, with 13 commits spanning multiple projects.

A focused day on constraint metadata and argument validation across the VGI ecosystem. Rusty drove significant work on per-argument constraint enforcement, touching four repositories with coordinated updates.

vgi-java received the bulk of the changes. He implemented per-argument constraint metadata for agent discovery, allowing functions like make_series to declare fine-grained constraints on specific arguments (count and step parameters). The work included enforcing these const-argument constraints across all bind paths, with corresponding updates to scalar binding logic. Three version bumps reflect the progression of this feature: 0.10.0 → 0.11.0 → 0.12.0. A new test fixture (multi_branch_iceberg) was added to example-worker for parity with existing test coverage.

vgi-lint-check saw parallel constraint validation work. New linting rules (VGI318, VGI319, VGI320) now validate declared argument constraints against actual function signatures. VGI317 was broadened to catch colon and or-list enumerations in constraint declarations. The uv.lock was synced to 0.57.0, and the package versioned from 0.56.0 to 0.57.0.

vgi-rust mirrored the Java work with equivalent constraint enforcement at the dispatch and function binding layers. He bumped the version twice (0.11.0 → 0.12.0 → 0.13.0) and updated the make_series example to declare its count/step constraints. A fixture correction removed framework-level bounds declarations from vgi_percentile.

vgi-units was updated to depend on the new VGI 0.14.0, bringing in all the constraint validation improvements downstream.

Beyond these repositories, Rusty also maintained 45 commits across three private projects, keeping ancillary systems in sync with the public work.

A prolific day across the VGI ecosystem and DuckDB community engagement, with 71 commits spanning 19 repositories and significant work on shared library consumption patterns.

Rust Compilation & CI Maintenance: Rusty tackled a wave of Rust 1.96 stability updates across multiple repositories. Key fixes included:

• vgi-bgp: Resolved cargo-audit job failures by correcting RUSTSEC advisory ignore syntax to comma-separated single-line format and fixing check-run permissions
• vgi-netflow: Fixed clippy collapsible_match lints and provisioned the inet extension in E2E testing
• vgi-iso20022, vgi-cbor: Applied stable 1.96 clippy lint corrections
• vgi-compress, vgi-x12, vgi-saml: Granted checks:write permissions to supply-chain audit jobs for improved CI reliability

Catalog & Query Infrastructure: The Rust and Java segments received significant architectural updates:

• vgi-rust and vgi-java: Implemented companion catalogs with new catalog-table scan branches, expanding query federation capabilities. A subsequent fix in vgi-rust restored CI stability after the port
• vgi-lint-check: Added VGI316 function to flag lone multi-dimensional-array arguments as table inputs, improving lint coverage

Azure Integration Suite: Five new Azure-focused modules were initialized (vgi-azure-signins, vgi-azure-node-auth, vgi-azure-risk, vgi-azure-directory, vgi-azure-defender, vgi-azure-loganalytics). Each module followed a consistent pattern:

• Initial repository setup
• MIT relicensing
• GitHub Actions CI integration via vgi-actions ts-ci.yml
• Dependency consumption progression: github shorthand → git+ssh deps → npm registry consumption of shared libraries

This progression demonstrates a shift toward decoupled, npm-based dependency management for zero-auth installation and reduced on-disk sibling coupling.

Documentation & Metadata: vgi-audio received a metadata quality pass including agent suite updates, category refinement, and structured documentation improvements, alongside dependency refreshes.

DuckDB Community Support: Rusty provided feedback on two important community discussions:

• Replied to PR #22564 on duckdb addressing the duckdb_secret_type_parameters system view feature
• Engaged with issue #21471 on duckdb regarding LogicalTypeId::VARIANT ADBC support limitations

Additional work included updating vgi-rust doc-examples CI to track the latest haybarn-cli release instead of a stale pin, and fixing a broken spacy download step in vgi-pii CI that was incompatible with uv virtual environments.

Private repositories also received 27 commits across 11 projects during this session.

Rusty spent the day performing systematic maintenance and upgrades across the VGI (Validated Grammar Infrastructure) ecosystem. The work focused on bumping dependencies to newer SDK versions and resolving linter findings across multiple specialized schema and format repositories.

The vgi-chart, vgi-tika, and vgi-hl7 repositories received updates to the VGI Java SDK, bringing them to versions 0.10.0/0.12.0 while clearing associated vgi-lint findings. The vgi-chart project improved its lint score from 83 to 96, while both vgi-tika and vgi-hl7 achieved clean lint reports.

Multiple schema-focused repositories—vgi-iso20022, vgi-mft, vgi-x12, and vgi-saml—received coordinated upgrades to VGI 0.11.0 and vgi-rpc 0.8.0. Additionally, the schema documentation in vgi-mft and vgi-x12 was restructured into Markdown format (doc_md), improving readability and consistency. The vgi-saml repository cleared schema documentation findings (VGI175/176).

The vgi-news repository achieved a perfect vgi-lint score of 98 with zero findings while also updating floating dependencies. Similarly, vgi-poi made significant progress, bumping the VGI Java SDK and Apache POI dependencies while improving its lint score from 90 to 98. The vgi-ical project updated both the VGI SDK and iCal4j library while resolving all linter 0.55.0 findings.

Beyond the VGI ecosystem, Rusty also maintained activity across 5 private repositories.

This was a coordinated dependency upgrade cycle across the entire VGI format library ecosystem, with particular emphasis on achieving clean linter passes and improving code quality metrics.

Rusty spent the day systematizing quality standards across the vgi ecosystem, pushing a coordinated wave of commits to improve linting compliance and dependency management.

Across vgi-jolt, vgi-elasticsearch, vgi-conform, vgi-sigma, vgi-causal, and vgi-xslt, he raised vgi-lint scores to 98 with zero findings, added agent-test suites and category registries where missing, and refreshed dependencies. The work followed a consistent pattern: identifying and fixing metadata violations, de-enumerating documentation, and updating SDK versions.

In vgi-scholar, vgi-docgen, and vgi-libpostal, similar improvements brought lint scores to 97–99 (static), including fixes for doc SQL fence formatting and complete clearing of findings. vgi-statsmodels achieved 100 static / 94 with --ai, demonstrating high metadata compliance.

Other repos received targeted attention: vgi-geocode and vgi-search gained agent task suites and category registries with de-enumerated docs. vgi-anomaly saw a significant jump from 70 to 98 through crash-proof concurrency fixes, documentation improvements, and agent suite additions. vgi-survival, vgi-vision, vgi-sympy, vgi-pdf, vgi-match, and vgi-pii all received similar linting fixes, with vgi-pii also warming up Presidio fully.

On haybarn, Rusty opened PR #4 to roll the ducklake extension pin forward from a1e7d2f8 to 06674268, syncing with upstream's v1.5 release branch after merging the fork with upstream/v1.5-variegata.

A major coordinated effort across the VGI ecosystem today, centered on upgrading to vgi 0.11.0 and vgi-rpc 0.8.0, along with systematic linting cleanup. The work spans 29 repositories and reflects both infrastructure updates and quality improvements.

Core infrastructure and linting tools:

The vgi-lint-check repository received substantial enhancements with several new linting rules and performance improvements. New VGI314 rule flags function documentation that redundantly re-documents arguments, while VGI142 identifies redundant get_/list_ naming prefixes in structures. Additional VGI175 and VGI176 rules reward well-structured Markdown in catalog and schema documentation. A major performance win came through parallelizing the LLM doc-review pass and splitting AI trace phases. He also added --trace timing mode, CPU-count execution parallelism, and attach-options configuration. A new feature introduces deterministic cross-object consistency rules that catch naming and type drift across the codebase.

The vgi-rust core library was bumped to 0.11.0 with new secret handling features: table-in-out two-phase secret binding, aggregate static secret support, and secret fixtures. Shared memory (shm) was enabled on vgi-rpc 0.8.0, with version tracking added to the doc-example harness. Meanwhile, vgi-java added aggregate and table-in-out secret binding with corresponding test fixtures.

Systematic ecosystem upgrades and quality improvements:

Across vgi-bgp, vgi-mask, vgi-image, vgi-ioc, vgi-compress, vgi-yara, vgi-netflow, vgi-secretscan, vgi-iso20022, vgi-tiktoken, vgi-cbor, vgi-mft, vgi-code, vgi-x12, vgi-fixedformat, vgi-feed, vgi-cve, vgi-pprof, vgi-quant, vgi-sourcemap, vgi-useragent, vgi-units, vgi-fhir, vgi-odata, vgi-tantivy, and vgi-saml—Rusty performed coordinated updates combining dependency bumps, vgi-lint finding clearance, and metadata quality improvements. Most repos achieved vgi-lint scores of 97–100, with several reaching perfect static and agent-check scores. Notable highlights include vgi-compress reaching 100 static / 0 findings, vgi-cbor achieving 100 static and 100 agent, and vgi-saml jumping from 67 to 97. Several repositories added category registries and per-set shaped documentation.

Additionally, 11 commits were made across private repositories as part of the broader ecosystem work.

This coordinated push demonstrates a comprehensive quality and infrastructure initiative, standardizing the entire VGI extension portfolio to the latest stable versions while enforcing consistent documentation and metadata standards.