v0.40.0: the ai plugin offers this machine's models to the network (#108)

ddiff --git a/STATUS.json b/STATUS.json
iindex 8cc67f5..e0914f3 100644
---- a/STATUS.json
++++ b/STATUS.json
@@@ -5,8 +5,8 @@
    "wave": "T15",
    "plan": "Plan track T15 (Bot complete) and ADR-043 (Bot: devices, pairing, control and safety); the computer plugin and the job worker serve OpenVibe.Actor and the Codes job runner (tracks T14/T17)",
    "kind": "client",
--  "version": "0.39.0",
--  "release": "v0.39.0: the computer-control review's fixes: the core has a local resume, a local approval id and an honest stop (#102); the computer plugin's approvals say what they will run, identity is checked at every gate, stopping generation ends a run and downloads stay confined (#103); the file API works through the folders' handles (#104); a guided first run reports each step (#105); the installer ships the Codes job runner v0.7.0 with conductor failover (#101). v0.36.0: the ai plugin (0.2.0) passes tools to the machine's own model server and hands back the calls the model asked for, never running one, so an agent on OpenVibe (Actor) can work on a model this machine serves; its capabilities say tools: true (contracts 0.277.0). v0.35.0: the Node applies the roles the network's machines hub gives it at each check-in (codes.worker starts the job worker it was installed with, desks.host and ai.host are checked against what the machine was installed for, an unknown role is ignored, and the local configuration always wins), and its status reports them back; a desk's first browser start in a cold sandbox gets 90 s. v0.34.0: on Windows a killed plugin takes every process it started with it (a Job Object with kill-on-close), as the process group does on Linux and macOS, so a bridge helper cannot keep a robot's link open after the Node stops or restarts its plugin; the Node reads what the coding tools remember (read-only, local, redacted) and `openvibe-node memory` uploads it to your own store; the heartbeat carries the machine's fleet of coding agents; the Codes job runner pin is v0.5.2",
++  "version": "0.40.0",
++  "release": "v0.40.0: the ai plugin (0.3.0) offers this machine's models to the network: the owner turns an offer on under the plugin's `offer` settings, which say the models, a local-time window, how many replies may run at once, a price in credits per million tokens (0 volunteers the model) and an audience (everyone, the owner's followers or a group); idle-only, on by default, pauses community replies while the machine is in use (the GPU, a game, stream or overlay, or the owner at the keyboard) and resumes after a quiet spell; the router still enforces the audience and verifies answers, and every community answer is labelled and carries the privacy sentence (a community machine sees the prompt). The plugin advertises the offer as `ai.offer` with per-model speed as `ai.speed`, and reports the community requests and tokens it served (#106). v0.39.0: the computer-control review's fixes: the core has a local resume, a local approval id and an honest stop (#102); the computer plugin's approvals say what they will run, identity is checked at every gate, stopping generation ends a run and downloads stay confined (#103); the file API works through the folders' handles (#104); a guided first run reports each step (#105); the installer ships the Codes job runner v0.7.0 with conductor failover (#101). v0.36.0: the ai plugin (0.2.0) passes tools to the machine's own model server and hands back the calls the model asked for, never running one, so an agent on OpenVibe (Actor) can work on a model this machine serves; its capabilities say tools: true (contracts 0.277.0). v0.35.0: the Node applies the roles the network's machines hub gives it at each check-in (codes.worker starts the job worker it was installed with, desks.host and ai.host are checked against what the machine was installed for, an unknown role is ignored, and the local configuration always wins), and its status reports them back; a desk's first browser start in a cold sandbox gets 90 s. v0.34.0: on Windows a killed plugin takes every process it started with it (a Job Object with kill-on-close), as the process group does on Linux and macOS, so a bridge helper cannot keep a robot's link open after the Node stops or restarts its plugin; the Node reads what the coding tools remember (read-only, local, redacted) and `openvibe-node memory` uploads it to your own store; the heartbeat carries the machine's fleet of coding agents; the Codes job runner pin is v0.5.2",
    "runtime": "go 1.24 (one static binary per platform); plugins in Python 3; an ESP32 Arduino library",
    "database": "none",
    "deployed": false,