BriefLoop v0.14.0 — Codex SQLite Runtime and Read-Only Review Surfaces

BriefLoop v0.14.0 — Codex SQLite Runtime and Read-Only Review Surfaces

BriefLoop v0.14.0 makes the current product boundary easier to see and operate:
new runs use the Experimental Codex SQLite path, initialization can use a
one-shot local web wizard, and a completed report can be exported as a
self-contained three-page read-only HTML view.

The engineering changes in this release were implemented, tested, and
iteratively repaired with Codex. Human maintainers authorized every merge, the
release tag, and the GitHub Release. Codex did not approve its own work.

What is included

• SQLite ControlStore (briefloop.db), accepted strict requests, Receipts, and
  ledger relations are the sole runtime authority for new runs.
• The packaged Codex Skill follows the Store-derived CoreRunNextAction
  protocol: delegate, deterministic, human_decision, blocked, or
  complete.
• briefloop init <workspace> --web starts a one-shot loopback wizard on the
  same strict bootstrap path as terminal initialization.
• briefloop quality html --workspace <workspace> [--open] writes a
  self-contained three-page read-only view for quality status, optional LAJ
  advisory findings, and improvement status.
• Legacy JSON control-plane modules are deleted. JSON-only workspaces have no
  importer, migration, dual-read, dual-write, or fallback path.

Legacy control files and report/status/handoff/finalize/Quality Panel exports
are non-authoritative projections. Strict action, envelope, and human-request
JSON payloads remain input carriers: the runtime revalidates them against the
Store, and the payloads are never authority by themselves.

Honest product limits

• LAJ remains Experimental and its utility is NOT MEASURED. It is an
  advisory second opinion, not a correctness, completeness, or quality proof.
• The three HTML pages and init wizard are interaction surfaces, not workflow,
  Gate, approval, delivery, or next-action authority.
• The Improvement Ledger lifecycle is unavailable in v0.14.0. The third page
  reports that state; there is no automatic learning or accepted-suggestion
  effect on a later run.
• package_ready is not delivered. Human approval and delivery remain
  explicit recorded actions.

Breaking changes

• fix!: retire the eval-cases command.
• fix!: retire the experiments 080 command family.
• fix!: retire the D1 fold-in keys guidance_manifestation and
  support_wording.
• fix!: retire the Improvement Ledger / Memory file lifecycle; the event
  vocabulary remains available for compatibility and audit classification.
• fix!: make the Quality Panel semantic_support section consistently
  not_available until a Store-native producer exists.
• fix!: retire the v1-RC readiness gate whose runner depended on the
  deleted legacy stack.

Start the Codex path

briefloop init ./my-brief --demo --force
briefloop runtime install --workspace ./my-brief --runtime codex
briefloop run --workspace ./my-brief --runtime codex

Open and trust the workspace in Codex, then follow the installed BriefLoop
Skill. The Skill only executes the exact current Store-derived action and never
falls back to a legacy JSON workspace, operator, or another runtime.

To try the new read-only surfaces:

briefloop init ./my-brief --web
briefloop quality html --workspace ./my-brief --open

The web wizard binds only to loopback. The HTML export contains no action or
write endpoint.