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

{specfuse_loop-0.3.24/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.24
+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.24 → specfuse_loop-0.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specfuse-loop"
-version = "0.3.24"
+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