@byollm/server 0.1.0-alpha.39 → 0.1.0-alpha.40

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.
Files changed (2) hide show
  1. package/README.md +15 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,5 +1,5 @@
1
1
  > [!WARNING]
2
- > **Alpha (`0.1.0-alpha.39`) — under active development. Don't use this yet.**
2
+ > **Alpha (`0.1.0-alpha.40`) — under active development. Don't use this yet.**
3
3
  >
4
4
  > Install it deliberately: `npm install @byollm/server@alpha`.
5
5
  >
@@ -105,12 +105,25 @@
105
105
  > packages published and `@byollm/server` did not: a Sigstore
106
106
  > transparency-log 409 on its provenance attestation. The workflow's
107
107
  > "already published" guard correctly refuses to resume a partial publish,
108
- > so `0.1.0-alpha.39` is that release, whole.
108
+ > so `0.1.0-alpha.40` is that release, whole.
109
109
  >
110
110
  > If you run the Supabase adapter, `alpha.21` needs
111
111
  > `20260819010000_completed_by_lease_id.sql`: alpha.19 shipped §3.6's
112
112
  > ordering without the column it stores the grant in.
113
113
 
114
+ <!-- release-note 0.1.0-alpha.40 -->
115
+ **`byollm install` — stop keeping a terminal open.** The daemon can now run
116
+ under your machine's own supervisor and restart itself if it stops: a launchd
117
+ agent on macOS, a `systemd --user` unit on Linux, a logon task on Windows. All
118
+ user-level — no root, no system directories, and `byollm uninstall` takes it
119
+ away. `byollm status` gained a line saying whether it is actually supervised
120
+ right now, including the state that matters most: installed but not running,
121
+ which looks fine from an app's dashboard and serves nothing.
122
+
123
+ If you are running via `npx`, install properly first (`npm install -g
124
+ byollm@alpha`) — `install` refuses to supervise a copy in npx's cache, because
125
+ npm deletes that directory and the service would fail at some later boot.
126
+
114
127
  # `@byollm/server`
115
128
 
116
129
  What app developers drop into their backend: framework-agnostic protocol
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@byollm/server",
3
- "version": "0.1.0-alpha.39",
3
+ "version": "0.1.0-alpha.40",
4
4
  "description": "Framework-agnostic BYOLLM protocol handlers, a reference in-memory store, a Next.js mount, and a Supabase adapter.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -30,7 +30,7 @@
30
30
  "node": ">=22.14"
31
31
  },
32
32
  "dependencies": {
33
- "@byollm/protocol": "0.1.0-alpha.39"
33
+ "@byollm/protocol": "0.1.0-alpha.40"
34
34
  },
35
35
  "peerDependencies": {
36
36
  "@supabase/supabase-js": "^2.58.0"