use db:schema:load rather than db:migrate to create clean DB
added custom matcher include_match_for
merging selectively
added logic in tasks controller to step to next question
This simpler version of question-sequencing logic lets you specify total
number of questions in activity schema.  Task#next_question! advances
the counter.  Thus the total number of trips through the task body
equals the number of questions in the activity schema divided by the
number of questions used up in each trip through the body.  **BUG:**
need specs to test this.
trying a simpler aproach to sequencing questions
rquire factory_girl_rails in development also, for interactive use
Condition now has a new field, body_repeat_count, which controls how
many times the body is repeated.  Activity schema's questions wrap
around if they run out.
@wip'd out 2 failing cuke scenarios
(https://www.pivotaltracker.com/story/show/74486922)
but otherwise question-sequencing logic working
Updated README to describe new condition body-repeat-count attribute,
modified template factory to include Javascript tags on templates.
for readability, i moved the seed questions into db/questions.yml and
the seed template into db/template.html, and modified the seeds.rb to
read from them