macrostates-cli 0.3.1__tar.gz

macrostates_cli-0.3.1/.macrostates/implementation/release.yaml

@@ -0,0 +1,3 @@
+version: "0.3.1"
+specification: "spec-0.3.0"
+release_date: "2026-10-09"

macrostates_cli-0.3.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Lucas Lopez
+
+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.

macrostates_cli-0.3.1/MANIFEST.in

@@ -0,0 +1 @@
+include .macrostates/implementation/release.yaml

macrostates_cli-0.3.1/PKG-INFO

@@ -0,0 +1,259 @@
+Metadata-Version: 2.4
+Name: macrostates-cli
+Version: 0.3.1
+Summary: Compose, install and validate versioned Macrostates specification packages.
+Author-email: Lucas Lopez <713375+lucaslopez@users.noreply.github.com>
+License-Expression: MIT
+Project-URL: Repository, https://github.com/Macrostates/macrostates-cli
+Project-URL: Documentation, https://github.com/Macrostates/macrostates-cli#readme
+Project-URL: Issues, https://github.com/Macrostates/macrostates-cli/issues
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML<7,>=6.0.2
+Dynamic: license-file
+
+# Macrostates CLI
+
+Install, inspect and check reusable specification packages. Packages stay in
+numbered, version-controlled directories such as `000_meta/` and `001_process/`.
+The `macrostates` command and the `macrostates` Python API share the same core.
+
+Requires Python 3.12 or newer. Distribution name: `macrostates-cli`.
+Import package and executable name: `macrostates`. Version 0.3.1 is an initial
+API; compatibility changes will be documented. Licensed under [MIT](https://github.com/Macrostates/macrostates-cli/blob/main/LICENSE).
+
+## Installation
+
+Install from [PyPI](https://pypi.org/project/macrostates-cli/) with pip in a
+Python 3.12 or newer environment:
+
+```bash
+python -m pip install macrostates-cli
+macrostates --help
+```
+
+Use `python -m pip install macrostates-cli==0.3.1` for a fixed version, or
+`python -m pip install --upgrade macrostates-cli` to update it. If your Python
+installation requires a virtual environment, create one with
+`python -m venv .venv` and activate it before installing.
+
+For a command available outside a project environment, use
+`pipx install macrostates-cli` or `uv tool install macrostates-cli`. Contributors
+can clone the repository and run `uv sync --locked` as described below.
+
+## Start a project
+
+Supply a composition whose package versions, authority and reading orders you
+have selected. [The minimal composition](https://github.com/Macrostates/macrostates-cli/blob/main/examples/composition.yaml) selects only
+Meta; add Process and the technology packages appropriate to your project.
+
+```bash
+macrostates init --from /path/to/composition.yaml
+macrostates install
+macrostates info
+macrostates check
+```
+
+For a short setup, `macrostates init --name my-project --package meta@2.1.0`
+creates a composition. Repeat `--package NAME@VERSION` for additional packages.
+This shorthand uses the order you supplied for both reading and authority
+(highest first); review those orders before installation. It does not select
+dependencies automatically or replace versions with the latest releases.
+Use `--from` for custom sources or deliberate orders.
+
+The default layout is:
+
+```text
+AGENTS.md
+.macrostates/
+  specs/
+    main.md
+    composition.yaml
+    composition.lock.yaml
+    000_meta/
+    ...
+  implementation/
+    main.md
+```
+
+Commit the manifest, lockfile, package directories and project specifications.
+Initialization preserves existing agent instructions and refuses to overwrite
+project files. It prepares specification files; it does not implement an app.
+Meta 2.0/2.1 and Process 3.0/4.0/4.1 define this layout. Their numbered packages and locks
+remain tracked in Git. The CLI is strongly recommended and optional; reading
+specifications and manual checks remain necessary for requirements beyond its
+coverage. Existing projects keep their selected policies until explicitly migrated.
+
+## Commands
+
+| Command | Purpose | Network / writes |
+| --- | --- | --- |
+| `init` | Prepare selected specification files | Local writes |
+| `install` | Download and validate selected archive releases | Network and package/lock writes |
+| `install --locked` | Restore an unchanged, locked selection | Network and package/lock writes |
+| `lock` | Compare existing copies with canonical releases, then record integrity | Network and lock write |
+| `verify` | Detect modified, missing or additional package files and executable changes | Offline, read-only |
+| `lint` | Check metadata, dependencies, cycles, entrypoints, orders and local links | Offline, read-only |
+| `info` | Display packages, provenance and dependency/order information | Offline, read-only |
+| `check` | Combine lint and verify | Offline, read-only |
+| `check --staged` | Check the Git index, including partially staged edits | Offline, read-only |
+
+All commands accept `--project PATH` and `--json` before or after the command.
+Project discovery selects the nearest composition and stops at the Git root.
+It rejects competing `.yaml`/`.yml` manifests and ambiguous legacy/modern layouts.
+Exit codes: **0** success, **1** failed checks, **2** invalid input/operation.
+Argparse usage errors use its standard text output and exit code 2.
+
+Local packages use `source: {type: local}` and are freely editable. Their metadata
+and links are linted; they are excluded from downloaded-package integrity checks.
+Every external package needs a real source to establish a lock. `lock` never
+accepts local modifications as the baseline: it compares against the release.
+
+### Updating and recovering
+
+Updates are deliberate manifest edits: change the
+selected `version` and `source.tag` together, update the human entrypoint, then
+run `install`. It replaces an old package only if its files still match its
+previous locked inventory. Modified packages are left intact. A missing package
+directory can be restored with `install --locked`.
+
+Locks record full commit IDs and SHA-256 hashes of extracted file contents and
+executable flags. ZIP/tar compression is not part of identity. Reinstallation
+checks that the tag still selects its locked commit and fails if the tag moved.
+The lock is a reviewable integrity baseline, not a digital signature: review its
+changes together with package changes. `verify` is offline and cannot determine
+whether a tag moved remotely.
+
+Package operations validate all downloads and dependencies before replacing
+files and roll back ordinary filesystem failures. A simultaneous CLI operation
+is refused. An unexpected process termination may leave `.macrostates-operation`
+and a `.macrostates-install-*` recovery directory; inspect those before removing
+the marker or attempting recovery. Power-loss/crash-atomic filesystem commits
+are not promised.
+
+### Private packages
+
+The downloader accepts credential-free GitHub HTTPS or SSH repository URLs.
+It uses an explicit Python API token, then `GH_TOKEN`/`GITHUB_TOKEN`, then an
+existing GitHub CLI login. Tokens are never stored in composition or lockfiles.
+Initialization and offline commands do not look up credentials. Package imports
+do not execute downloaded code.
+
+### Checks before commits
+
+Add the following entry to an existing pre-commit configuration after arranging
+installation of the selected CLI version:
+
+```yaml
+repos:
+  - repo: local
+    hooks:
+      - id: macrostates
+        name: Check staged Macrostates specifications
+        entry: macrostates check --staged
+        language: system
+        pass_filenames: false
+        always_run: true
+```
+
+Run `macrostates check` in CI too. The CLI does not install hooks or change Git
+settings automatically. Staged snapshots currently have a 128 MiB size limit
+and exclude submodule contents. Structural checks do not prove semantic
+consistency or implementation conformance. The local Markdown link checker
+checks file targets, skips fenced code, and does not validate heading anchors
+or implement a complete Markdown parser.
+
+## Python API
+
+```python
+from macrostates import Project
+
+project = Project.open("/path/to/project")
+print(project.info())
+report = project.check()
+for diagnostic in report.diagnostics:
+    print(diagnostic.code, diagnostic.message, diagnostic.path)
+assert report.ok
+```
+
+Supported root exports: `Project`, `Report`, `Diagnostic`, `MacrostatesError`,
+`GitHubSource`, and `SourceProvider`. `Project.open` and `Project.initialize`
+construct projects; `install`, `lock`, `verify`, `lint`, `check`, and `info` are
+the supported operations. `initialize` accepts a composition dictionary/path
+or a `name` plus ordered `(package_name, version)` selections and a `layout`
+of `modern` or `legacy`. Pass `source=GitHubSource(token=...)` for explicit
+authentication or a `SourceProvider` implementation for another test transport.
+`install(locked=True)` requires unchanged locked selections; `check(staged=True)`
+checks the index. Expected configuration/operation errors raise
+`MacrostatesError`; check failures are returned in `Report.diagnostics`.
+Ordinary file read failures can raise `OSError`. Imports perform no project-local
+or network I/O and do not configure logging. Accessing `__version__` explicitly
+reads installed distribution metadata; it does not read a project declaration. The CLI configures standard logging when explicitly invoked.
+
+## Compatibility and development
+
+Unversioned compositions use the retained legacy reader. New compositions use
+`schema_version: 1`. Both legacy `specs/` and `.macrostates/specs/` layouts are
+recognized. Existing `git-subtree` compositions can be inspected, linted and
+given an upstream-verified integrity lock without changing subtree history.
+Archive `install` refuses subtree sources; use Git subtree maintenance until an
+explicit migration is requested. Old branch-only/commit selectors need explicit
+tag migration and are reported instead of being silently reinterpreted.
+
+Package release versions are independent of format versions. Existing package
+metadata is format 1, as is an explicit `schema_version: 1`. Unknown manifest,
+metadata or lock formats fail clearly. Release policy adapters support Meta
+2.0.x/2.1.x and Process 2.3.x/2.4.x/3.0.x/4.0.x/4.1.x. Modern policies require the modern
+layout; Meta 2 also requires composition format 1. Earlier Meta releases and
+Process 1.x/2.0–2.2 retain their existing checks. Future policy releases receive
+explicit unsupported diagnostics rather than guessed requirements. Process 4's
+feature-branch and PR rules require manual workflow review; CLI checks do not
+verify branch discipline or authorize Git operations.
+
+`info` lists directory-scoped specifications under visible component directories;
+`lint` checks their local file links. The scope root is the component containing
+`.macrostates/`. Separately composed subprojects are checked independently.
+Tool/cache/build/temporary and hidden implementation directories are excluded
+from this discovery; inspect their applicable scopes manually. Scope authority,
+semantic requirements and workflow conformance always need specification reading.
+See [architecture](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/main.md) for adapter extension guidance and
+[project specifications](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/specs/main.md) for this repository's working rules.
+The [CLI specification package](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/specs/051_cli/README.md) defines the
+public library, commands, composition, integrity and versioning contracts;
+[conformance evidence](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/specification-conformance.md)
+maps those requirements to implementation and verification.
+
+```bash
+uv sync --locked
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+uv run pytest --cov=macrostates --cov-report=term-missing
+uv build
+```
+
+The contributor `uv.lock` is committed for repeatable development and CI.
+Builds go to ignored `dist/`; temporary work goes to `tmp/<activity>/`.
+Automated update planning, workflow commands, release publishing and migrations
+are future features.
+
+## This repository's specifications and version
+
+The CLI manages its own specification composition under `.macrostates/specs/`,
+using Meta 2.1.0, Process 4.1.0, Repository 3.1.0, Python 2.1.0 and Python-library
+1.1.0 as canonical archive snapshots. Its local CLI requirements remain editable.
+`macrostates check` and `check --staged` validate the same files contributors use.
+This is also a real integration test of the supported package installation path.
+
+The implementation's single version declaration is
+[release.yaml](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/release.yaml); the specification baseline
+is `project.version` in the composition. Setuptools reads the declaration during
+isolated builds. The sdist includes that one declaration, while the wheel reports
+its installed distribution version. Builds do not edit declarations, create tags
+or require Git/network access to obtain release metadata. Ordinary dependency
+installation may still require access to package indexes.
+
+## AI assistance
+
+This project was developed with AI assistance.

macrostates_cli-0.3.1/README.md

@@ -0,0 +1,244 @@
+# Macrostates CLI
+
+Install, inspect and check reusable specification packages. Packages stay in
+numbered, version-controlled directories such as `000_meta/` and `001_process/`.
+The `macrostates` command and the `macrostates` Python API share the same core.
+
+Requires Python 3.12 or newer. Distribution name: `macrostates-cli`.
+Import package and executable name: `macrostates`. Version 0.3.1 is an initial
+API; compatibility changes will be documented. Licensed under [MIT](https://github.com/Macrostates/macrostates-cli/blob/main/LICENSE).
+
+## Installation
+
+Install from [PyPI](https://pypi.org/project/macrostates-cli/) with pip in a
+Python 3.12 or newer environment:
+
+```bash
+python -m pip install macrostates-cli
+macrostates --help
+```
+
+Use `python -m pip install macrostates-cli==0.3.1` for a fixed version, or
+`python -m pip install --upgrade macrostates-cli` to update it. If your Python
+installation requires a virtual environment, create one with
+`python -m venv .venv` and activate it before installing.
+
+For a command available outside a project environment, use
+`pipx install macrostates-cli` or `uv tool install macrostates-cli`. Contributors
+can clone the repository and run `uv sync --locked` as described below.
+
+## Start a project
+
+Supply a composition whose package versions, authority and reading orders you
+have selected. [The minimal composition](https://github.com/Macrostates/macrostates-cli/blob/main/examples/composition.yaml) selects only
+Meta; add Process and the technology packages appropriate to your project.
+
+```bash
+macrostates init --from /path/to/composition.yaml
+macrostates install
+macrostates info
+macrostates check
+```
+
+For a short setup, `macrostates init --name my-project --package meta@2.1.0`
+creates a composition. Repeat `--package NAME@VERSION` for additional packages.
+This shorthand uses the order you supplied for both reading and authority
+(highest first); review those orders before installation. It does not select
+dependencies automatically or replace versions with the latest releases.
+Use `--from` for custom sources or deliberate orders.
+
+The default layout is:
+
+```text
+AGENTS.md
+.macrostates/
+  specs/
+    main.md
+    composition.yaml
+    composition.lock.yaml
+    000_meta/
+    ...
+  implementation/
+    main.md
+```
+
+Commit the manifest, lockfile, package directories and project specifications.
+Initialization preserves existing agent instructions and refuses to overwrite
+project files. It prepares specification files; it does not implement an app.
+Meta 2.0/2.1 and Process 3.0/4.0/4.1 define this layout. Their numbered packages and locks
+remain tracked in Git. The CLI is strongly recommended and optional; reading
+specifications and manual checks remain necessary for requirements beyond its
+coverage. Existing projects keep their selected policies until explicitly migrated.
+
+## Commands
+
+| Command | Purpose | Network / writes |
+| --- | --- | --- |
+| `init` | Prepare selected specification files | Local writes |
+| `install` | Download and validate selected archive releases | Network and package/lock writes |
+| `install --locked` | Restore an unchanged, locked selection | Network and package/lock writes |
+| `lock` | Compare existing copies with canonical releases, then record integrity | Network and lock write |
+| `verify` | Detect modified, missing or additional package files and executable changes | Offline, read-only |
+| `lint` | Check metadata, dependencies, cycles, entrypoints, orders and local links | Offline, read-only |
+| `info` | Display packages, provenance and dependency/order information | Offline, read-only |
+| `check` | Combine lint and verify | Offline, read-only |
+| `check --staged` | Check the Git index, including partially staged edits | Offline, read-only |
+
+All commands accept `--project PATH` and `--json` before or after the command.
+Project discovery selects the nearest composition and stops at the Git root.
+It rejects competing `.yaml`/`.yml` manifests and ambiguous legacy/modern layouts.
+Exit codes: **0** success, **1** failed checks, **2** invalid input/operation.
+Argparse usage errors use its standard text output and exit code 2.
+
+Local packages use `source: {type: local}` and are freely editable. Their metadata
+and links are linted; they are excluded from downloaded-package integrity checks.
+Every external package needs a real source to establish a lock. `lock` never
+accepts local modifications as the baseline: it compares against the release.
+
+### Updating and recovering
+
+Updates are deliberate manifest edits: change the
+selected `version` and `source.tag` together, update the human entrypoint, then
+run `install`. It replaces an old package only if its files still match its
+previous locked inventory. Modified packages are left intact. A missing package
+directory can be restored with `install --locked`.
+
+Locks record full commit IDs and SHA-256 hashes of extracted file contents and
+executable flags. ZIP/tar compression is not part of identity. Reinstallation
+checks that the tag still selects its locked commit and fails if the tag moved.
+The lock is a reviewable integrity baseline, not a digital signature: review its
+changes together with package changes. `verify` is offline and cannot determine
+whether a tag moved remotely.
+
+Package operations validate all downloads and dependencies before replacing
+files and roll back ordinary filesystem failures. A simultaneous CLI operation
+is refused. An unexpected process termination may leave `.macrostates-operation`
+and a `.macrostates-install-*` recovery directory; inspect those before removing
+the marker or attempting recovery. Power-loss/crash-atomic filesystem commits
+are not promised.
+
+### Private packages
+
+The downloader accepts credential-free GitHub HTTPS or SSH repository URLs.
+It uses an explicit Python API token, then `GH_TOKEN`/`GITHUB_TOKEN`, then an
+existing GitHub CLI login. Tokens are never stored in composition or lockfiles.
+Initialization and offline commands do not look up credentials. Package imports
+do not execute downloaded code.
+
+### Checks before commits
+
+Add the following entry to an existing pre-commit configuration after arranging
+installation of the selected CLI version:
+
+```yaml
+repos:
+  - repo: local
+    hooks:
+      - id: macrostates
+        name: Check staged Macrostates specifications
+        entry: macrostates check --staged
+        language: system
+        pass_filenames: false
+        always_run: true
+```
+
+Run `macrostates check` in CI too. The CLI does not install hooks or change Git
+settings automatically. Staged snapshots currently have a 128 MiB size limit
+and exclude submodule contents. Structural checks do not prove semantic
+consistency or implementation conformance. The local Markdown link checker
+checks file targets, skips fenced code, and does not validate heading anchors
+or implement a complete Markdown parser.
+
+## Python API
+
+```python
+from macrostates import Project
+
+project = Project.open("/path/to/project")
+print(project.info())
+report = project.check()
+for diagnostic in report.diagnostics:
+    print(diagnostic.code, diagnostic.message, diagnostic.path)
+assert report.ok
+```
+
+Supported root exports: `Project`, `Report`, `Diagnostic`, `MacrostatesError`,
+`GitHubSource`, and `SourceProvider`. `Project.open` and `Project.initialize`
+construct projects; `install`, `lock`, `verify`, `lint`, `check`, and `info` are
+the supported operations. `initialize` accepts a composition dictionary/path
+or a `name` plus ordered `(package_name, version)` selections and a `layout`
+of `modern` or `legacy`. Pass `source=GitHubSource(token=...)` for explicit
+authentication or a `SourceProvider` implementation for another test transport.
+`install(locked=True)` requires unchanged locked selections; `check(staged=True)`
+checks the index. Expected configuration/operation errors raise
+`MacrostatesError`; check failures are returned in `Report.diagnostics`.
+Ordinary file read failures can raise `OSError`. Imports perform no project-local
+or network I/O and do not configure logging. Accessing `__version__` explicitly
+reads installed distribution metadata; it does not read a project declaration. The CLI configures standard logging when explicitly invoked.
+
+## Compatibility and development
+
+Unversioned compositions use the retained legacy reader. New compositions use
+`schema_version: 1`. Both legacy `specs/` and `.macrostates/specs/` layouts are
+recognized. Existing `git-subtree` compositions can be inspected, linted and
+given an upstream-verified integrity lock without changing subtree history.
+Archive `install` refuses subtree sources; use Git subtree maintenance until an
+explicit migration is requested. Old branch-only/commit selectors need explicit
+tag migration and are reported instead of being silently reinterpreted.
+
+Package release versions are independent of format versions. Existing package
+metadata is format 1, as is an explicit `schema_version: 1`. Unknown manifest,
+metadata or lock formats fail clearly. Release policy adapters support Meta
+2.0.x/2.1.x and Process 2.3.x/2.4.x/3.0.x/4.0.x/4.1.x. Modern policies require the modern
+layout; Meta 2 also requires composition format 1. Earlier Meta releases and
+Process 1.x/2.0–2.2 retain their existing checks. Future policy releases receive
+explicit unsupported diagnostics rather than guessed requirements. Process 4's
+feature-branch and PR rules require manual workflow review; CLI checks do not
+verify branch discipline or authorize Git operations.
+
+`info` lists directory-scoped specifications under visible component directories;
+`lint` checks their local file links. The scope root is the component containing
+`.macrostates/`. Separately composed subprojects are checked independently.
+Tool/cache/build/temporary and hidden implementation directories are excluded
+from this discovery; inspect their applicable scopes manually. Scope authority,
+semantic requirements and workflow conformance always need specification reading.
+See [architecture](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/main.md) for adapter extension guidance and
+[project specifications](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/specs/main.md) for this repository's working rules.
+The [CLI specification package](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/specs/051_cli/README.md) defines the
+public library, commands, composition, integrity and versioning contracts;
+[conformance evidence](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/specification-conformance.md)
+maps those requirements to implementation and verification.
+
+```bash
+uv sync --locked
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+uv run pytest --cov=macrostates --cov-report=term-missing
+uv build
+```
+
+The contributor `uv.lock` is committed for repeatable development and CI.
+Builds go to ignored `dist/`; temporary work goes to `tmp/<activity>/`.
+Automated update planning, workflow commands, release publishing and migrations
+are future features.
+
+## This repository's specifications and version
+
+The CLI manages its own specification composition under `.macrostates/specs/`,
+using Meta 2.1.0, Process 4.1.0, Repository 3.1.0, Python 2.1.0 and Python-library
+1.1.0 as canonical archive snapshots. Its local CLI requirements remain editable.
+`macrostates check` and `check --staged` validate the same files contributors use.
+This is also a real integration test of the supported package installation path.
+
+The implementation's single version declaration is
+[release.yaml](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/release.yaml); the specification baseline
+is `project.version` in the composition. Setuptools reads the declaration during
+isolated builds. The sdist includes that one declaration, while the wheel reports
+its installed distribution version. Builds do not edit declarations, create tags
+or require Git/network access to obtain release metadata. Ordinary dependency
+installation may still require access to package indexes.
+
+## AI assistance
+
+This project was developed with AI assistance.

macrostates_cli-0.3.1/pyproject.toml

@@ -0,0 +1,60 @@
+[build-system]
+requires = ["setuptools>=77", "PyYAML>=6.0.2,<7"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "macrostates-cli"
+dynamic = ["version"]
+description = "Compose, install and validate versioned Macrostates specification packages."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{name = "Lucas Lopez", email = "713375+lucaslopez@users.noreply.github.com"}]
+dependencies = ["PyYAML>=6.0.2,<7"]
+
+[project.urls]
+Repository = "https://github.com/Macrostates/macrostates-cli"
+Documentation = "https://github.com/Macrostates/macrostates-cli#readme"
+Issues = "https://github.com/Macrostates/macrostates-cli/issues"
+
+[project.scripts]
+macrostates = "macrostates._cli:main"
+
+[dependency-groups]
+dev = ["pytest>=8", "pytest-cov>=6", "ruff>=0.9", "pyright>=1.1.390", "types-PyYAML>=6"]
+
+[tool.uv]
+cache-keys = [
+    {file = "pyproject.toml"},
+    {file = ".macrostates/implementation/release.yaml"},
+    {file = "README.md"},
+    {dir = "src"},
+]
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+macrostates = ["py.typed"]
+
+[tool.setuptools.dynamic]
+version = {attr = "macrostates._build_version.VERSION"}
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "--strict-markers"
+
+[tool.ruff]
+target-version = "py312"
+line-length = 100
+
+[tool.ruff.lint]
+select = ["E4", "E7", "E9", "F", "I", "UP", "B"]
+
+[tool.pyright]
+include = ["src", "examples"]
+pythonVersion = "3.12"
+typeCheckingMode = "standard"
+venvPath = "."
+venv = ".venv"

macrostates_cli-0.3.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

macrostates_cli-0.3.1/src/macrostates/__init__.py

@@ -0,0 +1,23 @@
+"""The public API. Imports perform no network or project-local file access."""
+
+from importlib.metadata import PackageNotFoundError, version
+
+from ._models import Diagnostic, MacrostatesError, Report
+from ._project import Project
+from ._sources import GitHubSource, SourceProvider
+
+__all__ = ["Diagnostic", "GitHubSource", "MacrostatesError", "Project", "Report", "SourceProvider"]
+
+
+def __getattr__(name: str) -> str:
+    if name != "__version__":
+        raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
+    # Read distribution metadata only when a caller explicitly requests a version.
+    try:
+        return version("macrostates-cli")
+    except PackageNotFoundError:
+        return "0+uninstalled"
+
+
+def __dir__() -> list[str]:
+    return sorted([*globals(), "__version__"])

macrostates_cli-0.3.1/src/macrostates/__main__.py

@@ -0,0 +1,4 @@
+from ._cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())