@unstable-dev/unmeshed-mcp 0.1.0

package/knowledge/execution/step-run.schema.md

@@ -0,0 +1,21 @@
+# Step Run Schema
+
+Use step run records to diagnose process execution issues.
+
+Step run records can include:
+- Step ref
+- Step name
+- Step type
+- Status
+- Input used at runtime
+- Output produced at runtime
+- Error or failure details
+- Start/end/update timestamps
+
+Debugging rules:
+- Find the first failed step by status.
+- Compare the failed step's input and script/configuration with previous step outputs.
+- For script failures, verify every `steps.<ref>.output...` path.
+- For HTTP-related failures, inspect the HTTP step's `output.response` and `output.statusCode`.
+- Explain the user-facing root cause and the exact workflow edit needed.
+

package/knowledge/process-definition.schema.md

@@ -0,0 +1,36 @@
+# Process Definition Schema
+
+Use this contract when creating or updating an Unmeshed process definition.
+
+Required top-level shape:
+
+```json
+{
+  "orgId": 1,
+  "namespace": "default",
+  "name": "kebab-case-name",
+  "version": 1,
+  "type": "API_ORCHESTRATION",
+  "description": "What this workflow does",
+  "configuration": null,
+  "steps": [],
+  "defaultInput": null,
+  "defaultOutput": null,
+  "outputMapping": null,
+  "signature": null,
+  "metadata": null,
+  "tags": null,
+  "dependencies": null,
+  "dependents": null
+}
+```
+
+Rules:
+- `name` should be a stable kebab-case workflow identifier.
+- `namespace` defaults to `default` when the user does not specify one.
+- `type` should be `API_ORCHESTRATION` unless the user explicitly needs a different supported process type.
+- `steps` must contain valid step definitions using the shared step schema.
+- `ref` values must be unique across all steps, including nested children.
+- Do not invent unsupported top-level fields.
+- Prefer a valid executable definition over pseudo-JSON.
+