@picked/client 0.0.1-dev.1787788898336 → 0.0.1-dev.1789541668638

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`.
@@ -136,18 +168,18 @@ const colourField = createField({
   multiple: false,
   required: true,
   policies: {
-    doNotTrackValue: false, // Send the value to analytics.
-    doNotStoreValue: false, // Keep the value in browser storage.
+    trackValue: true, // Send the value to analytics.
+    storeValue: true, // Keep the value in browser storage.
   },
 })
 ```
 
 **Privacy policies**:
 
-- `doNotTrackValue`: set it to `false` to put the value of the field in your analytics
-  events. At `true`, and when the policy is absent, the events carry the field ID only.
-- `doNotStoreValue`: set it to `false` to let the SDK put the value in browser storage.
-  At `true`, and when the policy is absent, the SDK keeps the value out of 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

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