Thanks for the thoughtful note @Curia , and agreed delegates should take time to review the changes.
On demand for Relay integration
This is a workflow problem. The current Relay integration path is publicly documented and has multiple moving parts that teams have to keep working together in local testing and CI, including node requirements, contracts wiring, relay server setup, and registration. RelayDevKit is scoped as a dev and CI reference harness that makes that workflow reproducible and easier to verify. It is not a production dependency, and it does not assume every team will adopt it.
https://gov.rootstockcollective.xyz/t/ecosystem-grant-themes-update/288
https://dev.rootstock.io/developers/integrate/rif-relay/deployment/
On the quick resubmission after the rescope
The intent was not to rush the process. Since this proposal has been under active review for several weeks and delegates were already engaging with it, we resubmitted so the on-chain version reflects the revised, safer scope rather than leaving the older version as the live artifact. Delegates should still take the time they need to review the update, and we will keep responding to questions in the thread as that review happens.