Keys per product, on the Connection tab

A Laravel app can use two Rekhu products, each with its own key: Rekhu Builder (the package that lets the builder read your code and fix errors) and Rekhu Assistant (the assistant inside your app, for your own users, with one key per environment). Until now a new project came with a Builder key, which was easy to take for the assistant's.

From today:

• A new project has no key. It opens on its Connection tab, where you make the key for what you want to connect: Rekhu Builder, Rekhu Assistant, or both. Each key is shown once, with its own install steps.
• The key appears where you made it, inside its card, with a Copy the key button and its install commands. It is still shown only once.
• Turn on the assistant right there. The Connection tab turns on Rekhu Assistant and makes its keys, one per environment. Its usage, monthly limit and pause stay under Assistant.
• The packages say when a key is the wrong one. php artisan rekhu:assistant-install refuses a Builder key, and php artisan rekhu:assistant names it, with where to make an assistant key instead. The same goes for @rekhu/assistant-node at start and in check().

Versions: rekhu/assistant-laravel 0.5.1 and @rekhu/assistant-node 0.3.1.