runtime-llama 0.10.3

Improves embedding recovery correctness and reduces coordinator/planning work while retaining the Python APIs, one shared scheduler, exact token counts and numerical thresholds.

• Recovery validates each pending record against its own historical limits and the full fresh server observation. Owner-local failure preserves other callers, original result indices and actual transport drain. Native failed or ambiguous POSTs remain non-replayable.
• embedding_max_response_bytes independently bounds decoded native JSON bodies, default 8 MiB.
• embedding_preparation_cache_entries and embedding_preparation_cache_bytes configure exact-token retention, default 1,024 entries / 8 MiB. Effective bytes remain capped by pending bytes / 4; zero disables retention.
• Remembered notifications and relevant deadlines replace the fixed global 10 ms coordinator poll. Arbitrary cancellation callbacks and custom coalescing clocks retain finite checks. Planning avoids unnecessary keys, scans, rotating copies and index searches while preserving fairness, topology, cancellation, backpressure and drained close.
• The qualification probe can select and report the existing close or opt-in reuse HTTP policy. The default stays close; no fallback or retry was added.

Verification: 1,578 retained tests, Ruff check/format, 33 publication packaging tests, normalized source/wheel checks, public manifest/license audit and a clean isolated installation. All 28 runtime payload files match the live-qualified candidate byte-for-byte.

The retained live pair used both already loaded, verified EmbeddingGemma 2 BF16 replicas and unchanged thresholds. Each 511-text pipeline used 539 HTTP requests = 511 exact tokenizations + 4 embedding POSTs + 24 metadata reads. All vectors matched exactly between policies and against retained 0.10.2 outputs. Separate prepared/raw repeat calls needed zero additional tokenizations after eight initial measurements.

Pipeline wall time was 4.8449 s with close / 4.6630 s with reuse. This single pair qualifies the current plain-HTTP route functionally; it does not establish a general latency improvement. Historical 0.10.2 profile digests differ, so this is not a controlled version-speed comparison. Measurements include preparation, client/server and transport work, not pure GPU time.

The lifecycle and evidence are managed with Flower MCP. See the engineering qualification and public release record.

Install the Python wheel below. The three optional tsnet archives retain byte-identical executables and license inventory from v0.6.0; this publication adds no new native build, OS execution or VPN enrollment/inference qualification. Apache-2.0 and upstream MIT attribution are unchanged. Consumer installations, pins, services and model configurations remain unchanged. No PyPI upload is included.

RELEASE-MANIFEST.json binds source and asset provenance. Verify downloads using SHA256SUMS. Public wheel SHA-256:

73870dc4f8ab421ad9d4ff4f944888a623d57756d1372aa6c8786ad0e7b9aecb