loop-engineer 0.8.0__tar.gz → 0.9.0__tar.gz

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/.claude-plugin/plugin.json

@@ -1,11 +1,25 @@
 {
   "name": "loop-engineer",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Design, launch, verify, repair, and improve agent loops. A Claude-Code-native architect+operator for long-running, verifiable, self-improving agentic-coding systems.",
-  "author": { "name": "Sollan Systems", "url": "https://github.com/SollanSystems" },
+  "author": {
+    "name": "Sollan Systems",
+    "url": "https://github.com/SollanSystems"
+  },
   "homepage": "https://github.com/SollanSystems/loop-engineer",
   "repository": "https://github.com/SollanSystems/loop-engineer",
-  "keywords": ["agent", "loop", "agentic", "verification", "harness", "orchestration", "self-improvement", "claude-code", "eval", "repair"],
+  "keywords": [
+    "agent",
+    "loop",
+    "agentic",
+    "verification",
+    "harness",
+    "orchestration",
+    "self-improvement",
+    "claude-code",
+    "eval",
+    "repair"
+  ],
   "license": "MIT",
   "hooks": {
     "Stop": [

loop_engineer-0.9.0/.github/dependabot.yml

@@ -0,0 +1,16 @@
+version: 2
+updates:
+  # Covers .github/workflows/*.yml and the root composite action.yml.
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      actions:
+        patterns: ["*"]
+
+  # Runtime is stdlib-only; this watches the optional extras and any future pins.
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/.github/workflows/ci.yml

@@ -5,6 +5,9 @@ on:
     branches: [main]
   pull_request:
 
+permissions:
+  contents: read
+
 jobs:
   gates:
     name: gates (py${{ matrix.python-version }})
@@ -14,14 +17,14 @@ jobs:
       matrix:
         python-version: ["3.10", "3.11", "3.12"]
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v6
         with:
           python-version: ${{ matrix.python-version }}
 
       - name: Install gate dependencies
-        run: python -m pip install --upgrade pip pyyaml pytest jsonschema
+        run: python -m pip install --upgrade pip pyyaml pytest jsonschema hypothesis
 
       - name: Frontmatter gate
         run: python -B scripts/validate_frontmatter.py
@@ -45,15 +48,27 @@ jobs:
 
       - name: Quickstart smoke test
         run: |
-          python -B -m loop doctor examples/coverage-repair
+          python -B -m loop doctor --mode release examples/coverage-repair
           python -B -m loop inspect examples/coverage-repair
 
+      - name: Plan lint smoke test
+        run: |
+          python -B -m loop plan-lint --mode release examples/plans/coverage-repair.plan.json
+          if python -B -m loop plan-lint --mode release examples/plans/invalid/cyclic-dependency.plan.json; then
+            echo "::error::cyclic-dependency.plan.json unexpectedly passed plan-lint"
+            exit 1
+          fi
+          if python -B -m loop plan-lint --mode release examples/plans/invalid/missing-goal.plan.json; then
+            echo "::error::missing-goal.plan.json unexpectedly passed plan-lint"
+            exit 1
+          fi
+
   recipe-langgraph:
     name: recipe (langgraph)
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v6
         with:
           python-version: "3.12"
       - name: Install recipe dependencies
@@ -65,8 +80,8 @@ jobs:
     name: recipe (temporal)
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v6
         with:
           python-version: "3.12"
       - name: Install recipe dependencies
@@ -81,7 +96,7 @@ jobs:
     name: action (dogfood on flagship example)
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
       # The repo root's live .loop/ is gitignored, so it does not exist in a fresh
       # CI checkout — the tracked flagship example is the contract the action gates
       # (doctor-clean, inspect 90/strong in the action's dependency-free install).

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/.github/workflows/publish.yml

@@ -4,13 +4,16 @@ on:
   push:
     tags: ["v*"]
 
+permissions:
+  contents: read
+
 jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v6
         with:
           python-version: "3.12"
 
@@ -38,7 +41,7 @@ jobs:
           /tmp/smoke/bin/loop doctor /tmp/smoke-loop
           /tmp/smoke/bin/loop inspect /tmp/smoke-loop || true
 
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/
@@ -50,7 +53,7 @@ jobs:
     permissions:
       id-token: write
     steps:
-      - uses: actions/download-artifact@v4
+      - uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/.gitignore

@@ -1,19 +1,20 @@
-# Ephemeral workbench
-.tmp/
+# Ephemeral workbench (root-anchored: examples/*-run fixtures may legitimately
+# contain same-named dirs — .claude/, .taskmaster/, memory/ — that MUST track)
+/.tmp/
 
 # Loop run telemetry (operating-contract state for the self-improvement run; not plugin content)
-.loop/
+/.loop/
 
 # Machine-local Claude Code config + GSD audit telemetry (not plugin content)
-.claude/
-.gsd/
+/.claude/
+/.gsd/
 
 # Local session memory / private build narrative (not plugin content)
-memory/
+/memory/
 
 # Workbench dirs (review scratch + roadmap drafts; not plugin content)
-review/
-roadmap/
+/review/
+/roadmap/
 
 # Python
 __pycache__/

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/CHANGELOG.md

@@ -14,6 +14,68 @@ All notable changes to `loop-engineer` are documented here.
   `WORKFLOW.md` and `README.md` are reworded to describe the mechanism; the 0.3.4
   history is left intact.
 
+## 0.9.0 — 2026-07-17
+
+**The event-sourced kernel.** The contract gains a durable runtime substrate:
+`loop-engineer/event@1` events in an append-only SQLite store
+(`.loop/events.db` — WAL, `synchronous=FULL`, no-update/no-delete triggers,
+`expected_sequence` compare-and-swap) folded by a deterministic reducer that
+enforces FSM legality, the all-required completion gate, and terminal
+immutability through the same `loop.fsm`/`loop.completion` modules the
+writers use (#62). Around it: a canonical intermediate-state FSM with
+unknown-state validation and writer timestamps (#59); `loop-engineer/plan@1`
+— a Loop Plan IR with a `plan-lint` verb and a typed capability vocabulary
+(#61); `loop-engineer/evidence@1` — hashed evidence objects with provenance,
+re-verifiable byte-for-byte (#63); administrative `terminal_superseded`
+events — the only event a terminated run admits, so a wrong terminal is
+corrected on the record instead of edited in place (#64); a run-control event
+vocabulary for approval, pause, and resume (#73); and explicit validation
+modes `--mode basic|strict|release` across the CLI (#60).
+
+**Runtime verbs.** `loop run` — event-sourced single-step dispatch with
+crash-safe resume (#71); read-only `loop status` and `loop replay` (#70);
+`loop simulate` — strictly read-only dry-run dispatch prediction (#75);
+`approve` / `pause` / `resume` / `cancel` (#74); a subprocess-isolated
+verifier runner — shlex argv, no shell, wall-clock cap, bounded output tail,
+typed failure classes — plus typed fail-loud stubs for the not-yet-shipped
+run modes (#72); `loop architect` as a typed fail-loud deferral (#76). And
+`loop doctor` now composes an event-store consistency gate over
+`status`/`replay` whenever `.loop/events.db` exists — one hard gate across
+the file layer and the event log (#77).
+
+**Completion-semantics hardening (Phase 0).** `Succeeded` now requires
+**all** required criteria satisfied plus evidence — the prior any-true
+reading was a correctness bug, fixed in one shared `loop/completion.py`
+wired into the writer API, the integrations projection, and the contract
+validator's G1 check. `terminal_state.json` is create-once (atomic;
+`force` always raises); iteration ids are canonical ints (legacy decimal
+strings stay read-compatible); `terminal@1` gains an additive
+`completion_policy` (#48).
+
+**Adversarial hardening.** A property-based kernel suite over FSM legality,
+G1 completion, supersession, and replay determinism (#65), and a
+process/security suite — real crash injection at code-controlled barriers,
+verifier tampering, workspace-escape TOCTOU (#66). The `verify_evidence()`
+symlink-swap TOCTOU that suite discovered (#67) is closed by fd-pinned
+open-then-verify (#69), retiring the strict xfail marker.
+
+**Scoreboard, funnel, housekeeping.** The ST5 harness scoreboard — 9 public
+harnesses read through a foreign-layout registry with 8 vendored fixtures
+(#41); contributor-funnel fixes — trigger-phrase disambiguation (#42),
+documentation-completeness labels on the self-eval (#43),
+`approval_requested`/`replanned` recognized as honest-red metrics tokens
+(#44), metrics-clean RUNLOG seeding (#45); Dependabot version updates and
+least-privilege workflow permissions (#46, #47).
+
+**Known limitation.** Read verbs over the event store leave SQLite
+`-wal`/`-shm` sidecars next to `.loop/events.db` (read-only connections
+recreate them and cannot checkpoint on close). Store content is never
+mutated, but tree-byte-identity checks over a store-backed workspace will
+notice them.
+
+Test baseline: 933 passed / 16 skipped with the `yaml`+`schemas` extras;
+864 / 85 in structural-fallback mode (PyYAML only).
+
 ## 0.8.0 — 2026-07-09
 
 **ST3 — integration adapters.** `loop/integrations.py`: an engine-neutral,

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/CONTRIBUTING.md

@@ -11,7 +11,7 @@ you open a PR, all of these must be green (CI runs them on every push):
 ```bash
 # from the repo root
 python3 scripts/validate_frontmatter.py     # SKILL.md frontmatter
-python3 scripts/self_eval.py                # 13 structural invariants
+python3 scripts/self_eval.py                # 13 structural/doc-completeness invariants
 python3 -m pytest -q scripts                # the test suite
 python3 -m py_compile loop/*.py scripts/*.py
 python3 -m loop doctor   examples/coverage-repair   # quickstart still works
@@ -20,6 +20,16 @@ python3 -m loop inspect  examples/coverage-repair
 
 If you don't have the deps, prefix with `uv run --with pyyaml --with pytest`.
 
+`scripts/test_adversarial_kernel.py` also uses the dev-only `hypothesis` dependency: install it with `pip install -e ".[dev]"`, or use `uv run --with hypothesis --with pytest`. A plain install never pulls it in; without it, those property tests skip rather than fail.
+
+`scripts/test_adversarial_process.py` spawns short-lived child processes and sends real `SIGKILL` signals to simulate mid-transaction crashes; it is POSIX-only (CI uses `ubuntu-latest`), requires no new dependency, and adds a few seconds of subprocess wall time.
+
+Most `self_eval.py` checks verify documentation-completeness — that the suite's
+canonical vocabulary (terminal states, repair-record fields, eval layers +
+metrics) is present in the skill prose — not that a running loop enforces it. The
+runtime/behavioral gate is `python3 -m loop doctor` and the contract's own
+`verify-*` scripts, which is why both appear in the list above.
+
 ## Start here — the contributor funnel
 
 Every open starter issue names **the gate that proves the fix** — a
@@ -53,7 +63,10 @@ Loop-Engineer-conformant contract v1. Drafts for the seeded issues live in
 
 ## Authoring or editing a skill
 
-The `self_eval.py` checks encode hard rules — match them or the gate fails:
+The `self_eval.py` checks encode hard rules — match them or the gate fails. Most
+are documentation-completeness checks (the canonical vocabulary must appear in the
+skill prose), not behavioral enforcement of a running loop — that gate is `loop
+doctor` and the contract's own `verify-*` scripts:
 
 - **Frontmatter** must have `name:` and `description:`. The directory name **must equal**
   the frontmatter `name`. Keep the `description` a *quoted* YAML scalar (the suite quotes

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: loop-engineer
-Version: 0.8.0
+Version: 0.9.0
 Summary: Portable Loop Contract Core: validate and inspect repo-native operating contracts for agent loops.
 Project-URL: Homepage, https://github.com/SollanSystems/loop-engineer
 Project-URL: Repository, https://github.com/SollanSystems/loop-engineer
@@ -29,6 +29,8 @@ License: MIT License
 License-File: LICENSE
 Keywords: agent,agentic,claude-code,eval,harness,loop,orchestration,repair,self-improvement,verification
 Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: hypothesis>=6; extra == 'dev'
 Provides-Extra: schemas
 Requires-Dist: jsonschema>=4; extra == 'schemas'
 Provides-Extra: yaml
@@ -42,7 +44,7 @@ Description-Content-Type: text/markdown
 [![CI](https://github.com/SollanSystems/loop-engineer/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/SollanSystems/loop-engineer/actions/workflows/ci.yml)
 [![Python 3.10–3.12](https://img.shields.io/badge/python-3.10%E2%80%933.12-blue)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
-[![Release](https://img.shields.io/badge/release-0.8.0-blue)](https://github.com/SollanSystems/loop-engineer/tags)
+[![Release](https://img.shields.io/badge/release-0.9.0-blue)](https://github.com/SollanSystems/loop-engineer/tags)
 
 Long-running agents commit **false completion**. After context compaction they
 forget what "done" meant, optimize to the visible test, patch in circles, and
@@ -57,7 +59,11 @@ ships, on disk and runnable today:
 - a **held-out gate** and an **anti-cheat scan** built to catch a loop gaming its
   own verifier;
 - a runnable example whose `false_completion: false` is backed by a committed,
-  real gate verdict — `.loop/artifacts/holdout-verdict.json`, not a hand-set flag.
+  real gate verdict — `.loop/artifacts/holdout-verdict.json`, not a hand-set flag;
+- an **event-sourced runtime** — `run`, `status`, `replay`, `simulate`, and
+  approve/pause/resume/cancel over an append-only SQLite event log
+  (`.loop/events.db`), folded by a deterministic reducer that enforces the same
+  completion gate as the writers, with crash-safe single-step resume.
 
 ![The inspector scores a self-asserted DIY loop 0/weak, then the gate-backed example 90/strong — both runs live](docs/demo.gif)
 
@@ -161,6 +167,7 @@ directory, and need no agent runtime to run.
 {
   "ok": true,
   "validation_mode": "structural-fallback",
+  "requested_mode": "auto",
   "schemas_checked": [
     "loop-engineer/manifest@1",
     "loop-engineer/state@1",
@@ -176,6 +183,15 @@ default, or real JSON-Schema validation against `schemas/*.json` when the
 optional `jsonschema` dependency is present (`pip install -e ".[schemas]"`), in
 which case it reads `"jsonschema"`.
 
+For `doctor`, `validate`, and `verify`, `--mode basic|strict|release` makes the
+choice explicit. With no flag, the current auto-detect behavior is unchanged
+for backward compatibility with existing foreign and scoreboard callers.
+`--mode basic` always uses the structural fallback, regardless of whether
+`jsonschema` happens to be installed. `--mode strict` and `--mode release`
+require real JSON-Schema validation and fail non-zero rather than silently
+downgrade if the `jsonschema` extra is missing. `release` currently has the
+same behavior as `strict`; it is reserved for a stricter future policy.
+
 `inspect` is a static contract linter: it scores the loop contract's structure —
 what proof machinery is present and what is missing — without running the loop:
 
@@ -253,7 +269,7 @@ terminal outcome:
   .loop/
     manifest.yaml        # contract metadata
     state.json           # live FSM cursor
-    terminal_state.json  # final exit record; written once — emit refuses overwrite without force=True
+    terminal_state.json  # final exit record; immutable once written
     artifacts/           # evidence bundles and intermediate outputs
     approvals/           # approval requests and resolutions
     checkpoints/         # recoverable snapshots
@@ -307,6 +323,12 @@ The portable core lives in `loop/` and validates schema-bearing artifacts in
 - `loop-engineer/state@1`
 - `loop-engineer/tasks@1`
 - `loop-engineer/terminal@1`
+- `loop-engineer/receipt@1`
+- `loop-engineer/repair@1`
+- `loop-engineer/rollout@1`
+- `loop-engineer/plan@1`
+- `loop-engineer/event@1`
+- `loop-engineer/evidence@1`
 
 ### Claude Code plugin
 
@@ -338,13 +360,14 @@ otherwise, the stop is blocked with the exact doctor issues. No-op without
 **Any Python runtime** — `loop.emit` is a pure-stdlib writer for foreign
 orchestrators (LangGraph, or anything that can call four functions):
 `open_contract`, `append_iteration`, `append_receipt`, `terminate`. The writer
-refuses an evidence-free `Succeeded` at write time. Recipe:
+refuses `Succeeded` unless every declared criterion is true and evidence is
+present. Recipe:
 [docs/integrations/langgraph.md](docs/integrations/langgraph.md).
 
 **CI** — one workflow step validates the contract and publishes a scorecard:
 
 ```yaml
-- uses: SollanSystems/loop-engineer@v0.8.0
+- uses: SollanSystems/loop-engineer@v0.9.0
   with:
     path: "."
 ```
@@ -426,16 +449,19 @@ claude plugin validate --strict .claude-plugin/plugin.json
 ```
 
 The structural self-eval checks skill presence, frontmatter, cross-links,
-terminal-state coverage, repair-record fields, eval metrics, templates, secret
-patterns, dispatch examples, the bring-your-own-verifier default, the MIT
-license, and README differentiation.
+templates, secret patterns, dispatch examples, the bring-your-own-verifier
+default, the MIT license, and README differentiation. Three further checks are
+documentation-completeness scans: they confirm the canonical vocabulary for
+terminal-state coverage, repair-record fields, and eval metrics is present in the
+skill prose — not that a running loop enforces it (that runtime gate is `loop
+doctor` and the contract's own `verify-*` scripts).
 
 ---
 
 ## Status
 
-- Version: `0.8.0`
-- Release tag: `v0.8.0` (PyPI publish trigger; plugin tags through 0.6.0 used `loop-engineer--v<version>`)
+- Version: `0.9.0`
+- Release tag: `v0.9.0` (PyPI publish trigger; plugin tags through 0.6.0 used `loop-engineer--v<version>`)
 - License: MIT
 - Primary interface: Claude Code plugin
 - Portable core: Python CLI + JSON schemas

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/README.md

@@ -5,7 +5,7 @@
 [![CI](https://github.com/SollanSystems/loop-engineer/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/SollanSystems/loop-engineer/actions/workflows/ci.yml)
 [![Python 3.10–3.12](https://img.shields.io/badge/python-3.10%E2%80%933.12-blue)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
-[![Release](https://img.shields.io/badge/release-0.8.0-blue)](https://github.com/SollanSystems/loop-engineer/tags)
+[![Release](https://img.shields.io/badge/release-0.9.0-blue)](https://github.com/SollanSystems/loop-engineer/tags)
 
 Long-running agents commit **false completion**. After context compaction they
 forget what "done" meant, optimize to the visible test, patch in circles, and
@@ -20,7 +20,11 @@ ships, on disk and runnable today:
 - a **held-out gate** and an **anti-cheat scan** built to catch a loop gaming its
   own verifier;
 - a runnable example whose `false_completion: false` is backed by a committed,
-  real gate verdict — `.loop/artifacts/holdout-verdict.json`, not a hand-set flag.
+  real gate verdict — `.loop/artifacts/holdout-verdict.json`, not a hand-set flag;
+- an **event-sourced runtime** — `run`, `status`, `replay`, `simulate`, and
+  approve/pause/resume/cancel over an append-only SQLite event log
+  (`.loop/events.db`), folded by a deterministic reducer that enforces the same
+  completion gate as the writers, with crash-safe single-step resume.
 
 ![The inspector scores a self-asserted DIY loop 0/weak, then the gate-backed example 90/strong — both runs live](docs/demo.gif)
 
@@ -124,6 +128,7 @@ directory, and need no agent runtime to run.
 {
   "ok": true,
   "validation_mode": "structural-fallback",
+  "requested_mode": "auto",
   "schemas_checked": [
     "loop-engineer/manifest@1",
     "loop-engineer/state@1",
@@ -139,6 +144,15 @@ default, or real JSON-Schema validation against `schemas/*.json` when the
 optional `jsonschema` dependency is present (`pip install -e ".[schemas]"`), in
 which case it reads `"jsonschema"`.
 
+For `doctor`, `validate`, and `verify`, `--mode basic|strict|release` makes the
+choice explicit. With no flag, the current auto-detect behavior is unchanged
+for backward compatibility with existing foreign and scoreboard callers.
+`--mode basic` always uses the structural fallback, regardless of whether
+`jsonschema` happens to be installed. `--mode strict` and `--mode release`
+require real JSON-Schema validation and fail non-zero rather than silently
+downgrade if the `jsonschema` extra is missing. `release` currently has the
+same behavior as `strict`; it is reserved for a stricter future policy.
+
 `inspect` is a static contract linter: it scores the loop contract's structure —
 what proof machinery is present and what is missing — without running the loop:
 
@@ -216,7 +230,7 @@ terminal outcome:
   .loop/
     manifest.yaml        # contract metadata
     state.json           # live FSM cursor
-    terminal_state.json  # final exit record; written once — emit refuses overwrite without force=True
+    terminal_state.json  # final exit record; immutable once written
     artifacts/           # evidence bundles and intermediate outputs
     approvals/           # approval requests and resolutions
     checkpoints/         # recoverable snapshots
@@ -270,6 +284,12 @@ The portable core lives in `loop/` and validates schema-bearing artifacts in
 - `loop-engineer/state@1`
 - `loop-engineer/tasks@1`
 - `loop-engineer/terminal@1`
+- `loop-engineer/receipt@1`
+- `loop-engineer/repair@1`
+- `loop-engineer/rollout@1`
+- `loop-engineer/plan@1`
+- `loop-engineer/event@1`
+- `loop-engineer/evidence@1`
 
 ### Claude Code plugin
 
@@ -301,13 +321,14 @@ otherwise, the stop is blocked with the exact doctor issues. No-op without
 **Any Python runtime** — `loop.emit` is a pure-stdlib writer for foreign
 orchestrators (LangGraph, or anything that can call four functions):
 `open_contract`, `append_iteration`, `append_receipt`, `terminate`. The writer
-refuses an evidence-free `Succeeded` at write time. Recipe:
+refuses `Succeeded` unless every declared criterion is true and evidence is
+present. Recipe:
 [docs/integrations/langgraph.md](docs/integrations/langgraph.md).
 
 **CI** — one workflow step validates the contract and publishes a scorecard:
 
 ```yaml
-- uses: SollanSystems/loop-engineer@v0.8.0
+- uses: SollanSystems/loop-engineer@v0.9.0
   with:
     path: "."
 ```
@@ -389,16 +410,19 @@ claude plugin validate --strict .claude-plugin/plugin.json
 ```
 
 The structural self-eval checks skill presence, frontmatter, cross-links,
-terminal-state coverage, repair-record fields, eval metrics, templates, secret
-patterns, dispatch examples, the bring-your-own-verifier default, the MIT
-license, and README differentiation.
+templates, secret patterns, dispatch examples, the bring-your-own-verifier
+default, the MIT license, and README differentiation. Three further checks are
+documentation-completeness scans: they confirm the canonical vocabulary for
+terminal-state coverage, repair-record fields, and eval metrics is present in the
+skill prose — not that a running loop enforces it (that runtime gate is `loop
+doctor` and the contract's own `verify-*` scripts).
 
 ---
 
 ## Status
 
-- Version: `0.8.0`
-- Release tag: `v0.8.0` (PyPI publish trigger; plugin tags through 0.6.0 used `loop-engineer--v<version>`)
+- Version: `0.9.0`
+- Release tag: `v0.9.0` (PyPI publish trigger; plugin tags through 0.6.0 used `loop-engineer--v<version>`)
 - License: MIT
 - Primary interface: Claude Code plugin
 - Portable core: Python CLI + JSON schemas

{loop_engineer-0.8.0 → loop_engineer-0.9.0}/action.yml

@@ -29,7 +29,7 @@ inputs:
 runs:
   using: "composite"
   steps:
-    - uses: actions/setup-python@v5
+    - uses: actions/setup-python@v6
       with:
         python-version: ${{ inputs.python-version }}
 

loop_engineer-0.9.0/docs/adr/0001-proof-kernel-and-runtime.md

@@ -0,0 +1,104 @@
+# ADR 0001: Separate the proof kernel from the execution runtime
+
+- **Status:** Accepted
+- **Date:** 2026-07-12
+- **Decision owners:** Loop Engineer maintainers
+
+## Context
+
+Loop Engineer began as a portable contract and proof layer. Its current core is
+valuable because it defines typed terminal states, evidence-gated completion,
+anti-cheat checks, bounded repair, and repo-native state without binding those
+concepts to a particular orchestration framework.
+
+The product goal is broader: a user should be able to provide a complex goal,
+receive a reviewable loop design, execute it through interchangeable agents and
+tools, pause for approvals, recover from failure, and obtain an independently
+verified terminal result.
+
+Keeping execution out of the project would preserve a small scope, but it would
+also leave the most important invariants as instructions that a host agent may
+ignore. Folding every concern into one package would create the opposite
+problem: provider-specific execution details would contaminate the portable
+proof protocol.
+
+## Decision
+
+Loop Engineer will have two first-party layers with a strict dependency
+direction.
+
+### 1. Proof kernel
+
+The proof kernel is the stable, runtime-neutral protocol. It owns:
+
+- contract and schema versions;
+- deterministic completion-policy evaluation;
+- legal state and terminal-state projection;
+- evidence and provenance rules;
+- verifier and anti-cheat interfaces;
+- policy validation and conformance tests;
+- event reduction and replay semantics.
+
+The kernel must not import model providers, agent frameworks, or workflow
+engines. It may be embedded by foreign runtimes.
+
+### 2. Execution runtime
+
+The execution runtime interprets a validated Loop Plan and owns:
+
+- planning and task scheduling;
+- worker leases and attempt numbers;
+- agent and tool dispatch;
+- budgets, retries, timeouts, pause, resume, and cancellation;
+- approvals and side-effect policy;
+- checkpointing and crash recovery;
+- persistence of immutable events and artifacts.
+
+The runtime depends on the kernel. The kernel never depends on the runtime.
+
+## Governing rule
+
+**Agents propose; the kernel disposes.**
+
+An agent may propose a command, patch, transition, or completion claim. Only the
+kernel may validate and commit a state transition or terminal result.
+
+## Immediate consequences
+
+1. `Succeeded` uses an explicit completion policy. The first supported policy is
+   `all_required`; every declared criterion must be proven true.
+2. Terminal records are immutable. Corrections will be represented by separate,
+   auditable administrative events rather than file replacement.
+3. New state writers use canonical integer iteration identifiers. Legacy
+   numeric strings remain a read-compatibility concern until a versioned state
+   migration removes them.
+4. The next persistence milestone will introduce an `EventStore` protocol and a
+   SQLite/WAL implementation. JSON and Markdown files become projections rather
+   than the sole authoritative state.
+5. Provider and model selection will be capability-based, not encoded in the
+   portable contract as vendor model names.
+
+## Non-goals of this decision
+
+This ADR does not select a distributed scheduler, hosted control plane, web UI,
+or model provider. It also does not make structural evidence equivalent to
+cryptographic attestation. Those require separate decisions.
+
+## Rejected alternatives
+
+### Remain contract-only
+
+Rejected because the desired product must execute and govern loops end to end.
+A prose-only state machine cannot reliably enforce concurrency, approvals,
+budgets, or immutable terminal decisions.
+
+### Build a monolithic provider-specific agent framework
+
+Rejected because it would erase the strongest differentiation: a portable proof
+contract that can sit above multiple runtimes.
+
+### Permit terminal overwrite for operator convenience
+
+Rejected because an overwritten terminal record destroys audit history and
+creates a race in which a later writer can launder an earlier result. A future
+supersession event can preserve both the original decision and the correction.