v0.1.2

A bug-fix release. Two of the three fixes are about things the kit did without
telling you: one sent an application a step early, the other left rejections
looking like open applications.

On a one-page Easy Apply form, "next" was Submit

The Easy Apply driver advances by taking the last non-cancel button in the
modal. On a multi-page form that is Next or Review. On a form with a single page
it is Submit, and the driver had no way to tell the two apart.

Measured 2 Oct: the modal opened with no page counter, the first advance sent
the application, and there was no review step. Nothing false went out, because
the contact page is checked before advancing. But the review step is also where
the pre-ticked "follow this company" box gets unticked, and that opt-in was left
on. If you use Easy Apply on 0.1.1, some of your one-page applications have
probably gone out the same way.

The driver now reads the page counter before every advance. A modal with no
counter is one page, so the next press submits, and the run reads the whole
form before deciding to.

The blacklist never saw the company name

The aggregator list and your profile's blacklist are both lists of company
names. The filter ran them over the posting's title, description and apply
host, which do not carry the company. Measured 2 Oct: an aggregator named in the
skill's own list got through every filter and was only caught once its job page
was open. The company is now part of what the filter reads. On LinkedIn the
reliable source for it is the first "name" in the detail response, because
companyDetails often comes back as ?.

Some rejections did not read as rejections

/seekter-log finds rejections with a regex. It had no phrasing for a role
being filled or closed, and it had not moving forward but not unable to move forward. Measured 2 Oct: one rejection used both phrasings and matched nothing.
A miss does not look like an error. It looks like an application that is still
open, so the row stays applied indefinitely. The list now covers the
filled/closed phrasings and unable to move / unable to proceed.

The same sweep found Outlook's [role=option] rows working again, four days
after they had disappeared. The inbox reference now says to probe all three list
selectors and use whichever one answers.

Also

• CHANGELOG.md is new since 0.1.1. The 0.1.1 zip did not include it, so this
  is the first download that does. /seekter-git now covers releases too: once a
  pull request is merged, it can write the entry and publish the version.
• The README opens on a new cover image. The image it used to point at had been
  deleted, so the first line had been broken.
• Indeed: the tenth measured pass returned nothing new for the tenth time.
• Jobicy: eight tags returned zero rows from an API that was otherwise
  answering normally.
• LinkedIn: notifications against searches, measured a seventh time. 13 ids of
  63 overlapped.

Upgrading

Nothing to migrate. Replace the files and keep your profile/, applications/
and runs/; they are git-ignored and are not touched.