specfuse-loop 0.29.1__tar.gz → 0.30.0__tar.gz

{specfuse_loop-0.29.1/specfuse_loop.egg-info → specfuse_loop-0.30.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specfuse-loop
-Version: 0.29.1
+Version: 0.30.0
 Summary: Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology.
 Author: Specfuse contributors
 License: Apache-2.0

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specfuse-loop"
-version = "0.29.1"
+version = "0.30.0"
 description = "Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology."
 readme = "README.md"
 requires-python = ">=3.10"

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/specfuse/loop/arm_eval.py

@@ -104,6 +104,7 @@ JUDGE_MODULES = tuple(
         "agent_policy.py",       # automerge dial, diff/merge caps, test paths
         "cost.py",               # spend, read by budget_projection
         "gate_commands.py",      # resolves which commands a gate must pass
+        "gen_contract.py",       # IS a `code` gate in component repos; an edit can turn a red contract green
         # What a work unit or a close must satisfy.
         "closing_requirements.py",
         "criteria_state.py",
@@ -157,6 +158,8 @@ NON_JUDGE_MODULES = {
     "learnings_query.py": "reads LEARNINGS.md for planning context",
     "lint_monitoring.py": "lints monitoring.yml, which no arm/close/merge "
         "verdict reads",
+    "layout.py": "resolves layout.yml for lint_roadmap and skills; no arm/"
+        "close/merge verdict reads it",
     "lint_roadmap.py": "lints roadmap.md, which no arm/close/merge verdict reads",
     "notify.py": "delivery of a message about a decision already made",
     "notify_escalation.py": "as notify.py",

specfuse_loop-0.30.0/specfuse/loop/data/VERSION

@@ -0,0 +1 @@
+0.30.0

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/specfuse/loop/data/docs/concepts/autonomy-stop-classes.md

@@ -48,6 +48,13 @@ cleared by editing driver code; it clears by changing the plan's numbers.
 file under a judge-path surface — paths that would let a work unit edit its
 own verification.
 
+**Does not cover the terminal gate.** The class reads only the successor
+gate's drafted units. A terminal gate has no successor, so what its own units
+change is never checked; a single-gate feature is never checked at all. The
+terminal close goes straight to the judge, and no judge-path check sits on
+that path (#3542). A feature that edits a judge surface in its last gate should
+run under `review`.
+
 **Fires when:** a drafted WU's `produces:` list contains a path matching one
 of `JUDGE_PATHS` — `.specfuse/verification.yml`, `.specfuse/hooks/`,
 `.specfuse/rules/`, `.github/workflows/`, or `pyproject.toml` (matched

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/specfuse/loop/data/docs/methodology.md

@@ -26,8 +26,8 @@ on both surfaces.
   both stay resumable: a human flips the feature back to `active` when the
   obstacle clears. Both are distinct from `abandoned` (dead) and `done`
   (complete).
-  - `blocked` — cannot proceed because a **named** dependency is unmet: an ADR
-    awaiting approval, or an upstream `FEAT-YYYY-NNNN` that must complete first.
+  - `blocked` — cannot proceed because a **named** dependency is unmet: a decision
+    awaiting approval (ADR or decision entry, per `layout.yml`), or an upstream `FEAT-YYYY-NNNN` that must complete first.
     A blocked feature always names and links its blocker, so the roadmap shows
     the dependency at a glance. Only `planned` or `active` may be blocked.
   - `deferred` — a *voluntary* park with no named blocker, pending an external
@@ -795,9 +795,12 @@ untouched** — the same eight stop classes, the same `would_arm`, the same
 single flip site. What changed is what an armed gate is armed *on*. Before the
 judge, an `auto` feature let the session that did the work write the verdict
 that advanced the feature; now a fresh evaluator that never sees that session's
-prose writes it, and can only lower it. The `judge_editing` stop class still
-vetoes any gate that edited the loop's own driver, so a feature that changes
-the machinery keeps its human checkpoint regardless of this default.
+prose writes it, and can only lower it. The `judge_editing` stop class vetoes
+arming a successor gate whose drafted units would edit a judge surface. It
+does **not** cover the terminal gate's own units, so a single-gate feature,
+or the last gate of any feature, that edits the loop's verdict machinery
+reaches its close with no human checkpoint under `auto` (#3542). Choose
+`review` for such a feature.
 
 Tighten to `review` when the judge cannot do its job — a feature whose criteria
 are not judgeable from the evidence bundle (see `judge_disabled` in §3), or one

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/specfuse/loop/data/docs/skills.md

@@ -49,7 +49,7 @@ roadmap ──/pick-feature──▶ active ──/draft-feature──▶ gate 1
 - **`/roadmap-add`** — add a new feature row to the roadmap before it's ready to
   pick.
 - **`/block-feature`** — flip a roadmap feature to `blocked` (or clear it) with a
-  linked `**Blocked by.**` blocker — an ADR awaiting approval or an upstream
+  linked `**Blocked by.**` blocker — a decision awaiting approval (ADR or decision entry, per `layout.yml`) or an upstream
   FEAT-ID that must complete first. Writes the row status, the detail block, and
   PLAN frontmatter, keeping intra-page feature links resolvable.
   `/block-feature FEAT-ID --unblock` clears the block and restores the status.

{specfuse_loop-0.29.1 → specfuse_loop-0.30.0}/specfuse/loop/data/roadmap.template.md

@@ -34,6 +34,7 @@ links to it.
 A `blocked` feature's detail section carries a `**Blocked by.**` block — blank
 line above it, one linked blocker per clause:
 
+<!-- layout:decisions-example -->
 **Blocked by.** [ADR-0007: event-schema versioning](../docs/adr/0007-event-schema-versioning.md) — awaiting approval; [FEAT-2026-0011](#feat-2026-0011) — scoring data must land first.
 
 Each blocker is a Markdown link: an ADR points at its `.md` file (kept under
@@ -41,6 +42,7 @@ Each blocker is a Markdown link: an ADR points at its `.md` file (kept under
 `../docs/adr/…`); a feature dependency points at the blocking
 feature's roadmap anchor (`#feat-yyyy-nnnn`). When every blocker clears, a human
 flips `blocked` → `active` (or `planned`) and removes the `**Blocked by.**` block.
+<!-- /layout:decisions-example -->
 
 ## Notes