Release notification: the event ovhost announce publishes is host.release.published (its own type in openvibe-contracts 0.58.0; host.deploy.activated stays tenant hosting's), in the deploy script's comment and the docs. Comments only (WS-P task 9)

ddiff --git a/deploy/scripts/deploy.sh b/deploy/scripts/deploy.sh
iindex 2b4cf7a6..42e03b4e 100755
---- a/deploy/scripts/deploy.sh
++++ b/deploy/scripts/deploy.sh
@@@ -225,7 +225,7 @@ restart_and_verify() {
  }
  
  # ── Release notification (WS-P task 9) ───────────────────────────────────────
--# OpenVibe.Host publishes host.deploy.activated to OpenVibe.Events, so open tabs check /release.json now
++# OpenVibe.Host publishes host.release.published to OpenVibe.Events, so open tabs check /release.json now
  # instead of at their next poll. ovhost announces the release Live's own /release.json reports, once per
  # release. Best effort: skipped when ovhost is missing or has no `announce`, 20 s at most, and it never
  # fails a deploy (see OpenVibe.Host docs/release-notifications.md).
ddiff --git a/docs/deploy.md b/docs/deploy.md
iindex 342f7e8d..ad99f45d 100644
---- a/docs/deploy.md
++++ b/docs/deploy.md
@@@ -66,7 +66,7 @@ but could not restore previous `node_modules`.
  - Content-hashed assets from the previous release are still served under their old hashes, so a page
    rendered before the switch never loads JavaScript from after it.
  - **Release notification.** After a deploy or `--rollback` that went live, the script runs
--  `ovhost announce live` (OpenVibe.Host, WS-P task 9). ovhost publishes `host.deploy.activated` for the
++  `ovhost announce live` (OpenVibe.Host, WS-P task 9). ovhost publishes `host.release.published` for the
    release `/release.json` now reports, once per release, to OpenVibe.Events. Open tabs (openvibe-shared
    1.17.0 release-watch) then check `/release.json` within about 20 s instead of at their next poll. It is
    best effort: skipped when `ovhost` is missing or has no `announce` (set `OVHOST` for another path), 20 s at