@feastalytics/cli 0.1.9 → 0.1.10

package/dist/cli.js

@@ -13603,6 +13603,30 @@ var CLI_MANIFEST = {
         "$schema": "http://json-schema.org/draft-07/schema#"
       }
     },
+    {
+      "id": "getCreatorConversation",
+      "domain": "creators",
+      "description": "One creator's full SMS thread, newest first \u2014 what the dashboard's creator chat view renders. userId comes from listCreatorConversations, which is the queue; this is the read you make before summarizing an exchange or drafting a reply for the human to send, because the queue only carries the last message. Each row has the body, direction (from/to the creator's number), and timestamps. Returns empty when the creator has no phone number on file. Read-only: sending the reply and marking the thread read stay in the dashboard.",
+      "type": "query",
+      "path": [
+        "api",
+        "users",
+        "getInfluencerMessages"
+      ],
+      "inputJsonSchema": {
+        "type": "object",
+        "properties": {
+          "userId": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "userId"
+        ],
+        "additionalProperties": false,
+        "$schema": "http://json-schema.org/draft-07/schema#"
+      }
+    },
     {
       "id": "getFunnelDraft",
       "domain": "funnel",
@@ -13723,6 +13747,66 @@ var CLI_MANIFEST = {
         "$schema": "http://json-schema.org/draft-07/schema#"
       }
     },
+    {
+      "id": "getMemberConversation",
+      "domain": "membersProgram",
+      "description": "One member's SMS thread and activity, newest first \u2014 what the dashboard's chat page renders, and the pair to searchUsers the way getCreatorConversation pairs with listCreatorConversations. serialNumber comes from searchUsers. eventTypes: ['sentText','receivedText'] is the conversation; adding scan, order, checkout, rewardAwarded or rewardRedeemed interleaves what happened between the messages. Unfiltered it fans out to every event source and returns the member's whole history unpaginated, so pass eventTypes unless you really want it all. Read-only: replying to a guest stays in the dashboard.",
+      "type": "query",
+      "path": [
+        "api",
+        "loyalty",
+        "app",
+        "listEventsForUser"
+      ],
+      "inputJsonSchema": {
+        "type": "object",
+        "properties": {
+          "serialNumber": {
+            "type": "string"
+          },
+          "eventTypes": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "receivedText",
+                "sentText",
+                "customerInference",
+                "scan",
+                "passCreated",
+                "passUpdated",
+                "order",
+                "rewardAwarded",
+                "rewardRedeemed",
+                "rewardExpiration",
+                "offerExpired",
+                "fbAttribution",
+                "influencerAttribution",
+                "tiktokAttribution",
+                "googleAttribution",
+                "miscAttribution",
+                "referralAttribution",
+                "passRegistered",
+                "passDeleted",
+                "checkout",
+                "reservationCreated",
+                "optOut",
+                "subscriptionStarted",
+                "subscriptionEnded",
+                "subscriptionInvoice",
+                "formSubmission",
+                "autoReplyDraft"
+              ]
+            }
+          }
+        },
+        "required": [
+          "serialNumber"
+        ],
+        "additionalProperties": false,
+        "$schema": "http://json-schema.org/draft-07/schema#"
+      }
+    },
     {
       "id": "getOnboardingForm",
       "domain": "core",
@@ -14142,7 +14226,7 @@ var CLI_MANIFEST = {
     {
       "id": "listCreatorConversations",
       "domain": "creators",
-      "description": "Every creator's SMS conversation with its unread state \u2014 the 'who is waiting on a reply' queue. `hasUnread` means their last message came in after ours and nobody has marked it read; those need a human. Each row carries the last message body, time and direction, the creator's handles, and `visitStatus`, a derived stage that is more reliable than reading raw columns off creatorVisitApplication. Read-only: replying to a creator and marking a conversation read both stay in the dashboard.",
+      "description": "Every creator's SMS conversation with its unread state \u2014 the 'who is waiting on a reply' queue. `hasUnread` means their last message came in after ours and nobody has marked it read; those need a human. Each row carries the last message body, time and direction, the creator's handles, and `visitStatus`, a derived stage that is more reliable than reading raw columns off creatorVisitApplication. Read the full thread behind a row with getCreatorConversation and its userId. Read-only: replying to a creator and marking a conversation read both stay in the dashboard.",
       "type": "query",
       "path": [
         "api",
@@ -14345,46 +14429,6 @@ var CLI_MANIFEST = {
         "$schema": "http://json-schema.org/draft-07/schema#"
       }
     },
-    {
-      "id": "markCreativesPublished",
-      "domain": "creators",
-      "description": "Record which Meta ad a recruitment creative was published in. The linkRecruitmentOffer effect on publishAds records this as part of the publish, so after an effect-declared publish there is nothing left to mark \u2014 call this only when ads were created outside publishAds or a publish's effect reported an error. Pass every creative that went into the ad \u2014 a dynamic ad rotates several at once, so they all take the same fbAdId. Without a record the creatives keep offering to be published again.",
-      "type": "mutation",
-      "path": [
-        "api",
-        "dfy",
-        "markCreativesPublished"
-      ],
-      "inputJsonSchema": {
-        "type": "object",
-        "properties": {
-          "creatives": {
-            "type": "array",
-            "items": {
-              "type": "object",
-              "properties": {
-                "creativeId": {
-                  "type": "string"
-                },
-                "fbAdId": {
-                  "type": "string"
-                }
-              },
-              "required": [
-                "creativeId",
-                "fbAdId"
-              ],
-              "additionalProperties": false
-            }
-          }
-        },
-        "required": [
-          "creatives"
-        ],
-        "additionalProperties": false,
-        "$schema": "http://json-schema.org/draft-07/schema#"
-      }
-    },
     {
       "id": "planAds",
       "domain": "ads",
@@ -14992,7 +15036,7 @@ Example - opted-in members with more than 5 visits, newest first:
     {
       "id": "searchUsers",
       "domain": "membersProgram",
-      "description": "Search members (loyalty guests) and their activity. Returns a page of the most recent user events, one per member, each carrying the member's serialNumber plus the event type, time and related object. isUnread: true narrows the results to unread inbound texts only, overriding any broader eventTypes; progressMinBound/progressMaxBound bound the visit count. Paginate by passing the returned `cursor` back \u2014 an undefined cursor means no more pages.",
+      "description": "Search members (loyalty guests) and their activity. Returns a page of the most recent user events, one per member, each carrying the member's serialNumber plus the event type, time and related object. isUnread: true narrows the results to unread inbound texts only, overriding any broader eventTypes; progressMinBound/progressMaxBound bound the visit count. Paginate by passing the returned `cursor` back \u2014 an undefined cursor means no more pages. This finds the member; getMemberConversation with their serialNumber loads their SMS thread or full timeline.",
       "type": "query",
       "path": [
         "api",

package/feast/references/domains.md

@@ -42,7 +42,3 @@ A template-driven publish pipeline: `listAdTemplates` → `planAds` → `publish
 ## The data catalog
 
 `describeData` / `queryData` expose a read-only, org-scoped query surface over the data model — guests, orders, menu items, texts, creator visits, payouts. When no purpose-built tool answers a read question, the catalog usually does; `describeData` with no arguments is the index.
-
----
-
-Maintenance note: this file is currently hand-authored. The richest source of this domain knowledge is the in-app agent's prompt files (`src/agent-core/src/prompts/` — AutomationsPrompt, CampaignsPrompt, LayoutEnginePrompt, MembersProgramPrompt, OfferPrompt). A future improvement is to generate this reference from those, so the skill and the in-app agent never drift.

package/feast/references/workflows/ads.md

@@ -29,10 +29,10 @@ For the *words* in the ads, read `facebook.md` first — copywriting is its own
 
 Bookkeeping that must happen once the ads exist travels *inside* the publish as `effects`, and the worker runs it as part of the job — because a follow-up call you're supposed to remember is a follow-up call that gets missed, silently.
 
-- **A recruitment publish must declare `linkRecruitmentOffer`** with its `offerId` and `creativeIds` — the server refuses the publish without it. The effect stamps the creatives as published (no separate `markCreativesPublished` call needed), stamps the offer that the monthly sourcing cap and the dashboard's spend both read, and texts the program's approver that sourcing is live.
+- **A recruitment publish must declare `linkRecruitmentOffer`** with its `offerId` and `creativeIds` — the server refuses the publish without it. The effect stamps the creatives as published, stamps the offer that the monthly sourcing cap and the dashboard's spend both read, and texts the program's approver that sourcing is live.
 - **`linkFeastCampaign`** records the published Meta campaign onto a Feast campaign, which is what makes its ads panel and KPIs see the spend.
 
-`markCreativesPublished` is the fallback for ads created outside `publishAds`, or for repairing a publish whose effect reported `error`.
+An effect that reports `error` in the job is a case for the dashboard, not for patching around — surface it to the user.
 
 ### Which template
 

package/feast/references/workflows/creators.md

@@ -59,8 +59,6 @@ The ads that bring applicants in are CLI-drivable end to end:
 3. Publish through the `recruitment` template in `ads.md`, declaring the **`linkRecruitmentOffer` effect** — the publish is refused without it. The effect stamps the creatives, links the offer (which the sourcing cap and dashboard spend read), and texts the program's approver that sourcing is live.
 4. Copy rules for the ad live in `facebook.md` (`recruitmentAdCopy` — the creator-facing half; conflating it with guest copy is the classic failure).
 
-`markCreativesPublished` is only the fallback for recording ads created outside `publishAds` or repairing an effect that reported `error`.
-
 ### The decision loop
 
 1. `listCreatorApplications` — the approval queue, newest first, across every location. Takes no arguments. Use this rather than querying the data model: it carries **`instagramFollowerCount`**, which is usually the deciding factor and isn't reachable any other way.
@@ -79,7 +77,9 @@ The ads that bring applicants in are CLI-drivable end to end:
 
 `listCreatorConversations` is the "who is waiting on a reply" queue: every creator's SMS thread with `hasUnread`, the last message body and direction, and a derived `visitStatus` chip that's more reliable than reading raw columns.
 
-**You cannot reply from the CLI, and you cannot clear the unread flag.** Both stay in the dashboard — texting a creator back is the highest-consequence action in this area. Surface who's waiting and what they said, then hand the user the conversation.
+`getCreatorConversation` with a row's `userId` loads the full thread behind it, newest first. Read it before characterizing an exchange or drafting a reply for the human — the queue's last-message snippet is not enough context to speak for a whole conversation.
+
+**You cannot reply from the CLI, and you cannot clear the unread flag.** Both stay in the dashboard — texting a creator back is the highest-consequence action in this area. Surface who's waiting, read the thread, propose the reply if asked, then hand the user the conversation to send it.
 
 ### Everything else: queryData
 

package/feast/references/workflows/guests.md

@@ -7,6 +7,8 @@
 - Filter with `query` (free-text name), `eventTypes` (e.g. `sentText`, `receivedText`, `scan`, `order`, `rewardAwarded`, `rewardRedeemed`, `checkout`, the `*Attribution` types), `progressMinBound`/`progressMaxBound` (visit-count range), `isUnread: true` (members with unanswered inbound texts), `orderBy` (ASC|DESC by event time).
 - Paginate with `limit` (default 100) and `cursor` (pass back the `cursor` from the previous call; an undefined cursor means no more pages).
 
+`getMemberConversation` with a member's `serialNumber` loads their thread, newest first — the pair to `searchUsers` the same way `getCreatorConversation` pairs with `listCreatorConversations`. Always pass `eventTypes`: `["sentText","receivedText"]` is the SMS thread, and adding `scan`/`order`/`checkout`/`rewardAwarded`/`rewardRedeemed` interleaves what happened between the messages. Unfiltered it returns the member's entire history unpaginated.
+
 **Replying by SMS is NOT exposed, deliberately.** The send primitive enforces opt-out, quiet-hours, dedup, and rate limits *downstream* (not at the endpoint), and opt-in is currently gated only by a UI control. If a reply capability is ever exposed, it must run with confirmation and must not bypass those guardrails. For now, tell the user that replying to guests is done in the app.
 
 ## Everything else: the data catalog

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feastalytics/cli",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Command-line client for the Feastalytics platform — list, create, and update campaigns, automations, offers, and members-program rewards from the terminal.",
   "type": "module",
   "bin": {