Questlock v0.10.0

Questlock 0.10.0 — plug it into your Go app

Experimental release, published and verified. Four native archives, two macOS
MCPB bundles, checksums and both Linux container architectures passed their gates.
Validation records the exact source and anonymous asset checks.
Immutable archives retain their source-era candidate wording. Existing broker
and inference APIs remain; execution wires the pieces together for Go apps.

• One process-local coordinator combines bounded admission, shared task/result
  reuse and optional content-free Langfuse export. Telemetry failure leaves the
  task result alone.
• Optional shared scope/UTC-day input, output and total token quotas reserve
  declared task caps before generation, settle known usage and retain unknown
  reservations. Existing per-call/day dollar controls stay separate.
• Strict task JSON loading and declarative examples cover local Ollama, pinned
  standalone SGLang, resource settings and explicit cost/token budgets.
• CPU-only runtimes use the same API. Device execution, GPU batching and KV
  storage stay with the inference engine. Router-backed serving still needs a
  qualified provider contract.

Live local validation now covers fresh generation and exact reuse through the
published Go example: 57 input + 20 output tokens once, then 0 new tokens and
no second generation. The quota settled correctly with paid fallback disabled
and $0 provider API spend. Pressure had returned to normal; admission defaults
were unchanged. Evidence and limits.

Read the Go guide, complete example
and measured overhead and reuse.
Resource admission is per process; quota accounting coordinates trusted workers
using one broker scope and matching policy. It does not meter outside calls or
turn the broker into a GPU scheduler. Provider-token cost and hardware cost are
separate; synthetic control-plane tests are not GPU or model-quality benchmarks.