Call funnel.test_end_to_end

Prove the WHOLE funnel — 'test the whole funnel', 'run a lead all the way through' — by running one synthetic lead all the way through it, in order: the form on the landing page, then the lead reaching the pipeline's first stage, then the sequence's first send, then the deal moving a stage on, then the closing event. It only runs once EVERY part has passed its own test, and it refuses by name if any has not. The lead is always synthetic and every send goes to the workspace's designated test address, never a real person. It writes passed, or failed naming the exact hop, onto the funnel's plan — and if a hop cannot be driven at all it says so and writes NOTHING, because a funnel that was never tested is not a funnel that failed. Not for testing one part on its own — that is funnel.test_part. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.