v4.8.0 — the plugin has a version, and a comment stays on its own element

• The plugin declares a version. Until now it shipped without one, so every
  commit to main counted as a release. Your host now compares version numbers
  and updates when this number changes. A copy installed before this release has
  no version on record and keeps comparing commits until it updates once.
• A comment lands on the element it was left on, not a lookalike. The
  selector recorded for a comment was cut off after eight steps, and a short
  path can first-match a different element elsewhere on the page, which is the
  one querySelector returns. The recorded selector is now the shortest one
  that matches a single element, and a path still ambiguous at full length is
  rooted at body so the chain is exact.
• Reanchoring prefers the element carrying the comment's words. When a
  selector still parses but its match shares nothing with what was captured, an
  element scoring on text or identity is now taken ahead of it.
• Both host manifests carry the full set of distribution metadata: version,
  display name, homepage, repository, license, and keywords covering what
  someone would search for. Descriptions across all three manifests are drawn
  from the README.
• CI runs the tests on Node 18 and 22, checks the stamped shell for drift, and
  validates both manifests with the same tool the community-marketplace review
  pipeline runs. A release workflow rejects a tag that disagrees with the
  manifest version.
• Issue and pull request templates, a changelog, and a release procedure in
  CONTRIBUTING.md.

Install

/plugin marketplace add Cavalry-Collective/visual-stack
/plugin install vstack@cavalry-collective

Already installed:

/plugin marketplace update cavalry-collective
/plugin update vstack@cavalry-collective
/reload-plugins

Full changelog: https://github.com/Cavalry-Collective/visual-stack/blob/main/CHANGELOG.md