millwork-solver 0.1.1__tar.gz → 0.1.2__tar.gz

{millwork_solver-0.1.1/src/millwork_solver.egg-info → millwork_solver-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: millwork-solver
-Version: 0.1.1
+Version: 0.1.2
 Summary: Sync and async Python clients for the Millwork Solver API
 Author: Millwork
 License-Expression: Apache-2.0
@@ -101,12 +101,10 @@ with Solver() as client:
           path_parameters={"verifierId": verifier_id}, idempotency_key=str(uuid.uuid4())))
 ```
 
-The protected-connection methods below describe this source checkout. The
-published `millwork-solver==0.1.0` wheel has six public verifier operation
-IDs in its catalog but does not include `verifier_connection`. Until a wheel carrying
-these methods is published and read back, use the
-[private CLI or dashboard path](https://docs.getmillwork.dev/guides/connect-an-output-check#connect-a-protected-endpoint)
-for a protected endpoint.
+The published `millwork-solver==0.1.1` wheel includes the public verifier
+operation IDs and `verifier_connection`. Install that pinned release to run
+the protected-connection methods below. The earlier `0.1.0` wheel does not
+include these methods.
 
 For a protected endpoint, register that endpoint with the same secretless
 `postVerifiers` body, then use **its** `verifier_id` for the private handoff.

{millwork_solver-0.1.1 → millwork_solver-0.1.2}/README.md

@@ -82,12 +82,10 @@ with Solver() as client:
           path_parameters={"verifierId": verifier_id}, idempotency_key=str(uuid.uuid4())))
 ```
 
-The protected-connection methods below describe this source checkout. The
-published `millwork-solver==0.1.0` wheel has six public verifier operation
-IDs in its catalog but does not include `verifier_connection`. Until a wheel carrying
-these methods is published and read back, use the
-[private CLI or dashboard path](https://docs.getmillwork.dev/guides/connect-an-output-check#connect-a-protected-endpoint)
-for a protected endpoint.
+The published `millwork-solver==0.1.1` wheel includes the public verifier
+operation IDs and `verifier_connection`. Install that pinned release to run
+the protected-connection methods below. The earlier `0.1.0` wheel does not
+include these methods.
 
 For a protected endpoint, register that endpoint with the same secretless
 `postVerifiers` body, then use **its** `verifier_id` for the private handoff.

{millwork_solver-0.1.1 → millwork_solver-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "millwork-solver"
-version = "0.1.1"
+version = "0.1.2"
 description = "Sync and async Python clients for the Millwork Solver API"
 readme = "README.md"
 requires-python = ">=3.11,<3.15"

{millwork_solver-0.1.1 → millwork_solver-0.1.2}/src/millwork_solver/_contract.json

@@ -2,8 +2,8 @@
   "schema_version": 1,
   "generated_from": {
     "python_operation_view": "contracts/developer-experience/python-operation-view.json",
-    "operation_manifest_version": "1.5.0",
-    "openapi_sha256": "98d1b8a882c20b3916fbb4a09d2c88f117ce3b8b922089789b80af68acb23857",
+    "operation_manifest_version": "2.2.0",
+    "openapi_sha256": "0a7d6b2e24ac80602e3ae0991ff6d964fc3727304a49144c6a5d73eb89d75d97",
     "retry_fixture": "contracts/developer-experience/fixtures/retry-error-idempotency.json"
   },
   "operations": [
@@ -122,6 +122,16 @@
       "method": "GET",
       "path": "/v1/receipts/{executionId}"
     },
+    {
+      "operation_id": "getReviewComposerAgents",
+      "method": "GET",
+      "path": "/v1/review-composer/agents"
+    },
+    {
+      "operation_id": "getReviewComposerAgentsByArmIdConnection",
+      "method": "GET",
+      "path": "/v1/review-composer/agents/{armId}/connection"
+    },
     {
       "operation_id": "getSourceConnections",
       "method": "GET",
@@ -237,6 +247,11 @@
       "method": "POST",
       "path": "/v1/executions/{executionId}/cancel"
     },
+    {
+      "operation_id": "postModelCatalogQuote",
+      "method": "POST",
+      "path": "/v1/model-catalog/quote"
+    },
     {
       "operation_id": "postProposalsByProposalIdApprove",
       "method": "POST",
@@ -247,6 +262,26 @@
       "method": "POST",
       "path": "/v1/proposals/{proposalId}/reject"
     },
+    {
+      "operation_id": "postReviewComposerAgents",
+      "method": "POST",
+      "path": "/v1/review-composer/agents"
+    },
+    {
+      "operation_id": "postReviewComposerAgentsByArmIdConnectionIntents",
+      "method": "POST",
+      "path": "/v1/review-composer/agents/{armId}/connection/intents"
+    },
+    {
+      "operation_id": "postReviewComposerAgentsByArmIdConnectionRevoke",
+      "method": "POST",
+      "path": "/v1/review-composer/agents/{armId}/connection/revoke"
+    },
+    {
+      "operation_id": "postReviewComposerAgentsByArmIdConnectionTest",
+      "method": "POST",
+      "path": "/v1/review-composer/agents/{armId}/connection/test"
+    },
     {
       "operation_id": "postSourceConnections",
       "method": "POST",

{millwork_solver-0.1.1 → millwork_solver-0.1.2}/src/millwork_solver/_core/catalog.py

@@ -89,9 +89,9 @@ class _OperationCatalog:
         sources = view.get("sources")
         expected_counts = view.get("expected_counts")
         if not isinstance(sources, dict) or expected_counts != {
-            "operations": 79,
-            "included": 63,
-            "excluded": 16,
+            "operations": 89,
+            "included": 70,
+            "excluded": 19,
         }:
             raise _OperationBoundaryError("PY1 pointer/count contract drifted")
 
@@ -130,10 +130,10 @@ class _OperationCatalog:
             for operation_id, classification in classification_by_id.items()
             if classification.get("disposition") == "exclude"
         }
-        if len(wire_operations) != 79 or len(f1_included) != 63 or len(f1_excluded) != 16:
-            raise _OperationBoundaryError("F1 62/16 operation partition drifted")
+        if len(wire_operations) != 89 or len(f1_included) != 70 or len(f1_excluded) != 19:
+            raise _OperationBoundaryError("F1 70/19 operation partition drifted")
         if included_set != f1_included or len(included_ids) != len(included_set):
-            raise _OperationBoundaryError("PY1 pointer does not resolve exactly to F1's 62 includes")
+            raise _OperationBoundaryError("PY1 pointer does not resolve exactly to F1's 70 includes")
         if set(classification_by_id) != set(wire_operations):
             raise _OperationBoundaryError("F1 classifications do not cover OpenAPI exactly")
 
@@ -162,8 +162,8 @@ class _OperationCatalog:
         if snapshot.get("schema_version") != 1:
             raise _OperationBoundaryError("installed Python wire snapshot version drifted")
         operations = snapshot.get("operations")
-        if not isinstance(operations, list) or len(operations) != 63:
-            raise _OperationBoundaryError("installed Python wire snapshot must contain 62 operations")
+        if not isinstance(operations, list) or len(operations) != 70:
+            raise _OperationBoundaryError("installed Python wire snapshot must contain 70 operations")
 
         allowed: dict[str, _Operation] = {}
         for item in operations:

{millwork_solver-0.1.1 → millwork_solver-0.1.2/src/millwork_solver.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: millwork-solver
-Version: 0.1.1
+Version: 0.1.2
 Summary: Sync and async Python clients for the Millwork Solver API
 Author: Millwork
 License-Expression: Apache-2.0
@@ -101,12 +101,10 @@ with Solver() as client:
           path_parameters={"verifierId": verifier_id}, idempotency_key=str(uuid.uuid4())))
 ```
 
-The protected-connection methods below describe this source checkout. The
-published `millwork-solver==0.1.0` wheel has six public verifier operation
-IDs in its catalog but does not include `verifier_connection`. Until a wheel carrying
-these methods is published and read back, use the
-[private CLI or dashboard path](https://docs.getmillwork.dev/guides/connect-an-output-check#connect-a-protected-endpoint)
-for a protected endpoint.
+The published `millwork-solver==0.1.1` wheel includes the public verifier
+operation IDs and `verifier_connection`. Install that pinned release to run
+the protected-connection methods below. The earlier `0.1.0` wheel does not
+include these methods.
 
 For a protected endpoint, register that endpoint with the same secretless
 `postVerifiers` body, then use **its** `verifier_id` for the private handoff.