vgi-python 0.32.0__tar.gz → 0.34.0__tar.gz

{vgi_python-0.32.0 → vgi_python-0.34.0}/CLAUDE.md

@@ -297,7 +297,7 @@ vgi-client --input data.parquet --function sum_all_columns --worker vgi-fixture-
 | `VGI_OAUTH_DEVICE_CODE_CLIENT_ID` | Client ID for device-code flow (optional, URL-safe chars only) |
 | `VGI_OAUTH_DEVICE_CODE_CLIENT_SECRET` | Client secret for device-code flow (optional, URL-safe chars only) |
 | `VGI_OAUTH_USE_ID_TOKEN` | When `1`/`true`/`yes`, clients use OIDC `id_token` as Bearer instead of `access_token` |
-| `VGI_INTROSPECT_PRINCIPALS` | Comma-separated principals permitted to call `__introspect_token__`. Required — no permissive default — whenever the worker implements `resolve_token()` (see below) |
+| `VGI_INTROSPECT_PRINCIPALS` | Comma-separated principals permitted to call `vgi_rpc.Identity.v1`'s `introspect_token`. Required — no permissive default — whenever the worker implements `resolve_token()` (see below) |
 | `VGI_INTROSPECT_RATE_LIMIT` | Introspection requests allowed per caller per second (default 20) |
 | `VGI_WORKER_ACCESS_LOG_SAMPLE` | Fraction of *successful* calls to keep in the access log, `0.0`–`1.0`. Errors are always kept; the decision is per call, so every record of one stream shares a fate |
 | `VGI_WORKER_ACCESS_LOG_ASYNC` | When `1`/`true`/`yes`, emit access-log records from a listener thread. Bounded queue; full means drop, and a crash loses whatever is queued |
@@ -420,10 +420,16 @@ Also available on `Worker.main --http` and the fixture server. Under
 
 ### Token Introspection (`resolve_token`)
 
-A worker may optionally expose `POST {prefix}/__introspect_token__`, which
-resolves an opaque bearer credential to a principal — for a reverse proxy that
-terminates the only public listener and must know the caller's identity before
-it can authorize anything.
+A worker may optionally host the `vgi_rpc.Identity.v1` protocol, whose
+`introspect_token` method resolves an opaque bearer credential to a principal —
+for a reverse proxy that terminates the only public listener and must know the
+caller's identity before it can authorize anything.
+
+Through vgi-rpc 0.45.x this was an HTTP JSON route, `POST
+{prefix}/__introspect_token__`, which meant it existed on exactly one
+transport. As of **vgi-rpc 0.46.0** identity lives at the RPC layer, so it
+reaches every transport, and a client discovers it through ordinary reflection
+(`list_protocols`) rather than by calling and reading an error.
 
 ```python
 from vgi.auth import AuthUnavailableError, TokenIdentity
@@ -444,9 +450,11 @@ class MyWorker(Worker):
         return TokenIdentity(principal=row.principal, token_name=row.label)
 ```
 
-**The route does not exist until `resolve_token` is overridden** — absent, not
-routed-and-refusing. That is what keeps a dependency upgrade from growing a
-credential-to-identity oracle on every existing worker.
+**The protocol is not hosted until `resolve_token` is overridden** — absent,
+not hosted-and-refusing. That is what keeps a dependency upgrade from growing a
+credential-to-identity oracle on every existing worker. Only the methods whose
+hooks exist are registered, so a worker that resolves credentials but does not
+mint grants hosts `introspect_token` and not `issue_grant`.
 
 Enabling it also requires an allowlist of principals permitted to ask, via
 `--introspect-principals` or `VGI_INTROSPECT_PRINCIPALS`. There is no permissive

{vgi_python-0.32.0 → vgi_python-0.34.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vgi-python
-Version: 0.32.0
+Version: 0.34.0
 Summary: Vector Gateway Interface - Connect DuckDB to external programs via Apache Arrow
 Project-URL: Homepage, https://query.farm
 Project-URL: Repository, https://github.com/Query-farm/vgi-python
@@ -162,7 +162,7 @@ Requires-Dist: httpx2>=2.9.1
 Requires-Dist: platformdirs
 Requires-Dist: pyarrow
 Requires-Dist: typer>=0.9
-Requires-Dist: vgi-rpc>=0.45.1
+Requires-Dist: vgi-rpc>=0.46.0
 Provides-Extra: azure
 Requires-Dist: azure-identity>=1.16.0; extra == 'azure'
 Requires-Dist: pymssql>=2.3.0; extra == 'azure'

{vgi_python-0.32.0 → vgi_python-0.34.0}/PROTOCOL.md

@@ -6,6 +6,7 @@ The canonical protocol documents live in [`docs/protocol/`](docs/protocol/index.
 - [VGI Filter Encoding v2 — normative proposed specification](docs/protocol/vgi-filter-encoding-v2-spec.md)
 - [Runtime-filter artifacts — proposed optional extension](docs/protocol/vgi-runtime-filter-artifacts.md)
 - [DuckDB filter adapter — informative implementation guide](docs/protocol/vgi-duckdb-filter-adapter.md)
+- [Catalog query pushdown — proposed implementation design](docs/protocol/vgi-catalog-query-pushdown-design.md)
 - [DuckDB 2.0 protocol design/audit report — informative](docs/protocol/vgi-protocol-proposed-changes.md)
 
 The executable language-neutral conformance corpus and retargetable worker runner are in

{vgi_python-0.32.0 → vgi_python-0.34.0}/docs/api/auth.md

@@ -18,6 +18,10 @@ require `pip install vgi-python[http]`; JWT authentication additionally requires
 `principal` plus an optional `token_name`. It lives in a private `vgi-rpc` module, so `vgi.auth`
 re-exports it — a worker that implements `resolve_token` never has to name a private import path.
 
+As of vgi-rpc 0.46.0 introspection is the `vgi_rpc.Identity.v1` protocol hosted on the RPC server,
+not an HTTP JSON route, so it reaches every transport rather than only HTTP. `TokenIdentity` and
+`TokenResolver` are correspondingly no longer gated on the `[http]` extra.
+
 ## Secret protocol
 
 ::: vgi.secret_protocol

{vgi_python-0.32.0 → vgi_python-0.34.0}/docs/protocol/index.md

@@ -8,6 +8,7 @@ Each document declares its own status; “proposed” means the contract is stil
 | [VGI Filter Encoding v2](vgi-filter-encoding-v2-spec.md) | **Normative, proposed** | Engine-neutral wire format, semantics, validation, and conformance requirements for `vgi.filters.v2`. |
 | [VGI Runtime-Filter Artifacts](vgi-runtime-filter-artifacts.md) | **Normative optional extension, proposed** | Additional requirements for capability-gated advisory runtime-pruning artifacts. Base filter-v2 conformance does not require this extension. |
 | [VGI DuckDB Filter Adapter](vgi-duckdb-filter-adapter.md) | **Informative implementation guide, proposed** | DuckDB 1.5 and 2.0 mappings into the normative filter-v2 wire contract. |
+| [VGI catalog query pushdown](vgi-catalog-query-pushdown-design.md) | **Informative implementation design, proposed** | Optional read-query preparation and streaming, Python provider API, DuckDB 1.5 explicit execution, and DuckDB 2.0 automatic pushdown. |
 | [Proposed VGI protocol changes for DuckDB 2.0](vgi-protocol-proposed-changes.md) | **Informative design/audit report** | Rationale, migration inventory, implementation status, and deferred protocol decisions. It is not an implementation specification. |
 
 ## Reading order
@@ -16,6 +17,10 @@ Protocol implementers should begin with the normative [Filter Encoding v2](vgi-f
 runtime-artifact extension only when implementing one of its negotiated algorithms. Engine adapters should then use
 the relevant implementation guide without treating engine-private classes as wire types.
 
+The [catalog query pushdown design](vgi-catalog-query-pushdown-design.md) describes a separate optional
+capability for executing whole eligible read queries at a catalog provider. It is a proposal, not
+an implemented extension of the filter-v2 contract.
+
 The language-neutral filter corpus at `conformance/filter-v2/` contains structural JSON cases and executable Arrow
 IPC vectors. Its worker runner sends the portable cases through the public VGI client and can target any SDK's
 standard example worker.