specfuse-loop 0.3.10__tar.gz → 0.3.11__tar.gz

{specfuse_loop-0.3.10/specfuse_loop.egg-info → specfuse_loop-0.3.11}/PKG-INFO

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

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/pyproject.toml

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

specfuse_loop-0.3.11/specfuse/loop/data/VERSION

@@ -0,0 +1 @@
+0.3.11

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/specfuse/loop/data/docs/concepts/architecture-addendum-gates-and-iterative-planning.md

@@ -24,7 +24,7 @@ implementation feature == a loop feature**: the receiving component's loop decom
 So gates are **internal to the loop**, not orchestrator state. The orchestrator owns
 `initiative → feature` decomposition, cross-repo dependency ordering, and the spec/generated
 interface contracts between features; it does **not** identify gates, run `plan-next`, or hold a
-per-gate `plan_review`. The loop owns all of that, per [`methodology.md`](methodology.md).
+per-gate `plan_review`. The loop owns all of that, per [`methodology.md`](../methodology.md).
 
 **Why Model B (summary).** The loop is single-repo + edit-and-commit; codegen freezes the
 cross-repo interface (generated `emit-*`/`on-*` contracts are immutable `_generated/`), so
@@ -60,7 +60,7 @@ gates were placed in the loop instead.
 
 ## 3. What the loop owns (the gate layer)
 
-Per [`methodology.md`](methodology.md): the gate cycle (plan → execute → close → review&arm), the
+Per [`methodology.md`](../methodology.md): the gate cycle (plan → execute → close → review&arm), the
 four-type closing sequence (`retrospective → lessons → docs → plan-next`), `plan-next` drafting
 the next gate (never arming it), `LEARNINGS.md`, and per-gate autonomy. These are **loop-internal**
 to each dispatched feature; the orchestrator sees only the feature's overall state (via issue

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/specfuse/loop/data/docs/concepts/ralph-lineage.md

@@ -50,7 +50,7 @@ independently-adoptable projects live under it:
   for multi-repo, spec-first feature delivery.
 
 The loop and the orchestrator are two execution surfaces of **one** methodology
-(see [`methodology.md`](methodology.md)); they share the gate cycle, the
+(see [`methodology.md`](../methodology.md)); they share the gate cycle, the
 work-unit contract, the correlation-ID scheme, and the verification discipline.
 The loop is the right home for work that lives in one repo or has no formal
 spec; the orchestrator is the right home when the work genuinely spans repos and

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/specfuse/loop/data/templates/WU.template.md

@@ -38,7 +38,7 @@ AUTHOR-SET FIELDS — fill or override these at draft/arm time:
 - `produces` — OPTIONAL. File path(s) this WU must produce; machine-enforced by the driver's
   presence gate (FEAT-2026-0022). Lint WARN when absent on `implementation` WUs.
 
-DRIVER-OWNED FIELDS — the driver writes these at outcome time; authors leave them absent:
+DRIVER-OWNED FIELDS - the driver writes these at outcome time; authors leave them absent:
 <!-- driver-owned: attempts, cost_usd, input_tokens, output_tokens, duration_seconds,
      cumulative_cost_usd, cumulative_duration_seconds, cumulative_input_tokens,
      cumulative_output_tokens, re_arm_count, re_arm_history -->

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/specfuse/loop/loop.py

@@ -62,7 +62,7 @@ SPECFUSE_DIR = Path(".specfuse")
 REPO_ROOT = SPECFUSE_DIR.parent
 FEATURES_DIR = SPECFUSE_DIR / "features"
 VERIFICATION_PATH = SPECFUSE_DIR / "verification.yml"
-DRIVER_VERSION = "0.3.10"
+DRIVER_VERSION = "0.3.11"
 # Oldest scaffold layout this driver can drive. init.sh stamps the scaffold's own
 # version into `.specfuse/VERSION`; check_scaffold_version() fails loud at startup if
 # the consumer's scaffold is older than this, pointing at `specfuse upgrade`. Bump

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11/specfuse_loop.egg-info}/PKG-INFO

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

{specfuse_loop-0.3.10 → specfuse_loop-0.3.11}/specfuse_loop.egg-info/SOURCES.txt

@@ -118,6 +118,7 @@ tests/test_roadmap_add_skill.py
 tests/test_roadmap_archive_skill.py
 tests/test_roadmap_row_parser.py
 tests/test_scaffold_data_in_sync.py
+tests/test_scaffold_doc_hygiene.py
 tests/test_scaffold_docs.py
 tests/test_scaffold_init.py
 tests/test_scaffold_manifest.py

specfuse_loop-0.3.11/tests/test_scaffold_doc_hygiene.py

@@ -0,0 +1,79 @@
+#
+# Copyright 2026 Specfuse Contributors
+# Licensed under the Apache License, Version 2.0. See LICENSE.
+#
+"""Issue #140 — vendored scaffold docs/templates must not carry defects that
+trip Markdown inspections downstream.
+
+Two genuine defects were observed in a freshly-initialized project:
+
+1. Broken relative links to `methodology.md` from `docs/concepts/*.md`: the
+   link uses a same-directory path but `methodology.md` lives one level up in
+   `docs/`. Correct target is `../methodology.md`.
+2. A "Bad character" parse error on the em-dash (U+2014) leading the inline
+   text of the `DRIVER-OWNED FIELDS` paragraph in `WU.template.md`.
+
+These guards run against the CANONICAL sources (`docs/`, `.specfuse/`); the
+byte-match drift guard in test_scaffold_data_in_sync.py keeps the vendored
+`specfuse/loop/data/` copies in lockstep, so fixing the canonicals + re-vendoring
+propagates the fix everywhere.
+"""
+
+from __future__ import annotations
+
+import pathlib
+import re
+import unittest
+
+REPO_ROOT = pathlib.Path(__file__).parent.parent
+DOCS = REPO_ROOT / "docs"
+WU_TEMPLATE = REPO_ROOT / ".specfuse" / "templates" / "WU.template.md"
+
+# Markdown inline link with a relative path target (skips absolute URLs and
+# pure-anchor links). Captures the path portion, dropping any `#anchor`.
+_LINK_RE = re.compile(r"\]\((?!https?://)([^)#][^)]*?)(?:#[^)]*)?\)")
+EM_DASH = "—"
+
+
+class TestScaffoldDocHygiene(unittest.TestCase):
+
+    def test_docs_relative_md_links_resolve(self):
+        """Every relative .md link in docs/ must resolve to an existing file
+        from the linking file's own directory (issue #140 defect 1)."""
+        broken: list[str] = []
+        for md in sorted(DOCS.rglob("*.md")):
+            for lineno, line in enumerate(
+                md.read_text(encoding="utf-8").splitlines(), start=1
+            ):
+                for target in _LINK_RE.findall(line):
+                    if not target.endswith(".md"):
+                        continue
+                    resolved = (md.parent / target).resolve()
+                    if not resolved.is_file():
+                        rel = md.relative_to(REPO_ROOT)
+                        broken.append(f"{rel}:{lineno} -> {target}")
+        self.assertEqual(
+            [], broken,
+            "broken relative .md links in docs/ (fix the path):\n"
+            + "\n".join(broken),
+        )
+
+    def test_wu_template_driver_owned_line_has_no_em_dash(self):
+        """The DRIVER-OWNED FIELDS paragraph must not carry the U+2014 em-dash
+        that IntelliJ flags as a Bad character (issue #140 defect 2)."""
+        matches = [
+            line
+            for line in WU_TEMPLATE.read_text(encoding="utf-8").splitlines()
+            if line.startswith("DRIVER-OWNED FIELDS")
+        ]
+        self.assertTrue(matches, "DRIVER-OWNED FIELDS line not found in template")
+        for line in matches:
+            self.assertNotIn(
+                EM_DASH, line,
+                "DRIVER-OWNED FIELDS line still contains the U+2014 em-dash "
+                "that trips the Markdown parser — use ' - ' instead",
+            )
+
+
+if __name__ == "__main__":
+    unittest.main()

specfuse_loop-0.3.10/specfuse/loop/data/VERSION

@@ -1 +0,0 @@
-0.3.10