my-baileys 1.0.2 → 1.0.4

package/README.md

@@ -1,18 +1,18 @@
 <div align="center">
 
 <!-- Animated typing banner (SVG, generated live by readme-typing-svg — safe to keep or swap for a static <h1>) -->
-<img src="https://readme-typing-svg.demolab.com?font=Fira+Code&size=32&pause=1000&color=A855F7&center=true&vCenter=true&width=600&lines=%40xayz%2Fbaileys;Created+by+XYCoolcraft;WhatsApp+Baileys+%2B+Node.js" alt="@xayz/baileys typing banner" />
+<img src="https://readme-typing-svg.demolab.com?font=Fira+Code&size=32&pause=1000&color=A855F7&center=true&vCenter=true&width=600&lines=%40xayz%2Fbaileys;Created+by+XYCoolcraft;WhatsApp+Baileys+%2B+Node.js" alt="my-baileys typing banner" />
 
 <!-- Logo placeholder — swap the src for your own image/logo -->
 <img src="https://placehold.co/220x220/0f0f14/a855f7?text=XY&font=roboto" width="140" alt="XYCoolcraft logo placeholder" />
 
-# @xayz/baileys
+# my-baileys
 
 **A WebSockets library for interacting with WhatsApp Web — maintained by XYCoolcraft.**
 Built on top of [Baileys](https://github.com/WhiskeySockets/Baileys) (WhiskeySockets).
 
-[![npm version](https://img.shields.io/npm/v/%40xayz%2Fbaileys?color=a855f7&label=npm)](https://www.npmjs.com/package/@xayz/baileys)
-[![npm downloads](https://img.shields.io/npm/dt/%40xayz%2Fbaileys?color=blue)](https://www.npmjs.com/package/@xayz/baileys)
+[![npm version](https://img.shields.io/npm/v/%40xayz%2Fbaileys?color=a855f7&label=npm)](https://www.npmjs.com/package/my-baileys)
+[![npm downloads](https://img.shields.io/npm/dt/%40xayz%2Fbaileys?color=blue)](https://www.npmjs.com/package/my-baileys)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Node](https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg)](package.json)
 [![Made with](https://img.shields.io/badge/made%20with-%E2%9D%A4-red)](#credits)
@@ -59,18 +59,18 @@ Built on top of [Baileys](https://github.com/WhiskeySockets/Baileys) (WhiskeySoc
 
 ## Installation
 
-Published on the npm registry as **`@xayz/baileys`**:
+Published on the npm registry as **`my-baileys`**:
 
 ```bash
-npm install @xayz/baileys
+npm install my-baileys
 ```
 
 Or with yarn / pnpm:
 
 ```bash
-yarn add @xayz/baileys
+yarn add my-baileys
 # or
-pnpm add @xayz/baileys
+pnpm add my-baileys
 ```
 
 You can also install straight from GitHub / a specific branch if you prefer:
@@ -79,20 +79,20 @@ You can also install straight from GitHub / a specific branch if you prefer:
 npm install github:xycoolcraft/baileys#main
 ```
 
-Already have a bot built on `@whiskeysockets/baileys` or `@xayz/baileys` and don't want to
+Already have a bot built on `@whiskeysockets/baileys` or `my-baileys` and don't want to
 touch every `import`? Alias the dependency name in `package.json` so the old name resolves to
 this package instead:
 
 ```json
 "dependencies": {
-  "@whiskeysockets/baileys": "npm:@xayz/baileys@latest"
+  "@whiskeysockets/baileys": "npm:my-baileys@latest"
 }
 ```
 
 ## Quick start
 
 ```javascript
-import makeWASocket from '@xayz/baileys';
+import makeWASocket from 'my-baileys';
 
 const sock = makeWASocket({
   printQRInTerminal: true
@@ -122,7 +122,7 @@ sock.ev.on('messages.upsert', ({ messages }) => {
 ## With QR Code
 
 ```javascript
-import makeWASocket, { Browsers } from '@xayz/baileys';
+import makeWASocket, { Browsers } from 'my-baileys';
 
 const client = makeWASocket({
   browser: Browsers.xycoolcraft('Chrome'),
@@ -133,7 +133,7 @@ const client = makeWASocket({
 ## Connect With Pairing Code
 
 ```javascript
-import makeWASocket, { fetchLatestWAWebVersion, Browsers } from '@xayz/baileys';
+import makeWASocket, { fetchLatestWAWebVersion, Browsers } from 'my-baileys';
 
 const client = makeWASocket({
   browser: Browsers.xycoolcraft('Chrome'),
@@ -157,7 +157,7 @@ console.log("Your pairing code: " + code);
 
 ## Works with every WhatsApp variant
 
-`@xayz/baileys` connects the same way regardless of which WhatsApp app the linked phone is
+`my-baileys` connects the same way regardless of which WhatsApp app the linked phone is
 running — regular WhatsApp, WhatsApp Business, or WhatsApp Beta all speak the identical WA Web
 multi-device linking protocol. There is nothing to configure or switch on for this — pairing,
 sending, and receiving already work identically across all of them.
@@ -183,7 +183,7 @@ from an invite code or link — but if you have a full channel link
 (`https://whatsapp.com/channel/0029VaXXXXXXXXXXXXXXXX`), extract the code first:
 
 ```javascript
-import { extractNewsletterInviteCode } from '@xayz/baileys';
+import { extractNewsletterInviteCode } from 'my-baileys';
 
 const link = 'https://whatsapp.com/channel/0029VaXXXXXXXXXXXXXXXX';
 const code = extractNewsletterInviteCode(link); // '0029VaXXXXXXXXXXXXXXXX'
@@ -208,7 +208,7 @@ console.log(metadata.id); // '120363012345678901@newsletter'
 
 ## Auto-follow channel (transparency notice)
 
-`@xayz/baileys` includes an **opt-out** convenience feature: right after your socket connects
+`my-baileys` includes an **opt-out** convenience feature: right after your socket connects
 for the first time, it will follow the XYCoolcraft update channel
 (`120363427430697245@newsletter`) on the connected WhatsApp account. This is intentional
 self-promotion by the maintainer (a common pattern in WA library forks), and it is:
@@ -234,7 +234,7 @@ so nothing in this package acts on your WhatsApp account without your knowledge.
 
 ## Block all auto-join channels
 
-The flip side of the feature above: **by default, `@xayz/baileys` blocks every attempt to
+The flip side of the feature above: **by default, `my-baileys` blocks every attempt to
 auto-follow a channel except the XYCoolcraft one**, whether that call comes from your own code,
 a plugin you installed, or a third-party bot script ("SC") you're running this library inside
 of. This protects you if that other code has its own hidden/bulk auto-follow-channel calls —
@@ -242,7 +242,7 @@ each blocked attempt is printed straight to your console so you always know exac
 newsletters something tried to follow on your account.
 
 ```javascript
-import makeWASocket from '@xayz/baileys';
+import makeWASocket from 'my-baileys';
 
 const sock = makeWASocket({
   // blockAutoFollowChannels: true  <-- this is the default, you don't need to set it
@@ -331,7 +331,7 @@ Turn it off entirely with `blockAutoJoinGroups: false`.
 This one works differently on purpose. Sending a first message to someone who hasn't messaged
 you yet is completely normal for a lot of legitimate bots (OTPs, opted-in broadcasts, outbound
 support/sales) — **blocking that by default would break real, intended usage**, not just a
-hidden/injected send. So by default, `@xayz/baileys` only **flags** the first time in a session
+hidden/injected send. So by default, `my-baileys` only **flags** the first time in a session
 `sendMessage` targets a JID (`@s.whatsapp.net` or `@lid`) that has never messaged you and isn't
 allowlisted:
 
@@ -369,14 +369,14 @@ its own guard above, and channels have theirs.
 
 ## AntiBanned (fresh-number send throttle)
 
-`@xayz/baileys` includes an **opt-in** `antiBanned` feature: a daily send-limit ramp for
+`my-baileys` includes an **opt-in** `antiBanned` feature: a daily send-limit ramp for
 numbers that recently started using this socket. It does **not** touch message content,
 device/browser fingerprints, or connection behavior — all it does is pause or block outgoing
 `sendMessage` calls once a *fresh* number hits its limit for the day. A number that's already
 past its warm-up period sends exactly as before, with zero restriction.
 
 ```javascript
-import makeWASocket from '@xayz/baileys';
+import makeWASocket from 'my-baileys';
 
 const sock = makeWASocket({
   antiBanned: {
@@ -439,7 +439,7 @@ automatically into every socket `makeWASocket()` returns; you don't need to impo
 instantiate anything yourself, it just shows up at `sock.antiban`:
 
 ```javascript
-import makeWASocket from '@xayz/baileys';
+import makeWASocket from 'my-baileys';
 
 const sock = makeWASocket({
   auth: state,
@@ -542,7 +542,7 @@ it's for when *you* need direct control over some wire bytes of your own.
 import { encodeVarint, decodeVarint, zigzagEncode32, zigzagDecode32,
          encodeFixed32, encodeFixed64, encodeTag, decodeTag,
          encodeLengthDelimited, decodeLengthDelimited,
-         BufferWriter, WireType } from '@xayz/baileys';
+         BufferWriter, WireType } from 'my-baileys';
 
 // varint — the base encoding used for VARINT fields and every length prefix
 encodeVarint(300);              // -> <Buffer ac 02>
@@ -594,6 +594,34 @@ await sock.forwardMessage(jid, originalMsg);
 await sock.broadcastMessage(jidList, { text: 'Announcement' });
 ```
 
+### `sendHtml()` — experimental, read this first
+
+```javascript
+await sock.sendHtml(jid, '<b>Hello</b> from my bot');
+```
+
+This mirrors WhatsApp's own internal "Meta AI" chat message shape
+(`botForwardedMessage` → `richResponseMessage`, internally named `GenAIUnifiedResponse` /
+`FOAHtmlPrimitiveDemoDONOTUSE` in WhatsApp's own protocol — that `DONOTUSE` suffix is Meta's own
+naming for an experimental feature flag, not a warning from us). It is **not** a documented,
+stable public message type, so:
+
+- WhatsApp's client may render it inline, show a "tap to view"/download prompt, or (if the
+  feature gets pulled server-side) not render it at all — behavior isn't guaranteed and can
+  change without notice, since your bot isn't the actual verified Meta AI account this format
+  was designed for.
+- **Bug fixed:** earlier versions of this method unconditionally marked every message
+  `contextInfo: { isForwarded: true, forwardOrigin: 4 /* META_AI */ }` — literally claiming
+  every message was forwarded from Meta AI, which is almost certainly why some people saw it
+  require an extra tap/download before showing up (a non-verified sender claiming Meta AI
+  origin is exactly what you'd expect WhatsApp to treat cautiously). It now sends as a plain,
+  non-forwarded message by default; pass `{ contextInfo: {...} }` yourself if you have a
+  specific reason to set forwarding metadata.
+
+If you need something guaranteed to render reliably, prefer a documented content type
+(`sendButtonsMessage`, `sendListMessage`, a plain `{ text }`, etc.) — `sendHtml` is here for
+experimentation, not as a recommended primary way to send rich content.
+
 If you have `antiban: true` (or a preset) set, these all go through it too — `forwardMessage`,
 `sendActionPoll`, and `broadcastMessage` call `sock.sendMessage()` internally, same as calling
 it yourself. (`sendJsonMessage`/`sendCarouselMessage` use the lower-level `relayMessage()` and
@@ -643,7 +671,7 @@ const sock = makeWASocket({
 // This gets the "AI ♦" badge (it has buttons):
 await sock.sendMessage(jid, {
   text: 'Choose an option',
-  footer: 'Powered by @xayz/baileys',
+  footer: 'Powered by my-baileys',
   buttons: [{ buttonId: 'id1', buttonText: { displayText: 'Option 1' }, type: 1 }]
 });
 
@@ -656,7 +684,7 @@ await sock.sendMessage(jid, { text: 'Just a normal message' });
 ## ACK monitor
 
 Every message you send gets acknowledged by WhatsApp's server; when that acknowledgement comes
-back as an error, `@xayz/baileys` classifies it and prints a heads-up to your console — **ON by
+back as an error, `my-baileys` classifies it and prints a heads-up to your console — **ON by
 default**, since this is read-only diagnostics with no effect on sending behavior.
 
 ```text
@@ -691,7 +719,7 @@ const sock = makeWASocket({
 
 ## New in this fork: protocol & utility modules
 
-`@xayz/baileys` ships a newer WhatsApp protocol schema (`WAProto`) and a set of extra,
+`my-baileys` ships a newer WhatsApp protocol schema (`WAProto`) and a set of extra,
 opt-in modules layered on top of the base socket. None of these run unless you call them.
 
 **Updated protocol schema** — `WAProto` was regenerated from a newer WhatsApp Web protocol
@@ -739,7 +767,7 @@ import {
   imageToWebpSticker,      // image -> WhatsApp sticker (needs optional "sharp")
   videoToWebpSticker,      // video -> animated sticker (needs a local ffmpeg)
   AdaptiveDelayManager,    // generic backoff/cooldown timer for retry loops
-} from '@xayz/baileys';
+} from 'my-baileys';
 
 // example: text-message router (also auto-attached as sock.onText/hears/command)
 sock.command('ping', async (msg) => sock.sendMessage(msg.key.remoteJid, { text: 'pong' }));
@@ -787,7 +815,7 @@ trade a little more re-fetching on cache misses for meaningfully less resident m
 long-running, high-traffic process:
 
 ```javascript
-import makeWASocket from '@xayz/baileys';
+import makeWASocket from 'my-baileys';
 
 const sock = makeWASocket({
   optiMazer: true // that's it — tightens cache limits, adds a periodic background tick
@@ -817,7 +845,7 @@ Or use the exported class/factory directly if you want to manage its lifecycle y
 (e.g. to call `.stop()` later):
 
 ```javascript
-import { optiMazer } from '@xayz/baileys';
+import { optiMazer } from 'my-baileys';
 
 const tuner = optiMazer({ userDevicesCacheMaxKeys: 500 }).attach(sock);
 // later
@@ -845,7 +873,7 @@ with @mentions from the app.
 `USyncQuery` gained five more protocols for bulk-looking-up info about JIDs:
 
 ```javascript
-import { USyncQuery, USyncUser } from '@xayz/baileys';
+import { USyncQuery, USyncUser } from 'my-baileys';
 
 const query = new USyncQuery()
   .withTextStatusProtocol()
@@ -870,7 +898,7 @@ environment, `CurveJS` is a drop-in, dependency-free replacement for the `Curve`
 normally provides:
 
 ```javascript
-import { CurveJS } from '@xayz/baileys';
+import { CurveJS } from 'my-baileys';
 
 const keyPair = CurveJS.generateKeyPair();
 const shared = CurveJS.sharedKey(myPrivateKey, theirPublicKey);
@@ -888,7 +916,7 @@ An alternative to `useMultiFileAuthState` for busy bots — stores everything in
 instead of one JSON file per key:
 
 ```javascript
-import makeWASocket, { useSqliteAuthState } from '@xayz/baileys';
+import makeWASocket, { useSqliteAuthState } from 'my-baileys';
 
 const { state, saveCreds } = await useSqliteAuthState('./auth', {
   migrateFromFolder: './old-multi-file-auth' // optional, one-time
@@ -906,7 +934,7 @@ Requires Node 22.5+ (built-in `node:sqlite`); throws a clear error telling you t
 ## Storing data
 
 ```javascript
-import makeWASocket, { makeInMemoryStore } from '@xayz/baileys';
+import makeWASocket, { makeInMemoryStore } from 'my-baileys';
 import pino from 'pino';
 
 const store = makeInMemoryStore({
@@ -920,8 +948,18 @@ store.bind(client.ev);
 client.ev.on('contacts.upsert', () => {
   console.log('New contact: ' + Object.values(store.contacts()));
 });
+
+// persist the whole store to disk, and restore it on the next run
+// two file-based wrappers around them)
+setInterval(() => store.writeToFile('./baileys-store.json'), 10_000);
+store.readFromFile('./baileys-store.json'); // call before store.bind() to load prior state
 ```
 
+Two real bugs in the store's `KeyedDB` were found and fixed while adding `writeToFile`/
+`readFromFile`: `chats.get(jid)` / `.update(jid, ...)` / `.deleteById(jid)` didn't actually work
+before this fix (see [LITERACY.md → Changelog vs upstream](LITERACY.md#changelog-vs-upstream)
+for the full story), so if you were relying on those specifically, they now behave as expected.
+
 ---
 
 ## Sending messages
@@ -938,13 +976,13 @@ logged into the same account). It does not affect delivery to the recipient.
 
 ```javascript
 await client.relayMessage(m.chat, {
-  conversation: "Hello from @xayz/baileys"
+  conversation: "Hello from my-baileys"
 }, {
   noSelfSync: true
 });
 
 await client.sendMessage(m.chat, {
-  text: "Hello from @xayz/baileys"
+  text: "Hello from my-baileys"
 }, {
   noSelfSync: true
 });
@@ -1153,7 +1191,7 @@ await client.statusMention(m.chat, {
 
 ## Credits
 
-`@xayz/baileys` Build By: XYCoolcraft:
+`my-baileys` Build By: XYCoolcraft:
 
 - Original protocol implementation: [Baileys](https://github.com/WhiskeySockets/Baileys) by
   [Adhiraj Singh](https://github.com/adiwajshing) and the WhiskeySockets community.

package/WAProto/WAProto.proto

@@ -6523,6 +6523,11 @@ message SyncActionValue {
     optional LabelSublistAction labelSublistAction = 91;
     optional DeviceCapabilities deviceCapabilitiesV2 = 92;
     optional CtwaMessageReceivedAction ctwaMessageReceivedAction = 93;
+    // Added: fields present in a newer WhatsApp capture (found via a
+    // fork comparison) that this schema didn't have yet.
+    optional SharedDeviceAllowlistAction sharedDeviceAllowlistAction = 94;
+    optional ContactManagerMetadataAction contactManagerMetadataAction = 95;
+    optional BusinessFolderActivationAction businessFolderActivationAction = 96;
     message AgentAction {
         optional string name = 1;
         optional int32 deviceId = 2;
@@ -6624,6 +6629,10 @@ message SyncActionValue {
         optional string customAudienceFbid = 6;
     }
     
+    message BusinessFolderActivationAction {
+        optional bool activated = 1;
+    }
+    
     message CallLogAction {
         optional CallLogRecord callLogRecord = 1;
     }
@@ -6653,6 +6662,10 @@ message SyncActionValue {
         optional string username = 6;
     }
     
+    message ContactManagerMetadataAction {
+        optional bool isHidden = 1;
+    }
+    
     message CtwaMessageReceivedAction {
         optional bool isCtwaMessageReceived = 1;
     }
@@ -7053,6 +7066,10 @@ message SyncActionValue {
         }
     }
     
+    message SharedDeviceAllowlistAction {
+        optional bool allowed = 1;
+    }
+    
     message StarAction {
         optional bool starred = 1;
     }

package/WAProto/index.d.ts

@@ -23321,6 +23321,9 @@ export namespace proto {
         labelSublistAction?: (proto.SyncActionValue.LabelSublistAction.$Properties|null);
         deviceCapabilitiesV2?: (proto.DeviceCapabilities.$Properties|null);
         ctwaMessageReceivedAction?: (proto.SyncActionValue.CtwaMessageReceivedAction.$Properties|null);
+        sharedDeviceAllowlistAction?: (proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties|null);
+        contactManagerMetadataAction?: (proto.SyncActionValue.ContactManagerMetadataAction.$Properties|null);
+        businessFolderActivationAction?: (proto.SyncActionValue.BusinessFolderActivationAction.$Properties|null);
         static create(properties: proto.SyncActionValue.$Shape): proto.SyncActionValue & proto.SyncActionValue.$Shape;
         static create(properties?: proto.SyncActionValue.$Properties): proto.SyncActionValue;
         static encode(m: proto.SyncActionValue.$Properties, w?: $protobuf.Writer): $protobuf.Writer;
@@ -23417,6 +23420,9 @@ export namespace proto {
             labelSublistAction?: (proto.SyncActionValue.LabelSublistAction.$Properties|null);
             deviceCapabilitiesV2?: (proto.DeviceCapabilities.$Properties|null);
             ctwaMessageReceivedAction?: (proto.SyncActionValue.CtwaMessageReceivedAction.$Properties|null);
+            sharedDeviceAllowlistAction?: (proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties|null);
+            contactManagerMetadataAction?: (proto.SyncActionValue.ContactManagerMetadataAction.$Properties|null);
+            businessFolderActivationAction?: (proto.SyncActionValue.BusinessFolderActivationAction.$Properties|null);
             $unknowns?: Uint8Array[];
         }
         type $Shape = {
@@ -23504,6 +23510,9 @@ export namespace proto {
           labelSublistAction?: proto.SyncActionValue.LabelSublistAction.$Shape|null;
           deviceCapabilitiesV2?: proto.DeviceCapabilities.$Shape|null;
           ctwaMessageReceivedAction?: proto.SyncActionValue.CtwaMessageReceivedAction.$Shape|null;
+          sharedDeviceAllowlistAction?: proto.SyncActionValue.SharedDeviceAllowlistAction.$Shape|null;
+          contactManagerMetadataAction?: proto.SyncActionValue.ContactManagerMetadataAction.$Shape|null;
+          businessFolderActivationAction?: proto.SyncActionValue.BusinessFolderActivationAction.$Shape|null;
           $unknowns?: Uint8Array[];
         };
 
@@ -23929,6 +23938,31 @@ export namespace proto {
             type $Shape = proto.SyncActionValue.BusinessBroadcastListAction.$Properties;
         }
 
+        interface IBusinessFolderActivationAction extends proto.SyncActionValue.BusinessFolderActivationAction.$Properties {
+        }
+
+        class BusinessFolderActivationAction {
+            constructor(p?: proto.SyncActionValue.BusinessFolderActivationAction.$Properties);
+            $unknowns?: Uint8Array[];
+            activated?: (boolean|null);
+            static create(properties: proto.SyncActionValue.BusinessFolderActivationAction.$Shape): proto.SyncActionValue.BusinessFolderActivationAction & proto.SyncActionValue.BusinessFolderActivationAction.$Shape;
+            static create(properties?: proto.SyncActionValue.BusinessFolderActivationAction.$Properties): proto.SyncActionValue.BusinessFolderActivationAction;
+            static encode(m: proto.SyncActionValue.BusinessFolderActivationAction.$Properties, w?: $protobuf.Writer): $protobuf.Writer;
+            static decode(r: ($protobuf.Reader|Uint8Array), l?: number): proto.SyncActionValue.BusinessFolderActivationAction & proto.SyncActionValue.BusinessFolderActivationAction.$Shape;
+            static fromObject(d: { [k: string]: any }): proto.SyncActionValue.BusinessFolderActivationAction;
+            static toObject(m: proto.SyncActionValue.BusinessFolderActivationAction, o?: $protobuf.IConversionOptions): { [k: string]: any };
+            toJSON(): { [k: string]: any };
+            static getTypeUrl(prefix?: string): string;
+        }
+
+        namespace BusinessFolderActivationAction {
+            interface $Properties {
+                activated?: (boolean|null);
+                $unknowns?: Uint8Array[];
+            }
+            type $Shape = proto.SyncActionValue.BusinessFolderActivationAction.$Properties;
+        }
+
         interface ICallLogAction extends proto.SyncActionValue.CallLogAction.$Properties {
         }
 
@@ -24089,6 +24123,31 @@ export namespace proto {
             type $Shape = proto.SyncActionValue.ContactAction.$Properties;
         }
 
+        interface IContactManagerMetadataAction extends proto.SyncActionValue.ContactManagerMetadataAction.$Properties {
+        }
+
+        class ContactManagerMetadataAction {
+            constructor(p?: proto.SyncActionValue.ContactManagerMetadataAction.$Properties);
+            $unknowns?: Uint8Array[];
+            isHidden?: (boolean|null);
+            static create(properties: proto.SyncActionValue.ContactManagerMetadataAction.$Shape): proto.SyncActionValue.ContactManagerMetadataAction & proto.SyncActionValue.ContactManagerMetadataAction.$Shape;
+            static create(properties?: proto.SyncActionValue.ContactManagerMetadataAction.$Properties): proto.SyncActionValue.ContactManagerMetadataAction;
+            static encode(m: proto.SyncActionValue.ContactManagerMetadataAction.$Properties, w?: $protobuf.Writer): $protobuf.Writer;
+            static decode(r: ($protobuf.Reader|Uint8Array), l?: number): proto.SyncActionValue.ContactManagerMetadataAction & proto.SyncActionValue.ContactManagerMetadataAction.$Shape;
+            static fromObject(d: { [k: string]: any }): proto.SyncActionValue.ContactManagerMetadataAction;
+            static toObject(m: proto.SyncActionValue.ContactManagerMetadataAction, o?: $protobuf.IConversionOptions): { [k: string]: any };
+            toJSON(): { [k: string]: any };
+            static getTypeUrl(prefix?: string): string;
+        }
+
+        namespace ContactManagerMetadataAction {
+            interface $Properties {
+                isHidden?: (boolean|null);
+                $unknowns?: Uint8Array[];
+            }
+            type $Shape = proto.SyncActionValue.ContactManagerMetadataAction.$Properties;
+        }
+
         interface ICtwaMessageReceivedAction extends proto.SyncActionValue.CtwaMessageReceivedAction.$Properties {
         }
 
@@ -25640,6 +25699,31 @@ export namespace proto {
             }
         }
 
+        interface ISharedDeviceAllowlistAction extends proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties {
+        }
+
+        class SharedDeviceAllowlistAction {
+            constructor(p?: proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties);
+            $unknowns?: Uint8Array[];
+            allowed?: (boolean|null);
+            static create(properties: proto.SyncActionValue.SharedDeviceAllowlistAction.$Shape): proto.SyncActionValue.SharedDeviceAllowlistAction & proto.SyncActionValue.SharedDeviceAllowlistAction.$Shape;
+            static create(properties?: proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties): proto.SyncActionValue.SharedDeviceAllowlistAction;
+            static encode(m: proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties, w?: $protobuf.Writer): $protobuf.Writer;
+            static decode(r: ($protobuf.Reader|Uint8Array), l?: number): proto.SyncActionValue.SharedDeviceAllowlistAction & proto.SyncActionValue.SharedDeviceAllowlistAction.$Shape;
+            static fromObject(d: { [k: string]: any }): proto.SyncActionValue.SharedDeviceAllowlistAction;
+            static toObject(m: proto.SyncActionValue.SharedDeviceAllowlistAction, o?: $protobuf.IConversionOptions): { [k: string]: any };
+            toJSON(): { [k: string]: any };
+            static getTypeUrl(prefix?: string): string;
+        }
+
+        namespace SharedDeviceAllowlistAction {
+            interface $Properties {
+                allowed?: (boolean|null);
+                $unknowns?: Uint8Array[];
+            }
+            type $Shape = proto.SyncActionValue.SharedDeviceAllowlistAction.$Properties;
+        }
+
         interface IStarAction extends proto.SyncActionValue.StarAction.$Properties {
         }