openframe-tooling 0.1.0

OpenFrame Microservice Suite - developer tooling meta-package. Install tools by name or group.

openframe-tooling

A metadata-only package that provides named install shortcuts for the openframe-tooling ecosystem. Install one tool, or everything — all with a single pip install command.

---

Install surface

Individual tools

pip install openframe-tooling[schemas]   # openframe-schemas — cross-service schema governance
pip install openframe-tooling[cli]       # openframe-cli     — service scaffolding
pip install openframe-tooling[docs]      # openframe-docs    — doc-truth CI

Everything

pip install openframe-tooling[all]       # all tools in the ecosystem

---

What each tool does

• openframe-schemas — publishes @contract-decorated Pydantic models (marked via openframe.core.schemas.contract) to a versioned, file-based registry and detects breaking changes between versions. Ships a CLI (openframe-schemas publish / check) for use as a CI gate.
• openframe-cli — service scaffolding via Copier templates. Generates a full hexagonal-architecture OpenFrame service — domain, ports, service, adapter, ApplicationBootstrap wiring, and tests/test_architecture.py enforcing the boundary — from a single openframe new service command. openframe check runs architecture/pins/contracts checks in CI.
• openframe-docs — doc-truth CI: derives documentation claims from source rather than trusting prose. Three independent checkers — check-pins (README version claims vs. real package version), check-sigs (README code-block calls vs. real installed signatures), and check-imports (README imports vs. what actually resolves) — each usable standalone as a CI gate.

Note: as of 0.1.0, all three tools — openframe-schemas, openframe-cli, and openframe-docs — are published.

---

Versioning

Each tool is versioned independently and published to PyPI under its own name (e.g. openframe-schemas). This meta-package pins each one to its own major-version range (see [project.optional-dependencies] in pyproject.toml), so patch and minor releases are picked up automatically on pip install --upgrade. Only a major version bump in an individual tool requires a meta-package update.

When a new tool is added to the ecosystem, only this pyproject.toml changes — one new line in [project.optional-dependencies] and an update to the all group. No other file in the monorepo is touched.