diff --git a/checkpoint.json b/checkpoint.json new file mode 100644 index 000000000..65ab96ad1 --- /dev/null +++ b/checkpoint.json @@ -0,0 +1,61 @@ +{ + "timestamp": "2026-03-19T13:47:58.849657Z", + "current_node": "draft", + "completed_nodes": [ + "start", + "draft" + ], + "node_retries": { + "start": 1, + "draft": 1 + }, + "context_values": { + "internal.node_visit_count": 1, + "internal.thread_id": "start", + "current_node": "draft", + "internal.retry_count.start": 1, + "outcome": "success", + "last_response": "# Testing Human Gate with Auto-Approve\n\nHere's a short greeting message:\n\n---\n\n**Hello! 👋**\n\nWelcome to Fabro! This test demonstrates how human gates work with auto-approval enabled. The workflow w", + "response.draft": "# Testing Human Gate with Auto-Approve\n\nHere's a short greeting message:\n\n---\n\n**Hello! 👋**\n\nWelcome to Fabro! This test demonstrates how human gates work with auto-approval enabled. The workflow will pause at the human gate stage, but since auto-approve is configured, it will automatically continue without requiring manual intervention.\n\nThis is useful for testing workflows that include human approval steps in CI/CD pipelines or automated processes where you want to validate the gate logic without blocking on actual human approval.\n\n---\n\nIf you're looking to set up this test, you'd typically:\n\n1. Define a workflow with a human gate stage\n2. Configure auto-approve in the test setup\n3. Run `fabro run ` to execute\n4. Verify the gate is triggered and auto-approved in the output logs\n\nLet me know if you need help setting up the workflow definition or test configuration!", + "thread.start.current_node": "draft", + "graph.rankdir": "LR", + "failure_class": "", + "graph.goal": "Test human gate with auto-approve", + "internal.retry_count.draft": 1, + "current.preamble": "Goal: Test human gate with auto-approve\n", + "failure_signature": "", + "internal.fidelity": "compact", + "internal.run_id": "01KM35MF571ZNDXSZW7E0R4D94", + "last_stage": "draft" + }, + "logs": [], + "node_outcomes": { + "draft": { + "status": "success", + "context_updates": { + "last_response": "# Testing Human Gate with Auto-Approve\n\nHere's a short greeting message:\n\n---\n\n**Hello! 👋**\n\nWelcome to Fabro! This test demonstrates how human gates work with auto-approval enabled. The workflow w", + "last_stage": "draft", + "response.draft": "# Testing Human Gate with Auto-Approve\n\nHere's a short greeting message:\n\n---\n\n**Hello! 👋**\n\nWelcome to Fabro! This test demonstrates how human gates work with auto-approval enabled. The workflow will pause at the human gate stage, but since auto-approve is configured, it will automatically continue without requiring manual intervention.\n\nThis is useful for testing workflows that include human approval steps in CI/CD pipelines or automated processes where you want to validate the gate logic without blocking on actual human approval.\n\n---\n\nIf you're looking to set up this test, you'd typically:\n\n1. Define a workflow with a human gate stage\n2. Configure auto-approve in the test setup\n3. Run `fabro run ` to execute\n4. Verify the gate is triggered and auto-approved in the output logs\n\nLet me know if you need help setting up the workflow definition or test configuration!" + }, + "notes": "Stage completed: draft", + "usage": { + "model": "claude-haiku-4-5", + "input_tokens": 2022, + "output_tokens": 202, + "cache_read_tokens": 0, + "cache_write_tokens": 0, + "cost": 0.0024256 + }, + "duration_ms": 3149 + }, + "start": { + "status": "success", + "duration_ms": 0 + } + }, + "next_node_id": "approve", + "node_visits": { + "start": 1, + "draft": 1 + } +} \ No newline at end of file diff --git a/nodes/draft/prompt.md b/nodes/draft/prompt.md new file mode 100644 index 000000000..75d67e5b4 --- /dev/null +++ b/nodes/draft/prompt.md @@ -0,0 +1,4 @@ +Goal: Test human gate with auto-approve + + +Write a short greeting message. \ No newline at end of file diff --git a/nodes/draft/provider_used.json b/nodes/draft/provider_used.json new file mode 100644 index 000000000..f79dec8be --- /dev/null +++ b/nodes/draft/provider_used.json @@ -0,0 +1,5 @@ +{ + "mode": "prompt", + "provider": "anthropic", + "model": "claude-haiku-4-5" +} \ No newline at end of file diff --git a/nodes/draft/response.md b/nodes/draft/response.md new file mode 100644 index 000000000..b14ec0ed9 --- /dev/null +++ b/nodes/draft/response.md @@ -0,0 +1,22 @@ +# Testing Human Gate with Auto-Approve + +Here's a short greeting message: + +--- + +**Hello! 👋** + +Welcome to Fabro! This test demonstrates how human gates work with auto-approval enabled. The workflow will pause at the human gate stage, but since auto-approve is configured, it will automatically continue without requiring manual intervention. + +This is useful for testing workflows that include human approval steps in CI/CD pipelines or automated processes where you want to validate the gate logic without blocking on actual human approval. + +--- + +If you're looking to set up this test, you'd typically: + +1. Define a workflow with a human gate stage +2. Configure auto-approve in the test setup +3. Run `fabro run ` to execute +4. Verify the gate is triggered and auto-approved in the output logs + +Let me know if you need help setting up the workflow definition or test configuration! \ No newline at end of file diff --git a/nodes/draft/status.json b/nodes/draft/status.json new file mode 100644 index 000000000..c4914f543 --- /dev/null +++ b/nodes/draft/status.json @@ -0,0 +1,6 @@ +{ + "status": "success", + "notes": "Stage completed: draft", + "failure_reason": null, + "timestamp": "2026-03-19T13:47:58.848985+00:00" +} \ No newline at end of file diff --git a/nodes/start/status.json b/nodes/start/status.json new file mode 100644 index 000000000..4b5f652c3 --- /dev/null +++ b/nodes/start/status.json @@ -0,0 +1,6 @@ +{ + "status": "success", + "notes": null, + "failure_reason": null, + "timestamp": "2026-03-19T13:47:55.697476+00:00" +} \ No newline at end of file