runtime-llama 0.10.1

Corrects persistent embedding batching so compatible records accumulate across source windows and callers for each verified replica. Small delivery windows no longer reduce the configured per-replica HTTP target. One scheduler still controls global and replica admission.

• Preparation and capacity events fill batches with the default embedding_batch_wait_sec=0.0; no fill timer is required. Finite tails and resource pressure ensure progress.
• Shared POSTs preserve owner indices, typed errors, cancellation/deadlines, backpressure and actual drained closure. Stopping one owner preserves survivors. Backend/transport failure affects all participants of that POST; native failed or ambiguous requests are never replayed.
• Fixes cleanup of an owner's unsent backlog after worker-side failure. Preparation admission retires independently of retained HTTP and result ownership.
• Public sync/async signatures and configurable total-text batch_size remain unchanged. Input context, aggregate HTTP token budgets and native computation batch sizes remain distinct.

Verification: 1,401 tests passed, Ruff check/format, normalized wheel/source audit and clean public-wheel install. Bounded functional qualification used both already loaded content-verified EmbeddingGemma 2 BF16 replicas: 511 texts in eight windows became four mixed-window POSTs (128/128/127/128), with two active embedding requests, one per alias, and zero coalescing delay. Exact preparation, ordered outputs and unchanged numerical thresholds passed. No model, server or consumer changes were made.

No 0.9.0 comparison or throughput improvement claim is included because an LLM workload remained permitted. Reported wall measurements include client, network, runtime and instrumentation; they are not pure GPU timings. Consumer acceptance remains separate.

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

Install the Python wheel below. The three optional tsnet archives reuse byte-identical executables and licenses from v0.6.0 (also shipped in v0.7.0 and v0.10.0); this release adds no new OS or VPN execution qualification. Apache-2.0 and upstream MIT attribution remain unchanged.

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

f36527cee8002263e346eb9f6dc7fb83d69b7209ca5efa60f64eda0a12937ae3