v0.1.8

Extension contract versions are unchanged: world 5, provider 5, bot 6.

Extensions and console

• A failed registry request now reports the host and the underlying error code, e.g.
  registry.npmjs.org: fetch failed (ERR_TLS_CERT_ALTNAME_INVALID: …), instead of undici's bare
  fetch failed (#190, Pal-AI-Lab/Coopanion#78).
• Search, package details and update checks use the registry that installs use: the result of
  pnpm config get registry --ignore-workspace in extensions/ (extensions/.npmrc, the user's .npmrc,
  pnpm_config_registry). It is read once per process; when pnpm cannot report one, the query fails with
  pnpm's output (#190).
• The extension page shows a package's author from package.json author (the name only, for both the
  string and the object form) instead of the npm publisher, which Trusted Publishing reports as
  GitHub Actions. A market card shows the author once the package document has arrived (#187, #186).
• The package detail drawer lists every version still in the registry and can install any of them through the
  existing check and install flow (pnpm add name@version, effective after a restart). Clicking a card opens its
  details; removing takes two clicks, and the second-click state says that other bots using the same extensions
  directory are affected (#178).

Worlds

• QQ: shared cards keep their source name, content title and target link in the message body
  ([分享 来源:… 标题:… 链接:…]). Only a single http(s) URL is taken as the link; source name and title are
  written as the card declares them and are not verified (#174, #170).

Thanks

• @DTMosken: QQ shared-card fields (#174, #170) and the extension author fix (#187, #186).
• @kwk1001: installing earlier extension versions and the card interaction changes (#178).
• @Lime809: the diagnostic report behind the registry error fix (Pal-AI-Lab/Coopanion#78).