@picked/client 0.0.1-dev.1787543060859 → 0.0.1-dev.1788925875333

package/dist/docs/reference/dashboard/fields.mdx

@@ -74,21 +74,27 @@ a visitor who matches the condition. See
 
 ## Privacy
 
-Two policies control where the value of a field can go. They are independent, and a
-sensitive field usually needs both.
+A field captures nothing until you permit it. Two checkboxes control where the value of
+a field can go. Both start off.
 
-| Policy | What it does |
+| Checkbox | What it does when you turn it on |
 | --- | --- |
-| **Do Not Track** | Picked keeps the value out of your analytics events. The events carry the field ID only. |
-| **Do Not Store** | The SDK reads the value but does not put it in browser storage. |
+| **Remember in the browser** | The SDK keeps the value on the device of the visitor. The value is available after a page load. |
+| **Send to analytics** | Picked puts the value in your analytics events. |
 
-Neither policy stops the flow from the use of the value inside the page. A field with both
-policies set still holds its value there. The flow validates the step with it, and it
-evaluates the conditions after the step with it. The policies control what leaves the
-page.
+Each checkbox is independent of the other.
+
+A new field that you leave alone sends no value to your analytics. It writes no value to
+the browser. Keep both checkboxes off for sensitive data such as a password, a tax
+number, or a payment detail.
 
-Set both for a password, a tax number, or a payment detail. A field that only takes a
-branch in a flow needs neither.
+Never turn on **Send to analytics** for personal data. A name, an email address, a phone
+number, a home address, or an identity number must not reach your analytics.
+
+Neither checkbox stops the flow from the use of the value inside the page. A field that
+captures nothing still holds its value there. The flow validates the step with it, and it
+evaluates the conditions after the step with it. The checkboxes control what leaves the
+page.
 
 ## Related
 

package/dist/docs/reference/delivery-api/preview-caching-crawling.md

@@ -30,7 +30,7 @@ SDK sends a `Picked-Client: sdk` request header:
 
 | Request | `Cache-Control` |
 | --- | --- |
-| Published, `Picked-Client: sdk` | `public, s-maxage=60, stale-while-revalidate=86400` |
+| Published, `Picked-Client: sdk` | `public, s-maxage=10` |
 | Published, other clients | `private, no-store` |
 | Preview | `no-store` |
 

package/dist/docs/reference/sdk/features.md

@@ -119,6 +119,11 @@ This is useful for QA, because you can test one bucket value and change no code.
 SDK keeps the override value in session storage. The browser clears it when you close
 the tab.
 
+When a URL parameter overrides a feature flag, the SDK registers that feature flag as
+enabled. Therefore `useFeatureEnabled` and `getFeatureEnabled` give `true`. A URL
+parameter can also override a feature flag that the dashboard **Enabled** toggle keeps
+off.
+
 ## Use a feature flag in an experience condition
 
 You can use a feature flag in an experience condition through JSON logic:

package/dist/docs/reference/sdk/fields.md

@@ -56,6 +56,38 @@ export const communicationMethods = createField({
 })
 ```
 
+## Register fields on the client
+
+Register fields when you create the Picked client. Pass a `fields` object. The key of an
+entry becomes the field `key` when the definition does not set one. A definition with its
+own `key` keeps it. Pass a function to build a definition once during the client setup:
+
+```ts
+import { createClient } from 'picked'
+
+const client = createClient({
+  projectId: 'your-project-id',
+  fields: {
+    email: {
+      id: 'email',
+      name: 'email',
+      label: 'Email Address',
+      type: 'text',
+      multiple: false,
+      required: true,
+    },
+    age: () => ({
+      id: 'age',
+      name: 'age',
+      label: 'Age',
+      type: 'number',
+      multiple: false,
+      required: false,
+    }),
+  },
+})
+```
+
 ## Field types
 
 A field has one of four basic types: `text`, `number`, `boolean`, or `object`.
@@ -124,36 +156,50 @@ const conditionalField = createField({
 
 ## Field policies
 
-Use a privacy policy to control how Picked tracks and stores the data of a field:
+A field captures nothing until you permit it. Use a privacy policy to let Picked track
+or store the data of a field:
 
 ```ts
-const sensitiveField = createField({
-  id: 'ssn',
-  name: 'ssn',
+const colourField = createField({
+  id: 'favourite-colour',
+  name: 'favourite-colour',
   type: 'text',
-  label: 'Social Security Number',
+  label: 'Favourite colour',
   multiple: false,
   required: true,
   policies: {
-    doNotTrackValue: true, // Do not send the value to analytics.
-    doNotStoreValue: true, // Do not keep the value in browser storage.
+    trackValue: true, // Send the value to analytics.
+    storeValue: true, // Keep the value in browser storage.
   },
 })
 ```
 
 **Privacy policies**:
 
-- `doNotTrackValue`: keeps the value of the field out of your analytics events. The
-  events carry the field ID only.
-- `doNotStoreValue`: stops the SDK, so that it does not put the value in browser
-  storage.
+- `trackValue`: set it to `true` to put the value of the field in your analytics events.
+  At `false`, and when the policy is absent, the events carry the field ID only.
+- `storeValue`: set it to `true` to let the SDK put the value in browser storage. At
+  `false`, and when the policy is absent, the SDK keeps the value out of storage.
+
+Both policies keep the value in the browser by default. A field with no `policies`
+object sends no value to your analytics and writes no value to browser storage. Keep
+the default for sensitive data such as a tax number, a credit card number, or a
+password. That data stays in the browser:
 
-Use these policies for sensitive data such as a tax number, a credit card number, or
-a password. That data must stay in the browser.
+```ts
+const sensitiveField = createField({
+  id: 'ssn',
+  name: 'ssn',
+  type: 'text',
+  label: 'Social Security Number',
+  multiple: false,
+  required: true,
+})
+```
 
-Neither policy stops the flow from the use of the value inside the page. A field with both
-policies set still holds its value there, for step validation and for the conditions after
-the step. The policies control what leaves the page: your analytics, and browser
+Neither policy stops the flow from the use of the value inside the page. A field that
+captures nothing still holds its value there, for step validation and for the conditions
+after the step. The policies control what leaves the page: your analytics, and browser
 storage.
 
 ## Field metadata

package/dist/docs/reference/sdk/type-generation.md

@@ -119,20 +119,31 @@ The generated `picked-env.d.ts` file looks like:
 
 ```typescript
 // GENERATED by `@picked/typegen` — do not edit by hand.
-// source: published   `x-picked-version-id`: `ver_456`
 // Reference: `https://docs.picked.app/reference/sdk/type-generation`
 
-export interface WelcomePage { /* ... */ }
-export interface FieldValues { /* ... */ }
-export type FeatureKey = 'default' | 'hero' | 'winter-sale'
+export type WelcomePage = { /* ... */ }
+export type FieldValues = { /* ... */ }
+export type FeatureKey =
+  | 'default'
+  | 'hero'
+  | 'winter-sale'
 
 declare module '@picked/client' {
   interface PickedSchemaRegistry {
-    contentModels: { 'welcome-page': WelcomePage }
-    stepContentModels: { intro: 'welcome-page' }
+    contentModels: {
+      'welcome-page': WelcomePage
+    }
+    stepContentModels: {
+      'intro': 'welcome-page'
+    }
+    featureValues: {
+      'hero':
+        | false
+        | 'hero-a'
+        | 'hero-b'
+    }
     fieldValues: FieldValues
     featureKeys: FeatureKey
-    featureValues: { hero: false | 'hero-a' | 'hero-b' }
   }
 }
 ```

package/dist/docs/reference/tools/mcp.md

@@ -15,9 +15,11 @@ Context Protocol (MCP).
 | Tool                     | Description                                                  |
 | ------------------------ | ------------------------------------------------------------ |
 | `list_projects`          | Lists your organizations and projects                        |
+| `list_workspaces`        | Lists the workspaces in a project                            |
 | `get_workspace_overview` | Reads the full workspace state                               |
 | `get_schema_info`        | Reads the documentation for Picked concepts and the data model |
-| `get_picked_docs`        | Reads the complete Picked documentation, as text for an agent |
+| `list_picked_docs`       | Lists every Picked documentation page with its URL              |
+| `read_picked_doc`        | Reads one documentation page, or one section of it              |
 
 ### Experiences