Separate difficult from expensive
A hard question can also be a poor use of time in the moment.
- Track questions that were correct but consumed an unusual share of module time.
- Rehearse a specific return rule instead of relying on test-day intuition.
- Protect a checking buffer for questions where small setup or reading errors are most costly.