@glyphteck/veyl 0.61.12 → 0.63.0

package/docs/agents.md

@@ -6,7 +6,7 @@ The SDK is not a privileged backend. It authenticates, decrypts the vault, signs
 
 ## Setup
 
-Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/legal#terms) and [Community Rules](https://veyl.glyphteck.com/community-rules).
+Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/terms#terms), which include the community rules.
 
 ```js
 import { open } from '@glyphteck/veyl';

package/docs/api.md

@@ -188,7 +188,7 @@ An unknown Spark send, payment-request payment, invoice payment, or withdrawal o
 
 ## Account
 
-Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/legal#terms) and [Community Rules](https://veyl.glyphteck.com/community-rules).
+Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/terms#terms), which include the community rules.
 
 ```js
 const accountKey = await veyl.account.create({
@@ -210,7 +210,7 @@ await veyl.account.delete({ confirm: true });
 - `login({ username?, key?, saveKey? })` authenticates with an account key. The key can instead come from `open({ accountKey })` or `VEYL_ACCOUNT_KEY`.
 - `loginPasskey({ username?, webUrl?, onUrl? })` authenticates through the browser-assisted passkey flow.
 - `me` returns the local account summary without forcing login.
-- `terms` reports the canonical Terms/Community Rules links, whether the account's acceptance is current, and when it last accepted an agreement.
+- `terms` reports the canonical Terms link, whether the account's acceptance is current, and when it last accepted the Terms.
 - `acceptTerms()` records the current agreement through the shared user owner without forcing a vault unlock.
 - `logout` signs out and tears down only this runtime.
 - `logoutAll` revokes every product session generation, tears down this runtime locally, and stops a persistent CLI owner after its in-flight work drains.
@@ -435,7 +435,7 @@ await veyl.listen({
 });
 ```
 
-`listen` subscribes to the shared live chat-list and transfer-store owners. It emits `ready`, `message`, `message-delete`, `transaction`, and `error` events. Message events carry a stable `chatId`, verified actor/member summaries, and a qualified message target. Compact, incoming-only events and transient chat subscriptions are the defaults: the encrypted chat list acts as a wake index, so a changed chat opens briefly, processes its current and history pages, and releases instead of retaining one listener per chat. Set `compact: false`, `incomingOnly: false`, or `persistentChats: true` only when the caller needs those broader behaviors. A headless viewer may set `read: true, relayReads: true`; the listener then advances each peer read from its existing decrypted batch through a short encrypted live-room lease before emitting the event, while the durable write remains coalesced.
+`listen` subscribes to the shared live chat-list and transfer-store owners. It emits `ready`, `message`, `message-delete`, `transaction`, and `error` events. Message events carry a stable `chatId`, verified actor/member summaries, and a qualified message target. Replies retain `message.replyId`; reaction controls are emitted as `message.type === 'rxn'` with `reactTo` pointing at the original message, so agents can preserve the exact action instead of flattening it into presentation text. Compact, incoming-only events and transient chat subscriptions are the defaults: the encrypted chat list acts as a wake index, so a changed chat opens briefly, processes its current and history pages, and releases instead of retaining one listener per chat. Set `compact: false`, `incomingOnly: false`, or `persistentChats: true` only when the caller needs those broader behaviors. A headless viewer may set `read: true, relayReads: true`; the listener then advances each peer read from its existing decrypted batch through a short encrypted live-room lease before emitting the event, while the durable write remains coalesced.
 
 Use `listen` for account-wide agent wakeups. Use `chat.enterById` when an agent is actively inside any notes/direct/group chat; use `chat.enter(peer)` only as a canonical-direct convenience.
 

package/docs/cli.md

@@ -32,7 +32,7 @@ veyl vault lock
 veyl vault export [--key VALUE]
 ```
 
-Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/legal#terms) and [Community Rules](https://veyl.glyphteck.com/community-rules). `account accept-terms` accepts their current revisions for an existing account. `account terms` reports the canonical links and whether the account's acceptance is current without unlocking the vault.
+Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/terms#terms), which include the community rules. `account accept-terms` accepts the current Terms for an existing account. `account terms` reports the canonical link and whether the account's acceptance is current without unlocking the vault.
 
 `vault export` returns the Spark mnemonic. Treat its JSON output as a secret.
 

package/examples/bot-fleet/policy.js

@@ -119,6 +119,37 @@ function sendAttachmentToEventChat(client, event, attachment, options) {
         : client.chat.sendAttachment(event.peer, attachment, options);
 }
 
+function eventMessageTarget(event, messageId) {
+    const id = String(messageId || '').trim();
+    if (!id) return null;
+    return {
+        chatId: eventChatId(event) || null,
+        peer: event.peer || null,
+        messageId: id,
+    };
+}
+
+function sendEchoText(account, client, event) {
+    const options = { cid: botActionCid(event, 'echo', account) };
+    const replyTarget = eventMessageTarget(event, event.message?.replyId);
+    return replyTarget
+        ? client.chat.reply(replyTarget, event.message.text || '', options)
+        : sendToEventChat(client, event, event.message.text || '', options);
+}
+
+function mirrorReaction(account, client, event) {
+    const payload = event.message?.payload || {};
+    const emoji = String(event.message?.emoji || payload.emoji || '').trim();
+    const target = event.reactTo || eventMessageTarget(
+        event,
+        event.message?.target || payload.target
+    );
+    if (!emoji || !target?.messageId) return null;
+    return client.chat.reactTo(target, emoji, {
+        cid: botActionCid(event, 'echo-reaction', account),
+    });
+}
+
 function groupEchoWinner(event, echoChatKeys) {
     const eligible = [...new Set(
         (event?.chat?.members || [])
@@ -218,9 +249,17 @@ async function mirrorEcho(journal, account, client, event) {
             event,
             'echo-text',
             { replaySafe: true },
-            () => sendToEventChat(client, event, event.message.text || '', {
-                cid: botActionCid(event, 'echo', account),
-            })
+            () => sendEchoText(account, client, event)
+        );
+    }
+    if (event.message.type === 'rxn') {
+        return runAction(
+            journal,
+            account,
+            event,
+            'echo-reaction',
+            { replaySafe: true },
+            () => mirrorReaction(account, client, event)
         );
     }
     if (event.message.type === 'req') {
@@ -575,6 +614,16 @@ export function createBotFleetPolicy(options = {}) {
         },
         async onEvent({ account, client, event }) {
             const roles = rolesFor(account);
+            if (!baseline && roles.has('live') && event?.type === 'message') {
+                const state = liveStates.get(account.profile);
+                if (state) {
+                    await ensureLiveChat(
+                        account,
+                        state,
+                        eventChatId(event)
+                    );
+                }
+            }
             if (checkpoint?.has(account.profile, event)) {
                 return null;
             }

package/package.json

@@ -41,5 +41,5 @@
         "start": "node src/cli.js",
         "lint": "eslint src --quiet"
     },
-    "version": "0.61.12"
+    "version": "0.63.0"
 }

package/readme.md

@@ -34,7 +34,7 @@ await veyl.close();
 
 To store the keys in your own secret manager, pass `saveKey: false` to both creation calls and provide them later through `open({ accountKey, vaultKey })`, `VEYL_ACCOUNT_KEY`, and `VEYL_VAULT_KEY`. Never log or commit either key.
 
-Use `REGTEST` for development and disposable accounts. `MAINNET` uses real funds. Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/legal#terms) and [Community Rules](https://veyl.glyphteck.com/community-rules).
+Use `REGTEST` for development and disposable accounts. `MAINNET` uses real funds. Creating an account accepts Veyl's [Terms](https://veyl.glyphteck.com/terms#terms), which include the community rules.
 
 ## CLI