Before beta, this sort of shift is fine. After this is API-exposed, this sort of change could be an issue. Can you add a follow-up item to capture these bounds in a test (probably a unit or integration test would be sufficient):    * largest successfully allowed recursion depth  * smallest disallowed recursion depth    That will give us some visibility on our side if that line shifts