Orphan ordering, filtering OSRA178,213-216

inclusive of:
OSRA178
OSRA213
OSRA214
OSRA215
OSRA216
I'm sorry, this is probably starting to sound nitpicky (or has for a long time already): Given that this is a high-level acceptance test, I would prefer to raise the descriptions to the level of user-application interaction. The user won't see the underlying HTML, but they will see the rendered panel. So, `Then I should see the "New Sponsor" panel`, and the step implementation can reuse `Then I should see html ...`. Step reuse is definitely a good goal to pursue, but not at the cost of sacrificing readability by non-technical users. Likewise in the following scenario.