Questlock 0.6.0 — checked revisions without new generation

Questlock 0.6.0 — checked edits without another generation

Published experimental release.
Release and downloads ·
Verified artifacts and installed-worker evidence

Published v0.5.0 and older releases/assets remain available unchanged. Four native
archives, both container architectures and the installed v0.6.0 worker are verified.
The immutable archives retain their source-era candidate wording; these web docs
record subsequent publication without replacing those assets.

New in 0.6.0

• A Go revision library and revise plan, run, and quest commands apply
  exact counted literal replacements to a SHA-256-pinned source. Required
  source/output checks bound what can be returned; no model is called.
• Immutable content-addressed results compose with the existing scoped broker
  and exact parent key/version/digest provenance. Failed source/count/checks and
  uncertain publication withhold text without a paid or local model fallback.
• questlock_revise shares the bounded MCP workspace, admission and cancellation
  boundary with questlock_delegate; neither gains a filesystem-edit tool.
• Opt-in revision accounting records known zero new usage/provider charge with
  deterministic_edit or exact-repeat reuse_zero. Human acceptance remains
  explicit. Revision outcome cohorts require v0.6.0+ readers/writers; keep them
  separate from older generation cohorts during upgrades.
• Three simple and three complex offline scenarios, complete JSON examples,
  editable architecture, and Codex/Claude skill guidance for preferring exact
  edits before new generation.

Read what, why and how, runnable examples,
and release evidence.
A formatting development run and exact repeat made zero new model calls; their
single observed latencies establish no benchmark or whole-session savings.
New facts, open-ended rewrites and reasoning changes still need reviewed tasks.

Go vet/race, packaging/public-source checks, all five offline quests, native
Darwin/Linux ARM64/AMD64 archive CI, source-container execution and disposable
Langfuse readback passed before publication. Anonymous registry verification
checked both image configs and all layers. Published binary/skills activation
used an independent rollback watchdog and a private complete known-good backup;
a fresh native MCP process discovered both tools and returned a checked exact
revision reuse with zero new generation. Installation changed no client settings.
The development workstation separately completed its guarded global local-Codex
instruction rollout; supported opt-in setup
is documented. This preference is not enabled by the library installer. Broader
local comparison evidence now records all six deterministic edits and repeats
passing with zero generation, alongside one passing local-model baseline and
five withheld failures. See the validation record for all measured usage, the
single passing timing pair and the comparison's limits.