you could try, what happens, using pdoMenu of pdoTools
I like to run this when things get weird:
http://bobsguides.com/sitecheck-promo.html.
I now remember running into exactly the same problem a couple years ago. Everything was fine until I started adding user groups, modifying ACLs etc. then WF started doing the same thing. I never did find the issue and had to go with a static menu to get around it. A disappointing solution. It seems I'm reliving the same choice. Very irritating.
Todd
You said earlier that the Contact page was not in a resource group. The only way an ACL entry could affect it showing up is if it has a parent or ancestor that's in a resource group (barring something weird like an invalid parent field or template somewhere -- which is why I like to run SiteCheck).
That's my point, the Contact page is not in any resource group, the act of simply creating an Editor rg is enough to screw up WF.
Todd
You may have an invalid modResourceGroupResource that's making WF think that the contact page is in the Editor resource group, though that wouldn't explain the oddness with the &limit property.
What I find curious is that I'm seeing what appears to be the exact same problem 2 years apart on different sites with different versions of MODX and WF. The only common point I can think of is the tutorial I mentioned earlier. It's all mind-numbingly irritating. I'm close to using EE for this site.
Todd