fix: restore the catalog, verify against OpenWA 0.23.3, and correct plugin defects

[rmyndharis]

Three things, in one release round because they share the version bump.

The catalog on main is not installable today

Every download URL in plugins.json names a release tag that was never pushed. The host defaults
PLUGIN_CATALOG_URL to this file on main (src/config/configuration.ts), so every marketplace
install answers 404, and the download is fetched before the #sha256= pin is consulted, so the
operator gets no hint about the cause.

plugins.json -> after-hours-v0.2.5/after-hours.zip   HTTP 404
newest tag   -> after-hours-v0.2.4                   HTTP 200

Nothing in CI can see this: catalog:check only proves plugins.json is regenerable from the working
tree. This PR folds forward rather than cutting the missing tags, so exactly one set of tags is ever
pushed and the 0.2.5-era versions simply never existed publicly.

• Adds scripts/catalog-live-check.mjs and a catalog-live CI job that fetches every download URL and
  verifies its bytes against the pin. It runs on push to main and nightly, deliberately not on pull
  requests, where a version bump is legitimately red until its tags land.
• This job will be red on main until the ten tags are pushed. That is the intended signal.

OpenWA 0.23.3

The plugin runtime contract did not move: src/core/plugins, src/core/hooks and the sandbox sources
are byte-identical from v0.20.0 through v0.23.3, and the engine interface gained only optional trailing
parameters that no capability verb exposes. All ten manifests pass the v0.23.3 loader.

One change is visible to plugins. v0.23.2 made the Baileys body extractor fill message.body for poll
questions, shared event names, business button labels and contact-card vCards, matching what
whatsapp-web.js has always returned. Five plugins used a non-empty body as the test for "a human typed
this", which that invalidates on both engines.

The vendored contract taught that idiom, so it is corrected first (types/openwa.d.ts), then the five
plugins gate on type, denying contact and poll. Two constraints, both easy to get backwards and
both covered by tests: unknown stays admitted, because business button and list replies land there;
and no plugin allowlists text, because media captions arrive in body under their own media type.

Defects across the plugins

Grouped by what they cost an operator.

Cross-tenant delivery and lost messages

• chatwoot-adapter: the retry queue is plugin-global, but a session's config resolves only inside a
  dispatch for that session, so the timer drain re-posted every queued message with the base account's
  origin, token, account id and inbox. On a multi-tenant install that put one tenant's customer message
  into another tenant's helpdesk, and for a chat with no mapping yet it created the conversation in the
  wrong account and stored that mapping permanently.
• supabase-otp-hook: the send was fired and forgotten to stay inside the ingress dispatch budget,
  which also swallowed instant rejections. Supabase had already been acked and never retries, so those
  OTPs were gone. The send is now raced against a short deadline; a failure inside it fails the delivery
  so the host retries and dead-letters it, while a merely slow send still finishes in the background.

Host-wide performance

• chatwoot-adapter and http-action wrote one storage key per chat and per answered message and
  pruned none of them. The host re-measures its quota by stat-ing every key on every write,
  synchronously, on the gateway event loop, so a long-running install slowed every plugin on the host.
  Both now use sharded buckets; existing keys are read and migrated on their next write, so nothing is
  orphaned and no Chatwoot conversation is re-created.

Wrong answers

• after-hours: an overnight window such as 22:00-06:00 was evaluated entirely inside its own
  weekday, so the plugin was silent on a morning nothing had declared open and replied on the morning
  its window actually covers. A window now belongs to the day it opens on.
• faq-bot: ambiguous repeated alternations are rejected at parse time. ^([a-z]|[a-z0-9])+$ takes
  259 ms against 23 characters and over a minute against 31, and a running regex cannot be interrupted,
  so one short message pinned the worker and every later message queued behind it.
• gsheets-logger: the spreadsheet formula guard checked only the character after a leading sign, so
  -1+IMPORTXML(...) was written unquoted.
• chat-flow: flow state is recorded before the message describing it is sent. A write failing after a
  delivered greeting left the flow unstarted, and with the documented empty trigger that greeted again
  on every later message.

Silent failure

• voice-transcription: the circuit breaker counted the host's shared concurrency rejections as backend
  failures, so a busy line stopped transcription for the full cooldown with a healthy backend.
• after-hours, voice-transcription and supabase-otp-hook gained a healthCheck. The host reports
  a plugin without one as healthy, so a config edit that stopped parsing, an open breaker and a dropped
  OTP were all invisible.

Privacy and access

• chat-flow no longer logs message bodies, stored menu paths or matched reply text at debug level.
• group-translate: /tr status is admin-gated (it prints the participant roster, which is the
  plugin's own access-control state) and /tr help is answered at most once a minute per group.

Correct floors

• group-translate and voice-transcription declared minOpenWAVersion 0.7.0 while resolving hosts
  through net.allowConfigHosts, which first shipped in 0.8.0. On a 0.7.x host both installed cleanly
  and then did nothing.

Tooling and contract

• The CI build job declares contents: read and no longer persists a git credential before running
  dependency lifecycle scripts.
• The catalog's reserved-id check is case-insensitive like the host's, so a mixed-case id can no longer
  be published and then refused at install; a homepage outside the declared repository is rejected;
  package.mjs checks the host's 200-file limit.
• Test discovery walks from the repository root, so a test file outside a plugin directory cannot sit
  unrun; loader:check loads bundles from outside the repo tree, where the host's module resolution
  actually applies (verified: injecting an unbundled require now fails the gate).
• types/openwa.d.ts gains the nine manifest fields the host types and this repo sets, narrows type
  to what is installable, and corrects the documented runtime bounds. README.md and
  PLUGIN-STANDARD.md correct the capability-error rule, the management-endpoint table (8 routes
  listed against 14 that exist) and the send-verb names.

Behavior changes worth a reviewer's attention

• chatwoot-adapter: a queued message now drains only after the plugin has seen an event for its
  session since it was last enabled. Until then it stays queued rather than being posted to whichever
  Chatwoot the base config names. Documented in the plugin README.
• group-translate: /tr status now requires an admin.
• faq-bot: the same inbound text is answered at most once every 10 seconds per chat. Keyed on the
  text, not the rule, so two different questions matching one rule are both still answered.
• gsheets-logger: a failing flush no longer retries on every inbound message, only on the timer.

Verification

npm run typecheck, npm test (631 tests, 44 new), npm run catalog:check, npm run loader:check,
and a rebuild confirming the packaged zips are byte-identical and match their catalog pins.

Each new test was checked to fail when its fix is reverted. Several assert the exposure first: the same
vCard that matches an faq-bot rule as plain text must not match it as a contact card.

Not verified against a running OpenWA host. Everything above is static analysis, unit tests and
targeted scenario runs against the real modules. The ingress acceptance path for the two webhook
plugins, and the storage migrations under a live gateway, are unproven here.

After merge

Push the ten tags one at a time (git push origin <tag> per tag: a single push carrying many tags has
repeatedly failed to trigger the release workflow), confirm each produced a run, then check
npm run catalog:live goes green.