agentic-development-framework 0.1.0__tar.gz

agentic_development_framework-0.1.0/.gitignore

@@ -0,0 +1,26 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.venv/
+venv/
+build/
+dist/
+
+# Local framework runtime data
+.agentic/
+
+# Local secrets and editor metadata
+.env
+.env.*
+!.env.example
+.idea/
+.vscode/
+

agentic_development_framework-0.1.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## Unreleased
+
+### Added
+
+- Initial package and CLI foundation.
+- Validated YAML configuration models.
+- Console logging and structured JSONL event logging.
+- Phase 1 unit tests and project documentation.
+- Safe, idempotent project initialization for new and existing repositories.
+- Project, Git, technology, and package-manager discovery.
+- Conflict proposals and human-readable initialization reports.
+- Atomic, hash-verified requirements ingestion with immutable source versions.
+- Requirement-ID traceability, duplicate detection, version comparison, and impact reports.
+- Requirements management unit, integration, and acceptance coverage.
+- SQLite runtime state, JSON snapshots, events, integrity-checked checkpoints, and recovery.
+- Central lifecycle command registry with CLI and chat-command mappings.
+- Canonical workflow, policy, and eleven-agent registry generation.
+- Documented Codex skill/instructions and Antigravity rule generation.
+- Wheel-installed Django + React release acceptance harness.
+- Single-source package versioning and explicit wheel/source-distribution content rules.
+- Installed-distribution resource and full-suite regression tests.
+- Python 3.11–3.13 CI plus tag-only PyPI OIDC Trusted Publishing.
+- Maintainer checklist for building, inspecting, testing, and publishing releases.
+

agentic_development_framework-0.1.0/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 Agentic Development Framework 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.
+

agentic_development_framework-0.1.0/PKG-INFO

@@ -0,0 +1,175 @@
+Metadata-Version: 2.4
+Name: agentic-development-framework
+Version: 0.1.0
+Summary: A local-first framework for agentic software development workflows.
+Project-URL: Homepage, https://github.com/Badsha-ugv/ide-agentic-development-framework
+Project-URL: Repository, https://github.com/Badsha-ugv/ide-agentic-development-framework
+Project-URL: Issues, https://github.com/Badsha-ugv/ide-agentic-development-framework/issues
+Project-URL: Changelog, https://github.com/Badsha-ugv/ide-agentic-development-framework/blob/main/CHANGELOG.md
+Author: Agentic Development Framework contributors
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Requires-Dist: pydantic<3,>=2.7
+Requires-Dist: pyyaml<7,>=6.0
+Requires-Dist: typer<1,>=0.12
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.2; extra == 'dev'
+Requires-Dist: pytest-cov<8,>=5.0; extra == 'dev'
+Requires-Dist: pytest<9,>=8.0; extra == 'dev'
+Requires-Dist: ruff<1,>=0.8; extra == 'dev'
+Requires-Dist: twine<7,>=5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Agentic Development Framework
+
+Agentic Development Framework (ADF) is a local-first foundation for persistent,
+human-controlled software development workflows driven through IDE coding agents.
+
+The project is being delivered incrementally. The current implementation provides the
+installable package, strict configuration validation, structured logging, safe project
+initialization, immutable requirements versioning, SQLite workflow state, recovery checkpoints,
+lifecycle commands, and Codex/Antigravity project configuration.
+
+## Requirements
+
+- Python 3.11 or newer
+
+## Installation
+
+Install the latest released version from PyPI:
+
+```bash
+python -m pip install agentic-development-framework
+adt --help
+```
+
+## Development setup
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e '.[dev]'
+pytest
+```
+
+## CLI
+
+Both entry points expose the same application:
+
+```bash
+adt --help
+python -m agentic_framework --help
+adt --version
+adt init
+adt config validate path/to/config.yaml
+adt requirements ingest
+adt start
+adt status
+adt pause
+adt resume
+adt continue
+adt stop
+adt review
+adt approve requirements_review
+adt revise requirements_review "Clarify the acceptance criteria"
+adt tasks
+```
+
+The validation command prints the normalized configuration as YAML and exits with code 2
+for missing, malformed, or invalid configuration.
+
+## Project initialization
+
+Run `adt init` or `python -m agentic_framework init` from the project directory. Initialization:
+
+- detects new and existing projects, common technologies, package managers, and parent Git roots;
+- creates the ADF runtime, requirements, documentation, and IDE discovery directories;
+- installs initial configuration and project guidance without replacing existing files;
+- writes proposed content under `.agentic/proposals/` when a generated file conflicts; and
+- initializes Git only when no repository is already present.
+
+Use `--path DIRECTORY` to target another directory or `--no-git` to suppress Git initialization.
+The operation is idempotent. Its latest report is written to
+`.agentic/reports/initialization.md`.
+
+## Requirements management
+
+Add one or more source files below `requirements/inbox/`, including files in nested folders,
+then run:
+
+```bash
+adt requirements ingest
+```
+
+Each changed submission creates the next directory under `requirements/versions/`. The version
+contains byte-for-byte source copies, SHA-256 hashes, a manifest, consolidated extracted text, a
+requirement index, and initial traceability records. Existing versions are hash-validated before
+use and are never updated. An unchanged inbox is reported as a duplicate without creating a new
+version.
+
+Starting with the second version, ADF compares source files and `REQ-NNN` requirement blocks and
+writes an impact report under `requirements/reports/`. Added, modified, removed, and unchanged
+items are reported separately, along with documentation, architecture, implementation, testing,
+and approval review prompts.
+
+Markdown, text, CSV, TSV, JSON, YAML, and reStructuredText are extracted as UTF-8 text. Other
+formats—including PDF, DOCX, XLSX, and images—are still preserved exactly and recorded with a
+clear unsupported-extraction status. Optional binary-format extractors are future work.
+
+See `docs/REQUIREMENTS_MANAGEMENT.md` for the file contract and safety behavior.
+
+## Runtime state and recovery
+
+Initialization creates `.agentic/database/agentic.db` as the transactional source of truth,
+inspection snapshots under `.agentic/state/`, a JSONL event history, and checkpoint storage.
+Pause and stop persist checkpoints. Resume verifies checkpoint integrity and restores the
+checkpoint stage instead of trusting potentially inconsistent conversational context or snapshot
+files. Mandatory workflow approval stages cannot advance until approval is recorded.
+
+## IDE configuration
+
+ADF generates root `AGENTS.md`, a shared command skill under
+`.agents/skills/agentic-commands/`, and Antigravity rules under `.agents/rules/`. The Codex adapter
+uses the documented root instructions and repository-local skill surfaces. The `.codex/agents/`
+directory contains an informational compatibility note; ADF does not claim an undocumented
+custom-agent file format is automatically discovered.
+
+## Configuration
+
+ADF configuration uses YAML and rejects unknown keys to catch mistakes early:
+
+```yaml
+schema_version: 1
+project:
+  name: example-project
+  mode: auto
+runtime:
+  directory: .agentic
+  log_level: INFO
+ide:
+  enabled:
+    - codex
+policies:
+  allow_network: false
+  allow_destructive_operations: false
+```
+
+Runtime directories must be project-relative and cannot contain parent-directory traversal.
+
+## Logging
+
+`configure_logging()` sets up readable console output and can additionally write a JSONL
+event stream. Reconfiguration is idempotent and only replaces handlers managed by ADF.
+
+See `docs/IMPLEMENTATION_PLAN.md` and `docs/IMPLEMENTATION_PROGRESS.md` for scope and status. The
+maintainer release procedure is documented in `docs/PYPI_RELEASE.md`.

agentic_development_framework-0.1.0/README.md

@@ -0,0 +1,143 @@
+# Agentic Development Framework
+
+Agentic Development Framework (ADF) is a local-first foundation for persistent,
+human-controlled software development workflows driven through IDE coding agents.
+
+The project is being delivered incrementally. The current implementation provides the
+installable package, strict configuration validation, structured logging, safe project
+initialization, immutable requirements versioning, SQLite workflow state, recovery checkpoints,
+lifecycle commands, and Codex/Antigravity project configuration.
+
+## Requirements
+
+- Python 3.11 or newer
+
+## Installation
+
+Install the latest released version from PyPI:
+
+```bash
+python -m pip install agentic-development-framework
+adt --help
+```
+
+## Development setup
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e '.[dev]'
+pytest
+```
+
+## CLI
+
+Both entry points expose the same application:
+
+```bash
+adt --help
+python -m agentic_framework --help
+adt --version
+adt init
+adt config validate path/to/config.yaml
+adt requirements ingest
+adt start
+adt status
+adt pause
+adt resume
+adt continue
+adt stop
+adt review
+adt approve requirements_review
+adt revise requirements_review "Clarify the acceptance criteria"
+adt tasks
+```
+
+The validation command prints the normalized configuration as YAML and exits with code 2
+for missing, malformed, or invalid configuration.
+
+## Project initialization
+
+Run `adt init` or `python -m agentic_framework init` from the project directory. Initialization:
+
+- detects new and existing projects, common technologies, package managers, and parent Git roots;
+- creates the ADF runtime, requirements, documentation, and IDE discovery directories;
+- installs initial configuration and project guidance without replacing existing files;
+- writes proposed content under `.agentic/proposals/` when a generated file conflicts; and
+- initializes Git only when no repository is already present.
+
+Use `--path DIRECTORY` to target another directory or `--no-git` to suppress Git initialization.
+The operation is idempotent. Its latest report is written to
+`.agentic/reports/initialization.md`.
+
+## Requirements management
+
+Add one or more source files below `requirements/inbox/`, including files in nested folders,
+then run:
+
+```bash
+adt requirements ingest
+```
+
+Each changed submission creates the next directory under `requirements/versions/`. The version
+contains byte-for-byte source copies, SHA-256 hashes, a manifest, consolidated extracted text, a
+requirement index, and initial traceability records. Existing versions are hash-validated before
+use and are never updated. An unchanged inbox is reported as a duplicate without creating a new
+version.
+
+Starting with the second version, ADF compares source files and `REQ-NNN` requirement blocks and
+writes an impact report under `requirements/reports/`. Added, modified, removed, and unchanged
+items are reported separately, along with documentation, architecture, implementation, testing,
+and approval review prompts.
+
+Markdown, text, CSV, TSV, JSON, YAML, and reStructuredText are extracted as UTF-8 text. Other
+formats—including PDF, DOCX, XLSX, and images—are still preserved exactly and recorded with a
+clear unsupported-extraction status. Optional binary-format extractors are future work.
+
+See `docs/REQUIREMENTS_MANAGEMENT.md` for the file contract and safety behavior.
+
+## Runtime state and recovery
+
+Initialization creates `.agentic/database/agentic.db` as the transactional source of truth,
+inspection snapshots under `.agentic/state/`, a JSONL event history, and checkpoint storage.
+Pause and stop persist checkpoints. Resume verifies checkpoint integrity and restores the
+checkpoint stage instead of trusting potentially inconsistent conversational context or snapshot
+files. Mandatory workflow approval stages cannot advance until approval is recorded.
+
+## IDE configuration
+
+ADF generates root `AGENTS.md`, a shared command skill under
+`.agents/skills/agentic-commands/`, and Antigravity rules under `.agents/rules/`. The Codex adapter
+uses the documented root instructions and repository-local skill surfaces. The `.codex/agents/`
+directory contains an informational compatibility note; ADF does not claim an undocumented
+custom-agent file format is automatically discovered.
+
+## Configuration
+
+ADF configuration uses YAML and rejects unknown keys to catch mistakes early:
+
+```yaml
+schema_version: 1
+project:
+  name: example-project
+  mode: auto
+runtime:
+  directory: .agentic
+  log_level: INFO
+ide:
+  enabled:
+    - codex
+policies:
+  allow_network: false
+  allow_destructive_operations: false
+```
+
+Runtime directories must be project-relative and cannot contain parent-directory traversal.
+
+## Logging
+
+`configure_logging()` sets up readable console output and can additionally write a JSONL
+event stream. Reconfiguration is idempotent and only replaces handlers managed by ADF.
+
+See `docs/IMPLEMENTATION_PLAN.md` and `docs/IMPLEMENTATION_PROGRESS.md` for scope and status. The
+maintainer release procedure is documented in `docs/PYPI_RELEASE.md`.

agentic_development_framework-0.1.0/docs/ACCEPTANCE_REPORT.md

@@ -0,0 +1,84 @@
+# Release acceptance report
+
+Date: 2026-11-02
+
+## Verdict
+
+The repository passes the local release gates for the `agentic-development-framework` 0.1.0
+alpha release. No package was uploaded, no tag was created, and no remote repository state was
+changed. The remaining work is maintainer review plus the external GitHub environment and PyPI
+Trusted Publisher configuration documented in `PYPI_RELEASE.md`.
+
+This verdict covers the functionality represented by the package and README. Unfinished items in
+the broader framework roadmap remain explicitly marked incomplete in `IMPLEMENTATION_PROGRESS.md`.
+
+## Artifacts and metadata
+
+- Python used for local verification: 3.14.4
+- Wheel: `agentic_development_framework-0.1.0-py3-none-any.whl` (31,613 bytes, 26 entries)
+- Wheel SHA-256: `ed08bb8b3c408c43461da56a37481374f628acea1c73d8c110c32e8930e91394`
+- Source distribution: `agentic_development_framework-0.1.0.tar.gz` (51 entries)
+- Distribution/import/command: `agentic-development-framework` / `agentic_framework` / `adt`
+- Version/Python: `0.1.0` / `>=3.11`
+- Build backend: Hatchling 1.26 through 1.31, producing Core Metadata 2.4
+- License: MIT (SPDX expression and packaged license file)
+
+The wheel contains every Python module and the runtime command skill at
+`agentic_framework/templates/skills/agentic-commands/SKILL.md`. Runtime YAML, policy, workflow,
+agent-registry, Codex, and Antigravity files are deterministically generated from packaged Python
+code. The source distribution contains source, tests, release scripts, documentation, changelog,
+license, README, and build metadata.
+
+Neither archive contains local `.agentic` state, SQLite databases, `.env` files, virtual
+environments, caches, Git data, or nested build artifacts.
+
+## Passed checks
+
+- `ruff check .`: passed.
+- Repository pytest suite: 58 passed with 90.65% branch-aware coverage.
+- The same 58 tests imported the non-editable installed wheel from a disposable environment and
+  passed with 90.65% coverage.
+- `python -m build`: built the wheel and source distribution through isolated environments.
+- `python -m twine check dist/*`: both artifacts passed.
+- Editor diagnostics for changed Python, TOML, and workflow files: none.
+- Wheel and source-distribution member inspection: passed.
+- Secret, database, local-state, cache, virtual-environment, and nested-build exclusion scan:
+  passed.
+
+## Clean-install acceptance
+
+Both the wheel and source distribution were separately installed into disposable, non-editable
+virtual environments outside the repository. Each artifact passed:
+
+- `adt --help`, `adt --version`, and `python -m agentic_framework --help`;
+- valid generated configuration validation;
+- initialization of a completely empty project;
+- initialization of a representative existing Django + React project;
+- Codex instructions, command skill, Antigravity rules, workflow, policies, and eleven-agent
+  registry generation;
+- SQLite schema and expected runtime-state generation;
+- a second initialization with zero newly created files;
+- preservation of a conflicting existing `AGENTS.md` and creation of a proposal;
+- two requirements ingestions, immutable versions, comparison, and impact-report generation; and
+- start, continue, pause, resume, stop, and recovery across CLI processes.
+
+These projects lived under operating-system temporary directories and had no access to package
+files through the repository source tree.
+
+## Release automation
+
+Normal CI runs lint, coverage-enforced tests on Python 3.11, 3.12, and 3.13, builds both artifacts,
+validates them with Twine, runs installed-wheel tests, exercises wheel and source-distribution
+acceptance, and uploads the artifacts.
+
+The separate publish workflow triggers only for pushed `v*` tags. Its publish job depends on all
+test and build gates, uses the protected `pypi` GitHub environment, grants `id-token: write` only
+to that job, downloads the already-tested artifacts, and invokes
+`pypa/gh-action-pypi-publish@release/v1` without a token or password.
+
+## Issue fixed during packaging review
+
+Hatchling 1.32 changed its default to Core Metadata 2.5, which Twine 6.2 rejects. The build-system
+requirement is intentionally constrained to `hatchling>=1.26,<1.32`; Hatchling 1.31 produces Core
+Metadata 2.4, preserves SPDX license metadata, and passes Twine. This can be relaxed after the
+release toolchain supports Metadata 2.5.

agentic_development_framework-0.1.0/docs/IMPLEMENTATION_PLAN.md

@@ -0,0 +1,27 @@
+# Implementation plan
+
+The framework will be delivered in the ten phases defined by the product specification.
+Each phase depends on passing verification for the preceding phase.
+
+1. **Foundation** — package metadata, source layout, CLI entry point, validated configuration,
+   logging, repository guidance, and unit tests.
+2. **Project initialization** — safe and idempotent project discovery and file generation.
+3. **Runtime and persistence** — SQLite state, repositories, events, checkpoints, and snapshots.
+4. **Command system** — shared registry and lifecycle commands for CLI and chat adapters.
+5. **Requirements management** — immutable source versions, extraction boundaries, comparison,
+   impact reporting, and traceability.
+6. **Agent and workflow system** — canonical contracts, configurable stages, dependencies,
+   approval gates, and sequential execution fallback.
+7. **IDE adapters** — verified Codex, Antigravity, and VS Code configuration generators.
+8. **Engineering integrations** — safe Git wrapper, Docker detection/templates, CI templates,
+   and documentation maintenance.
+9. **Existing project and design workflows** — repository analysis, Figma boundary, prototype
+   generation workflow, and implementation handoff.
+10. **Acceptance and release** — end-to-end verification, security review, package builds,
+    installation test, example project, and release documentation.
+
+## Phase gates
+
+At the end of every phase, run its tests and static checks, update progress documentation, and
+record remaining work. A later phase must not start while current-phase verification is failing.
+

agentic_development_framework-0.1.0/docs/IMPLEMENTATION_PROGRESS.md

@@ -0,0 +1,131 @@
+# Implementation progress
+
+## Phase 1 — Foundation
+
+Status: complete (2026-11-02)
+
+Planned deliverables:
+
+- [x] Repository metadata and packaging configuration
+- [x] Python source package and CLI entry points
+- [x] YAML configuration models and validation
+- [x] Console and JSONL event logging
+- [x] Repository agent guidance
+- [x] Focused unit tests
+- [x] Ruff verification passes
+- [x] Pytest suite passes (15 tests, 90.81% branch-aware coverage)
+- [x] Editable installation, wheel build, and both CLI entry points are verified
+
+Verification environment: Python 3.14.4.
+
+Phase 1 review (2026-11-02): package boundaries, configuration safety, logging handler
+ownership, CLI error handling, and tests were reviewed. No blocking defects were found; the
+original Phase 1 gate was rerun successfully before Phase 2 work began.
+
+## Phase 2 — Project initialization
+
+Status: complete (2026-11-02)
+
+Planned deliverables:
+
+- [x] `python -m agentic_framework init` and `adt init`
+- [x] New and existing project detection
+- [x] Git repository detection and optional safe initialization
+- [x] Common technology and package-manager detection
+- [x] Required project directory generation
+- [x] Safe file conflict proposals
+- [x] Deterministic initialization report
+- [x] Repeatable initialization that preserves project files
+- [x] Unit and acceptance tests
+- [x] Ruff verification passes
+- [x] Full pytest suite passes (30 tests, 91.46% branch-aware coverage)
+- [x] Wheel build and two-run CLI/module smoke checks pass
+
+Phase 2 deliberately creates the directory and configuration foundation without creating
+placeholder SQLite state, workflow state, canonical agent definitions, or IDE adapter files.
+Those remain owned by Phases 3, 6, and 7 respectively.
+
+## Phase 5 — Requirements management
+
+Status: complete for the requested standalone capability (2026-11-02)
+
+This capability was explicitly requested before Phases 3 and 4. It remains independent of the
+future SQLite runtime and command registry.
+
+- [x] Recursive multi-file inbox inventory
+- [x] SHA-256 hashing and byte-for-byte source preservation
+- [x] Atomic immutable version publication
+- [x] Existing-version integrity validation
+- [x] Hash-based duplicate submission detection
+- [x] UTF-8 text extraction boundary with explicit unsupported/failed statuses
+- [x] `REQ-NNN` parsing, conflict detection, and initial traceability records
+- [x] Added, modified, removed, and unchanged comparison with the previous version
+- [x] Human-readable impact report
+- [x] Concurrent-ingestion lock and symbolic-link rejection
+- [x] CLI entry point and actionable expected-error handling
+- [x] Unit, integration, and acceptance tests
+- [x] Ruff verification passes
+- [x] Full suite passes (45 tests, 92.22% branch-aware coverage)
+
+## Phase 3 — Runtime and persistence
+
+Status: core acceptance scope complete (2026-11-02)
+
+- [x] SQLite schema and idempotent initialization
+- [x] Persistent workflow, task, approval, checkpoint, and event tables
+- [x] Workflow, task, and execution JSON snapshots
+- [x] JSONL event history
+- [x] Integrity-checked pause/stop checkpoints
+- [x] Cross-process recovery from the verified checkpoint stage
+
+## Phase 4 — Command system
+
+Status: lifecycle acceptance scope complete (2026-11-02)
+
+- [x] Central command registry
+- [x] Start, status, pause, resume, continue, stop, and help
+- [x] Review, approve, revise, requirements, and tasks
+- [x] Expected failures return actionable errors without tracebacks
+
+## Phase 6 — Agent and workflow system
+
+Status: configuration foundation complete; execution remains incomplete
+
+- [x] Canonical configurable lifecycle with approval metadata
+- [x] Eleven canonical agent definitions and safety fields
+- [x] Approval-gate enforcement
+- [ ] Task dependencies and genuine sequential specialist execution
+
+## Phase 7 — IDE adapters
+
+Status: Codex and Antigravity acceptance scope complete; VS Code remains incomplete
+
+- [x] Root Codex `AGENTS.md`
+- [x] Validated repository-local Codex command skill
+- [x] Antigravity rules and shared skill
+- [x] Explicit documentation of unsupported/undocumented custom-agent discovery
+- [ ] VS Code agent-environment generation and validation
+
+## Release acceptance review
+
+Status: PyPI 0.1.0 release gates passed (2026-11-02)
+
+- [x] Clean wheel- and source-distribution-installed new and Django + React projects
+- [x] Idempotent actual initialization command
+- [x] Existing-file conflict preservation and proposal generation
+- [x] Codex and Antigravity configuration validation
+- [x] Requirements version and impact-report workflow
+- [x] State database, commands, approval gates, and cross-process recovery
+- [x] Wheel runtime resource and source-distribution content inspection
+- [x] Twine metadata and README validation
+- [x] Full source and installed-wheel suites pass (58 tests, 90.65% branch-aware coverage)
+- [x] Python 3.11, 3.12, and 3.13 CI matrix configured
+- [x] Tag-only PyPI OIDC Trusted Publishing configured
+- [x] Detailed evidence recorded in `docs/ACCEPTANCE_REPORT.md`
+
+## Remaining phases
+
+Phase 8, Phase 9, the VS Code portion of Phase 7, and the execution portion of Phase 6 remain on
+the broader framework roadmap. They are not represented as implemented in the 0.1.0 alpha release;
+their scope and dependencies are documented in `docs/IMPLEMENTATION_PLAN.md`.
+