pgc-assembler 2.0.0__tar.gz → 3.0.0__tar.gz

{pgc_assembler-2.0.0/pgc_assembler.egg-info → pgc_assembler-3.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pgc-assembler
-Version: 2.0.0
+Version: 3.0.0
 Summary: PGC snapshot assembler — composes compiled projections into a manifest-pinned executable snapshot (import package: assembler)
 Author-email: Bhash Ganti <bachipeachy@gmail.com>
 License-Expression: Apache-2.0
@@ -20,6 +20,7 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
+Requires-Dist: pyyaml
 Dynamic: license-file
 
 # snapshot_assembler
@@ -118,7 +119,7 @@ Apache-2.0.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -140,9 +141,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v3` is `3.0.0`.** The standard the packages implement is a
 separate artifact on its own track and is not this number.
 
 The standard these packages implement is published separately: https://doi.org/10.5281/zenodo.22150616

{pgc_assembler-2.0.0 → pgc_assembler-3.0.0}/README.md

@@ -94,7 +94,7 @@ Apache-2.0.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -116,9 +116,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v3` is `3.0.0`.** The standard the packages implement is a
 separate artifact on its own track and is not this number.
 
 The standard these packages implement is published separately: https://doi.org/10.5281/zenodo.22150616

pgc_assembler-3.0.0/VERSION

@@ -0,0 +1 @@
+15

pgc_assembler-3.0.0/assembler/VERSION

@@ -0,0 +1 @@
+15

{pgc_assembler-2.0.0 → pgc_assembler-3.0.0/pgc_assembler.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pgc-assembler
-Version: 2.0.0
+Version: 3.0.0
 Summary: PGC snapshot assembler — composes compiled projections into a manifest-pinned executable snapshot (import package: assembler)
 Author-email: Bhash Ganti <bachipeachy@gmail.com>
 License-Expression: Apache-2.0
@@ -20,6 +20,7 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
+Requires-Dist: pyyaml
 Dynamic: license-file
 
 # snapshot_assembler
@@ -118,7 +119,7 @@ Apache-2.0.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -140,9 +141,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v3` is `3.0.0`.** The standard the packages implement is a
 separate artifact on its own track and is not this number.
 
 The standard these packages implement is published separately: https://doi.org/10.5281/zenodo.22150616

{pgc_assembler-2.0.0 → pgc_assembler-3.0.0}/pgc_assembler.egg-info/SOURCES.txt

@@ -15,4 +15,5 @@ pgc_assembler.egg-info/PKG-INFO
 pgc_assembler.egg-info/SOURCES.txt
 pgc_assembler.egg-info/dependency_links.txt
 pgc_assembler.egg-info/entry_points.txt
+pgc_assembler.egg-info/requires.txt
 pgc_assembler.egg-info/top_level.txt

pgc_assembler-3.0.0/pgc_assembler.egg-info/requires.txt

@@ -0,0 +1 @@
+pyyaml

{pgc_assembler-2.0.0 → pgc_assembler-3.0.0}/pyproject.toml

@@ -5,7 +5,7 @@ backend-path = ["."]
 
 [project]
 name = "pgc-assembler"
-version = "2.0.0"
+version = "3.0.0"
 description = "PGC snapshot assembler — composes compiled projections into a manifest-pinned executable snapshot (import package: assembler)"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -25,7 +25,10 @@ classifiers = [
   "Topic :: Software Development :: Build Tools",
 ]
 
-dependencies = []
+# `_profile_declaration` parses the snapshot profile's YAML block, and it is reached from
+# `verify_snapshot` — the `verify` subcommand and the profile check inside assembly. A standalone
+# install without this raises ModuleNotFoundError there instead of refusing.
+dependencies = ["pyyaml"]
 
 [project.scripts]
 snapshot_assembler = "assembler.cli:main"

pgc_assembler-2.0.0/VERSION

@@ -1 +0,0 @@
-14

pgc_assembler-2.0.0/assembler/VERSION

@@ -1 +0,0 @@
-14