Our Jira app ships jira:workflowValidator rules and I went looking for the supported way to remove one.
The REST reference blocks it. PUT /rest/api/3/workflow/rule/config/delete says “Only Connect apps can use this operation”, and its Scopes block adds “Forge and OAuth2 apps cannot access this REST resource.” The GET and PUT on the same resource both name Connect and Forge, and only the delete operation carries that line.
Step 3 of the app migration tutorial for workflow rules reads the other way. It shows a rule with "ruleKey": "forge:workflow-post-function" and an ari:cloud:ecosystem key, then tells the cloud app to use its cloudWorkflowRuleIds to “Delete the workflow transition rule configuration”, linking to that same Connect-only operation. ECO-1244 lists all three endpoints, expects “Newly added forge rules can be removed”, and was closed as Fixed in April.
For a rule I create rather than migrate, I have assumed POST /rest/api/3/workflows/update is the Forge path, since the capabilities docs describe a Forge rule as forge:expression-validator with its config inside parameters. The PUT can disable a rule, so I am not stuck today.
Did ECO-1244 open the delete operation to Forge apps and the reference has not caught up, or is that tutorial link wrong for Forge?