App Functions — Validate Before Save

A successful save is the START of validation, not the end. salla_functions action=save returns 200 once the wrapper's first and last line match — it does not type-check or run your body, so a 200 ≠ a correct function. Treat every salla_functions action=save as the trigger for one closed loop: validate → fix → re-save → re-validate until clean. A handler that type-fails or breaks at runtime surfaces after save, once it deploys to the demo stores.

The loop (each step below): (1) wrapper first/last line matches the template → (2) the TypeScript compiler against the trigger's .d.ts at the editor's bar (non-strict, ignore unused TS6133) → (3) each outbound Admin API call's request/response validates against its documented OpenAPI → (4) salla_functions action=preview runs clean on a demo store (→ salla-app-functions-test) → fix any failure, re-save, and run the loop again. Steps 1–2 are the only pre-save safety net; run them before each save.