Okay, yah.  It seems you're right that ```action_variable``` is never made true.  It looks like the cases that it used to report are now individually calling the new ```loose_action``` function.  So I support we can just pull out references to ```action_variable``` unless you see a need for it?  The new function gets us the code re-use that it seemed to be aiming for initially.

When you talk about ```:action``` in both URL and options, do you mean something like this:
```ruby
match '/:controller/:action', action: 'blah'
```
It seems we catch that currently:
```
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
| Confidence | Class | Method | Warning Type   | Message                                                                       >>
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
| High       |       |        | Default Routes | All public methods in controllers are available as actions in routes.rb near l>>
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
```

Though I'll admit, I'm not sure if Rails itself will accept conflicting route directives like that.