@parag.more.withsurface.com/forms-sdk 0.1.5 → 0.1.7

package/skills/surface-forms-sdk/SKILL.md

@@ -35,8 +35,30 @@ references alongside this file — read the one that matches the job:
   docs may say `@parag.more.withsurface.com/forms-sdk`; the installed name wins.
 - Bundler `target: "esnext"` (top-level await), or wrap `init` in an async fn.
 
+## Decisions to confirm with the form owner (before authoring)
+
+The record can't express these and the SDK deliberately doesn't decide them —
+ask, don't assume. One question each, with the default stated:
+
+- **Invalid email address** — default: annotate only (`emailValidation: true`;
+  the visitor continues, the response carries `isEmailValid: false` for the
+  owner's workflows). Alternatives: soft-warn inline, block the step with a
+  message, or `disqualify()`. Never gate navigation on `validateEmail` unless
+  the owner picked block/disqualify.
+- **Required fields** — the binding map's `required` is advisory: the SDK
+  never blocks a step, your page does (native forms block). Confirm which
+  fields block Continue and what the message says.
+- **Selection limits** — `selectionLimit` on a multi-select is not enforced
+  by the SDK; enforce it in markup (disable extra checkboxes) if the owner
+  wants parity with the hosted form.
+
 ## The workflow
 
+Binding to an EXISTING published record (the common integration case): skip
+step 2, read the contract with `get_sdk_binding_map` (`source: "live"` when
+you don't own the draft), then author → validate → deploy. Preview (6) needs
+a draft you own; publish (7) only when you changed the record.
+
 1. **Plan (optional).** Vague requirements → `plan_form` with `sdk: true`.
    Branching stays prose (`routingIntent`) — your page implements it; never
    encode structured routing for an SDK form.
@@ -53,7 +75,13 @@ references alongside this file — read the one that matches the job:
 5. **Validate.** `validate_form_html` until clean. Scheduler/file questions
    report as notes (no binding needed — code writes their answers). If your
    navigation/submit is JS-driven, declare `data-surface-nav="js"` on any
-   element instead of adding fake buttons.
+   element instead of adding fake buttons. For a JSX/React page the check is a
+   one-shot against transcribed markup — ALSO commit a drift test: extract
+   every `data-question-id` / `data-step-id` / choice `value` from the
+   component source (regex over the file is fine) and assert them against the
+   binding map's ids saved in your contract module. Binding drift is silent
+   data loss; only a committed test catches the refactor that renames a
+   question wrapper.
 6. **Preview before publishing.** `init({ preview: true, previewToken })`
    serves the DRAFT record with zero network writes; the scheduler returns a
    synthetic booking. Skip `simulate_response` — it evaluates record routing,
@@ -78,22 +106,39 @@ references alongside this file — read the one that matches the job:
   explicit `data-field-name` per control.
 - **Boot flash** — mark every step container after the first `hidden`; the SDK
   reveals the current one after async init.
+- **Continue is instant** — `next()`/`goToStep()` switch the step immediately
+  and the partial save lands behind it; never disable the CTA or wait for
+  `saved` before showing the next step. Only `submit()`/`disqualify()` await
+  their write — disable THAT button until the promise resolves.
 - **Teardown** — the finishing write is awaited (`submit()` resolving means the
-  server has it), but partial saves are beacons: `await form.flush()` before a
-  programmatic page close or your test harness records a partial.
-- **Email validation fails open** — `{ isValid: true, failed: true }` on vendor
-  outage, and a fresh domain may resolve to a definitive verdict later. Check
-  `failed` to soft-warn; don't write tests expecting stable verdicts for new
-  domains.
+  server has it), but partial saves run in the background: `await form.flush()`
+  before a programmatic page close or your test harness records a partial. In
+  a React effect cleanup call `destroy()` alone — a cleanup cannot await, and
+  queued saves survive an SPA unmount; `flush()` is for closing the whole
+  page/process.
+- **Email validation never blocks by default** — `emailValidation: true`
+  annotates the response; an invalid address still continues. Gate with
+  `validateEmail` only when the owner chose block/disqualify (Decisions
+  above). Verdicts fail open (`{ isValid: true, failed: true }` on vendor
+  outage) and a fresh domain may resolve to a definitive verdict later —
+  check `failed` to soft-warn; don't write tests expecting stable verdicts.
 - **Enrichment can be silently inert** — check `form.capabilities.enrichment`
   before promising enriched fields; a declared source field without an enabled
   provider does nothing (`debug: true` warns).
 - **Custom values on the response** — `form.mergeMeta({ qualificationScore })`;
   reserved SDK keys are dropped. Don't invent external-state types.
-- **Scheduler** — mount the SDK's widget (never iframe the hosted page), write
-  the answer in `onComplete` via `setAnswer({ ...toSchedulerAnswerState(b),
-type: "CalendlyScreen" })`. Labels are human-readable with raw values in
-  `data-value`; style via the `surface-booking-*` classes (tree in llms.txt).
+- **Scheduler** — default to ONE call: `mountScheduler({ form, container })`
+  renders the record's scheduler (any provider — Surface widget default-styled,
+  or the third-party embed), tracks the lifecycle on `form.on("scheduler")`,
+  and persists the booking automatically. Never iframe the hosted booking
+  page. Build custom UI only when explicitly asked: `mountBookingWidget` +
+  `setAnswer({ ...toSchedulerAnswerState(b), type: "CalendlyScreen" })` in
+  `onComplete`. Traps: Clari emits no booking signal (embed-only);
+  Calendly/Zoom/Reclaim mounts create the response early (their embed URLs
+  carry the responseId); `styled: false` opts out of the injected scoped CSS.
+  The Surface widget opens on the first month with availability — a
+  persistent "No availability" means the event type really has none (host
+  schedule / max advance), not a wrong month.
 - **Business logic is invisible to Surface tooling.** Your qualification/
   branching thresholds live in page code no validator can see — test them in a
   real browser walk (both branches, plus a boundary case).
@@ -101,14 +146,13 @@ type: "CalendlyScreen" })`. Labels are human-readable with raw values in
 ## Starter template
 
 ```html
-<div id="form" data-surface-nav="js" hidden>
+<div id="form" hidden>
   <section data-step-id="STEP_1_ID">
     <label
       >Work email <input type="email" data-question-id="Q_EMAIL_ID" />
       <!-- EmailForm infers type+field -->
     </label>
-    <p class="error" hidden></p>
-    <button type="button" id="to-step-2">Continue</button>
+    <button type="button" class="surface-next-button">Continue</button>
   </section>
 
   <section data-step-id="STEP_2_ID" hidden>
@@ -131,23 +175,19 @@ const form = await SurfaceForms.init({
   formId: "FORM_ID",
   apiBaseUrl: "API_BASE_URL", // from get_sdk_binding_map — do not omit
   container: document.querySelector("#form"),
-  emailValidation: true, // opt-in: writes native-parity verdict meta
+  emailValidation: true, // default policy: annotate the response, never block
 });
 document.querySelector("#form").hidden = false;
 
-// JS-driven forward nav: gate on the email verdict, then branch yourself.
-document.querySelector("#to-step-2").addEventListener("click", async () => {
-  const email = document.querySelector("[data-question-id=Q_EMAIL_ID]").value;
-  const { isValid, reason } = await form.validateEmail(email);
-  if (!isValid) return showError(`That address looks undeliverable (${reason}).`);
-  form.next(); // or form.goToStep("…") / form.disqualify() per your rules
-});
-
 form.on("saved", ({ responseId, resumeToken }) =>
   localStorage.setItem("surface-resume", JSON.stringify({ responseId, resumeToken }))
 );
 ```
 
-Back navigation can stay markerless JS too (`form.back()`), or use the
-declarative markers (`surface-next-button`, `data-surface-goto-step`,
-`surface-disqualify-button`) when no async gate is needed.
+Declarative markers (`surface-next-button`, `data-surface-goto-step`,
+`surface-disqualify-button`, `surface-submit-button`) cover linear and static
+branching. Owner-requested gates (block on an invalid email, required-field
+checks) and dynamic branching are JS: call `form.next()` /
+`form.goToStep(…)` / `form.disqualify()` from your own handler and put
+`data-surface-nav="js"` on any element so `validate_form_html` knows —
+snippets in `patterns.md` §Invalid-email policy.

package/skills/surface-forms-sdk/debugging.md

@@ -29,25 +29,27 @@ that is the only end-to-end truth.
 
 ## Symptom table
 
-| Symptom                                           | Likely cause                                                                                                                                             | Check                                                                                                                 |
-| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `init` throws "could not fetch runtime config"    | Wrong/missing `apiBaseUrl` — the error names the exact URL and host it tried                                                                             | Use the `apiBaseUrl` from `get_sdk_binding_map`; curl the URL from the error                                          |
-| No responses at all                               | `preview: true` left in the deployed page (blocks ALL writes)                                                                                            | Grep the page for `preview`; `saved` event never fires in preview                                                     |
-| No responses at all                               | Form never published — runtime-config serves the "not published yet" placeholder, so step/question ids don't match                                       | Console shows unbound-questionId warnings; `publish_form`                                                             |
-| Some answers missing                              | Binding drift: questionId unbound or misspelled                                                                                                          | Console warning "record declares questionIds with no bound element"; `validate_form_html`                             |
-| Some answers missing                              | Partial saves off and visitor abandoned mid-form                                                                                                         | `trackPartialResponses` in settings; expected behavior                                                                |
-| Finished response stored as a partial             | SDK < 0.1.3 sent the terminal write fire-and-forget; current SDK awaits it — remaining cause is tearing the page down mid-flight                         | Upgrade; `await form.submit()` then `await form.flush()` before any programmatic close                                |
-| 400 "Fields are missing or incorrectly formatted" | Hand-built `setAnswer` with the wrong shape (choice questions want structured lists, not label strings)                                                  | Compare the payload with the binding map's `answerShape`; prefer `data-*` binding, which builds choice answers itself |
-| Choice answers wrong/empty                        | Radio/checkbox `value` attrs drifted from the record's option keys                                                                                       | `validate_form_html` warns option-key drift; diff against `choiceKeys`                                                |
-| Same email accepted one day, rejected the next    | Fail-open verdict (`isValid: true, failed: true`) later resolving to a definitive one — expected waterfall behavior, not a bug                           | Check `failed` on the verdict; don't write tests expecting stable verdicts for fresh domains                          |
-| Thank-you never shows                             | Record has no `endStepKind: "thank_you"` step, or the HTML has no container for it                                                                       | Binding map: does a step carry `endStepKind`? Submit reveals it automatically when it exists                          |
-| Disqualified visitors see the thank-you           | No `endStepKind: "disqualified"` step; or page routes them manually to the wrong container                                                               | Same check; `disqualify()` only reveals a `disqualified` ending                                                       |
-| Steps don't switch                                | `data-step-id` doesn't match record stepIds, or goto target invalid                                                                                      | Console warns on invalid `goToStep`; `validate_form_html` blocks unknown step ids                                     |
-| Duplicate responses per visitor                   | `init` called more than once without `destroy()` (SPA remounts)                                                                                          | One engine per page-life; call `form.destroy()` on teardown                                                           |
-| GTM/GA4/Meta events not firing                    | Preview mode (tracking is fully blocked in preview), or settings not set                                                                                 | Deployed page without preview; `window.dataLayer` after a step submit; settings via `update_form_settings`            |
-| Conversions (ads rules) not firing                | Rules gate on the trigger + URL conditions; terminal rules only fire on `completed`, never on disqualify; everything queues until the first `responseId` | Check rule trigger/conditions in the dashboard; watch for the `saved` event before expecting queued fires             |
-| Enrichment fields empty                           | The environment has no ENABLED enrichment provider — a record-declared `enrichmentSourceField` is then silently inert                                    | `form.capabilities.enrichment` (false = inert); `debug: true` warns at boot; enable a provider in the dashboard       |
-| Lead attribution missing                          | `identify` blocked (preview) or ad-blocked; re-identify after SPA route change                                                                           | `form.identify()`; network tab `identify` call                                                                        |
+| Symptom                                           | Likely cause                                                                                                                                              | Check                                                                                                                 |
+| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `init` throws "could not fetch runtime config"    | Wrong/missing `apiBaseUrl` — the error names the exact URL and host it tried                                                                              | Use the `apiBaseUrl` from `get_sdk_binding_map`; curl the URL from the error                                          |
+| No responses at all                               | `preview: true` left in the deployed page (blocks ALL writes)                                                                                             | Grep the page for `preview`; `saved` event never fires in preview                                                     |
+| No responses at all                               | Form never published — runtime-config serves the "not published yet" placeholder, so step/question ids don't match                                        | Console shows unbound-questionId warnings; `publish_form`                                                             |
+| Some answers missing                              | Binding drift: questionId unbound or misspelled                                                                                                           | Console warning "record declares questionIds with no bound element"; `validate_form_html`                             |
+| Some answers missing                              | Partial saves off and visitor abandoned mid-form                                                                                                          | `trackPartialResponses` in settings; expected behavior                                                                |
+| Finished response stored as a partial             | SDK < 0.1.3 sent the terminal write fire-and-forget; current SDK awaits it — remaining cause is tearing the page down mid-flight                          | Upgrade; `await form.submit()` then `await form.flush()` before any programmatic close                                |
+| 400 "Fields are missing or incorrectly formatted" | Hand-built `setAnswer` with the wrong shape (choice questions want structured lists, not label strings)                                                   | Compare the payload with the binding map's `answerShape`; prefer `data-*` binding, which builds choice answers itself |
+| Choice answers wrong/empty                        | Radio/checkbox `value` attrs drifted from the record's option keys                                                                                        | `validate_form_html` warns option-key drift; diff against `choiceKeys`                                                |
+| Same email accepted one day, rejected the next    | Fail-open verdict (`isValid: true, failed: true`) later resolving to a definitive one — expected waterfall behavior, not a bug                            | Check `failed` on the verdict; don't write tests expecting stable verdicts for fresh domains                          |
+| Thank-you never shows                             | Record has no `endStepKind: "thank_you"` step, or the HTML has no container for it                                                                        | Binding map: does a step carry `endStepKind`? Submit reveals it automatically when it exists                          |
+| Disqualified visitors see the thank-you           | No `endStepKind: "disqualified"` step; or page routes them manually to the wrong container                                                                | Same check; `disqualify()` only reveals a `disqualified` ending                                                       |
+| Steps don't switch                                | `data-step-id` doesn't match record stepIds, or goto target invalid                                                                                       | Console warns on invalid `goToStep`; `validate_form_html` blocks unknown step ids                                     |
+| Continue looks dead, then the step switches later | Earlier SDK builds awaited the partial save before switching; the current SDK switches immediately and saves behind (`debug: true` logs `next requested`) | Upgrade; `next()` resolves on the step change, `saved` fires when the write lands                                     |
+| Scheduler says "No availability this month"       | The event type has no bookable slots (host schedule, max advance, no connected host) — the widget already opens on the first month the summary reports    | `getAvailabilitySummary` → `next_available_date`; the host's schedule in the dashboard; `preview: true` mocks slots   |
+| Duplicate responses per visitor                   | `init` called more than once without `destroy()` (SPA remounts)                                                                                           | One engine per page-life; call `form.destroy()` on teardown                                                           |
+| GTM/GA4/Meta events not firing                    | Preview mode (tracking is fully blocked in preview), or settings not set                                                                                  | Deployed page without preview; `window.dataLayer` after a step submit; settings via `update_form_settings`            |
+| Conversions (ads rules) not firing                | Rules gate on the trigger + URL conditions; terminal rules only fire on `completed`, never on disqualify; everything queues until the first `responseId`  | Check rule trigger/conditions in the dashboard; watch for the `saved` event before expecting queued fires             |
+| Enrichment fields empty                           | The environment has no ENABLED enrichment provider — a record-declared `enrichmentSourceField` is then silently inert                                     | `form.capabilities.enrichment` (false = inert); `debug: true` warns at boot; enable a provider in the dashboard       |
+| Lead attribution missing                          | `identify` blocked (preview) or ad-blocked; re-identify after SPA route change                                                                            | `form.identify()`; network tab `identify` call                                                                        |
 
 ## Reading a response back
 

package/skills/surface-forms-sdk/patterns.md

@@ -104,6 +104,44 @@ Dynamic branching instead of static buttons: keep a handle from `init` and call
 code-driven. Full event list for your own listeners: `viewed`, `started`, `stepChanged`,
 `stepCompleted`, `completed`, `disqualified`, `saved`, `error`.
 
+Timing: `next()`/`goToStep()` switch the step immediately — the partial save lands behind
+them, so the visitor never waits on the network. `submit()`/`disqualify()` await the finishing
+write before the ending shows; disable that button while the promise is pending:
+
+```js
+submitButton.addEventListener("click", async () => {
+  submitButton.disabled = true;
+  await form.submit();
+});
+```
+
+## Invalid-email policy (ask the owner — default is "annotate only")
+
+The SDK never decides what an invalid address means for the visitor. Confirm the owner's
+choice, then pick ONE shape:
+
+```js
+// Default — annotate only: verdict meta rides the response; the visitor continues.
+SurfaceForms.init({ ..., emailValidation: true });
+// (declarative surface-next-button markup is enough — no JS gate)
+
+// Block — keep the visitor on the step until the address is deliverable.
+continueButton.addEventListener("click", async () => {
+  const { isValid, reason, failed } = await form.validateEmail(emailInput.value);
+  if (isValid || failed) return form.next(); // fail-open: never lock out on a vendor outage
+  errorEl.textContent = `That address looks undeliverable (${reason}).`;
+});
+
+// Disqualify — end the form on the "not a fit" ending.
+continueButton.addEventListener("click", async () => {
+  const { isValid } = await form.validateEmail(emailInput.value);
+  isValid ? form.next() : form.disqualify();
+});
+```
+
+Block/disqualify pages carry `data-surface-nav="js"`. Both paths share one per-address cache
+with automatic mode, so pairing a gate with `emailValidation: true` bills each address once.
+
 ## Multi-field component
 
 `data-field-name` resolves per control — set it on each input, not (only) the wrapper. `IdentityInfo` is the standard contact-details component; bind only the fields the record declares (its `fieldNames` in the binding map):
@@ -116,14 +154,41 @@ code-driven. Full event list for your own listeners: `viewed`, `started`, `stepC
 </div>
 ```
 
-## Scheduler step (Surface scheduler)
+## Scheduler step
 
-A `CalendlyScreen` with `calendarType: "Surface"` renders through the SDK's own unstyled widget — never iframe the hosted booking page, and never bind the question in HTML (the `onComplete` writes the answer):
+Default: one call. `mountScheduler` renders the record's scheduler question for ANY supported
+provider (Surface's widget default-styled, or the record's third-party embed — Calendly,
+Cal.com, SavvyCal, Chili Piper, HubSpot, RevenueHero, Zoom, Reclaim.ai, Clari), emits the
+lifecycle on `form.on("scheduler")`, and persists the booking into the response by itself.
+Never iframe the hosted booking page, and never bind the question in HTML:
 
 ```html
 <section data-step-id="step_book" hidden>
   <div id="booking"></div>
 </section>
+<script>
+  const teardown = SurfaceFormsSDK.mountScheduler({
+    form,
+    container: document.querySelector("#booking"),
+    onEvent(e) {
+      if (e.type === "booking_confirmed") form.submit(); // or next()/goToStep, per your flow
+    },
+  });
+</script>
+```
+
+Note the booking itself needs no wiring — persistence is automatic (`persist: false` opts out);
+`onEvent` here only drives navigation. `styled: false` skips the injected scoped stylesheet
+(Surface provider). Clari is embed-only (no booking signal → drive navigation yourself).
+In preview mode the Surface path books synthetically and nothing is written. The Surface widget
+opens on the current month and, when that month has no slots, jumps to the first bookable date
+the availability summary reports — "No availability this month" after that means the event type
+has none.
+
+Custom booking UI (only when asked): mount the unstyled widget directly and write the answer
+yourself —
+
+```html
 <script>
   const { createSchedulerClient, createTransport, mountBookingWidget, toSchedulerAnswerState } =
     SurfaceFormsSDK;
@@ -144,8 +209,7 @@ A `CalendlyScreen` with `calendarType: "Surface"` renders through the SDK's own
 The widget emits semantic markup under stable `surface-booking-*` classes (full DOM tree in
 `llms.txt`) and injects no CSS — style from the page. Labels are locale-formatted by default
 with the raw value on each element's `data-value`; pass `formatters: { month?, date?, time? }`
-to override the copy. In preview mode the client returns a synthetic booking, so the flow is
-testable offline.
+to override the copy.
 
 ## React adapter (SPA)
 
@@ -209,7 +273,9 @@ function QualifySteps({ form }: { form: SurfaceForm }) {
 }
 ```
 
-`state` is `useSyncExternalStore`-backed: referentially stable between engine mutations, safe to render from directly. `submit()`/`disqualify()` move `state.currentStepId` to the record's matching ending step, so the same step-switch renders the confirmation. On SPA route changes call `form.identify()` to re-attribute the visitor; on programmatic teardown after a submit flow, `await form.flush()` first.
+`state` is `useSyncExternalStore`-backed: referentially stable between engine mutations, safe to render from directly. `state.answers` is keyed by stepId then questionId — the example reads the current step (`state.answers[state.currentStepId]`), but an EARLIER step's answer (booking prefill, a summary screen) is read by that step's id: `state.answers["step_role"]?.["q_role"]`. `submit()`/`disqualify()` move `state.currentStepId` to the record's matching ending step, so the same step-switch renders the confirmation. On SPA route changes call `form.identify()` to re-attribute the visitor.
+
+React teardown rule: `destroy()` alone in the effect cleanup is correct — a cleanup cannot await, partial saves are beacons that survive unmount, and the finishing write was already awaited by `submit()` itself before the cleanup can run. Reserve `await form.flush()` for programmatic teardown where the process itself may die with a write still queued (a test harness closing the browser), not for ordinary SPA unmounts.
 
 ## Tracking setup
 

package/dist/types/bind/bindForm.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/bind/bookingWidget.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/emailValidation.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/responses.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/runtimeConfig.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/runtimeConfig.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/scheduler.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/scheduler.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/client/transport.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/answerAudit.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/answerStates.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/formEngine.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/redirect.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/responsePayload.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/responsePayload.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/urlData.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/urlData.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/engine/urlPrefill.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/dropoffDetection.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/emitter.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/formJourneyTracker.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/formJourneyTracker.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/pushEvents.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/pushEvents.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/startedDetection.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/events/viewDetection.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/browserFingerprint.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/ensureIdentified.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/identify.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/identify.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/journey.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/journey.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/core/identity/journey.testStubs.d.ts

@@ -1,3 +0,0 @@
-export declare const stubJourneyDom: ({ href }?: {
-    href?: string;
-}) => Map<string, string>;

package/dist/types/core/identity/leadDataCache.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/enrichment/attachEnrichment.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/react/ssr.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/react/useSurfaceForm.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/surfaceForms.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/tracking/attachTracking.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/tracking/conversionRules.contract.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/tracking/conversionRules.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/tracking/vendors.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/validation/attachEmailValidation.test.d.ts

@@ -1 +0,0 @@
-export {};