The 10 gravityflow_* tools (branch feat/gravity-flow) have routes verified against the Gravity Flow plugin source and full mocked unit coverage, but no endpoint has been exercised live. This is the largest remaining gap before merging into develop.
To do
Suggested target: /Users/marcel/Projects/Kiron/wordpress (has Gravity Flow). See docs/gravity-flow-testing-plan.md.
Branch: feat/gravity-flow
The 10
gravityflow_*tools (branchfeat/gravity-flow) have routes verified against the Gravity Flow plugin source and full mocked unit coverage, but no endpoint has been exercised live. This is the largest remaining gap before merging intodevelop.To do
npm run verify:tool-namesagainst a live WP install with Gravity Flow (pinGRAVITY_FORMS_*to the local site — see AGENTS.md "Bench" gotchas about not hitting a remote site).gravityflow_get_workflow_status,_get_current_step,_get_steps_by_entry,_get_steps_by_formgravityflow_process_step(approve, then a separate reject/revert), incl.note+inputsgravityflow_send_to_step,_restart_step,_restart_workflow,_cancel_workflowstep_id: "current"alias resolves on get/process/restartSuggested target:
/Users/marcel/Projects/Kiron/wordpress(has Gravity Flow). Seedocs/gravity-flow-testing-plan.md.Branch:
feat/gravity-flow