Engraphis 1.1: one front door for the engine

Engraphis 1.1 tightened the path from installation to a connected agent. The release adds the missing client half of device connection, gives the command line one predictable front door, and makes an installation's identity stable without putting hosted behavior in the local core.

What changed

• Connect flow. engraphis connect --token engr_ct_… completes the client side of device connection.
• Unified CLI. The engraphis command dispatches to the existing engraphis-<verb> entry points, so common operations share one discoverable surface.
• Stable installation identity. Each installation gets a durable identity at ~/.engraphis/client_identity.json.
• Explicit compute consent. Managed compute consent travels with the cloud account instead of being implied by a local installation.
• Cleaner product boundaries. An unimplemented hosted export claim was removed from public product surfaces rather than being presented as available.

Try the upgrade

See the full changelog for the connect protocol and hosted-compute details.

Connect deliberately. Remember locally.