BriefLoop v0.13.0 — SQLite ControlStore Sole Authority And LEGACY-DELETE Tier-1

BriefLoop v0.13.0 — SQLite ControlStore Sole Authority And LEGACY-DELETE Tier-1

v0.13.0 lands the CX cutover: the SQLite ControlStore becomes the sole runtime
authority for BriefLoop workspaces, and the first LEGACY-DELETE batch removes
the retired legacy CLI handler layer. It also carries forward the Python 3.12
floor and the explicit runtime-identity contract.

Highlights

• Makes the SQLite ControlStore the sole runtime authority. JSON-only
  workspaces are classified unsupported — there is no importer, migration,
  dual read/write, or fallback. The Codex runtime host
  (briefloop run --workspace <path> --runtime codex, followed by
  briefloop runtime next, invocation-start, invocation-accept|fail, and
  apply) is the active execution path, verified green on macOS and Windows
  without fail-fast.
• Retires the legacy JSON/operator public commands: they fail closed with
  typed rejections (runtime_command_unsupported /
  legacy_workspace_unsupported) and zero writes. Deterministic source
  acquisition executes only the initialization-frozen provider plan; mutable
  sources.yaml is never re-read after initialization.
• LEGACY-DELETE tier-1 removes the retired handler layer, six
  import-graph-unreachable modules, and three unreferenced scripts. Parser
  registrations stay so the typed rejections keep working. The legacy JSON
  runtime-state stack ships as declared internal debt tracked for
  LEGACY-DELETE-2.
• sources decide is retired by design; source discovery runs through the
  runtime-host route. Finalize, approval, and delivery run as typed Store
  actions through runtime apply.
• Moves requires-python from >=3.9 to >=3.12 and makes runtime identity
  explicit for every new run (hermes, claude, opencode, codex,
  codebuddy, or operator); historical auto / manual manifests remain
  read-only diagnostics.

Boundaries

This release adds no migration path, legacy fallback, dual authority, or
compatibility CLI for retired surfaces. The Codex runtime host is
Experimental; LAJ advisory tooling remains advisory-only with utility and
efficacy NOT MEASURED. The v1.0 RC readiness gate
(docs/v1-pilot-evidence.md) still reports not_satisfied; v1.0-ready
wording remains governed by that gate.

For the complete change list, see CHANGELOG.md.