dirigent-integration 0.29.0__tar.gz → 0.30.0__tar.gz

{dirigent_integration-0.29.0 → dirigent_integration-0.30.0}/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: dirigent-integration
-Version: 0.29.0
+Version: 0.30.0
 Summary: The control center for the dirigent plugin ecosystem: assemble every pack, run everyone's tests and examples together.
 License-Expression: LicenseRef-Proprietary
 License-File: LICENSE
-Requires-Dist: dirigent-plugin==0.29.0
+Requires-Dist: dirigent-plugin==0.30.0
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 
@@ -32,8 +32,12 @@ runnable at all.
 - **`ecosystem.yaml`** -- the manifest: every component and the ref it tracks, the source of
   truth for what gets assembled. `dirigent` (the runtime monorepo) is `role: runtime`,
   installed as dependencies and never cloned; each adapter is `role: pack`, cloned and
-  self-tested here. `dirigent-dhis2` is the first; a future pack becomes real with a single
-  entry.
+  self-tested here. `dirigent-dhis2`, `dirigent-contrib` (Chap and the open climate service)
+  and `dirigent-fhir` (one FHIR R4 server) are the three today; a future pack becomes real with
+  a single entry. A pack entry may name `pytest_args` for its suite and `examples` for its
+  example directories: contrib's and fhir's suites run with `-m "not live"`, leaving out the
+  tests that reach a real Chap, climate service or FHIR server, and their shelves under `src/`
+  are validated, never run.
 - **`pyproject.toml`** -- the assembled runtime: every dirigent runtime package plus every
   pack, wired through `[tool.uv.sources]` as git dependencies on `branch = main`, unpinned, so
   the integration always assembles the latest ecosystem.
@@ -59,8 +63,9 @@ make test
 One target, one green or red:
 
 1. clone every `role: pack` in `ecosystem.yaml` into `checkouts/` (gitignored), at its ref;
-2. run each pack's own pytest suite against the assembled environment;
-3. validate each pack's own examples against the merged catalog;
+2. run each pack's own pytest suite against the assembled environment, with the arguments its
+   manifest entry names;
+3. validate each pack's own examples against the merged catalog, connection bodies included;
 4. validate the cross-boundary examples against the merged catalog;
 5. run the integration's own tests;
 6. ask every DHIS2 play demo an example names for its system info, and fail on any that no

{dirigent_integration-0.29.0 → dirigent_integration-0.30.0}/README.md

@@ -22,8 +22,12 @@ runnable at all.
 - **`ecosystem.yaml`** -- the manifest: every component and the ref it tracks, the source of
   truth for what gets assembled. `dirigent` (the runtime monorepo) is `role: runtime`,
   installed as dependencies and never cloned; each adapter is `role: pack`, cloned and
-  self-tested here. `dirigent-dhis2` is the first; a future pack becomes real with a single
-  entry.
+  self-tested here. `dirigent-dhis2`, `dirigent-contrib` (Chap and the open climate service)
+  and `dirigent-fhir` (one FHIR R4 server) are the three today; a future pack becomes real with
+  a single entry. A pack entry may name `pytest_args` for its suite and `examples` for its
+  example directories: contrib's and fhir's suites run with `-m "not live"`, leaving out the
+  tests that reach a real Chap, climate service or FHIR server, and their shelves under `src/`
+  are validated, never run.
 - **`pyproject.toml`** -- the assembled runtime: every dirigent runtime package plus every
   pack, wired through `[tool.uv.sources]` as git dependencies on `branch = main`, unpinned, so
   the integration always assembles the latest ecosystem.
@@ -49,8 +53,9 @@ make test
 One target, one green or red:
 
 1. clone every `role: pack` in `ecosystem.yaml` into `checkouts/` (gitignored), at its ref;
-2. run each pack's own pytest suite against the assembled environment;
-3. validate each pack's own examples against the merged catalog;
+2. run each pack's own pytest suite against the assembled environment, with the arguments its
+   manifest entry names;
+3. validate each pack's own examples against the merged catalog, connection bodies included;
 4. validate the cross-boundary examples against the merged catalog;
 5. run the integration's own tests;
 6. ask every DHIS2 play demo an example names for its system info, and fail on any that no

{dirigent_integration-0.29.0 → dirigent_integration-0.30.0}/pyproject.toml

@@ -1,12 +1,12 @@
 [project]
 name = "dirigent-integration"
-version = "0.29.0"
+version = "0.30.0"
 description = "The control center for the dirigent plugin ecosystem: assemble every pack, run everyone's tests and examples together."
 readme = "README.md"
 requires-python = ">=3.13"
 license = "LicenseRef-Proprietary"
 license-files = ["LICENSE"]
-dependencies = ["dirigent-plugin==0.29.0"]
+dependencies = ["dirigent-plugin==0.30.0"]
 
 [project.entry-points."dirigent.plugins.v1"]
 integration = "dirigent_integration:plugin"
@@ -31,6 +31,8 @@ assembly = [
     "dirigent-client",
     "dirigent-examples",
     "dirigent-dhis2",
+    "dirigent-contrib",
+    "dirigent-fhir",
 ]
 dev = [
     "dirigent-testing",
@@ -138,6 +140,11 @@ git = "https://github.com/winterop-com/dirigent"
 subdirectory = "packages/dirigent-examples"
 branch = "main"
 
+[tool.uv.sources.dirigent-mcp]
+git = "https://github.com/winterop-com/dirigent"
+subdirectory = "packages/dirigent-mcp"
+branch = "main"
+
 [tool.uv.sources.dirigent-testing]
 git = "https://github.com/winterop-com/dirigent"
 subdirectory = "packages/dirigent-testing"
@@ -147,6 +154,14 @@ branch = "main"
 git = "https://github.com/winterop-com/dirigent-dhis2"
 branch = "main"
 
+[tool.uv.sources.dirigent-contrib]
+git = "https://github.com/winterop-com/dirigent-contrib"
+branch = "main"
+
+[tool.uv.sources.dirigent-fhir]
+git = "https://github.com/winterop-com/dirigent-fhir"
+branch = "main"
+
 [tool.pytest.ini_options]
 asyncio_mode = "auto"
 testpaths = ["tests"]

{dirigent_integration-0.29.0 → dirigent_integration-0.30.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "dirigent-integration"
-version = "0.29.0"
+version = "0.30.0"
 description = "The control center for the dirigent plugin ecosystem: assemble every pack, run everyone's tests and examples together."
 readme = "README.md"
 requires-python = ">=3.13"
@@ -10,7 +10,7 @@ license-files = ["LICENSE"]
 # A published install carries the cross-boundary shelves and nothing else: each document
 # names the packs it needs under requires, and the Examples screen marks what is missing.
 dependencies = [
-    "dirigent-plugin==0.29.0",
+    "dirigent-plugin==0.30.0",
 ]
 
 # dirigent-testing is dev-only: the packs' suites import it, and nothing at runtime does,
@@ -38,6 +38,8 @@ assembly = [
     "dirigent-client",
     "dirigent-examples",
     "dirigent-dhis2",
+    "dirigent-contrib",
+    "dirigent-fhir",
 ]
 dev = [
     "dirigent-testing",
@@ -51,7 +53,7 @@ dev = [
 
 # All component packages ride their tracked branch, unpinned: the integration always assembles
 # the latest ecosystem. The dirigent runtime packages come from the monorepo by subdirectory;
-# dirigent-dhis2 comes from its own repository.
+# dirigent-dhis2, dirigent-contrib and dirigent-fhir come from their own repositories.
 [tool.uv]
 default-groups = ["dev", "assembly"]
 
@@ -74,8 +76,11 @@ dirigent-plugin = { git = "https://github.com/winterop-com/dirigent", subdirecto
 dirigent-common = { git = "https://github.com/winterop-com/dirigent", subdirectory = "packages/dirigent-common", branch = "main" }
 dirigent-client = { git = "https://github.com/winterop-com/dirigent", subdirectory = "packages/dirigent-client", branch = "main" }
 dirigent-examples = { git = "https://github.com/winterop-com/dirigent", subdirectory = "packages/dirigent-examples", branch = "main" }
+dirigent-mcp = { git = "https://github.com/winterop-com/dirigent", subdirectory = "packages/dirigent-mcp", branch = "main" }
 dirigent-testing = { git = "https://github.com/winterop-com/dirigent", subdirectory = "packages/dirigent-testing", branch = "main" }
 dirigent-dhis2 = { git = "https://github.com/winterop-com/dirigent-dhis2", branch = "main" }
+dirigent-contrib = { git = "https://github.com/winterop-com/dirigent-contrib", branch = "main" }
+dirigent-fhir = { git = "https://github.com/winterop-com/dirigent-fhir", branch = "main" }
 
 # The control center is itself a distribution: it registers one plugin whose only
 # contribution is the cross-boundary shelves the module carries.

{dirigent_integration-0.29.0 → dirigent_integration-0.30.0}/src/dirigent_integration/shelves/fhir/README.md

@@ -6,9 +6,8 @@ validate blocks from the runtime, and neither knows the other exists -- only an
 environment runs any of these at all.
 
 Most of them read a `d2w fhir serve` facade, which publishes one DHIS2 instance as a FHIR
-endpoint and takes captures back. Two are running on this machine at `http://localhost:8095`
-and `http://localhost:8096`; `fhir_base` defaults to the first, so every read below works
-against a real server. Where a general-purpose FHIR server is the point -- an Encounter, an
+endpoint and takes captures back. Their `fhir-facade` connection points at one on
+`http://localhost:8095`, so start a facade there, or repoint the connection, before a run. Where a general-purpose FHIR server is the point -- an Encounter, an
 Observation, a Subscription, a `_lastUpdated` search, none of which the facade serves -- the
 default is the public HAPI R4 sandbox at `https://hapi.fhir.org/baseR4` instead, and the
 document's header says why.