devsper 2.1.6__tar.gz → 2.1.7__tar.gz

devsper-2.1.7/.github/workflows/release-on-tag.yml

@@ -0,0 +1,56 @@
+# When you push a version tag (e.g. v1.6.0), create a GitHub Release and publish to PyPI.
+# Note: Creating a release with GITHUB_TOKEN does NOT trigger other workflows.
+# Docs versioning and deploy live in the docs repo.
+#
+# Usage:
+#   git tag v1.6.0
+#   git push origin v1.6.0
+#
+# PyPI: Add a Trusted Publisher on PyPI with workflow filename release-on-tag.yml (job: pypi-publish).
+
+name: Release on tag
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Get version from tag
+        id: version
+        run: |
+          V="${GITHUB_REF#refs/tags/v}"
+          echo "version=$V" >> $GITHUB_OUTPUT
+          echo "Tag: v$V"
+
+      - name: Extract changelog section
+        run: |
+          V="${{ steps.version.outputs.version }}"
+          awk -v ver="$V" '
+            $0 ~ "^## \\[" ver "\\]" { found=1; next }
+            found && /^## \[/ { exit }
+            found { print }
+          ' CHANGELOG.md > release_notes.md
+          [ -s release_notes.md ] || echo "See CHANGELOG.md for details." > release_notes.md
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          name: v${{ steps.version.outputs.version }}
+          body_path: release_notes.md
+          draft: false
+          generate_release_notes: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+

{devsper-2.1.6 → devsper-2.1.7}/.gitignore

@@ -24,7 +24,7 @@ env/
 registry/.env
 
 # Hivemind runtime and output
-.hivemind/
+.devsper/
 .events/
 
 # Example outputs (generated)
@@ -33,12 +33,6 @@ examples/output/
 # MkDocs build output
 site/
 
-# Docusaurus (website/)
-website/node_modules/
-website/build/
-website/.docusaurus/
-website/.cache/
-
 # System
 .DS_Store
 Thumbs.db
@@ -55,5 +49,6 @@ tmp
 
 node_modules
 
-# Rust (worker crate)
+# Rust (workspace and worker crate)
+target/
 worker/target/

{devsper-2.1.6 → devsper-2.1.7}/CHANGELOG.md

@@ -7,6 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.1.7] — 2026-03-18
+
+### Added
+
+- **Multi-format run export** — New `devsper export-runs` command exports run history bundles to Markdown, reStructuredText, LaTeX, BibTeX, HTML, JSON, and DOCX (when `python-docx` is available), with per-run markdown artifacts under `runs/`.
+- **Dual PDF pipelines** — Export supports both LaTeX (`pdflatex`) and HTML (`wkhtmltopdf`/`pandoc`) PDF generation, plus manifest reporting for generated outputs and pipeline errors.
+- **Branding-aware documents** — Export templates now consume branding tokens and logo assets from `homepage` for consistent "docproc/devsper" presentation.
+- **Export docs and tests** — Added `docs/export-runs.md` and automated tests covering format generation and event-path resolution.
+
+### Changed
+
+- **Distributed run stability** — Controller dispatch/claim handling is more robust (slot-aware routing, shorter unclaimed-task requeue path, safer task-completion fallback parsing) to reduce stuck runs.
+- **Snapshot restore safety** — Leader restore now avoids rolling back to stale/equivalent snapshots, reducing repeated re-dispatch loops.
+- **HITL/MCQ UX** — Clarification prompts now use interactive numeric selection with a custom answer option and explicit "answer received" feedback.
+- **Run summary accuracy** — Duration/cost aggregation now uses event-log grounded values for more reliable final summaries.
+- **CLI/TUI branding and noise** — Theme/style namespace now prefers `devsper.*` aliases, and TUI logging suppression reduces controller log flooding during active runs.
+
 ## [2.1.6] — 2026-03-14
 
 ### Added

{devsper-2.1.6 → devsper-2.1.7}/CONTRIBUTING.md

@@ -36,7 +36,7 @@ Run a subset: `uv run python -m pytest tests/test_swarm.py -v`. Version-specific
 
 - Keep PRs focused (one feature or fix when possible).
 - Ensure all tests pass and lint/format checks succeed.
-- Update docs in `website/docs/` if you change user-facing behavior or add features (site: [docs.devsper.com](https://docs.devsper.com)).
+- Update docs in the **docs** repo if you change user-facing behavior or add features (site: [docs.devsper.com](https://docs.devsper.com)).
 - For new tools or providers, add a short note in the relevant doc (e.g. [tools](https://docs.devsper.com/docs/tools), [providers](https://docs.devsper.com/docs/providers)).
 
 ## Adding tools or features