v0.5.5

• A Jev outage costs a batch, not the run. After two 5xx answers in a row, a batch of questions is asked one
  at a time within the retries it had left, and the answers that came back are kept.
  (#131)
• Back stays on the task's site. Back is offered only when the page before is on the same site, so a wizard
  that shares one address no longer steps back to a blank page. (#132)
• Counts over long lists fit in the run's notes. Records are tallied compactly with their citations, code
  computes the totals and rankings, and a run that still fills its notes ends observation_limit with what it
  had grounded rather than an error. (#133)
• Star ratings drawn as icons are read. A rating shown only as a class such as star-rating Three, or an
  accessible label, now appears in the page text. (#134)
• Date pickers and date fields can be used. Links that act as buttons, such as a calendar's days, are
  offered as controls, and native date, time, month and week fields are filled in ISO form and read back.
  (#135, #136)
• A browser that never loads the first page reports unavailable. Such a timeout is retried once; a
  timeout on the agent's own later navigation remains an error. (#137)
• Evals record what they measured. Every task has a version that a test forces up when its grader changes,
  every result row records the build and task version it ran, published results are committed rows that are
  never rewritten, and the tables in the docs are generated from them. --only searches every suite and rejects
  a task it cannot find. (#139)
• A comparison missing one of its records no longer names a winner. When a page of a list named a record the
  reader could not tie to the page's text, or more records than one page holds, the record was dropped and a later
  page could still settle "the cheapest" without it. That requirement now stays open for the rest of the run, so
  the run reports it could not settle the comparison instead of answering from part of the list. A page that
  states its own order still settles it on the leading record.
  (#129)
• An answer about what the run bought is checked against the page it bought on. An Amazon run bought one pen
  and reported another, citing the search listing; the checkout page it had read named the right one. In a run authorized to commit, Jev
  now judges which of its clicks, Enters and accepted dialogs committed something, once the run answers and only
  for those whose pages it read; the answer is checked against those pages, and the composer is told which notes
  come from them. Other runs make no extra call. (#117)
• A click that found its element redrawn no longer spends a step. A date picker that redraws under a click
  dispatches nothing, but the stale step counted toward max_steps, and Google Flights runs spent two to four of
  them. It still counts toward the stall budget, which bounds a page that never stops redrawing.
  (#101, #94)
• Fewer wasted steps on forms and lists. The target question now sets a form's mode (a trip type) before its
  submit, and knows that a broad "Explore" control is not the search asked for; a calendar's fare per day is an
  input, not evidence to stop and read; a plan no longer turns "report the total" into "the total once the order
  is finished"; and a shortcut for a count over records goes to the page listing them, not a page about one of
  them. (#99, #101)