That was nonsense. Note-collision resolution happens in the
"Preprocessing graphical objects..." phase, which completes for all
three scores in your regtest before the "Fitting music on 1 page..."
phase, which is when we pass the code with the comment //trigger note
collision

Yup. It allows calc_stem_position to skip all of the beam business

and get to

the setting of note positions.

You must mean something like "get to the business of /looking up/ stem
attachment points" that were set long ago.
Could you change the comment and commit message to whatever you thought
I meant when you said "Yup", because what I thought it meant isn't true.
http://codereview.appspot.com/5934050/