make the trigger steps's fake scheduler behave like the real one

The fake scheduler in the trigger step's test had drifted away from the real thing.
I had relied on the interface assertion to keep them in sync, but the interface doesn't capture cardinality of return values.

Not sure how to improve the test coverage, but it's fixed now.