Skip to content

feat: ScenarioBundle JSON Schema (request + response v1)#26

Closed
George-iam wants to merge 2 commits intomainfrom
feat/scenario-bundle-schema-20260310
Closed

feat: ScenarioBundle JSON Schema (request + response v1)#26
George-iam wants to merge 2 commits intomainfrom
feat/scenario-bundle-schema-20260310

Conversation

@George-iam
Copy link
Contributor

Summary

  • Adds api.scenarios.bundle.request.v1.json: full ScenarioBundle schema covering agents, humans, workflow steps (retry, human_task, reminders, escalation, per-step deadlines) and intent submission settings (deadline_at, reminders, escalate_to, max_delivery_attempts)
  • Adds api.scenarios.bundle.response.v1.json: response from POST /v1/scenarios/bundle with intent_id, status, pending_with, resolved agents, and workflow_compile_id

Part of the Durable Workflow & Scenario Execution Plan, Group 5-A.

Test plan

  • JSON Schema is valid (draft 2020-12)
  • scenario_id pattern allows dot-separated lowercase identifiers
  • WorkflowStepSpec required fields: step_id, tool_id
  • IntentSpec required field: type

Made with Cursor

Adds two new public-API schemas:
- api.scenarios.bundle.request.v1.json: full ScenarioBundle definition
  covering agents, humans, workflow steps (with retry, human_task,
  reminders, escalation, deadlines) and intent submission settings.
- api.scenarios.bundle.response.v1.json: response from POST /v1/scenarios/bundle
  including intent_id, status, pending_with, resolved agents, and
  workflow_compile_id.

These schemas are the canonical contract for the durable scenario
execution feature described in DURABLE_WORKFLOW_PLAN.md.

Made-with: Cursor
@George-iam George-iam closed this Mar 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant