It seems if I have a folder path:
/Folder/Parent/Child
And I use the "send to" context menu and select Child (/Folder/Parent/Child) to TextCrawler2 and search it works fine, and then if I use the "send to" context menu again and pick its parent later (/Folder/Parent), then /Folder/Parent/Child shows up instead. Once I manually select /Folder/Parent, it will work from then on.
It appears what happens is that TextCrawler caches used paths, and then when it is invoked with a path passed in, it searches to see if that the current path matches a previously used path, but the match doesn't appear to need to be an exact match, so /Folder/Parent is the start of /Folder/Parent/Child so it picks /Folder/Parent/Child instead of /Folder/Parent.
This is a very undesirable response. I hope this post is articulate enough.