@north-light/cli 0.3.459 → 0.3.460

package/dist/builtin-memory/crouter-sdk/guides/apps-on-northlight.md

@@ -36,7 +36,7 @@ Then join your laptop to the account:
    crtr sys join --directory https://account.northlight.ai --token <token> --name my-laptop
    ```
 
-   It answers with `registered: true`, the machine id (`runtime:<id>`), your user id and `daemon: restarted` (`daemon: not_running` when crtr was not running; the next crtr command starts it). Your open viewers and nodes reconnect on their own.
+   It answers with `registered: true`, the machine id (`runtime:<id>`), your user id and `daemon: restarted` (`daemon: started` when crtr was not running: join starts the daemon, and its first grant sync installs `crtr cloud …` and your other provider plugins). Your open viewers and nodes reconnect on their own.
 3. Check it: `crtr cloud apps mine` lists the apps you manage. Before you have joined, it answers `not_joined` and prints these same steps.
 
 Things to know before you join:

package/dist/builtin-memory/crouter-sdk/release-notes.md

@@ -9,6 +9,12 @@ when-and-why-to-read: When you need Release notes, this knowledge should be read
 
 Changes to `@north-light/sdk` that can change what an existing app sees. Newest first.
 
+## 0.3.460
+
+### `crouter-sdk keygen` releases its key file when the add fails (no app change)
+
+When `keygen` cannot add the public key to the app (the machine is not joined, or the directory refuses), it deletes the `local/app-key.json` it had reserved, so a rerun after fixing the cause starts clean. It keeps the file when the add timed out or returned no key, because the add may have landed.
+
 ## 0.3.459
 
 ### `ProfileDTO.profile_path` replaces `memory_path` (additive, no app change)