agentic-dev-loop 0.11.0__tar.gz → 0.11.1__tar.gz

{agentic_dev_loop-0.11.0/src/agentic_dev_loop.egg-info → agentic_dev_loop-0.11.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentic-dev-loop
-Version: 0.11.0
+Version: 0.11.1
 Summary: Turn an LLM into a gated, sandboxed, resumable construction loop over your codebase.
 Author: Luke Wilson
 License-Expression: Apache-2.0
@@ -51,13 +51,7 @@ trusted actions - and `agentic-dev-loop` runs it end to end: agent and command s
 kernel-level sandboxing via Docker, verdicts route the graph, every boundary is
 checkpointed, and nothing gets committed until every gate passes.
 
-```mermaid
-flowchart LR
-    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
-    test -- fail --> dev
-    review -- fail --> dev
-    qa -- fail --> dev
-```
+![The live graph view - pipeline graph with fail loopbacks, summary tiles, per-stage consoles, and event log](https://raw.githubusercontent.com/lukedawilson/agentic-dev-loop/main/docs/viz-pipeline.png)
 
 - **A tool, not a wiring project.** One CLI entry point, opinionated defaults,
   fixed safety policies. You write the pipeline and the agent definitions -
@@ -175,7 +169,13 @@ the next startup retries it. Pass
 
 **What a run looks like** (the shipped self-loop example):
 
-![The live graph view - pipeline stages with verdict badges, retry cycles, and per-stage consoles](docs/viz-screenshot.png)
+```mermaid
+flowchart LR
+    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
+    test -- fail --> dev
+    review -- fail --> dev
+    qa -- fail --> dev
+```
 
 1. **dev** - the dev agent works with full context (loaded docs + shared files).
    Its edits are untracked; only declared `produces:` files are hygiene-tracked.

{agentic_dev_loop-0.11.0 → agentic_dev_loop-0.11.1}/README.md

@@ -7,13 +7,7 @@ trusted actions - and `agentic-dev-loop` runs it end to end: agent and command s
 kernel-level sandboxing via Docker, verdicts route the graph, every boundary is
 checkpointed, and nothing gets committed until every gate passes.
 
-```mermaid
-flowchart LR
-    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
-    test -- fail --> dev
-    review -- fail --> dev
-    qa -- fail --> dev
-```
+![The live graph view - pipeline graph with fail loopbacks, summary tiles, per-stage consoles, and event log](https://raw.githubusercontent.com/lukedawilson/agentic-dev-loop/main/docs/viz-pipeline.png)
 
 - **A tool, not a wiring project.** One CLI entry point, opinionated defaults,
   fixed safety policies. You write the pipeline and the agent definitions -
@@ -131,7 +125,13 @@ the next startup retries it. Pass
 
 **What a run looks like** (the shipped self-loop example):
 
-![The live graph view - pipeline stages with verdict badges, retry cycles, and per-stage consoles](docs/viz-screenshot.png)
+```mermaid
+flowchart LR
+    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
+    test -- fail --> dev
+    review -- fail --> dev
+    qa -- fail --> dev
+```
 
 1. **dev** - the dev agent works with full context (loaded docs + shared files).
    Its edits are untracked; only declared `produces:` files are hygiene-tracked.

{agentic_dev_loop-0.11.0 → agentic_dev_loop-0.11.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "agentic-dev-loop"
-version = "0.11.0"
+version = "0.11.1"
 description = "Turn an LLM into a gated, sandboxed, resumable construction loop over your codebase."
 readme = "README.md"
 requires-python = ">=3.12"

{agentic_dev_loop-0.11.0 → agentic_dev_loop-0.11.1/src/agentic_dev_loop.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentic-dev-loop
-Version: 0.11.0
+Version: 0.11.1
 Summary: Turn an LLM into a gated, sandboxed, resumable construction loop over your codebase.
 Author: Luke Wilson
 License-Expression: Apache-2.0
@@ -51,13 +51,7 @@ trusted actions - and `agentic-dev-loop` runs it end to end: agent and command s
 kernel-level sandboxing via Docker, verdicts route the graph, every boundary is
 checkpointed, and nothing gets committed until every gate passes.
 
-```mermaid
-flowchart LR
-    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
-    test -- fail --> dev
-    review -- fail --> dev
-    qa -- fail --> dev
-```
+![The live graph view - pipeline graph with fail loopbacks, summary tiles, per-stage consoles, and event log](https://raw.githubusercontent.com/lukedawilson/agentic-dev-loop/main/docs/viz-pipeline.png)
 
 - **A tool, not a wiring project.** One CLI entry point, opinionated defaults,
   fixed safety policies. You write the pipeline and the agent definitions -
@@ -175,7 +169,13 @@ the next startup retries it. Pass
 
 **What a run looks like** (the shipped self-loop example):
 
-![The live graph view - pipeline stages with verdict badges, retry cycles, and per-stage consoles](docs/viz-screenshot.png)
+```mermaid
+flowchart LR
+    dev["agent: dev"] --> test{{"test gate"}} --> review["agent: review"] --> qa["agent: qa"] --> commit["action: commit"]
+    test -- fail --> dev
+    review -- fail --> dev
+    qa -- fail --> dev
+```
 
 1. **dev** - the dev agent works with full context (loaded docs + shared files).
    Its edits are untracked; only declared `produces:` files are hygiene-tracked.