The decision to give an entry the "in" CSS class, which displays it as open, is made in an angularjs controller method, instead of in the view.

Right now this is functionally identical, but it opens the door to more complex logic in this function, e.g. to allow for several entries to be open at once.
Instead of storing in the angularjs root scope a single currently open entry, an array of open entries is stored.

Currently this array only has at most a single entry, and current behavior is functionally identical to the previous one. But this is a step towards having several open entries in the app.
Added comments to openEntrySvc angularjs methods.
Changed openEntrySvc methods to that they potentially could work with several entries open at once.
Fix: when opening an entry, if the user has not selected the "open all entries" checkbox, any other open entry is closed.
When loading entries from the server, if the user has selected the "open all entries" config option, new entries are shown open by default.

The default behavior is the same as until now: new entries are shown closed by default, and at most a single entry is open at a given time (if the user opens an entry, any other open entry is closed).
Acceptance test for Quick Reading mode should now pass either if the entry being scrutinized has become read or is in the process os becoming read.
Acceptance test for Quick Reading mode creates just 10 entries instead of 100 during test setup. It runs much faster now.
Added acceptance tests for the "open all entries by default" feature.