macrostates-cli 0.4.0__tar.gz → 0.5.0__tar.gz

macrostates_cli-0.5.0/.macrostates/implementation/application.yaml

@@ -0,0 +1,10 @@
+schema_version: 1
+name: macrostates-cli
+version: 0.5.0
+status: candidate
+specification: specs-2.0.0
+implementation: imp-2.0.0
+release_date: '2026-10-13'
+source:
+  tag: v0.5.0
+source_sha256: 9b1ce349710c5f6875d4c0b59027a5e0b023392d38822792df0df0e9028b4f90

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

@@ -0,0 +1,4 @@
+version: imp-2.0.0
+specification: specs-2.0.0
+release_date: '2026-10-13'
+schema_version: 2

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: macrostates-cli
-Version: 0.4.0
+Version: 0.5.0
 Summary: Compose, install and validate versioned Macrostates specification packages.
 Author-email: Lucas Lopez <713375+lucaslopez@users.noreply.github.com>
 License-Expression: MIT
@@ -25,8 +25,11 @@ operations. Requires Python 3.12 or newer. Distribution name: `macrostates-cli`.
 Import package and executable name: `macrostates`.
 Licensed under [MIT](https://github.com/Macrostates/macrostates-cli/blob/main/LICENSE).
 
-This release introduces application version `0.4.0` and support for the released
-Meta 2.2, Process 5, Repository 4, Python 2.1.1 and Python-library 2 packages.
+Application version `0.5.0` supports Meta 3.0 and Process 5.1 alongside earlier
+selected policies. Its own composition uses released Meta 3.0.0, Process 5.1.0,
+Repository 4, Python 2.1.1 and Python-library 2 packages. Under Meta 3.0 and
+Process 5.1, implementers choose version impact within requested work without a
+separate Major-number approval.
 The CLI application version is independent from its Macrostates specification
 and implementation baselines. Older projects retain their selected formats and
 policies until explicitly adopted and migrated.
@@ -38,13 +41,13 @@ Install the published package from
 newer environment:
 
 ```bash
-python -m pip install "macrostates-cli>=0.4.0"
+python -m pip install "macrostates-cli>=0.5.0"
 macrostates --help
 ```
 
-Use `python -m pip install macrostates-cli==0.4.0` to select this release, or
-`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1`
-release remains available for projects that deliberately retain it. A virtual environment can be created with
+Use `python -m pip install macrostates-cli==0.5.0` to select this release, or
+`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1` and `0.4.0`
+releases remain available for projects that deliberately retain it. A virtual environment can be created with
 `python -m venv .venv`; activate it before installing when your environment
 requires one. For a command outside a project environment, use
 `pipx install macrostates-cli` or `uv tool install macrostates-cli`.
@@ -69,7 +72,7 @@ macrostates info
 macrostates check
 ```
 
-The shorthand `macrostates init --name my-project --package meta@2.2.0`
+The shorthand `macrostates init --name my-project --package meta@3.0.0`
 creates a composition. Repeat `--package NAME@VERSION` for additional packages.
 Input order supplies both reading order and authority, highest first; review them
 before installation. No dependency or latest release is selected automatically.
@@ -158,7 +161,7 @@ inspection before retrying. See
 ## Development And Baseline Releases
 
 The following development commands require explicit selection of supported
-Process 5.0. `branch-status` and `branch-sync` also serve projects retaining older
+Process 5.0 or 5.1. `branch-status` and `branch-sync` also serve projects retaining older
 version policies. Core operations work with Git refs and commits; your repository
 policy defines the review/integration mechanism and required external checks.
 
@@ -315,11 +318,12 @@ integration-preparation checks belong at their dedicated gate, since ordinary
 development commits legitimately contain open workflows. Index checks preserve
 partial staging, have documented resource limits, and exclude submodule contents.
 
-The CLI tracks its own composition under `.macrostates/specs/`. Adoption of the
-new official releases, exact selections, lock, and final baseline declarations
-will be verified separately. This development branch uses an independent
+The CLI tracks its own composition under `.macrostates/specs/`. The exact
+released selections passed canonical installation, locked reinstallation and
+offline checks. Baseline finalization and application publication retain their
+separate verification gates. The source uses an independent
 [application declaration](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/application.yaml)
-for independent build version `0.4.0`; the Macrostates implementation declaration is a
+for independent build version `0.5.0`; the Macrostates implementation declaration is a
 separate identity. Candidate/finalized builds bind verified shipped source and
 rebuild from source distributions without Git. Builds do not mutate declarations
 or publish artifacts.

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/README.md

@@ -10,8 +10,11 @@ operations. Requires Python 3.12 or newer. Distribution name: `macrostates-cli`.
 Import package and executable name: `macrostates`.
 Licensed under [MIT](https://github.com/Macrostates/macrostates-cli/blob/main/LICENSE).
 
-This release introduces application version `0.4.0` and support for the released
-Meta 2.2, Process 5, Repository 4, Python 2.1.1 and Python-library 2 packages.
+Application version `0.5.0` supports Meta 3.0 and Process 5.1 alongside earlier
+selected policies. Its own composition uses released Meta 3.0.0, Process 5.1.0,
+Repository 4, Python 2.1.1 and Python-library 2 packages. Under Meta 3.0 and
+Process 5.1, implementers choose version impact within requested work without a
+separate Major-number approval.
 The CLI application version is independent from its Macrostates specification
 and implementation baselines. Older projects retain their selected formats and
 policies until explicitly adopted and migrated.
@@ -23,13 +26,13 @@ Install the published package from
 newer environment:
 
 ```bash
-python -m pip install "macrostates-cli>=0.4.0"
+python -m pip install "macrostates-cli>=0.5.0"
 macrostates --help
 ```
 
-Use `python -m pip install macrostates-cli==0.4.0` to select this release, or
-`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1`
-release remains available for projects that deliberately retain it. A virtual environment can be created with
+Use `python -m pip install macrostates-cli==0.5.0` to select this release, or
+`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1` and `0.4.0`
+releases remain available for projects that deliberately retain it. A virtual environment can be created with
 `python -m venv .venv`; activate it before installing when your environment
 requires one. For a command outside a project environment, use
 `pipx install macrostates-cli` or `uv tool install macrostates-cli`.
@@ -54,7 +57,7 @@ macrostates info
 macrostates check
 ```
 
-The shorthand `macrostates init --name my-project --package meta@2.2.0`
+The shorthand `macrostates init --name my-project --package meta@3.0.0`
 creates a composition. Repeat `--package NAME@VERSION` for additional packages.
 Input order supplies both reading order and authority, highest first; review them
 before installation. No dependency or latest release is selected automatically.
@@ -143,7 +146,7 @@ inspection before retrying. See
 ## Development And Baseline Releases
 
 The following development commands require explicit selection of supported
-Process 5.0. `branch-status` and `branch-sync` also serve projects retaining older
+Process 5.0 or 5.1. `branch-status` and `branch-sync` also serve projects retaining older
 version policies. Core operations work with Git refs and commits; your repository
 policy defines the review/integration mechanism and required external checks.
 
@@ -300,11 +303,12 @@ integration-preparation checks belong at their dedicated gate, since ordinary
 development commits legitimately contain open workflows. Index checks preserve
 partial staging, have documented resource limits, and exclude submodule contents.
 
-The CLI tracks its own composition under `.macrostates/specs/`. Adoption of the
-new official releases, exact selections, lock, and final baseline declarations
-will be verified separately. This development branch uses an independent
+The CLI tracks its own composition under `.macrostates/specs/`. The exact
+released selections passed canonical installation, locked reinstallation and
+offline checks. Baseline finalization and application publication retain their
+separate verification gates. The source uses an independent
 [application declaration](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/application.yaml)
-for independent build version `0.4.0`; the Macrostates implementation declaration is a
+for independent build version `0.5.0`; the Macrostates implementation declaration is a
 separate identity. Candidate/finalized builds bind verified shipped source and
 rebuild from source distributions without Git. Builds do not mutate declarations
 or publish artifacts.

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/src/macrostates/_project.py

@@ -23,6 +23,7 @@ from ._validation import (
     check_process,
     has_contract_version,
     process_requires_modern_layout,
+    process_uses_prefixed_baselines,
     validate_packages,
 )
 
@@ -154,7 +155,9 @@ class Project:
             }
             process = next((item for item in selection if item["name"] == "process"), None)
             if process and has_contract_version(process["version"]):
-                prefix = "specs-" if version(process["version"])[:2] == (5, 0) else "spec-"
+                prefix = (
+                    "specs-" if process_uses_prefixed_baselines(process["version"]) else "spec-"
+                )
                 data["project"]["version"] = prefix + "0.1.0"
         composition = read_composition(data)
         specs = safe_path(directory, LAYOUTS[layout])
@@ -183,8 +186,8 @@ class Project:
         if composition.schema_version == 1:
             meta = next((item for item in composition.packages if item.name == "meta"), None)
             guidance = (
-                "These locations and snapshot sources follow the selected Meta 2 layout."
-                if meta and version(meta.version)[0] == 2
+                "These locations and snapshot sources follow the selected Meta layout."
+                if meta and version(meta.version)[0] >= 2
                 else "These explicit project-level location and transport choices take precedence over selected packages' older layout and subtree conventions."
             )
             overview += f"\n## Layout and verification\n\nSpecification files live under `{specs.relative_to(directory).as_posix()}/`; implementation documentation lives under `{project.implementation.relative_to(directory).as_posix()}/`. Packages marked `github-archive` are tracked release snapshots checked against `composition.lock.yaml`. {guidance} Local packages remain editable. Process, when selected, owns composition/implementation version policy. CLI checks supplement specification reading and do not establish implementation conformance.\n"
@@ -399,9 +402,9 @@ class Project:
         selected = next(
             (item for item in self._composition().packages if item.name == "process"), None
         )
-        if selected is None or version(selected.version)[:2] != (5, 0):
+        if selected is None or not process_uses_prefixed_baselines(selected.version):
             raise MacrostatesError(
-                "This operation requires an explicitly selected Process 5.0 policy; older projects are not migrated implicitly"
+                "This operation requires an explicitly selected Process 5.0 or 5.1 policy; older projects are not migrated implicitly"
             )
         if git_scope:
             from ._git import git

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/src/macrostates/_validation.py

@@ -216,7 +216,7 @@ class Process50Policy:
         from ._versioning import baselines
 
         if implementation.parent.name != ".macrostates":
-            report.add("process.layout", "Process 5.0 requires .macrostates/implementation/")
+            report.add("process.layout", f"{self.label} requires .macrostates/implementation/")
             return
         root = implementation.parent.parent
         try:
@@ -237,6 +237,12 @@ class Process50Policy:
             report.add("process.release_invalid", str(exc))
 
 
+class Process51Policy(Process50Policy):
+    """5.1 relaxes Major assignment authority without changing baseline formats."""
+
+    label = "Process 5.1"
+
+
 PROCESS_POLICIES = {
     (2, 3): Process23Policy(),
     (2, 4): Process24Policy(),
@@ -244,6 +250,7 @@ PROCESS_POLICIES = {
     (4, 0): Process40Policy(),
     (4, 1): Process41Policy(),
     (5, 0): Process50Policy(),
+    (5, 1): Process51Policy(),
 }
 
 
@@ -257,6 +264,11 @@ def process_requires_modern_layout(process_version: str) -> bool:
     return policy is not None and policy.requires_modern_layout
 
 
+def process_uses_prefixed_baselines(process_version: str) -> bool:
+    """Opt only explicitly reviewed policies into the schema-2 baseline operations."""
+    return isinstance(PROCESS_POLICIES.get(version(process_version)[:2]), Process50Policy)
+
+
 class Meta20Policy:
     """Meta 2.0 layout and explicit composition-format checks."""
 
@@ -283,7 +295,18 @@ class Meta22Policy(Meta21Policy):
     label = "Meta 2.2"
 
 
-META_POLICIES = {(2, 0): Meta20Policy(), (2, 1): Meta21Policy(), (2, 2): Meta22Policy()}
+class Meta30Policy(Meta22Policy):
+    """3.0 relaxes package Major assignment authority, retaining layout and formats."""
+
+    label = "Meta 3.0"
+
+
+META_POLICIES = {
+    (2, 0): Meta20Policy(),
+    (2, 1): Meta21Policy(),
+    (2, 2): Meta22Policy(),
+    (3, 0): Meta30Policy(),
+}
 
 
 def check_meta(composition: Composition, specs: Path, root: Path, report: Report) -> None:

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/src/macrostates/_versioning.py

@@ -56,6 +56,8 @@ def composition_path(root: Path) -> Path:
 
 def declarations(root: Path) -> dict[str, Any]:
     """Read authoritative finalized/candidate numbers, never infer source readiness."""
+    from ._validation import process_uses_prefixed_baselines
+
     manifest = composition_path(root)
     composition = read_yaml(manifest)
     packages = composition.get("packages")
@@ -65,8 +67,10 @@ def declarations(root: Path) -> dict[str, Any]:
         (item for item in packages if isinstance(item, dict) and item.get("name") == "process"),
         None,
     )
-    if process is None or version(process.get("version"))[:2] != (5, 0):
-        raise MacrostatesError("This operation requires the supported Process 5.0 policy")
+    if process is None or not process_uses_prefixed_baselines(
+        string(process.get("version"), "process.version")
+    ):
+        raise MacrostatesError("This operation requires a supported Process 5.0 or 5.1 policy")
     project = mapping(composition.get("project"), "composition.project")
     specification = string(project.get("version"), "project.version")
     spec_numbers = baseline(specification, "specification")

{macrostates_cli-0.4.0 → macrostates_cli-0.5.0}/src/macrostates_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: macrostates-cli
-Version: 0.4.0
+Version: 0.5.0
 Summary: Compose, install and validate versioned Macrostates specification packages.
 Author-email: Lucas Lopez <713375+lucaslopez@users.noreply.github.com>
 License-Expression: MIT
@@ -25,8 +25,11 @@ operations. Requires Python 3.12 or newer. Distribution name: `macrostates-cli`.
 Import package and executable name: `macrostates`.
 Licensed under [MIT](https://github.com/Macrostates/macrostates-cli/blob/main/LICENSE).
 
-This release introduces application version `0.4.0` and support for the released
-Meta 2.2, Process 5, Repository 4, Python 2.1.1 and Python-library 2 packages.
+Application version `0.5.0` supports Meta 3.0 and Process 5.1 alongside earlier
+selected policies. Its own composition uses released Meta 3.0.0, Process 5.1.0,
+Repository 4, Python 2.1.1 and Python-library 2 packages. Under Meta 3.0 and
+Process 5.1, implementers choose version impact within requested work without a
+separate Major-number approval.
 The CLI application version is independent from its Macrostates specification
 and implementation baselines. Older projects retain their selected formats and
 policies until explicitly adopted and migrated.
@@ -38,13 +41,13 @@ Install the published package from
 newer environment:
 
 ```bash
-python -m pip install "macrostates-cli>=0.4.0"
+python -m pip install "macrostates-cli>=0.5.0"
 macrostates --help
 ```
 
-Use `python -m pip install macrostates-cli==0.4.0` to select this release, or
-`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1`
-release remains available for projects that deliberately retain it. A virtual environment can be created with
+Use `python -m pip install macrostates-cli==0.5.0` to select this release, or
+`python -m pip install --upgrade macrostates-cli` to update. The older `0.3.1` and `0.4.0`
+releases remain available for projects that deliberately retain it. A virtual environment can be created with
 `python -m venv .venv`; activate it before installing when your environment
 requires one. For a command outside a project environment, use
 `pipx install macrostates-cli` or `uv tool install macrostates-cli`.
@@ -69,7 +72,7 @@ macrostates info
 macrostates check
 ```
 
-The shorthand `macrostates init --name my-project --package meta@2.2.0`
+The shorthand `macrostates init --name my-project --package meta@3.0.0`
 creates a composition. Repeat `--package NAME@VERSION` for additional packages.
 Input order supplies both reading order and authority, highest first; review them
 before installation. No dependency or latest release is selected automatically.
@@ -158,7 +161,7 @@ inspection before retrying. See
 ## Development And Baseline Releases
 
 The following development commands require explicit selection of supported
-Process 5.0. `branch-status` and `branch-sync` also serve projects retaining older
+Process 5.0 or 5.1. `branch-status` and `branch-sync` also serve projects retaining older
 version policies. Core operations work with Git refs and commits; your repository
 policy defines the review/integration mechanism and required external checks.
 
@@ -315,11 +318,12 @@ integration-preparation checks belong at their dedicated gate, since ordinary
 development commits legitimately contain open workflows. Index checks preserve
 partial staging, have documented resource limits, and exclude submodule contents.
 
-The CLI tracks its own composition under `.macrostates/specs/`. Adoption of the
-new official releases, exact selections, lock, and final baseline declarations
-will be verified separately. This development branch uses an independent
+The CLI tracks its own composition under `.macrostates/specs/`. The exact
+released selections passed canonical installation, locked reinstallation and
+offline checks. Baseline finalization and application publication retain their
+separate verification gates. The source uses an independent
 [application declaration](https://github.com/Macrostates/macrostates-cli/blob/main/.macrostates/implementation/application.yaml)
-for independent build version `0.4.0`; the Macrostates implementation declaration is a
+for independent build version `0.5.0`; the Macrostates implementation declaration is a
 separate identity. Candidate/finalized builds bind verified shipped source and
 rebuild from source distributions without Git. Builds do not mutate declarations
 or publish artifacts.

macrostates_cli-0.4.0/.macrostates/implementation/application.yaml

@@ -1,10 +0,0 @@
-schema_version: 1
-name: macrostates-cli
-version: 0.4.0
-status: candidate
-specification: specs-1.0.0
-implementation: imp-1.0.0
-release_date: '2026-10-13'
-source:
-  tag: v0.4.0
-source_sha256: add414d530542993e6805a29a04e52c253e44bec69111d28bc6f887d19d19328

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

@@ -1,4 +0,0 @@
-version: imp-1.0.0
-specification: specs-1.0.0
-release_date: '2026-10-13'
-schema_version: 2