C1 — CLICK-TO-EXECUTE ("we ask a question. Questions are solved. And I go to execute... I could just click a thing and execute"). Body: {"record_id": <yield record id>} OR {"question": <text resolving to a record>}.

Wraps the SAME execution path the MCP execute_algorithm verb uses (execution.execute) to map the route; for records carrying an execution_blueprint it runs motherboard/engine/spine.run_blueprint — the real runtime, runnable-prefix semantics.

HONESTY: nothing fake-fires. steps[] reports exactly what happened: "fired" (ran with a confirm), "blocked" (could not fire — the recruit lane), "skipped" (not reached / mapped only). A record with no resolved blueprint is MAPPED (skipped steps), never pretend-run. The engine being unimportable is a 503, never a crash.