loopengt 0.1.0__tar.gz

loopengt-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,94 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    name: Lint & Type Check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: uv pip install --system -e ".[dev]"
+
+      - name: Ruff check
+        run: ruff check src/ tests/
+
+      - name: Ruff format check
+        run: ruff format --check src/ tests/
+
+      - name: Mypy
+        run: mypy src/loopengt/ --ignore-missing-imports
+
+  test:
+    name: Test (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv pip install --system -e ".[dev]"
+
+      - name: Run tests
+        run: pytest tests/ -v --tb=short --cov=loopengt --cov-report=xml
+
+      - name: Upload coverage
+        if: matrix.python-version == '3.12'
+        uses: codecov/codecov-action@v4
+        with:
+          file: coverage.xml
+
+  build:
+    name: Build Package
+    runs-on: ubuntu-latest
+    needs: [lint, test]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Build
+        run: |
+          uv build
+          for dir in plugins/*/; do
+            if [ -f "$dir/pyproject.toml" ]; then
+              echo "Building plugin in $dir..."
+              uv build --directory "$dir" --out-dir dist/
+            fi
+          done
+
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/

loopengt-0.1.0/.github/workflows/workflow.yml

@@ -0,0 +1,55 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Build package
+        run: |
+          uv build
+          for dir in plugins/*/; do
+            if [ -f "$dir/pyproject.toml" ]; then
+              echo "Building plugin in $dir..."
+              uv build --directory "$dir" --out-dir dist/
+            fi
+          done
+
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - name: Download artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          skip-existing: true

loopengt-0.1.0/.gitignore

@@ -0,0 +1,165 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.pyc
+*.pyo
+*.pyd
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+/*.manifest
+/*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if delegates have different python versions passed
+#   to --python flag, pipenv will throw an warning and refuse to install dependencies.
+#   In that case, uncomment the next line to ignore Pipfile.lock.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipenv, Pyproject.toml should be version controlled.
+#   poetry.lock and poetry.toml may be ignored or committed.
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Poetry and Pipenv, pyproject.toml should be version controlled.
+#   pdm.lock may be ignored or committed.
+#pdm.lock
+.pdm-plugins/
+.pdm-python
+
+# PEP 582; used by e.g. github.com/lincolnloop/layman and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site/
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+.idea/
+
+# VS Code
+.vscode/
+
+# LOOPENGT run traces and temporary databases
+.loopengt/runs/
+.loopengt/*.db
+.loopengt/*.sqlite
+loop.yaml
+LOOP_DESIGN.md

loopengt-0.1.0/.loopengt/config.toml

@@ -0,0 +1,20 @@
+# Loop Engineering configuration
+
+[general]
+default_pattern = "sequential"
+trace_format = "jsonl"
+
+[llm]
+provider = "openai"
+model = "gpt-4o"
+temperature = 0.7
+# api_key_env = "OPENAI_API_KEY"
+
+[mcp]
+transport = "stdio"
+host = "localhost"
+port = 8765
+
+[tracing]
+backend = "jsonl"
+directory = "runs"

loopengt-0.1.0/.loopengt/prompts/LOOPENGT.md

@@ -0,0 +1,12 @@
+# LOOPENGT — Loop Engineering Architect
+
+You are the Loop Engineering Architect.  Given a goal, you design
+the optimal agent loop by selecting the right pattern, defining
+agents, steps, tools, and policies.
+
+## Principles
+1. Minimal agents — each must justify its existence
+2. Clear handoff contracts between steps
+3. Verification gates at critical boundaries
+4. Graceful degradation on failure
+5. Observable by default (structured traces)

loopengt-0.1.0/ACCEPTANCE_TESTS.md

@@ -0,0 +1,36 @@
+# Acceptance Tests: LOOPENGT Platform
+
+This document outlines the strict criteria that must be met before the platform is considered fully implemented and ready for release.
+
+## General Requirements
+1. `uv pip install -e .` (or `pip install -e .`) works without errors.
+2. `loopengt` CLI is globally accessible.
+3. CI passes lint (`ruff check`), type-check (`mypy`), tests (`pytest`), and build.
+4. Docs explain architecture, plugin development, and MCP usage.
+
+## CLI & Core Flow
+- [ ] `loopengt init` successfully scaffolds the `.loopengt/` directory with `config.toml`, prompts, and templates.
+- [ ] `loopengt design "code review loop"` queries the configured LLM and generates a valid `LOOP_DESIGN.md` and `loop.yaml`.
+- [ ] `loopengt run loop.yaml` parses the generated config, initializes the agents, invokes the LLM, and successfully runs the loop.
+- [ ] Execution gracefully halts upon hitting a defined stop condition or turn limit.
+- [ ] Execution traces are saved correctly to `.loopengt/runs/<id>.json`.
+- [ ] `loopengt trace <run_id>` reads the trace and outputs it to the console in a human-readable format.
+- [ ] `loopengt eval <run_id>` reads the trace, queries an LLM evaluator, and reports the run score.
+
+## Templates
+- [ ] At least one built-in template (e.g., `planner-executor`) can be executed end-to-end without failing.
+- [ ] `loopengt template list` returns the built-in templates.
+
+## MCP Functionality
+- [ ] `loopengt mcp serve` starts a standard stdio MCP server.
+- [ ] External clients (like Cursor or Claude Code) can list exposed tools (`design_loop`, `run_loop`).
+- [ ] Executing `run_loop` via MCP successfully triggers a background run and returns the run ID.
+
+## Plugin & Adapter Ecosystem
+- [ ] `loopengt doctor` detects loaded plugins and adapters.
+- [ ] The terminal adapter works out-of-the-box (renders rich output during `loopengt run`).
+- [ ] Skeleton structures exist for `Antigravity`, `Cursor`, `Claude Code`, and `Codex` adapters in the `plugins/` directory.
+
+## Quality Gates
+- **Code Quality**: No `type: ignore` without justification.
+- **Test Coverage**: > 80% coverage in `src/loopengt/core/runtime/`.

loopengt-0.1.0/ARCHITECTURE.md

@@ -0,0 +1,91 @@
+# Architecture
+
+## Overview
+
+LOOPENGT is a framework for designing, orchestrating, and evaluating agent
+loops.  It follows a layered architecture with clear separation of concerns.
+
+```
+┌─────────────────────────────────────────────────────┐
+│                    CLI / IDE Adapters                │
+│          (Typer, Cursor, Claude Code, Codex)         │
+├─────────────────────────────────────────────────────┤
+│                      MCP Server                      │
+│              (FastMCP — tools, resources, prompts)    │
+├─────────────────────────────────────────────────────┤
+│                    Plugin System                     │
+│        (Entry-point discovery, hot-reload)            │
+├─────────────────────────────────────────────────────┤
+│                   Core Runtime                       │
+│    ┌───────────┬──────────┬──────────┬────────────┐  │
+│    │ Executor  │Scheduler │ Handoff  │ Checkpoint │  │
+│    └───────────┴──────────┴──────────┴────────────┘  │
+├─────────────────────────────────────────────────────┤
+│                    Core Models                       │
+│    LoopSpec │ AgentRole │ ToolSpec │ Policy │ State  │
+├─────────────────────────────────────────────────────┤
+│                Tracing & Memory                      │
+│    Events │ TraceStore │ Exporters │ MemoryStore     │
+├─────────────────────────────────────────────────────┤
+│                     Storage                          │
+│              SQLite │ JSONL                          │
+└─────────────────────────────────────────────────────┘
+```
+
+## Core Models
+
+All configuration is expressed as **Pydantic v2 models** with strict
+validation.  The central model is `LoopSpec`, which is the single source
+of truth for a loop's configuration.
+
+### Key Models
+
+| Model | Purpose |
+|-------|---------|
+| `LoopSpec` | Complete loop definition — agents, steps, tools, policies |
+| `AgentRole` | Agent identity, capabilities, LLM config |
+| `ToolSpec` | Tool definition (MCP, function, or built-in) |
+| `Policy` | Execution constraints — turns, retries, timeouts, gates |
+| `LoopState` | Mutable runtime state for a running loop |
+
+## Orchestration Patterns
+
+The executor supports five patterns:
+
+1. **Sequential** — steps execute in declaration order
+2. **Supervisor-Worker** — a supervisor decides which worker to invoke next
+3. **Parallel Fan-out** — independent steps execute concurrently
+4. **Handoff** — agents pass enriched context to the next agent
+5. **Evaluator-Optimizer** — iterative quality improvement loop
+
+## Plugin Architecture
+
+Plugins are discovered via Python entry points:
+
+- `loopengt.adapters` — IDE/environment adapters
+- `loopengt.mcp_tools` — Additional MCP tools
+- `loopengt.templates` — Loop template packs
+- `loopengt.skills` — Agent skills
+- `loopengt.verifiers` — Custom verification gates
+
+## Data Flow
+
+```
+Goal → LOOPENGT Design → LoopSpec (YAML)
+                              │
+                    LoopExecutor.execute()
+                              │
+                 ┌────────────┼────────────┐
+                 │            │            │
+              Step 1       Step 2       Step N
+            (Agent A)    (Agent B)    (Agent C)
+                 │            │            │
+                 └────────────┼────────────┘
+                              │
+                    LoopState (completed)
+                              │
+                 ┌────────────┼────────────┐
+                 │            │            │
+              Trace        Metrics      Export
+             (JSONL)       (Evals)    (OTel/MD)
+```