@picked/client 0.0.1-dev.1777506629683 → 0.0.1-dev.1777530309364

package/dist/docs/pickedql/index.md

@@ -22,7 +22,7 @@ PickedQL handles table mapping and dimension joins automatically. You write conc
 1. **Virtual table expansion**: Table names like `metrics` map to underlying data tables
 2. **Virtual function expansion**: Shorthand functions like `control_users()` expand to full aggregate expressions
 3. **Auto dimension joins**: References to dimension columns (like `device_category` or `country_code`) trigger automatic `LEFT JOIN` clauses — you never write joins yourself
-4. **Tenant isolation**: Every query must include a tenant filter in the `WHERE` clause — usually `project_id`, but `projects` uses `id` (the row's `id` IS the project id). PickedQL extracts the filter and verifies you have permission to access that project
+4. **Tenant isolation**: Every query must include a `project_id` filter in the `WHERE` clause. PickedQL extracts it and verifies you have permission to access that project
 5. **SQL passthrough**: Standard SQL (including `CASE WHEN`, window functions, and subqueries) works alongside virtual functions
 
 ## Best practices
@@ -32,5 +32,4 @@ PickedQL handles table mapping and dimension joins automatically. You write conc
 - **Use `experience_journey` for sankey / funnel charts**: One line of SQL returns `source, target, users` — the 8-CTE scaffold (dedup, top-N path ranking, lagInFrame) is handled internally; pass parameters via `WHERE`
 - **Don't write JOINs**: PickedQL injects them automatically when you reference dimension columns
 - **Group by any dimension**: Add dimension columns to `SELECT` and `GROUP BY` freely — required joins are handled for you
-- **Reference table metadata for free**: Use `step_title`, `experience_title`, `project_name` directly in `events` queries — PickedQL auto-joins the `steps`, `experiences`, and `projects` reference tables
 

package/dist/docs/pickedql/schema.md

@@ -83,36 +83,6 @@ These columns are joined automatically when referenced — no `JOIN` syntax need
 | `product_name` | dim_product | Product name |
 | `product_category` | dim_product | Product category |
 | `product_page` | dim_product | Product page |
-| `step_title` | steps | Step title (joined on `project_id` + `experience_id` + `step_id`) |
-| `experience_title` | experiences | Experience title (joined on `project_id` + `experience_id`) |
-| `project_name` | projects | Project name |
-| `project_timezone` | projects | Project timezone |
-
-## `steps`, `experiences`, `projects`
-
-Reference tables describing your Picked configuration. Auto-joined onto `events` when their analyst-facing columns are referenced; require a per-table tenant filter when queried directly.
-
-| Source | Real Columns | Analyst Columns (when referenced from `events`) | Tenant filter (when queried directly) |
-|---|---|---|---|
-| `steps` | `id`, `title`, `experience_id`, `project_id`, `organization_id` | `step_title` | `project_id = '…'` |
-| `experiences` | `id`, `title`, `project_id`, `organization_id` | `experience_title` | `project_id = '…'` |
-| `projects` | `id`, `name`, `timezone`, `organization_id` | `project_name`, `project_timezone` | `id = '<project_id>'` |
-
-When queried directly, use the real column names:
-
-```sql
--- List all experiences for a project
-SELECT id, title FROM experiences WHERE project_id = 'your-project-id'
-```
-
-When referenced from `events`, use the prefixed analyst names — joins are injected automatically:
-
-```sql
-SELECT experience_title, step_title, count(*)
-FROM events
-WHERE project_id = 'your-project-id'
-GROUP BY experience_title, step_title
-```
 
 ## `features`
 
@@ -147,10 +117,7 @@ Aggregated step-transition edges for sankey / funnel charts. Parameters are supp
 | `num_nodes_after_start` | Integer |  | Forward window from start: keep steps where `seq_pos < start_seq + N` (card 4129 semantics). |
 | `num_nodes_before_target` | Integer |  | Backward window from target: keep steps where `seq_pos >= target_seq - N` (card 2740 semantics). Requires `targeting_step`. |
 | `top_n_path` | Integer |  | Keep only the top-N most-walked paths by user count. Defaults to no limit. |
-| `user_cohort_event` | String |  | Restrict to users who have at least one `fact_events` row with this `event_type`. Implemented as `user_canonical_id IN (SELECT DISTINCT user_canonical_id FROM fact_events WHERE event_type = '…')`. |
-| `client_local_date` | Date |  | Date range filter, pushed into the underlying scan. Supports `=`, `<`, `<=`, `>`, `>=`, `BETWEEN`. |
-| `event_timestamp` | DateTime64 |  | Server-side timestamp filter. Same operators as `client_local_date`. |
 
-When both window params are set, both predicates apply (intersection). Date filters combine via `AND` with the other params.
+When both window params are set, both predicates apply (intersection).
 
 See [data sources → experience_journey](./data-sources#experience_journey--sankey-ready-step-transitions) for usage examples.

package/dist/docs/pickedql/virtual-functions.md

@@ -21,12 +21,12 @@ Virtual functions are shorthand for aggregate expressions. They are **table-awar
 
 | Function | Description |
 |---|---|
-| `all_purchase_users()` | Users who completed a purchase |
+| `total_purchase_users()` | Users who completed a purchase |
 | `control_purchase_users()` | Control users who purchased (`metrics` only) |
 | `variant_purchase_users()` | Variant users who purchased (`metrics` only) |
-| `all_purchase_sessions()` | Sessions with a purchase (`metrics` only) |
-| `all_purchase_orders()` | Unique order count (`metrics` only) |
-| `all_cart_add_users()` | Users who added to cart |
+| `total_purchase_sessions()` | Sessions with a purchase (`metrics` only) |
+| `total_purchase_orders()` | Unique order count (`metrics` only) |
+| `total_cart_add_users()` | Users who added to cart |
 
 ## Conversion rates
 

package/dist/docs/{projects.mdx → projects.md}

@@ -2,17 +2,10 @@
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
-
 # Projects
 
 A project represents one website or app you want to instrument with Picked. Each project has its own set of experiences, entities, and configuration.
 
-<Screenshot
-  route="/{orgSlug}"
-  alt="The organization home page on the Picked dashboard, listing the projects in an organization"
-/>
-
 ## Create a project
 
 You need an organization first. If you don't have one, create it when you sign up.

package/dist/docs/{reports.mdx → reports.md}

@@ -2,17 +2,10 @@
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
-
 # Reports
 
 Reports show analytics data for your project. Track how visitors interact with your experiences and features.
 
-<Screenshot
-  route="/{orgSlug}/{projectId}/reports"
-  alt="The reports list for a project on the Picked dashboard"
-/>
-
 ## View report data
 
 Open a report to see its analytics. Data updates as new visitor interactions are recorded.

package/dist/docs/{steps.mdx → steps.md}

@@ -2,17 +2,10 @@
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
-
 # Steps
 
 A step is a visual screen or card shown to visitors during an experience. Each step holds one or more fields that collect data or display content.
 
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/steps"
-  alt="The steps list for a workspace on the Picked dashboard"
-/>
-
 ## Create a step
 
 1. Open your project.

package/dist/docs/{workspaces.mdx → workspaces.md}

@@ -2,18 +2,10 @@
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
-
 # Workspaces
 
 A workspace is a version of your project's configuration. Use workspaces to stage changes, preview them, and publish when ready.
 
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces"
-  alt="The workspaces list inside a project on the Picked dashboard"
-  hide={['[data-testid="workspace-row-relative-time"]']}
-/>
-
 ## How workspaces work
 
 Each project has a workspace that holds your experiences, features, and entity configurations. When you make changes in the dashboard — editing a flow, updating a feature, or modifying an entity — those changes exist in the workspace until you publish.

package/dist/esm/form/index.js

@@ -1,4 +1,4 @@
-import { t as e } from "../../rules-logic-BTIxfrJJ.js";
+import { t as e } from "../../rules-logic-D7dL30U1.js";
 import { attach as t, combine as n, createEffect as r, createEvent as i, createStore as a, sample as o, split as s } from "effector";
 //#region src/form/build-responses.ts
 function c(e, t, n) {
@@ -70,16 +70,10 @@ function m(e, n, i) {
 			staged: i,
 			committed: e.responses.getAllStore
 		},
-		effect: r(async ({ allFields: t, fieldKeys: n, staged: r, committed: i }) => {
-			let a = new Map(t.map((e) => [e.key, e]));
-			return await p(e, n.flatMap((e) => {
-				let t = a.get(e);
-				return t ? [t] : [];
-			}), { responses: {
-				...i,
-				...r
-			} });
-		})
+		effect: r(async ({ allFields: t, fieldKeys: n, staged: r, committed: i }) => await p(e, t.filter((e) => n.includes(e.key)), { responses: {
+			...i,
+			...r
+		} }))
 	});
 	return o({
 		clock: c.doneData,