0.2.2

An interface release, and the release process is part of it: the quota rhythm is
editable on the page, the capsule's gear opens the settings dialog rather than the
plugins list, and a tag publishes the package and its notes without a stored
token.

Fixed

• The quota rhythm section reads as one row. Its two intervals are labelled
  Shortest/Longest quota update interval, share a line at the same width, and
  no longer carry the three explanatory paragraphs; a row that reports no
  intervals at all says so instead of waiting on them forever.
• The capsule's gear opens Settings on the plugin's row, not the Plugins
  page. It presses the shell's own way in — its trigger, or the account
  launcher's Settings row where a package has taken that seat — then this
  plugin's nav row; the usage panel's Plugin settings button does the same, and
  both fall back to the Plugins page where the shell answers neither press.

Added

• The quota rhythm is editable on the page. The two intervals were
  config-file-only; they now have a section of their own, saved as one setting,
  with a floor above its ceiling refused where the reader can see it.
• A tag publishes the release. release.yml checks the tag against the
  manifest, re-runs the suite, and publishes to npm through trusted publishing —
  no token is stored — then opens the release page from the changelog section.
• npm run check:pack, which packs the tarball and reads it, because
  files is an allowlist whose two failure modes are both silent.
• The activation suite runs in CI, on the harness packages from npm when no
  DSH installation is present.
• CI reads either line ending. A checkout on Windows has CRLF by default, and
  the suite's workflow parser found nothing in one — worth a case, since that
  reads as "CI does not run the tests" on one platform only.
• The workflows use current actions. checkout and setup-node moved to v7,
  which is what makes the publish path OIDC alone: before v7 setup-node left a
  dummy NODE_AUTH_TOKEN in the environment.

Changed

• 398 offline checks, up from 370.
• The workflows are checked too, by a new ci suite: an action pinned to a
  branch, a tab in the YAML, or a release that could publish before comparing the
  tag with the manifest fails the suite rather than a release.