@byollm/protocol 0.1.0-alpha.83 → 0.1.0-alpha.84

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
@@ -1,5 +1,5 @@
1
1
  > [!WARNING]
2
- > **Alpha (`0.1.0-alpha.83`) — under active development. Don't use this yet.**
2
+ > **Alpha (`0.1.0-alpha.84`) — under active development. Don't use this yet.**
3
3
  >
4
4
  > Install it deliberately: `npm install @byollm/protocol@alpha`.
5
5
  >
@@ -90,16 +90,16 @@
90
90
  > ordering without the column it stores the grant in.
91
91
 
92
92
  <!-- release-note 0.1.0-alpha.40 -->
93
- **`byollm install` — stop keeping a terminal open.** The daemon can now run
93
+ **`byollm start` — stop keeping a terminal open.** The daemon can now run
94
94
  under your computer's own supervisor and restart itself if it stops: a launchd
95
95
  agent on macOS, a `systemd --user` unit on Linux, a logon task on Windows. All
96
- user-level — no root, no system directories, and `byollm uninstall` takes it
96
+ user-level — no root, no system directories, and `byollm stop` takes it
97
97
  away. `byollm status` gained a line saying whether it is actually supervised
98
98
  right now, including the state that matters most: installed but not running,
99
99
  which looks fine from an app's dashboard and serves nothing.
100
100
 
101
101
  If you are running via `npx`, install properly first (`npm install -g
102
- byollm@alpha`) — `install` refuses to supervise a copy in npx's cache, because
102
+ byollm@latest`) — `install` refuses to supervise a copy in npx's cache, because
103
103
  npm deletes that directory and the service would fail at some later boot.
104
104
 
105
105
  <!-- release-note 0.1.0-alpha.41 -->