abmp-npm 2.0.77 → 2.0.78

package/.claude/skills/wix-data-query/references/recipes.md

@@ -1,264 +0,0 @@
-# Query cookbook
-
-All bodies below are the JSON body for
-`POST https://www.wixapis.com/wix-data/v2/items/query`
-([docs](https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/query-data-items)).
-
-Send them via `CallWixSiteAPI(siteId, url, method: "POST", body)` or via curl with
-`Authorization: $WIX_API_KEY` + `wix-site-id: <siteId>`.
-
----
-
-## Look up one member
-
-By profile slug (from the URL in the ticket):
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "filter": { "url": "karriknowles" }, "paging": { "limit": 1 } }
-}
-```
-
-By PAC member ID — **number, not string**:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "filter": { "memberId": 731898 }, "paging": { "limit": 1 } }
-}
-```
-
-By email:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "filter": { "email": "someone@example.com" }, "paging": { "limit": 1 } }
-}
-```
-
-By name — `fullName` only, never the encrypted `firstName`/`lastName`:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "filter": { "fullName": { "$contains": "Knowles" } }, "paging": { "limit": 20 } }
-}
-```
-
-## Return only the fields you care about
-
-Large records (galleries, testimonials, rich text) drown the useful bits. Project:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": {
-    "filter": { "memberId": 949741 },
-    "fields": [
-      "memberId",
-      "url",
-      "fullName",
-      "bookingUrl",
-      "showBookingUrl",
-      "apiBookingUrl",
-      "APIBookingUrl",
-      "isVisible",
-      "action"
-    ],
-    "paging": { "limit": 1 }
-  }
-}
-```
-
-## Count / scope an issue
-
-How many members are affected, without pulling them all. Use the **dedicated count
-endpoint** — `POST https://www.wixapis.com/wix-data/v2/items/count`
-([docs](https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/count-data-items)).
-Note the different body shape: `filter` sits at the top level, there is no `query` wrapper.
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "filter": { "showBookingUrl": false, "bookingUrl": { "$ne": "" } }
-}
-```
-
-Returns `{"totalCount": 82449}`.
-
-> ⚠️ **Do not rely on `returnTotalCount` in the query endpoint.** Verified 2026-08-04 against
-> `MembersDataLatest`: passing `"returnTotalCount": true` — with or without an explicit
-> `paging.offset` — returns `pagingMetadata` containing `count`, `offset`, `tooManyToCount`,
-> `cursors` and `hasNext`, but **no `total` field**. Use `/items/count` for totals.
-
-## Members who should have been dropped but are still visible
-
-The shape behind the "multies not renewing / expired members still listed" class of ticket:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": {
-    "filter": { "action": "drop", "isVisible": true },
-    "fields": ["memberId", "url", "fullName", "action", "isVisible", "memberships"],
-    "paging": { "limit": 100 }
-  }
-}
-```
-
-Inverse — visible members whose membership already expired:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": {
-    "filter": { "isVisible": true, "memberships.expiration": { "$lt": "2026-08-04T00:00:00" } },
-    "fields": ["memberId", "url", "memberships", "action"],
-    "paging": { "limit": 100 }
-  }
-}
-```
-
-> ⚠️ **`memberships.expiration` is a plain ISO string, not a date.** Compare it as a string.
-> Verified 2026-08-04 on ABMP prod: `{"$lt": {"$date": "2026-08-04T00:00:00.000Z"}}` counts
-> **0**, while `{"$lt": "2026-08-04T00:00:00"}` counts **1008**. The `$date` wrapper is only
-> correct for true DATETIME fields such as `_createdDate` / `_updatedDate`. Note the stored
-> strings have no `Z` suffix and no milliseconds — match that format.
-
-## Recently synced records
-
-Useful for confirming whether a nightly run touched a member at all:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": {
-    "filter": { "_updatedDate": { "$gte": { "$date": "2026-08-01T00:00:00.000Z" } } },
-    "sort": [{ "fieldName": "_updatedDate", "order": "DESC" }],
-    "fields": ["memberId", "url", "_updatedDate", "action", "pageNumber"],
-    "paging": { "limit": 50 }
-  }
-}
-```
-
-## Combining conditions
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": {
-    "filter": {
-      "$and": [
-        { "isVisible": true },
-        { "$or": [{ "showBookingUrl": true }, { "showWebsite": true }] }
-      ]
-    },
-    "paging": { "limit": 25 }
-  }
-}
-```
-
-## Paging past 100
-
-Offset paging (each request may carry its own filter/sort):
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "filter": {}, "paging": { "limit": 100, "offset": 100 } }
-}
-```
-
-Cursor paging for a long scan — set `filter`/`sort` on the **first** request only, then pass
-back `pagingMetadata.cursors.next` alone:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "query": { "cursorPaging": { "limit": 100, "cursor": "<cursors.next>" } }
-}
-```
-
----
-
-## Simulate a site query to test whether a filter really excludes something
-
-The highest-value technique in this skill. When a ticket claims "X shouldn't be showing but is",
-rebuild the site's own filters against `/items/count` and check whether the record survives. This
-tests the filter's real semantics instead of reasoning about the code.
-
-The directory query (`buildMembersSearchQuery` in `backend/cms-data-methods.js`) is:
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "filter": {
-    "optOut": { "$ne": true },
-    "action": { "$ne": "drop" },
-    "memberships.membertype": { "$ne": "PAC STAFF" },
-    "isVisible": true
-  }
-}
-```
-
-Add the member you are investigating and read the count. **Always run the control too** — the
-same filter _without_ the clause under test — or a `0` tells you nothing:
-
-```
-with the PAC STAFF clause     -> 0   (excluded)
-without the PAC STAFF clause  -> 1   (would otherwise appear)
-```
-
-To ask "does _anything_ slip through?", combine both conditions on the same field with `$and`
-(a filter object cannot hold two operators under one key):
-
-```json
-{
-  "dataCollectionId": "MembersDataLatest",
-  "filter": {
-    "$and": [
-      { "memberships.membertype": { "$contains": "PAC" } },
-      { "memberships.membertype": { "$ne": "PAC STAFF" } },
-      { "optOut": { "$ne": true } },
-      { "isVisible": true }
-    ]
-  }
-}
-```
-
-Nested paths into array fields (`memberships.membertype`, `addresses.postalcode`) work
-throughout.
-
-> Caveat proven on 2026-08-04: this validates **filter semantics**, not that the deployed site
-> applies them. A filter can be provably correct while the live page still misbehaves. To settle
-> that, get the site's actual API response — the browser devtools network tab is faster than any
-> amount of reasoning, and `?nearby=true` style search UIs often need geolocation before they
-> return anything at all.
-
-## Other endpoints
-
-**Collection schema** — field names, types, and which operators each field allows:
-
-```
-GET https://www.wixapis.com/wix-data/v2/collections/MembersDataLatest
-```
-
-**List all collections on the site:**
-
-```
-GET https://www.wixapis.com/wix-data/v2/collections
-```
-
-**Full-text search** across fields (`POST .../wix-data/v2/items/search`) — note it takes
-`data_collection_id` (snake_case) and a `search` object rather than `query`. Only works on
-CMS-native collections. See
-[Search Data Items](https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/search-data-items).
-
-**Aggregate** (`AGGREGATE` is supported on `MembersDataLatest`) for group-by counts, e.g.
-distribution of `action` values across the directory.
-
-Other collections worth knowing, from `COLLECTIONS` in `public/consts.js`:
-`SiteConfigs`, `CompiledStateCityMap`, `State`, `City`, `interests`,
-`contactUsSubmissions`, `updatedLoginEmails`, `QA_Users`, `ButtonClicks`.

package/.claude/worktrees/fix-save-button-disable/.husky/pre-commit

@@ -1,19 +0,0 @@
-echo "Running ESLint check..."
-npm run lint
-
-if [ $? -ne 0 ]; then
-  echo "❌ ESLint check failed. Please fix the linting errors before committing."
-  exit 1
-fi
-
-echo "Running Prettier check..."
-npm run format:check
-
-if [ $? -ne 0 ]; then
-  echo "❌ Prettier check failed. Please format your code before committing."
-  echo "Run 'npm run format' to automatically format your files."
-  exit 1
-fi
-
-echo "✅ All checks passed!"
-

package/.claude/worktrees/fix-save-button-disable/.prettierignore

@@ -1,7 +0,0 @@
-node_modules
-dist
-build
-coverage
-*.min.js
-package-lock.json
-

package/.claude/worktrees/fix-save-button-disable/.prettierrc.json

@@ -1,16 +0,0 @@
-{
-  "singleQuote": true,
-  "trailingComma": "es5",
-  "printWidth": 100,
-  "tabWidth": 2,
-  "semi": true,
-  "bracketSpacing": true,
-  "bracketSameLine": false,
-  "arrowParens": "avoid",
-  "endOfLine": "lf",
-  "quoteProps": "as-needed",
-  "jsxSingleQuote": false,
-  "requirePragma": false,
-  "insertPragma": false,
-  "proseWrap": "preserve"
-}

package/.claude/worktrees/fix-save-button-disable/README.md

@@ -1 +0,0 @@
-# abmp-npm

package/.claude/worktrees/fix-save-button-disable/backend/README-member-contact-flows.md

@@ -1,136 +0,0 @@
-# Member–Contact Flows
-
-How Wix **Members** (login identity) and **CRM Contacts** (form/submission identity) stay in sync in ABMP.
-
-## Concepts
-
-| Concept                | Meaning                                                                                                    |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------- |
-| **Single entity**      | Member and contact use the same Wix ID (`wixContactId === wixMemberId`). One person, one record.           |
-| **Separate contact**   | Member has a login email; contact has a different “form” email. Two Wix entities: one Member, one Contact. |
-| **Login email**        | `memberData.email` — used to sign in (Wix Member).                                                         |
-| **Contact form email** | `memberData.contactFormEmail` — email used on forms; can differ from login.                                |
-
----
-
-## 1. Login / first-time flow: `createContactAndMemberIfNew`
-
-**Used when:** A user logs in or is created and we need to ensure they have both a Wix Member and (if needed) a CRM Contact.
-
-**File:** `members-data-methods.js` → `createContactAndMemberIfNew(memberData)`
-
-### Logic in short
-
-- If no **Wix Member** → create one (login identity).
-- If no **Wix Contact** and contact form email **differs** from login email → create a separate Contact.
-- If contact form email **equals** login email → no separate contact; we use the member ID as the contact ID (single entity).
-- Persist `wixMemberId` and `wixContactId` on the member record.
-
-### Flow diagram
-
-```mermaid
-flowchart TD
-    A[createContactAndMemberIfNew] --> B{Has wixMemberId?}
-    B -->|No| C[Create Wix Member]
-    B -->|Yes| D{Has wixContactId?}
-    C --> D
-    D -->|No| E{contactFormEmail !== email?}
-    D -->|Yes| K[Keep existing IDs]
-    E -->|Yes| F[Create Wix Contact]
-    E -->|No| G[Use member ID as contact ID]
-    F --> H[Resolve IDs]
-    G --> H
-    K --> H
-    H[newWixContactId = createdContact OR memberId] --> I[Set wixMemberId, wixContactId on member]
-    I --> J[updateMember + return]
-```
-
-### Parallel work
-
-```
-                    ┌─────────────────────────────────────┐
-                    │  createContactAndMemberIfNew         │
-                    └─────────────────────────────────────┘
-                                        │
-                    ┌───────────────────┴───────────────────┐
-                    │           Promise.all([              │
-                    │  runIf(needsWixMember, createMember),  │
-                    │  runIf(needsContact && differentEmail, │
-                    │        createContact)                 │
-                    │           ])                          │
-                    └───────────────────┬───────────────────┘
-                                        │
-          newWixContactId = createdWixContactId || newWixMemberId
-          (if no separate contact, member ID is the contact ID)
-                                        │
-                    ┌───────────────────┴───────────────────┐
-                    │  updateMember({ ...memberData,        │
-                    │    wixMemberId, wixContactId })      │
-                    └───────────────────────────────────────┘
-```
-
-### Outcome
-
-| Scenario                                | wixMemberId   | wixContactId                        |
-| --------------------------------------- | ------------- | ----------------------------------- |
-| New user, same email for login and form | New member ID | Same as wixMemberId (single entity) |
-| New user, form email ≠ login email      | New member ID | New contact ID (separate contact)   |
-| Existing user (already has both IDs)    | Unchanged     | Unchanged                           |
-
----
-
-## 2. Update contact email flow: `updateContactEmail`
-
-**Used when:** User changes their contact/form email in the app and we need to update CRM and optionally the member record.
-
-**File:** `member-contact-orchestration.js` → `updateContactEmail(newContactEmail, existingMemberData)` (used by `updateMemberContactInfo`).
-
-### Logic in short
-
-- **Single entity** (`wixContactId === wixMemberId`):
-  - If new email **equals** login → no change.
-  - If new email **differs** → create a new Contact with the new email and point the member to it (we now have a separate contact).
-- **Separate contact** (different IDs):
-  - If new email **equals** login → delete the extra contact and set `wixContactId = wixMemberId` (collapse to single entity).
-  - If new email **differs** → update the existing contact’s email in CRM.
-
-### Flow diagram
-
-```mermaid
-flowchart TD
-    A[updateContactEmail] --> B{contactEmail === loginEmail?}
-    B -->|Yes| C{Single entity?}
-    B -->|No| D{Single entity?}
-    C -->|Yes| E[No-op: already in sync]
-    C -->|No| F[Delete contact\nSet wixContactId = wixMemberId]
-    D -->|Yes| G[Create new Contact with new email\nUpdate member wixContactId]
-    D -->|No| H[Update existing contact email in CRM]
-```
-
-### Decision table
-
-| Single entity? | New email vs login | Action                                                            |
-| -------------- | ------------------ | ----------------------------------------------------------------- |
-| Yes            | Same               | No-op                                                             |
-| Yes            | Different          | Create new Contact; set member’s `wixContactId` to new contact ID |
-| No             | Same               | Delete Contact; set member’s `wixContactId = wixMemberId`         |
-| No             | Different          | Update existing Contact’s email in CRM (no member change)         |
-
-### Where it’s used
-
-`updateContactEmail` is called from `updateMemberContactInfo` when the **contactFormEmail** field changes (e.g. profile or form update). So:
-
-- **Login flow** → `createContactAndMemberIfNew` (ensure member + contact exist and IDs stored).
-- **Profile/form email change** → `updateMemberContactInfo` → `updateContactEmail` (keep contact and member in sync).
-
----
-
-## File roles
-
-| File                              | Role                                                                                                                                |
-| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `contacts-methods.js`             | Contact CRUD only: create/update/delete contact in Wix CRM.                                                                         |
-| `member-contact-orchestration.js` | Orchestration: when to create/update/delete contact and when to update member’s `wixContactId`. Uses injected `updateMember`.       |
-| `members-data-methods.js`         | Member CRUD, `createContactAndMemberIfNew`; requires `updateMemberContactInfo` and calls `updateMember` once with its return value. |
-
-Dependency direction: **members-data** → **member-contact-orchestration** → **contacts** (no cycle).

package/.claude/worktrees/fix-save-button-disable/backend/__tests__/daily-pull-execution-check.test.js

@@ -1,124 +0,0 @@
-jest.mock('../elevated-modules', () => ({
-  wixData: { query: jest.fn() },
-}));
-jest.mock('psdev-task-manager', () => ({ taskManager: jest.fn() }));
-
-const { taskManager } = require('psdev-task-manager');
-
-const { buildDailyPullTasks } = require('../daily-pull/schedule-methods');
-const { wixData } = require('../elevated-modules');
-const { TASKS_NAMES } = require('../tasks/consts');
-const { dailyPullExecutionCheck } = require('../tasks/daily-pull-check-methods');
-
-const makeQueryResult = items => ({ items, hasNext: () => false });
-
-const mockTasksQuery = items => {
-  const query = {
-    hasSome: jest.fn().mockReturnThis(),
-    ge: jest.fn().mockReturnThis(),
-    find: jest.fn().mockResolvedValue(makeQueryResult(items)),
-  };
-  wixData.query.mockReturnValue(query);
-  return query;
-};
-
-describe('buildDailyPullTasks', () => {
-  test('schedules one ScheduleMembersDataPerAction task per action, excluding none by default', () => {
-    const tasks = buildDailyPullTasks();
-
-    expect(tasks.map(task => task.data.action).sort()).toEqual(['drop', 'new', 'update']);
-    tasks.forEach(task => {
-      expect(task.name).toBe(TASKS_NAMES.ScheduleMembersDataPerAction);
-      expect(task.type).toBe('scheduled');
-      expect(task.data).toEqual({ action: task.data.action });
-    });
-  });
-
-  test('includes the none action and flag when includeNone is set', () => {
-    const tasks = buildDailyPullTasks({ includeNone: true });
-
-    expect(tasks.map(task => task.data.action).sort()).toEqual(['drop', 'new', 'none', 'update']);
-    tasks.forEach(task => expect(task.data.includeNone).toBe(true));
-  });
-
-  test('propagates isTestEnvironment and backupDate to every task', () => {
-    const tasks = buildDailyPullTasks({ isTestEnvironment: true, backupDate: '2026-06-01' });
-
-    tasks.forEach(task => {
-      expect(task.data.isTestEnvironment).toBe(true);
-      expect(task.data.backupDate).toBe('2026-06-01');
-    });
-  });
-});
-
-describe('dailyPullExecutionCheck', () => {
-  let scheduleInBulk;
-
-  beforeEach(() => {
-    wixData.query.mockReset();
-    scheduleInBulk = jest.fn().mockResolvedValue(undefined);
-    taskManager.mockReturnValue({ scheduleInBulk });
-  });
-
-  test('counts the per-action tasks the cron creates as evidence the pull ran', async () => {
-    const query = mockTasksQuery([{ name: TASKS_NAMES.ScheduleMembersDataPerAction }]);
-
-    const result = await dailyPullExecutionCheck({});
-
-    expect(query.hasSome).toHaveBeenCalledWith('name', [
-      TASKS_NAMES.ScheduleMembersDataPerAction,
-      TASKS_NAMES.ScheduleDailyMembersDataSync,
-    ]);
-    expect(result.success).toBe(true);
-    expect(result.fallbackScheduled).toBeUndefined();
-    expect(scheduleInBulk).not.toHaveBeenCalled();
-  });
-
-  test('schedules the per-action fallback with environment flags when no pull is found', async () => {
-    mockTasksQuery([]);
-
-    const result = await dailyPullExecutionCheck({ isTestEnvironment: true, includeNone: true });
-
-    expect(result.success).toBe(false);
-    expect(result.fallbackScheduled).toBe(true);
-    expect(scheduleInBulk).toHaveBeenCalledTimes(1);
-    const scheduledTasks = scheduleInBulk.mock.calls[0][0];
-    expect(scheduledTasks.map(task => task.data.action).sort()).toEqual([
-      'drop',
-      'new',
-      'none',
-      'update',
-    ]);
-    scheduledTasks.forEach(task => {
-      expect(task.name).toBe(TASKS_NAMES.ScheduleMembersDataPerAction);
-      expect(task.data.isTestEnvironment).toBe(true);
-      expect(task.data.includeNone).toBe(true);
-    });
-  });
-
-  test('fallback defaults to production flags when no task data is provided', async () => {
-    mockTasksQuery([]);
-
-    await dailyPullExecutionCheck(undefined);
-
-    const scheduledTasks = scheduleInBulk.mock.calls[0][0];
-    expect(scheduledTasks.map(task => task.data.action).sort()).toEqual(['drop', 'new', 'update']);
-    scheduledTasks.forEach(task => {
-      expect(task.data.isTestEnvironment).toBeUndefined();
-      expect(task.data.includeNone).toBeUndefined();
-    });
-  });
-
-  test('uses the provided lookback window', async () => {
-    const query = mockTasksQuery([{ name: TASKS_NAMES.ScheduleDailyMembersDataSync }]);
-    const before = Date.now();
-
-    const result = await dailyPullExecutionCheck({ hoursBack: 12 });
-
-    const sinceDate = query.ge.mock.calls[0][1];
-    expect(query.ge).toHaveBeenCalledWith('_createdDate', expect.any(Date));
-    const expectedSince = before - 12 * 60 * 60 * 1000;
-    expect(Math.abs(sinceDate.getTime() - expectedSince)).toBeLessThan(5000);
-    expect(result.success).toBe(true);
-  });
-});