specfuse-loop 0.3.23__tar.gz → 0.4.0__tar.gz

{specfuse_loop-0.3.23/specfuse_loop.egg-info → specfuse_loop-0.4.0}/PKG-INFO

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

{specfuse_loop-0.3.23 → specfuse_loop-0.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specfuse-loop"
-version = "0.3.23"
+version = "0.4.0"
 description = "Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -45,11 +45,21 @@ dev = [
 Homepage = "https://github.com/specfuse/loop"
 Source = "https://github.com/specfuse/loop"
 
-# Minimal ruff config — keep defaults (E + F). Target the loop's actual
-# minimum Python (matches pyproject's `requires-python`).
+# Target the loop's actual minimum Python (matches `requires-python`).
 [tool.ruff]
 target-version = "py310"
 
+[tool.ruff.lint]
+# Pin the ruleset EXPLICITLY rather than relying on ruff's implicit default.
+# ruff 0.16 broadened its default `select` to a large opinionated set
+# (B/SIM/PLW/RUF/I/…); a bare config inherited that overnight and flagged ~300
+# findings across code that had been clean for months — breaking CI on every PR
+# purely from a version bump. This repo intends only the classic default
+# (pyflakes + the core pycodestyle subset); pinning it here makes that intent
+# version-independent. Adopting the broader ruleset is a separate, deliberate
+# decision (see the roadmap), never an implicit consequence of upgrading ruff.
+select = ["E4", "E7", "E9", "F", "PLW1510", "B", "BLE001", "S110", "TRY004"]
+
 [project.scripts]
 specfuse-loop = "specfuse.loop.loop:main"
 specfuse-lint = "specfuse.loop.lint_plan:main"

specfuse_loop-0.4.0/specfuse/loop/data/VERSION

@@ -0,0 +1 @@
+0.4.0

{specfuse_loop-0.3.23 → specfuse_loop-0.4.0}/specfuse/loop/data/docs/skills.md

@@ -48,6 +48,11 @@ roadmap ──/pick-feature──▶ active ──/draft-feature──▶ gate 1
   `/draft-feature`.
 - **`/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
+  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.
 
 ### 2. Draft — turn a picked feature into a runnable gate
 

{specfuse_loop-0.3.23 → specfuse_loop-0.4.0}/specfuse/loop/data/roadmap.template.md

@@ -23,8 +23,24 @@ the canonical column order below.
 |----------------|-------|--------|--------|--------|
 
 Status: `planned` → `active` → `done` (or `abandoned`). `deferred` = parked
-pending an external decision/dependency; resumable (a human flips it back to
-`active` when the blocker clears), distinct from `abandoned` (dead).
+by choice pending an external decision/dependency; resumable (a human flips it
+back to `active` when the blocker clears), distinct from `abandoned` (dead).
+`blocked` = cannot proceed because a *named* dependency is unmet — an ADR
+awaiting approval, or an upstream feature that must complete first. Resumable
+like `deferred`, but where `deferred` is a voluntary park with no named blocker,
+`blocked` always names its blocker so the roadmap shows what it waits on and
+links to it.
+
+A `blocked` feature's detail section carries a `**Blocked by.**` block — blank
+line above it, one linked blocker per clause:
+
+**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
+`docs/adr/` by convention, so from `.specfuse/roadmap.md` the link is
+`../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.
 
 ## Notes
 

{specfuse_loop-0.3.23 → specfuse_loop-0.4.0}/specfuse/loop/data/templates/PLAN.template.md

@@ -7,7 +7,7 @@ roadmap_goal: <one line copied from the roadmap — the north star this feature
   plan-next anchors every drafted gate to this and flags if a retrospective implies
   it should change>
 autonomy_default: review        # auto | review | supervised
-status: active                  # active | deferred | done | abandoned
+status: active                  # active | blocked | deferred | done | abandoned
                                 # deferred = parked pending an external decision/dependency; resumable, non-dispatchable
 # planned_cost_usd: 0.00        # OPTIONAL — sum of WU planned costs; lint warns when missing or when delta from WU sum > 10%
 ---

{specfuse_loop-0.3.23 → specfuse_loop-0.4.0}/specfuse/loop/lint_plan.py

@@ -46,7 +46,7 @@ VALID_STATUS = {"draft", "pending", "ready", "in_progress", "in_review", "done",
 # unrecognized status that passes lint and then behaves differently at dispatch
 # is the class #183 (deferred) and #185 exist to close. Keep in sync with
 # find_feature / the gate-status transitions in loop.py.
-VALID_FEATURE_STATUS = {"planned", "active", "deferred", "done", "abandoned"}
+VALID_FEATURE_STATUS = {"planned", "active", "blocked", "deferred", "done", "abandoned"}
 VALID_GATE_STATUS = {"open", "awaiting_review", "passed"}
 CLOSING_SEQUENCE = ["retrospective", "lessons", "docs", "plan-next"]
 # New compact closing shapes (FEAT-2026-0015):