v0.7.4

Fixed: bots created from CozyChat now become ready on their own

On a native install (install.sh), creating a Hermes bot from the phone used to hang on the incubation screen and then show "gateway setup needed" forever. The gateway created the profile but nothing on the machine provisioned its attach binding, and cozygateway repair aborted on such a profile because Hermes copies the launch profile's token into every new one.

The gateway now runs the installer's own provisioning unattended after a bot is created or deleted from the phone, and the installer mints a fresh token instead of reusing a copied one. The row moves setup_required → starting → ready with nobody at a terminal. The run restarts the gateway service once; the app already tolerates that. (#353)

Also in this release

• Installs interrupted mid-way are recovered on the next run, and an update preserves the existing listener, public origin, tokens, and owned services. (#347, #348)
• Windows: the installer records the Node identity it installed and starts Hermes compatibly after a reboot or logoff. (#352)
• Runners: the gateway sends a complete hello acknowledgement, so a paired computer attaches on the first try. (#346)
• Public readiness: bounded WebSocket and Compose ingress, verified CozyAgents installer, pinned supply chain, attested release artifacts. (#340)

What to do

Re-run the one-liner or cozygateway repair on each machine. A bot that is already stuck at "gateway setup needed" becomes ready after the update's repair run; if it does not within a minute, delete it from the phone and create it again.

Windows installs still do not auto-provision phone-created bots; run cozygateway repair after creating one.

Full changelog: v0.7.3...v0.7.4