@byollm/server 0.1.0-alpha.19 → 0.1.0-alpha.21

package/README.md

@@ -1,5 +1,5 @@
 > [!WARNING]
-> **Alpha (`0.1.0-alpha.19`) — under active development. Don't use this yet.**
+> **Alpha (`0.1.0-alpha.21`) — under active development. Don't use this yet.**
 >
 > Install it deliberately: `npm install @byollm/server@alpha`.
 >

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@byollm/server",
-  "version": "0.1.0-alpha.19",
+  "version": "0.1.0-alpha.21",
   "description": "Framework-agnostic BYOLLM protocol handlers, a reference in-memory store, a Next.js mount, and a Supabase adapter.",
   "license": "MIT",
   "type": "module",
@@ -30,7 +30,7 @@
     "node": ">=22.14"
   },
   "dependencies": {
-    "@byollm/protocol": "0.1.0-alpha.19"
+    "@byollm/protocol": "0.1.0-alpha.21"
   },
   "peerDependencies": {
     "@supabase/supabase-js": "^2.58.0"

package/supabase/migrations/20260819000000_drop_runner_token.sql

@@ -84,3 +84,4 @@ begin
   return v_runner;
 end;
 $$;
+

package/supabase/migrations/20260819010000_completed_by_lease_id.sql

@@ -0,0 +1,25 @@
+-- Which grant recorded a result — cloud_008 §3.6.
+--
+-- `complete` now checks terminal state **before** the holder, so
+-- `RESULT_IDEMPOTENT` is enforced by the branch named after it rather than as
+-- a side effect of the lease being nulled on success. Answering a replay
+-- correctly means knowing which grant recorded the result, and `lease_id` is
+-- cleared at completion by design: "who holds this" and "who finished this"
+-- are different questions with different lifetimes.
+--
+-- ## Why this is its own file
+--
+-- It was first appended to `20260819000000_drop_runner_token.sql`, which had
+-- already shipped in alpha.19. An applied migration is immutable — that is the
+-- whole reason a migrations folder can be trusted — and the fact that this one
+-- is only days old and probably applied nowhere does not make editing it a
+-- different act. The rule is worth more than the tidiness.
+--
+-- ## Nullable, and not backfilled
+--
+-- Rows completed before this migration have no recorded grant, so a replay of
+-- one of them is answered as a plain refusal rather than as a duplicate. That
+-- is the safe direction: it withholds a reassurance rather than inventing one,
+-- and the daemons that produced those rows stopped retrying long ago.
+alter table byollm_jobs
+  add column if not exists completed_by_lease_id text;