ai-forge-cli 2.0.2__tar.gz → 2.0.3__tar.gz

{ai_forge_cli-2.0.2/src/ai_forge_cli.egg-info → ai_forge_cli-2.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-forge-cli
-Version: 2.0.2
+Version: 2.0.3
 Summary: Context walker for the Forge spec system
 Requires-Python: >=3.11
 License-File: LICENSE

{ai_forge_cli-2.0.2 → ai_forge_cli-2.0.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ai-forge-cli"
-version = "2.0.2"
+version = "2.0.3"
 description = "Context walker for the Forge spec system"
 requires-python = ">=3.11"
 dependencies = ["pyyaml>=6.0"]

{ai_forge_cli-2.0.2 → ai_forge_cli-2.0.3/src/ai_forge_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-forge-cli
-Version: 2.0.2
+Version: 2.0.3
 Summary: Context walker for the Forge spec system
 Requires-Python: >=3.11
 License-File: LICENSE

{ai_forge_cli-2.0.2/src/cli/skills/forge-design → ai_forge_cli-2.0.3/src/cli/skills/forge-build}/references/framework.md

@@ -229,6 +229,12 @@ operations:
     visibility: <Visibility>
     contract: <contract.id>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: <integer>
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: [<error.id>]                   # errors surfaced at this step
+        condition: <expression>                # omit if unconditional
 relationships:
   - target: <element.id>
     type: <RelationshipType>
@@ -562,3 +568,4 @@ forge graph                             # visualise the dependency graph
 - `implementation/` exists only directly under a system directory and contains only `datastores.yaml`, `tests.yaml`, `environments.yaml`, `deployments.yaml`.
 - Element files contain only inline properties and operations.
 - `workbench/` exists only directly under a system directory and contains only forge process artifacts.
+- Operation `steps` are required for `command`, `async_command`, and `event_handler` operations with non-trivial logic (any operation that calls another operation, writes to a datastore, or branches). Simple `query` and `subscription` operations may omit steps.

{ai_forge_cli-2.0.2/src/cli/skills/forge-cast → ai_forge_cli-2.0.3/src/cli/skills/forge-build}/references/templates.yaml

@@ -110,7 +110,14 @@ operations:
     outputs: []
     raises: []
     visibility: <public | internal | private>
+    contract: <contract.id or omit>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: 1
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: []
+        condition: <expression>                # omit if unconditional
 relationships: []
 policies: []
 

{ai_forge_cli-2.0.2/src/cli/skills/forge-review → ai_forge_cli-2.0.3/src/cli/skills/forge-cast}/references/framework.md

@@ -229,6 +229,12 @@ operations:
     visibility: <Visibility>
     contract: <contract.id>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: <integer>
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: [<error.id>]                   # errors surfaced at this step
+        condition: <expression>                # omit if unconditional
 relationships:
   - target: <element.id>
     type: <RelationshipType>
@@ -562,3 +568,4 @@ forge graph                             # visualise the dependency graph
 - `implementation/` exists only directly under a system directory and contains only `datastores.yaml`, `tests.yaml`, `environments.yaml`, `deployments.yaml`.
 - Element files contain only inline properties and operations.
 - `workbench/` exists only directly under a system directory and contains only forge process artifacts.
+- Operation `steps` are required for `command`, `async_command`, and `event_handler` operations with non-trivial logic (any operation that calls another operation, writes to a datastore, or branches). Simple `query` and `subscription` operations may omit steps.

{ai_forge_cli-2.0.2/src/cli/skills/forge-build → ai_forge_cli-2.0.3/src/cli/skills/forge-cast}/references/templates.yaml

@@ -110,7 +110,14 @@ operations:
     outputs: []
     raises: []
     visibility: <public | internal | private>
+    contract: <contract.id or omit>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: 1
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: []
+        condition: <expression>                # omit if unconditional
 relationships: []
 policies: []
 

{ai_forge_cli-2.0.2/src/cli/skills/forge-cast → ai_forge_cli-2.0.3/src/cli/skills/forge-design}/references/framework.md

@@ -229,6 +229,12 @@ operations:
     visibility: <Visibility>
     contract: <contract.id>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: <integer>
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: [<error.id>]                   # errors surfaced at this step
+        condition: <expression>                # omit if unconditional
 relationships:
   - target: <element.id>
     type: <RelationshipType>
@@ -562,3 +568,4 @@ forge graph                             # visualise the dependency graph
 - `implementation/` exists only directly under a system directory and contains only `datastores.yaml`, `tests.yaml`, `environments.yaml`, `deployments.yaml`.
 - Element files contain only inline properties and operations.
 - `workbench/` exists only directly under a system directory and contains only forge process artifacts.
+- Operation `steps` are required for `command`, `async_command`, and `event_handler` operations with non-trivial logic (any operation that calls another operation, writes to a datastore, or branches). Simple `query` and `subscription` operations may omit steps.

{ai_forge_cli-2.0.2 → ai_forge_cli-2.0.3}/src/cli/skills/forge-design/references/templates.yaml

@@ -110,7 +110,14 @@ operations:
     outputs: []
     raises: []
     visibility: <public | internal | private>
+    contract: <contract.id or omit>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: 1
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: []
+        condition: <expression>                # omit if unconditional
 relationships: []
 policies: []
 

{ai_forge_cli-2.0.2/src/cli/skills/forge-build → ai_forge_cli-2.0.3/src/cli/skills/forge-review}/references/framework.md

@@ -229,6 +229,12 @@ operations:
     visibility: <Visibility>
     contract: <contract.id>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: <integer>
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: [<error.id>]                   # errors surfaced at this step
+        condition: <expression>                # omit if unconditional
 relationships:
   - target: <element.id>
     type: <RelationshipType>
@@ -562,3 +568,4 @@ forge graph                             # visualise the dependency graph
 - `implementation/` exists only directly under a system directory and contains only `datastores.yaml`, `tests.yaml`, `environments.yaml`, `deployments.yaml`.
 - Element files contain only inline properties and operations.
 - `workbench/` exists only directly under a system directory and contains only forge process artifacts.
+- Operation `steps` are required for `command`, `async_command`, and `event_handler` operations with non-trivial logic (any operation that calls another operation, writes to a datastore, or branches). Simple `query` and `subscription` operations may omit steps.

{ai_forge_cli-2.0.2 → ai_forge_cli-2.0.3}/src/cli/skills/forge-review/references/templates.yaml

@@ -110,7 +110,14 @@ operations:
     outputs: []
     raises: []
     visibility: <public | internal | private>
+    contract: <contract.id or omit>
     policies: []
+    steps:                            # required for command/async_command/event_handler with non-trivial logic
+      - order: 1
+        description: <what happens in this step>
+        calls: <operation.id or datastore.id>  # omit if no cross-boundary call
+        raises: []
+        condition: <expression>                # omit if unconditional
 relationships: []
 policies: []