Creating or editing a task through dash.openwaf.dev (dashboard, API, CLI) answered 403 from our own edge WAF when the script, the input or the agent goal contained text that looks like a shell command, SQL, HTML or a file path, such as cat /etc/passwd in an input; even the script of the quickstart was refused. On the task routes (/v1/orgs/{org}/tasks and below) the WAF now skips the injection rules that such text triggers; they need a session or a token, and the API validates every field. The other WAF rules, the shields and the rest of the API keep their inspection.
script is accepted as is; script_base64 keeps working but is no longer needed.
The fix uses a new form of WAF exception path: a * before the end of path_pattern stands for any characters except /, so /v1/orgs/*/tasks covers that route for every organization and nothing else under /v1/orgs/. A trailing * is still a prefix.