@alook/daemon 0.1.12 → 0.1.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -25,6 +25,40 @@ is what's reusable — plug in whatever host you like.
25
25
 
26
26
  ---
27
27
 
28
+ ## Daemon lifecycle commands
29
+
30
+ The web Machines sheet generates the full command. Production commands use the
31
+ built-in Alook endpoints; local development commands include explicit local URLs:
32
+
33
+ ```sh
34
+ npx --yes @alook/daemon@latest daemon start --machine-key '<cmt_pair_token>'
35
+ ```
36
+
37
+ Restart a previously paired machine without rotating its credential:
38
+
39
+ ```sh
40
+ npx --yes @alook/daemon@latest daemon start --id '<machine_id>'
41
+ ```
42
+
43
+ Reconnect/rotate only with the command generated for that exact machine:
44
+
45
+ ```sh
46
+ npx --yes @alook/daemon@latest daemon reconnect \
47
+ --id '<machine_id>' --machine-key '<cmt_reconnect_token>'
48
+ ```
49
+
50
+ Reconnect first takes replacement ownership and stops only the matching saved
51
+ PID, then activates the token. A proven pre-commit rejection resumes the prior
52
+ launch record. If a committed response is received and local launch then fails,
53
+ the newly persisted record remains offline and is recovered with
54
+ `daemon start --id '<machine_id>'`. A network error, timeout, 5xx, or otherwise
55
+ ambiguous activation response never restarts the possibly revoked old credential;
56
+ because the new credential was not received, mint a fresh reconnect token in the
57
+ UI and run `daemon reconnect` again. Never paste pairing or machine credentials
58
+ into logs, bug reports, or chat.
59
+
60
+ ---
61
+
28
62
  ## The big idea
29
63
 
30
64
  The daemon never speaks a runtime's native protocol directly. Each runtime is