@glyphteck/veyl 0.68.0 → 0.69.0

package/examples/bot-fleet/readme.md

@@ -1,6 +1,6 @@
 # SDK bot fleet example
 
-This is a reference implementation of a long-lived multi-account agent fleet built entirely on `@glyphteck/veyl`. It uses no Firebase Admin connection, privileged chat path, server action queue, or cloud secret store. The Glyphteck-owned runtime under `bots` consumes this policy with its own local lineup and operator controls.
+This is a reference implementation of a long-lived multi-account agent fleet built entirely on `@glyphteck/veyl`. It uses no Firebase Admin connection, privileged chat path, server action queue, or cloud secret store. The Veyl-managed runtime under `bots` consumes this policy with its own local lineup and operator controls.
 
 The secret-free version-2 manifest stores account indices, usernames, networks, roles, and enabled state. One owner-only root at `$VEYL_HOME/fleets/<name>.seed` derives isolated account keys, vault keys, and Veyl master seeds for monotonic account indices. Per-account private material is never stored in the manifest.
 

package/examples/codex-agent/readme.md

@@ -77,7 +77,7 @@ Use a process supervisor appropriate to the host. The process handles `SIGINT` a
 
 The configured owner is allowed by username only during first resolution. The connector then pins the owner's stable Veyl uid and chat public key and publishes `direct: closed`, `groups: closed`, plus one opaque direct grant for that owner. Closed accounts disappear from other clients' new-chat and group-invite choices, while the private pair capability still lets the owner start the direct chat. The fixed-size public grant set does not reveal which account is allowed.
 
-Veyl's existing blocklist remains authoritative and is checked first. Blocking the owner therefore rejects the chat even though the owner has a grant. The local identity check then admits only a signed/decrypted two-member direct Welcome from the pinned owner; groups and every other sender fail closed before owner-row persistence. Existing established chats and chats this account starts outbound are not invalidated by the admission policy, but this example's event loop responds only to the pinned owner.
+Veyl's existing blocked-user state remains authoritative and is checked first. Blocking the owner therefore rejects the chat even though the owner has a grant. The local identity check admits only the pinned owner's signed/decrypted two-member direct traffic. The published closed policy is ongoing rather than creation-only: Veyl hides disallowed existing chats and rejects ungranted open, materialize, send, and receive paths without deleting a direct or leaving a group. This account can converse only with the granted owner.
 
 For each accepted owner message, the process enters the ordinary encrypted live room and stays present for the process lifetime. It publishes a stable composition id while Codex streams, renews the writing lease, stops typing at completion, and sends the durable final with the same composition id so the temporary writing row becomes the final response in place.
 

package/package.json

@@ -53,5 +53,5 @@
         "start": "node src/cli.js",
         "lint": "eslint src --quiet"
     },
-    "version": "0.68.0"
+    "version": "0.69.0"
 }