specfuse-loop 0.2.0__tar.gz

specfuse_loop-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

specfuse_loop-0.2.0/NOTICE

@@ -0,0 +1,6 @@
+Specfuse Loop
+Copyright 2026 Specfuse contributors
+
+This product is part of the Specfuse methodology suite
+(https://github.com/specfuse). It is licensed under the Apache License,
+Version 2.0. See the LICENSE file for the full text.

specfuse_loop-0.2.0/PKG-INFO

@@ -0,0 +1,192 @@
+Metadata-Version: 2.4
+Name: specfuse-loop
+Version: 0.2.0
+Summary: Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology.
+Author: Specfuse contributors
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/specfuse/loop
+Project-URL: Source, https://github.com/specfuse/loop
+Keywords: specfuse,agents,planning,ralph,gate-cycle
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: dev
+Requires-Dist: PyYAML>=6.0; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Requires-Dist: bandit>=1.7; extra == "dev"
+Requires-Dist: coverage>=7.0; extra == "dev"
+Requires-Dist: jsonschema>=4.0; extra == "dev"
+Dynamic: license-file
+
+# Specfuse Loop
+
+**For engineers using AI coding agents** — a local-first driver that structures features as verified, work-unit sequences so each agent session runs focused on one task instead of accumulating context drift.
+
+A small, local-first executor for the **Plan + Work Unit** pattern in a single
+repository. You plan a feature as a sequence of *gates*, each a batch of
+self-contained *work units* with explicit acceptance criteria and verification.
+The loop dispatches each work unit to a fresh agent session, verifies the result
+itself, commits one squashed commit per unit, and stops at each gate so you can
+reflect — with the next gate already drafted and waiting for your review.
+
+Specfuse Loop is one of three independently-adoptable projects under the Specfuse
+methodology suite:
+
+- **`specfuse/codegen`** — deterministic source code from OpenAPI / AsyncAPI /
+  Arazzo specifications.
+- **`specfuse/loop`** — *this project*. Single-repo, spec-optional, lightweight.
+  You author the task graph directly; no specification and no agent-coordination
+  overhead are required.
+- **`specfuse/orchestrator`** — multi-repo, spec-first, agent coordination across
+  many component repositories.
+
+Use any one without the others. The loop and the orchestrator share the same
+gate-cycle methodology (see [`docs/methodology.md`](docs/methodology.md)); the
+loop is the lightweight surface for work that lives in one repo and may have no
+formal specification.
+
+## Why it exists
+
+AI coding agents do well on narrow, well-scoped work and poorly on large, vague
+work. The loop's bet is that the leverage is in the *planning*: if you remove
+ambiguity up front — crisp work units with hard boundaries and machine-checkable
+verification — then execution can run with a fresh agent per unit, re-grounding
+from durable files each time rather than accumulating context drift. It is the
+[Ralph loop](docs/concepts/ralph-lineage.md) idea applied at work-unit granularity, with
+the planning rigor Ralph's bare task list lacks.
+
+## How it works (in one minute)
+
+- A **feature** lives in `.specfuse/features/FEAT-YYYY-NNNN-slug/`, with a
+  `PLAN.md` (the task graph: gate order, work-unit membership, dependencies),
+  one `GATE-NN.md` per gate, and one `WU-*.md` per work unit (frontmatter + the
+  prompt body a fresh session receives). The loop also handles *orchestrated*
+  features dispatched by the Specfuse Orchestrator, identified by
+  `INIT-YYYY-NNNN/FNN` IDs — the loop treats both namespaces identically; only
+  the ID root differs. Use `.specfuse/scripts/gh_features.py` to discover a
+  target repo's open `specfuse:feature` issues as feature candidates; use
+  `.specfuse/scripts/adopt_feature.py <repo> <issue-number>` (or the
+  interactive `/adopt-feature` skill) to scaffold a dispatchable feature
+  folder from a picked issue.
+- The **driver** (`.specfuse/scripts/loop.py`) walks the current gate's ready
+  work units, dispatches each as a fresh `claude -p` session, runs the unit's
+  verification itself as the exit oracle, and commits one squashed,
+  trailer-carrying commit per unit. A failed gate is retried with a fresh
+  session carrying the failure evidence, up to three attempts, then escalated.
+- Each gate ends with a **closing sequence** so reflection, a durable
+  cross-feature `LEARNINGS.md`, documentation, and *drafting the next gate* all
+  happen systematically. Non-terminal gates use a two-WU form
+  (`close-intermediate` + `plan-next`); the terminal gate uses a single `close`
+  WU. A legacy four-WU form (`retrospective → lessons → docs → plan-next`) is
+  accepted but emits a lint warning.
+- The gate is the **human boundary.** The driver runs unattended within a gate
+  and stops at it; you review the next gate's draft and arm it. (Under automatic
+  mode, safe gates can self-arm; the dangerous edges always pull you back in —
+  see the methodology doc.)
+
+## Quickstart
+
+In a target single-repo project:
+
+**Contributing to this repo?** Run `./scripts/install-hooks.sh` once after
+cloning to enable the pre-push hook (runs `scripts/smoke-test.sh` — same
+checks CI runs — before each `git push`). Bypass with `git push --no-verify`.
+
+The driver installs from PyPI and the skills from the Claude Code marketplace:
+
+```bash
+pip install specfuse-loop                       # the driver: `specfuse-loop` on PATH
+# in Claude Code: skills under the /specfuse: namespace
+#   /plugin marketplace add specfuse/specfuse
+#   /plugin install specfuse@specfuse
+
+# scaffold a target repo's .specfuse/ state (templates, rules, verification.yml)
+./init.sh /path/to/your-project                 # legacy installer (v1.0; removed in v1.1)
+
+cd /path/to/your-project
+$EDITOR .specfuse/verification.yml              # match the `code` gates to your stack
+# author your first feature folder under .specfuse/features/ from .specfuse/templates/
+specfuse-loop --dry-run                          # or: python .specfuse/scripts/loop.py --dry-run
+specfuse-loop
+```
+
+> **Distribution (FEAT-2026-0019).** Code ships via pip (`specfuse-loop`), the
+> `specfuse` umbrella CLI bridges pip ↔ plugin (`specfuse upgrade`), and Claude
+> assets ship via the [`specfuse/specfuse`](https://github.com/specfuse/specfuse)
+> marketplace. `init.sh` remains the scaffold bootstrap (laying down `.specfuse/`
+> state) until pip-native scaffolding lands; it prints a deprecation banner.
+
+> **One driver per working tree.** The driver holds an exclusive advisory lock on
+> `.specfuse/.loop.lock` for the duration of a run; a second driver targeting the
+> same checkout exits immediately with a clear error message. To run two features
+> in parallel, use separate `git worktree` checkouts — each gets its own lock.
+> `--dry-run` is exempt and may run alongside a live driver.
+
+This repository is also a **self-demonstrating reference installation**: its own
+`.specfuse/` contains a worked example feature
+(`features/FEAT-2026-0001-health-endpoint/`). From the repo root you can run:
+
+```bash
+python .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint
+python .specfuse/scripts/loop.py --dry-run
+```
+
+## Layout
+
+```
+specfuse-loop/
+├── LICENSE  NOTICE  CONTRIBUTING.md  README.md  .gitignore
+├── init.sh                      scaffold .specfuse/ into a target repo
+├── docs/
+│   ├── getting-started.md       narrated first-feature + operator walkthrough
+│   ├── methodology.md           the gate-cycle contract (shared with the orchestrator)
+│   ├── skills.md                the skills catalog, ordered by lifecycle phase
+│   ├── concepts/                why it exists; orchestrator mapping
+│   │   ├── ralph-lineage.md     the Ralph / Gas Town lineage
+│   │   └── architecture-addendum-gates-and-iterative-planning.md
+│   └── dev/                     internal working notes (not user-facing)
+└── .specfuse/                   canonical scaffold + worked example
+    ├── README.md
+    ├── roadmap.template.md  verification.yml.example  LEARNINGS.md
+    ├── rules/result-contract.md
+    ├── skills/verification/SKILL.md
+    ├── scripts/{loop.py, lint_plan.py, gh_features.py, adopt_feature.py, gh_backend.py}
+    ├── templates/{PLAN,GATE,WU}.template.md
+    └── features/FEAT-2026-0001-health-endpoint/   (the worked example)
+```
+
+`init.sh` also ships the durable docs — `methodology.md`, `skills.md`, and
+`concepts/` — into a target's `.specfuse/docs/`, so an initialized repo is
+self-documenting without this checkout.
+
+## Status
+
+Early but exercised. The driver, linter, parsing, dependency ordering, draft/arm
+gating, the deterministic auto-close predicate, and verification wiring are all
+tested, and the loop dogfoods itself — its own `.specfuse/features/` holds 20+
+features taken through the full gate cycle, including multi-gate features whose
+forward-design model (each gate's `plan-next` drafts the next) has held across
+four consecutive gates.
+
+What works today: single-feature and orchestrator-dispatched features; adopting a
+GitHub `specfuse:feature` issue into a dispatchable folder; GitHub issue-label
+state transitions for adopted features; per-gate auto-close on clean runs with a
+full-ceremony fallback when a gate goes off-plan; and a single-driver working-tree
+lock so two drivers can't corrupt one checkout.
+
+Expect rough edges. The interfaces (WU contract, RESULT block, correlation-ID
+scheme, `verification.yml` shape) are stable; tooling around them is still
+hardening.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

specfuse_loop-0.2.0/README.md

@@ -0,0 +1,163 @@
+# Specfuse Loop
+
+**For engineers using AI coding agents** — a local-first driver that structures features as verified, work-unit sequences so each agent session runs focused on one task instead of accumulating context drift.
+
+A small, local-first executor for the **Plan + Work Unit** pattern in a single
+repository. You plan a feature as a sequence of *gates*, each a batch of
+self-contained *work units* with explicit acceptance criteria and verification.
+The loop dispatches each work unit to a fresh agent session, verifies the result
+itself, commits one squashed commit per unit, and stops at each gate so you can
+reflect — with the next gate already drafted and waiting for your review.
+
+Specfuse Loop is one of three independently-adoptable projects under the Specfuse
+methodology suite:
+
+- **`specfuse/codegen`** — deterministic source code from OpenAPI / AsyncAPI /
+  Arazzo specifications.
+- **`specfuse/loop`** — *this project*. Single-repo, spec-optional, lightweight.
+  You author the task graph directly; no specification and no agent-coordination
+  overhead are required.
+- **`specfuse/orchestrator`** — multi-repo, spec-first, agent coordination across
+  many component repositories.
+
+Use any one without the others. The loop and the orchestrator share the same
+gate-cycle methodology (see [`docs/methodology.md`](docs/methodology.md)); the
+loop is the lightweight surface for work that lives in one repo and may have no
+formal specification.
+
+## Why it exists
+
+AI coding agents do well on narrow, well-scoped work and poorly on large, vague
+work. The loop's bet is that the leverage is in the *planning*: if you remove
+ambiguity up front — crisp work units with hard boundaries and machine-checkable
+verification — then execution can run with a fresh agent per unit, re-grounding
+from durable files each time rather than accumulating context drift. It is the
+[Ralph loop](docs/concepts/ralph-lineage.md) idea applied at work-unit granularity, with
+the planning rigor Ralph's bare task list lacks.
+
+## How it works (in one minute)
+
+- A **feature** lives in `.specfuse/features/FEAT-YYYY-NNNN-slug/`, with a
+  `PLAN.md` (the task graph: gate order, work-unit membership, dependencies),
+  one `GATE-NN.md` per gate, and one `WU-*.md` per work unit (frontmatter + the
+  prompt body a fresh session receives). The loop also handles *orchestrated*
+  features dispatched by the Specfuse Orchestrator, identified by
+  `INIT-YYYY-NNNN/FNN` IDs — the loop treats both namespaces identically; only
+  the ID root differs. Use `.specfuse/scripts/gh_features.py` to discover a
+  target repo's open `specfuse:feature` issues as feature candidates; use
+  `.specfuse/scripts/adopt_feature.py <repo> <issue-number>` (or the
+  interactive `/adopt-feature` skill) to scaffold a dispatchable feature
+  folder from a picked issue.
+- The **driver** (`.specfuse/scripts/loop.py`) walks the current gate's ready
+  work units, dispatches each as a fresh `claude -p` session, runs the unit's
+  verification itself as the exit oracle, and commits one squashed,
+  trailer-carrying commit per unit. A failed gate is retried with a fresh
+  session carrying the failure evidence, up to three attempts, then escalated.
+- Each gate ends with a **closing sequence** so reflection, a durable
+  cross-feature `LEARNINGS.md`, documentation, and *drafting the next gate* all
+  happen systematically. Non-terminal gates use a two-WU form
+  (`close-intermediate` + `plan-next`); the terminal gate uses a single `close`
+  WU. A legacy four-WU form (`retrospective → lessons → docs → plan-next`) is
+  accepted but emits a lint warning.
+- The gate is the **human boundary.** The driver runs unattended within a gate
+  and stops at it; you review the next gate's draft and arm it. (Under automatic
+  mode, safe gates can self-arm; the dangerous edges always pull you back in —
+  see the methodology doc.)
+
+## Quickstart
+
+In a target single-repo project:
+
+**Contributing to this repo?** Run `./scripts/install-hooks.sh` once after
+cloning to enable the pre-push hook (runs `scripts/smoke-test.sh` — same
+checks CI runs — before each `git push`). Bypass with `git push --no-verify`.
+
+The driver installs from PyPI and the skills from the Claude Code marketplace:
+
+```bash
+pip install specfuse-loop                       # the driver: `specfuse-loop` on PATH
+# in Claude Code: skills under the /specfuse: namespace
+#   /plugin marketplace add specfuse/specfuse
+#   /plugin install specfuse@specfuse
+
+# scaffold a target repo's .specfuse/ state (templates, rules, verification.yml)
+./init.sh /path/to/your-project                 # legacy installer (v1.0; removed in v1.1)
+
+cd /path/to/your-project
+$EDITOR .specfuse/verification.yml              # match the `code` gates to your stack
+# author your first feature folder under .specfuse/features/ from .specfuse/templates/
+specfuse-loop --dry-run                          # or: python .specfuse/scripts/loop.py --dry-run
+specfuse-loop
+```
+
+> **Distribution (FEAT-2026-0019).** Code ships via pip (`specfuse-loop`), the
+> `specfuse` umbrella CLI bridges pip ↔ plugin (`specfuse upgrade`), and Claude
+> assets ship via the [`specfuse/specfuse`](https://github.com/specfuse/specfuse)
+> marketplace. `init.sh` remains the scaffold bootstrap (laying down `.specfuse/`
+> state) until pip-native scaffolding lands; it prints a deprecation banner.
+
+> **One driver per working tree.** The driver holds an exclusive advisory lock on
+> `.specfuse/.loop.lock` for the duration of a run; a second driver targeting the
+> same checkout exits immediately with a clear error message. To run two features
+> in parallel, use separate `git worktree` checkouts — each gets its own lock.
+> `--dry-run` is exempt and may run alongside a live driver.
+
+This repository is also a **self-demonstrating reference installation**: its own
+`.specfuse/` contains a worked example feature
+(`features/FEAT-2026-0001-health-endpoint/`). From the repo root you can run:
+
+```bash
+python .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint
+python .specfuse/scripts/loop.py --dry-run
+```
+
+## Layout
+
+```
+specfuse-loop/
+├── LICENSE  NOTICE  CONTRIBUTING.md  README.md  .gitignore
+├── init.sh                      scaffold .specfuse/ into a target repo
+├── docs/
+│   ├── getting-started.md       narrated first-feature + operator walkthrough
+│   ├── methodology.md           the gate-cycle contract (shared with the orchestrator)
+│   ├── skills.md                the skills catalog, ordered by lifecycle phase
+│   ├── concepts/                why it exists; orchestrator mapping
+│   │   ├── ralph-lineage.md     the Ralph / Gas Town lineage
+│   │   └── architecture-addendum-gates-and-iterative-planning.md
+│   └── dev/                     internal working notes (not user-facing)
+└── .specfuse/                   canonical scaffold + worked example
+    ├── README.md
+    ├── roadmap.template.md  verification.yml.example  LEARNINGS.md
+    ├── rules/result-contract.md
+    ├── skills/verification/SKILL.md
+    ├── scripts/{loop.py, lint_plan.py, gh_features.py, adopt_feature.py, gh_backend.py}
+    ├── templates/{PLAN,GATE,WU}.template.md
+    └── features/FEAT-2026-0001-health-endpoint/   (the worked example)
+```
+
+`init.sh` also ships the durable docs — `methodology.md`, `skills.md`, and
+`concepts/` — into a target's `.specfuse/docs/`, so an initialized repo is
+self-documenting without this checkout.
+
+## Status
+
+Early but exercised. The driver, linter, parsing, dependency ordering, draft/arm
+gating, the deterministic auto-close predicate, and verification wiring are all
+tested, and the loop dogfoods itself — its own `.specfuse/features/` holds 20+
+features taken through the full gate cycle, including multi-gate features whose
+forward-design model (each gate's `plan-next` drafts the next) has held across
+four consecutive gates.
+
+What works today: single-feature and orchestrator-dispatched features; adopting a
+GitHub `specfuse:feature` issue into a dispatchable folder; GitHub issue-label
+state transitions for adopted features; per-gate auto-close on clean runs with a
+full-ceremony fallback when a gate goes off-plan; and a single-driver working-tree
+lock so two drivers can't corrupt one checkout.
+
+Expect rough edges. The interfaces (WU contract, RESULT block, correlation-ID
+scheme, `verification.yml` shape) are stable; tooling around them is still
+hardening.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

specfuse_loop-0.2.0/pyproject.toml

@@ -0,0 +1,63 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "specfuse-loop"
+version = "0.2.0"
+description = "Local-first executor for the Specfuse Plan + Work Unit gate-cycle methodology."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [
+  { name = "Specfuse contributors" },
+]
+keywords = ["specfuse", "agents", "planning", "ralph", "gate-cycle"]
+classifiers = [
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Intended Audience :: Developers",
+  "Topic :: Software Development",
+]
+# The loop driver and linter have no runtime dependencies — YAML parsing is
+# done by .specfuse/scripts/_miniyaml.py against the documented subset, using
+# only the Python 3 standard library.
+dependencies = []
+
+# Dev tooling for this repo's own `code` gates (see .specfuse/verification.yml
+# and scripts/smoke-test.sh). PyYAML is dev-only: the equivalence tests for
+# _miniyaml compare its output against yaml.safe_load on every real file.
+# ruff/bandit/coverage are for the reference implementation's own gates.
+[project.optional-dependencies]
+dev = [
+  "PyYAML>=6.0",
+  "ruff>=0.6",
+  "bandit>=1.7",
+  "coverage>=7.0",
+  "jsonschema>=4.0",
+]
+
+[project.urls]
+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`).
+[tool.ruff]
+target-version = "py310"
+
+[project.scripts]
+specfuse-loop = "specfuse.loop.loop:main"
+specfuse-lint = "specfuse.loop.lint_plan:main"
+
+[tool.setuptools.packages.find]
+# Ship ONLY the specfuse namespace package. Without this scope, setuptools'
+# auto-discovery sweeps tests/, docs/, and scripts/ into the wheel. The driver's
+# data (templates, rules, features) lives in the consumer's `.specfuse/`, not in
+# the wheel, so the package is pure code.
+include = ["specfuse*"]
+namespaces = true

specfuse_loop-0.2.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

specfuse_loop-0.2.0/specfuse/loop/__init__.py

@@ -0,0 +1,5 @@
+#
+# Copyright 2026 Specfuse Contributors
+# Licensed under the Apache License, Version 2.0. See LICENSE.
+#
+"""specfuse.loop — the Specfuse loop driver package."""