jevkit-runtime 0.1.0__tar.gz

jevkit_runtime-0.1.0/.github/workflows/downstream.yml

@@ -0,0 +1,39 @@
+name: downstream compatibility
+on:
+  pull_request:
+  push:
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      consumer-ref:
+        description: Branch or tag available in all five migrated consumer repos
+        required: false
+        default: main
+        type: string
+permissions:
+  contents: read
+jobs:
+  consumers:
+    # Enabled after all five migration PRs land; manual runs remain available.
+    if: vars.JEVKIT_CONSUMERS_READY == 'true' || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        tool: [jgrep, jsort, jlink, jselect, jcol]
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          path: jevkit-core
+      - uses: actions/checkout@v4
+        with:
+          repository: keltokhy/${{ matrix.tool }}
+          ref: ${{ inputs.consumer-ref || 'main' }}
+          path: ${{ matrix.tool }}
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+      - run: python jevkit-core/scripts/dev.py --tool ${{ matrix.tool }} setup
+      - run: python jevkit-core/scripts/dev.py --tool ${{ matrix.tool }} check
+      - run: python jevkit-core/scripts/dev.py --tool ${{ matrix.tool }} wheel-check

jevkit_runtime-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,33 @@
+name: publish
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Verified release tag to publish to PyPI
+        required: true
+        default: v0.1.0
+        type: string
+jobs:
+  pypi:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.tag }}
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+      - name: Verify the selected tag matches the package version
+        env:
+          RELEASE_TAG: ${{ inputs.tag }}
+        run: test "$RELEASE_TAG" = "v$(uv version --short)"
+      - run: uv sync --locked
+      - run: uv run ruff check src tests scripts
+      - run: uv run ruff format --check src tests scripts
+      - run: uv run pytest -q
+      - run: uv build --no-sources
+      - run: uv publish --trusted-publishing always

jevkit_runtime-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,18 @@
+name: test
+on: [push, pull_request]
+permissions:
+  contents: read
+jobs:
+  core:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.10", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --locked --python ${{ matrix.python }}
+      - run: uv run ruff check src tests scripts
+      - run: uv run ruff format --check src tests scripts
+      - run: uv run pytest -q
+      - run: uv build --no-sources

jevkit_runtime-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+dist/
+.DS_Store
+.venv-*/
+.checks/

jevkit_runtime-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Khaled Eltokhy
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

jevkit_runtime-0.1.0/PKG-INFO

@@ -0,0 +1,179 @@
+Metadata-Version: 2.5
+Name: jevkit-runtime
+Version: 0.1.0
+Summary: Shared transport, configuration, caching, and accounting for JevKit tools
+Project-URL: Homepage, https://github.com/keltokhy/jevkit-core
+Project-URL: Issues, https://github.com/keltokhy/jevkit-core/issues
+Author: Khaled Eltokhy
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Provides-Extra: http2
+Requires-Dist: httpx[http2]>=0.27; extra == 'http2'
+Description-Content-Type: text/markdown
+
+# JevKit core
+
+Distribution: **`jevkit-runtime`**. Python import: **`jevkit_core`**.
+The PyPI name `jevkit-core` belongs to a different project.
+
+Shared provider definitions, backend configuration, HTTP transport, retries, deadlines,
+SQLite answer storage, in-flight requests, usage accounting, and answer provenance
+for jgrep, jsort, jlink, jselect, and jcol.
+
+Each product remains a separate repository and package. This core imports none of them.
+Product adapters retain prompts, cache identities, reuse policies, budget policies, and public APIs.
+
+Version 0.1.0 is a **local development release**, not a published PyPI release.
+Ordinary source edits in an editable core installation apply on the next run;
+already-running Python processes need to restart.
+
+## Development
+
+Keep the six checkouts as siblings. Each consumer declares a normal versioned
+dependency on `jevkit-runtime` and a uv development override:
+
+```toml
+[tool.uv.sources]
+jevkit-runtime = { path = "../jevkit-core", editable = true }
+```
+
+Clone `keltokhy/jevkit-core` beside `keltokhy/jgrep`, `keltokhy/jsort`,
+`keltokhy/jlink`, `keltokhy/jselect`, and `keltokhy/jcol`. All six repositories
+remain independently versioned. For isolated development checkouts named
+`jgrep-jevkit` and so on, use the `--suffix=-jevkit` option shown below.
+
+From this directory:
+
+```bash
+python3 scripts/dev.py --suffix=-jevkit setup
+python3 scripts/dev.py --suffix=-jevkit check
+python3 scripts/dev.py --suffix=-jevkit wheel-check
+python3 scripts/dev.py --suffix=-jevkit run jgrep -- --help
+```
+
+`run` uses the selected worktree's virtual environment and preserves the caller's
+working directory. To use it with data, replace `--help` with the normal tool arguments.
+For ordinary unsuffixed clones, omit `--suffix`. `--repos-root` selects their parent;
+`--tool jgrep` limits setup and checks to one consumer.
+
+`setup` installs dependencies and prepares the public tiktoken encoding files needed
+by jselect. It performs no model inference. `check` runs each suite in its own
+environment, strips model credentials, isolates configuration/cache directories,
+and blocks outbound sockets while permitting local fake HTTP servers. It also proves
+that every consumer calls the shared transport and imports this exact source tree,
+and compares its fixture behavior to the commits in `consumer-baselines.json`.
+Those commits must be present locally; use a full clone or fetch that history.
+
+`wheel-check` builds the core and consumer wheels, installs each consumer alongside
+the core wheel in a separate temporary environment, and exercises model fixtures and
+CLI entry points outside the source trees. It also checks packaged browser/review assets
+and jcol's installed process workflow. Dependency installation may use the package index;
+inference checks stay offline.
+
+## Shared boundary
+
+| Module | Responsibility |
+|---|---|
+| `backends.py` | Provider catalog, credential/configuration lookup, capabilities, selection |
+| `transport.py` | HTTP requests, total deadlines, retries, JSON/error handling |
+| `client.py` | Client lifecycle, shared in-flight requests, transport delegation, common answer validation |
+| `cache.py` | SQLite answer storage and atomic provenance writes, key serialization |
+| `usage.py` | Usage validation, reported/estimated costs, meter and report accumulation |
+| `provenance.py` | Versioned answer origins with literal or unknown responder identity |
+| `errors.py` | Shared failure types and structured request exhaustion |
+
+`DecisionClient` is an adapter base, not a complete standalone scoring SDK. Product
+adapters supply their own `ask` and `_record` contracts. jselect calls the shared
+transport directly while retaining its relevance batching, score cache, and statistics.
+Tool-specific meter fields remain in small subclasses.
+
+`backend_catalog` selects provider definitions in each tool's priority order and
+accepts model overrides. The four decision clients retain moving model aliases;
+jselect keeps its pinned defaults. The catalog also defines two opt-in local providers; tools choose whether to expose them. Adding a catalog entry does not automatically enable it in every tool.
+
+`DecisionClient.share_request` returns a task and an ownership flag. It invokes a
+lazy request factory only for the owner, allowing jlink's cache-only callers to
+join existing requests and jsort to charge only the initiating caller. It removes
+finished, failed, and cancelled tasks from the registry. Awaiting, cancellation,
+cache identity, and jcol's hedging policy remain with the adapters; sharing does
+not introduce cancellation shielding or change how a hedge is charged.
+
+`Meter.record` and `record_usage` accumulate the same call/token/cost fields for
+the four clients and jselect's dictionary reports. Meter callbacks run after
+totals change and before latency/model updates. Cost-source labels, jsort's
+maximum call cost, jlink's provenance summaries, and model fallback remain local.
+`answer_provenance` constructs the shared version-1 metadata for jsort and jlink;
+missing responder identity stays unknown rather than inheriting a requested alias.
+
+No product imports another product, and the core imports none of them. NumPy,
+pandas, SciPy, Polars, tokenizers, and browser dependencies stay in their owning
+tools. HTTP/2 is an optional core extra used by jcol.
+
+## Compatibility
+
+- Existing prompts, CLI flags, supported backend choices, cache-key bytes, and
+  saved project/scale/index formats are retained by the adapters.
+- Existing `~/.config/jev` and cache locations continue to work. No user cache or
+  credential files were opened or migrated during development.
+- Legacy answer keys remain explicitly tool-owned. The shared `answer_key` function
+  offers an opt-in, versioned provider/endpoint identity for future consumers; it
+  never falls back to an ambiguous legacy entry. In particular, jlink's existing
+  cross-backend cache behavior has not silently changed.
+- jcol checkpoints and jselect's score cache remain separate from shared answer storage.
+- Budget meanings remain local: zero is unlimited for jgrep/jsort, cache-only for
+  jlink, and rejected by jselect's semantic scorer. jcol retains its scheduler policy.
+- The separate experimental jgrep branch retains joint-read caching and keyless
+  local backends. The main-branch migration exposes its original three providers;
+  unrelated experiments and benchmark graphics are not part of that migration.
+- All clients now use a true total HTTP deadline. jlink and jcol previously passed
+  the remaining time only to httpx's individual network waits.
+- All five use validated usage parsing. Malformed, negative, nonfinite, or boolean
+  usage values fail rather than corrupting accounting; jselect retains its
+  fractional-token and missing-token estimate policy.
+
+These last two points are deliberate hardening accompanying the extraction.
+The adapter tests remain the source of truth for each tool's external behavior.
+
+## Cross-repository validation
+
+```bash
+python3 scripts/dev.py --suffix=-jevkit check
+```
+
+For a before/after request, result, and metering comparison, use a consumer's
+environment with `scripts/probe_consumer.py TOOL --baseline-repo PATH --baseline-ref COMMIT`.
+The probe covers cold/warm caches, repeated requests, in-flight sharing, typed
+jcol answers, and provider definitions/defaults. It verifies shared accounting
+for all five, request sharing for the four decision clients, and provenance
+construction for jsort/jlink. It is a focused compatibility fixture, not an
+exhaustive equivalence proof.
+
+The core CI tests Python 3.10 and 3.13. The downstream workflow tests the exact
+core revision against all five consumer main branches in separate jobs, including
+wheel installs. Pull-request and main-push runs are enabled with the repository
+variable `JEVKIT_CONSUMERS_READY=true` after bootstrap. Manual dispatch can select
+a common consumer branch/tag before then. All five consumer repositories are public.
+
+## Release sequence
+
+The five packages retain independent releases. Their wheels contain a dependency
+on `jevkit-runtime>=0.1.0,<0.2.0`, never a local source path; jcol requests the `http2` extra.
+
+Before publishing any migrated consumer to PyPI:
+
+1. Merge and tag the verified core as `v0.1.0`. Consumer CI checks out this tag
+   beside its own source, so tests do not depend on PyPI publication timing.
+2. Configure a PyPI Trusted Publisher for `jevkit-runtime`, repository
+   `keltokhy/jevkit-core`, workflow `publish.yml`, environment `pypi`. Dispatch the
+   publish workflow with the verified release tag. Publishing is explicit; creating
+   a Git tag alone does not upload a package.
+3. Release each consumer through its existing versioning/publishing process. Update
+   its supported core range, lockfile, and CI core reference together on upgrades.
+
+Until the runtime distribution is available on PyPI, source development uses the
+sibling checkout. The cross-repository wheel checks install a freshly built core
+wheel explicitly alongside each consumer. Existing published tool versions remain
+independent of this migration. Once the runtime is published, standalone source
+clones can use `uv sync --no-sources`; published wheels use ordinary dependencies.

jevkit_runtime-0.1.0/README.md

@@ -0,0 +1,164 @@
+# JevKit core
+
+Distribution: **`jevkit-runtime`**. Python import: **`jevkit_core`**.
+The PyPI name `jevkit-core` belongs to a different project.
+
+Shared provider definitions, backend configuration, HTTP transport, retries, deadlines,
+SQLite answer storage, in-flight requests, usage accounting, and answer provenance
+for jgrep, jsort, jlink, jselect, and jcol.
+
+Each product remains a separate repository and package. This core imports none of them.
+Product adapters retain prompts, cache identities, reuse policies, budget policies, and public APIs.
+
+Version 0.1.0 is a **local development release**, not a published PyPI release.
+Ordinary source edits in an editable core installation apply on the next run;
+already-running Python processes need to restart.
+
+## Development
+
+Keep the six checkouts as siblings. Each consumer declares a normal versioned
+dependency on `jevkit-runtime` and a uv development override:
+
+```toml
+[tool.uv.sources]
+jevkit-runtime = { path = "../jevkit-core", editable = true }
+```
+
+Clone `keltokhy/jevkit-core` beside `keltokhy/jgrep`, `keltokhy/jsort`,
+`keltokhy/jlink`, `keltokhy/jselect`, and `keltokhy/jcol`. All six repositories
+remain independently versioned. For isolated development checkouts named
+`jgrep-jevkit` and so on, use the `--suffix=-jevkit` option shown below.
+
+From this directory:
+
+```bash
+python3 scripts/dev.py --suffix=-jevkit setup
+python3 scripts/dev.py --suffix=-jevkit check
+python3 scripts/dev.py --suffix=-jevkit wheel-check
+python3 scripts/dev.py --suffix=-jevkit run jgrep -- --help
+```
+
+`run` uses the selected worktree's virtual environment and preserves the caller's
+working directory. To use it with data, replace `--help` with the normal tool arguments.
+For ordinary unsuffixed clones, omit `--suffix`. `--repos-root` selects their parent;
+`--tool jgrep` limits setup and checks to one consumer.
+
+`setup` installs dependencies and prepares the public tiktoken encoding files needed
+by jselect. It performs no model inference. `check` runs each suite in its own
+environment, strips model credentials, isolates configuration/cache directories,
+and blocks outbound sockets while permitting local fake HTTP servers. It also proves
+that every consumer calls the shared transport and imports this exact source tree,
+and compares its fixture behavior to the commits in `consumer-baselines.json`.
+Those commits must be present locally; use a full clone or fetch that history.
+
+`wheel-check` builds the core and consumer wheels, installs each consumer alongside
+the core wheel in a separate temporary environment, and exercises model fixtures and
+CLI entry points outside the source trees. It also checks packaged browser/review assets
+and jcol's installed process workflow. Dependency installation may use the package index;
+inference checks stay offline.
+
+## Shared boundary
+
+| Module | Responsibility |
+|---|---|
+| `backends.py` | Provider catalog, credential/configuration lookup, capabilities, selection |
+| `transport.py` | HTTP requests, total deadlines, retries, JSON/error handling |
+| `client.py` | Client lifecycle, shared in-flight requests, transport delegation, common answer validation |
+| `cache.py` | SQLite answer storage and atomic provenance writes, key serialization |
+| `usage.py` | Usage validation, reported/estimated costs, meter and report accumulation |
+| `provenance.py` | Versioned answer origins with literal or unknown responder identity |
+| `errors.py` | Shared failure types and structured request exhaustion |
+
+`DecisionClient` is an adapter base, not a complete standalone scoring SDK. Product
+adapters supply their own `ask` and `_record` contracts. jselect calls the shared
+transport directly while retaining its relevance batching, score cache, and statistics.
+Tool-specific meter fields remain in small subclasses.
+
+`backend_catalog` selects provider definitions in each tool's priority order and
+accepts model overrides. The four decision clients retain moving model aliases;
+jselect keeps its pinned defaults. The catalog also defines two opt-in local providers; tools choose whether to expose them. Adding a catalog entry does not automatically enable it in every tool.
+
+`DecisionClient.share_request` returns a task and an ownership flag. It invokes a
+lazy request factory only for the owner, allowing jlink's cache-only callers to
+join existing requests and jsort to charge only the initiating caller. It removes
+finished, failed, and cancelled tasks from the registry. Awaiting, cancellation,
+cache identity, and jcol's hedging policy remain with the adapters; sharing does
+not introduce cancellation shielding or change how a hedge is charged.
+
+`Meter.record` and `record_usage` accumulate the same call/token/cost fields for
+the four clients and jselect's dictionary reports. Meter callbacks run after
+totals change and before latency/model updates. Cost-source labels, jsort's
+maximum call cost, jlink's provenance summaries, and model fallback remain local.
+`answer_provenance` constructs the shared version-1 metadata for jsort and jlink;
+missing responder identity stays unknown rather than inheriting a requested alias.
+
+No product imports another product, and the core imports none of them. NumPy,
+pandas, SciPy, Polars, tokenizers, and browser dependencies stay in their owning
+tools. HTTP/2 is an optional core extra used by jcol.
+
+## Compatibility
+
+- Existing prompts, CLI flags, supported backend choices, cache-key bytes, and
+  saved project/scale/index formats are retained by the adapters.
+- Existing `~/.config/jev` and cache locations continue to work. No user cache or
+  credential files were opened or migrated during development.
+- Legacy answer keys remain explicitly tool-owned. The shared `answer_key` function
+  offers an opt-in, versioned provider/endpoint identity for future consumers; it
+  never falls back to an ambiguous legacy entry. In particular, jlink's existing
+  cross-backend cache behavior has not silently changed.
+- jcol checkpoints and jselect's score cache remain separate from shared answer storage.
+- Budget meanings remain local: zero is unlimited for jgrep/jsort, cache-only for
+  jlink, and rejected by jselect's semantic scorer. jcol retains its scheduler policy.
+- The separate experimental jgrep branch retains joint-read caching and keyless
+  local backends. The main-branch migration exposes its original three providers;
+  unrelated experiments and benchmark graphics are not part of that migration.
+- All clients now use a true total HTTP deadline. jlink and jcol previously passed
+  the remaining time only to httpx's individual network waits.
+- All five use validated usage parsing. Malformed, negative, nonfinite, or boolean
+  usage values fail rather than corrupting accounting; jselect retains its
+  fractional-token and missing-token estimate policy.
+
+These last two points are deliberate hardening accompanying the extraction.
+The adapter tests remain the source of truth for each tool's external behavior.
+
+## Cross-repository validation
+
+```bash
+python3 scripts/dev.py --suffix=-jevkit check
+```
+
+For a before/after request, result, and metering comparison, use a consumer's
+environment with `scripts/probe_consumer.py TOOL --baseline-repo PATH --baseline-ref COMMIT`.
+The probe covers cold/warm caches, repeated requests, in-flight sharing, typed
+jcol answers, and provider definitions/defaults. It verifies shared accounting
+for all five, request sharing for the four decision clients, and provenance
+construction for jsort/jlink. It is a focused compatibility fixture, not an
+exhaustive equivalence proof.
+
+The core CI tests Python 3.10 and 3.13. The downstream workflow tests the exact
+core revision against all five consumer main branches in separate jobs, including
+wheel installs. Pull-request and main-push runs are enabled with the repository
+variable `JEVKIT_CONSUMERS_READY=true` after bootstrap. Manual dispatch can select
+a common consumer branch/tag before then. All five consumer repositories are public.
+
+## Release sequence
+
+The five packages retain independent releases. Their wheels contain a dependency
+on `jevkit-runtime>=0.1.0,<0.2.0`, never a local source path; jcol requests the `http2` extra.
+
+Before publishing any migrated consumer to PyPI:
+
+1. Merge and tag the verified core as `v0.1.0`. Consumer CI checks out this tag
+   beside its own source, so tests do not depend on PyPI publication timing.
+2. Configure a PyPI Trusted Publisher for `jevkit-runtime`, repository
+   `keltokhy/jevkit-core`, workflow `publish.yml`, environment `pypi`. Dispatch the
+   publish workflow with the verified release tag. Publishing is explicit; creating
+   a Git tag alone does not upload a package.
+3. Release each consumer through its existing versioning/publishing process. Update
+   its supported core range, lockfile, and CI core reference together on upgrades.
+
+Until the runtime distribution is available on PyPI, source development uses the
+sibling checkout. The cross-repository wheel checks install a freshly built core
+wheel explicitly alongside each consumer. Existing published tool versions remain
+independent of this migration. Once the runtime is published, standalone source
+clones can use `uv sync --no-sources`; published wheels use ordinary dependencies.

jevkit_runtime-0.1.0/TESTING.md

@@ -0,0 +1,95 @@
+# Validation record — 2026-09-22
+
+The five source baselines are recorded in `consumer-baselines.json`. Bootstrap
+fetches verified current remote main branches. No model inference was performed. Tests used mock
+transports or local HTTP fixtures with outbound sockets blocked and model
+credentials removed. Dependency installation and public tokenizer preparation
+are separate from those inference-free checks.
+
+| Package | Interpreter | Result |
+|---|---|---|
+| jevkit-core | Python 3.13.15 | 44 passed |
+| jevkit-core | Python 3.10.21 | 44 passed |
+| jgrep | Python 3.12.14 | 282 passed |
+| jsort | Python 3.13.15 | 159 passed |
+| jlink | Python 3.12.14 | 720 passed |
+| jselect | Python 3.13.15 | 164 passed |
+| jcol | Python 3.12.14 | 138 passed, 3 existing warnings |
+
+The consumer total for the main-branch migrations is 1,463. All existing consumer test files were retained
+without modifying their assertions. The core now includes 17 additional tests
+for provider selection/model overrides, accounting callback order, unknown-model
+provenance, single-owner charges, cache-only sharing, task isolation, and cleanup
+after success, failure, or cancellation. All five baselines were also tested before
+the extraction; jselect's first attempt had an incorrect tokenizer-cache path,
+then passed all 164 tests after pointing to the existing local cache. The first
+migrated jselect run exposed a timeout error-message regression, fixed in the
+adapter without changing its test.
+
+Additional checks:
+
+- All five import `/Volumes/K3/GitHub/jevkit-core/src/jevkit_core` from their separate
+  editable development environments. Instrumentation verifies that each actually
+  calls the shared transport.
+- All five match their original Git versions on the focused request/result/metering
+  probe: raw request bodies, responses, warm-cache reuse, common counters, and
+  effective provider definitions/defaults. The provider comparison normalizes
+  capability fields that were implicit in older adapters.
+  The four client adapters also exercise in-flight request sharing; jcol includes
+  binary, categorical, and scale answers. This is bounded fixture evidence, not
+  exhaustive equivalence across every input.
+- Instrumentation verifies that all five use shared usage accumulation, the four
+  decision clients use shared in-flight request handling, and jsort/jlink construct
+  answer provenance through the core. jselect keeps its relevance batching and
+  separate score-cache behavior. Existing tests retain coverage for jsort's charge
+  attribution, jlink's cache-only sharing, and jcol's hedging.
+- Fresh core and consumer wheels install in five independent temporary environments
+  outside source checkouts. Every installed CLI reports its version and every
+  installed consumer uses the wheel's core, not the editable checkout.
+- jlink review HTML/JS/CSS and jcol's browser HTML are present in the installed wheels.
+- The installed jcol process checks pass for pipes, partial completion/resume,
+  offline export, Parquet stdin, and SIGINT recovery.
+- Core and jselect lint/format checks pass. All modified GitHub workflow YAML parses;
+  all repository diffs pass whitespace checks. Hosted CI has not been run.
+
+Reproduce the suite from the core checkout:
+
+```bash
+python3 scripts/dev.py --suffix=-jevkit setup
+python3 scripts/dev.py --suffix=-jevkit check
+python3 scripts/dev.py --suffix=-jevkit wheel-check
+```
+
+Current logs are retained in `/Volumes/K3/agent-working-space/jevkit/`:
+`core-followup-check.log`, `core-followup-wheels.log`, and
+`core-followup-py310.log`. The initial extraction logs and two preliminary
+provider-comparison runs are preserved separately. Those preliminary comparisons
+needed normalization of implicit legacy capability fields; consumer behavior did
+not require a correction. These logs are development artifacts, not package contents.
+
+Release boundary: this validates the local development implementation and locally
+built packages. It does not establish live model quality, hosted CI status, or
+publication. The core remote/tag/package must be published before migrated consumer
+CI and public releases can resolve their pinned core dependency.
+
+
+## GitHub bootstrap
+
+The distribution is named `jevkit-runtime`: the PyPI project `jevkit-core` belongs
+to another developer. The repository remains `keltokhy/jevkit-core`, and Python
+imports remain `jevkit_core`. The five source overrides and lockfiles use the new
+distribution name. Wheel checks install the freshly built runtime explicitly.
+
+The jgrep PR is based on main (`7b2c867`), excluding the separate experimental
+backend and benchmark commits used in the first local exploration. Its 282-test main-branch suite passes; the earlier local 299-test run covered
+that experimental branch. The other four baselines are unchanged.
+
+All six repositories are public, so the hosted downstream matrix can check out
+all five consumers without extra repository credentials. The matrix is gated by
+`JEVKIT_CONSUMERS_READY` during the initial six-PR bootstrap, then enabled for
+future core pull requests and pushes. PyPI publishing is manually dispatched after
+Trusted Publishing is configured; Git tags alone do not publish a distribution.
+
+Bootstrap logs: `publish-setup.log`, `publish-check.log`, and `publish-wheels.log`
+in the same local report directory. The source-only jgrep migration, distribution
+rename, and installed wheel paths are verified again before merging.

jevkit_runtime-0.1.0/consumer-baselines.json

@@ -0,0 +1,7 @@
+{
+  "jgrep": "7b2c86752a1b5d1ec0a250069bb4bce8f98a30f6",
+  "jsort": "4fa1e5e6d68543f24e7c1f390fd7167612b2f6c2",
+  "jlink": "3cce3e3446e90b7407bf8b6cf8023e2fedac8c03",
+  "jselect": "5bad1145c5c4a7f05b201d7d15e23e6608caa588",
+  "jcol": "7d2b9892342e90fbd8745487e378df294d6096f8"
+}

jevkit_runtime-0.1.0/pyproject.toml

@@ -0,0 +1,39 @@
+[project]
+name = "jevkit-runtime"
+version = "0.1.0"
+description = "Shared transport, configuration, caching, and accounting for JevKit tools"
+readme = "README.md"
+license = "MIT"
+authors = [{ name = "Khaled Eltokhy" }]
+requires-python = ">=3.10"
+dependencies = ["httpx>=0.27"]
+
+[project.urls]
+Homepage = "https://github.com/keltokhy/jevkit-core"
+Issues = "https://github.com/keltokhy/jevkit-core/issues"
+
+[project.optional-dependencies]
+http2 = ["httpx[http2]>=0.27"]
+
+[dependency-groups]
+dev = ["pytest>=8", "ruff>=0.11"]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/jevkit_core"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.uv.workspace]
+members = []
+
+[tool.ruff]
+line-length = 110
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B"]