Yes, the screenshots in the beta forum address what the parent-folder script did before. But it is different than what you want.
In the screenshots, you have a pop-up that allows you to apply the conditions underneath to any or all subfiles. But, the actions still work on the top level folder that is being matched. You can use this to color a parent folder a certain color based on the subfiles underneath it.
Ex: "If, for any subfile, date modified is after date last matched, color the current file (the parent folder) green"
What you want is for some files to be acted on based on conditions of the parent folder (it's the opposite direction). What is in the 3.0 version doesn't do that. What I suggested above was adding "parent folder" to that pop-up. That way, the conditions underneath that heading would apply to the parent folder while the actions apply to the file underneath it.
Ex: "If, for the parent folder, date modified is after date last matched, color the current file (the file underneath the parent folder) green"
In the first example, the parent folder is colored green if any subfile has been modified. In the second example (which doesn't exist yet but I am considering it), the file is color green if the parent folder has been modified, which is more in line with what you want.
As I said before, I'm considering adding this before I start the 3.0 beta. One issue is that it's not exactly the reverse of the first one. The first one will match subfiles any level deep from the folder being matched. In the second one, it only goes one level up from the file being matched. I'm not sure if this matters to people that would need this functionality but it's something I am pondering.