devflow-toolkit 0.3.0__tar.gz

devflow_toolkit-0.3.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+dist/
+build/
+*.egg-info/

devflow_toolkit-0.3.0/CHANGELOG.md

@@ -0,0 +1,146 @@
+# Changelog
+
+All notable changes to DevFlow Toolkit are documented in this file.
+
+## 0.3.0 - 2026-11-02
+
+First public release. Persistent Discovery decides whether a request is
+ready to become a specification. This release still covers the
+discovery and specification stages only.
+
+### Added
+
+- Persistent `.devflow/specs/<id>-<slug>/discovery.yaml` records with
+  questions, categories, blocking flags, answers and acceptance
+  metadata.
+- Question classification for functional scope, user-visible behaviour,
+  data and persistence, security and authentication, external
+  integrations, architecture boundaries, dependencies and deployment.
+- Blocking and non-blocking questions. Non-blocking questions may
+  remain pending without preventing specification generation.
+- Proposed assumptions with `source: agent_default` and explicit
+  `pending_acceptance` / `accepted` status. DevFlow never accepts an
+  assumption on the user's behalf.
+- `devflow spec --continue <id>` to resume a change across sessions.
+- Deterministic Discovery for the `--no-agent` path. It stops when a
+  blocking decision remains and never invents an answer.
+- Workflow status `awaiting_clarification`.
+- Discovery as a registered artifact whose digest is bound into the
+  specification and into `approve --stage spec`.
+- Approval binding to the declared architecture digest when a manifest
+  applies.
+- Invalidation and archiving when Discovery changes before approval:
+  the old specification is marked stale, preserved under `history/`,
+  and regenerated with a new digest.
+- Interactive Discovery prompt for harnesses that can record answers.
+- Tests for Discovery classification, persistence, blocking, resume,
+  invalidation, non-blocking questions, legacy compatibility and
+  interactive recording.
+
+### Changed
+
+- Package version is `0.3.0`.
+- `spec` without `--continue` always creates a new change.
+- `spec --continue` refuses an already approved or advanced change.
+- `approve --stage spec` rejects incomplete Discovery and binds the
+  specification, Discovery and manifest digests.
+- Legacy `0.2.0` changes without `discovery.yaml` remain approvable
+  with a warning.
+- `status` reports Discovery status, questions, answers and assumption
+  acceptance.
+- Prompts require the Discovery digest in the generated specification.
+
+### Known limitations
+
+- Planning, implementation and review workflows are still not
+  implemented.
+- Greenfield does not scaffold projects or generate application code.
+- DevFlow does not certify architectural quality.
+- Only OpenCode has been verified end-to-end.
+- POSIX only; Windows is not supported.
+
+## 0.2.0 - 2026-11-01 (internal, unpublished)
+
+Greenfield specification support. This release remains an internal
+baseline and was not published to PyPI.
+
+### Added
+
+- `ProjectMode` with `existing` (default) and `greenfield` contexts.
+- `--project-mode` on `init` and `spec`, with per-run override and no
+  silent mode switching.
+- `.devflow/architecture.yaml` as a persistent, reviewable declared
+  architecture manifest separate from `config.yaml`.
+- Safe manifest template creation that never overwrites user files.
+- Structural manifest validation for required values, duplicate names,
+  unknown references, dependency-cycle warnings, invalid YAML, symlink
+  escapes and size limits.
+- Greenfield context and prompt selection without extracting a new
+  workflow abstraction.
+- Deterministic Greenfield specifications with target architecture,
+  architecture decisions and risks, and the 11-section contract.
+- `Appendix A: Declared Architecture Manifest` with the manifest digest
+  in the generated specification and context.
+- Existing-mode specifications treat a present manifest as an
+  architectural constraint.
+- Backward-compatible configuration: projects without `project.mode`
+  load as `existing`.
+
+### Changed
+
+- Package version is `0.2.0`.
+- Existing-mode specifications record the project mode.
+- The agent-output cleaner preserves a trailing fenced manifest
+  appendix instead of stripping it.
+
+### Known limitations
+
+- Planning, implementation and review workflows are still not
+  implemented.
+- Greenfield does not scaffold projects or generate application code.
+- DevFlow does not certify architectural quality.
+- Only OpenCode has been verified end-to-end.
+- POSIX only; Windows is not supported.
+
+## 0.1.0 - 2026-10-31
+
+Initial MVP release. This release covers the specification stage only.
+
+### Added
+
+- Installable `devflow` CLI with `init`, `spec`, `status`, `approve` and
+  `version` commands.
+- Project detection for Python, JavaScript/TypeScript, Go, Rust, PHP,
+  Ruby, Java and common frameworks and databases.
+- Bundled base, Django, FastAPI and AI/RAG profiles.
+- Project constitution installation without overwriting existing files.
+- Project configuration with contained paths and managed file markers.
+- Harness-independent specification workflow with deterministic static
+  analysis, context generation and structural validation.
+- OpenCode integration, verified end-to-end in non-interactive mode.
+- Integration scaffolds for Codex, Claude Code and Kiro (unverified in
+  this release).
+- Digest-bound specification approvals.
+- Append-only `events.jsonl` event log with `workflow.yaml` projection,
+  full replay, semantic validation, stale detection and recovery.
+- Atomic artifact, configuration and integration-file writes.
+- Per-change locks and serialized specification id allocation.
+- Explicit rejection of paths and symlinks that escape the project.
+
+### Security
+
+- Constitution document names must be plain file names inside the
+  constitution directory.
+- Symlinks and project files resolving outside the project root are
+  rejected or ignored during detection and analysis.
+- Managed integration files cannot follow symlinks outside the project.
+- Existing user files, specifications and approvals are preserved.
+
+### Known limitations
+
+- Planning, implementation and review workflows are not implemented.
+- Only OpenCode has been verified end-to-end.
+- Interactive harness mode is implemented but not part of the verified
+  release path.
+- POSIX only; Windows is not supported.
+- Static analysis is heuristic and requires human review.

devflow_toolkit-0.3.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 DevFlow contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.