@clipform/mcp-server 2.16.0 → 2.16.1

package/dist/{chunk-ZHXMQ2PV.js → chunk-Z4ZGF6OV.js}

@@ -48,6 +48,19 @@ var FEATURES = {
     status: "live",
     category: "builder"
   },
+  // Backfilled (#4338): apps/viewer/components/FormViewer.tsx renders exactly
+  // one node at a time (`currentNode = nodes[currentIndex]`, single
+  // `AnimatePresence` block gating on `currentNode`) and transitions to the
+  // next on answer - never a scrollable list of every question. No
+  // enabled/status change (this has always been the viewer's shape), so no
+  // wentLiveAt.
+  one_question_at_a_time: {
+    name: "One question at a time",
+    description: "The viewer shows a single question and transitions to the next, never a scrollable list of every question",
+    enabled: true,
+    status: "live",
+    category: "builder"
+  },
   branching: {
     name: "Conditional branching",
     description: "Choice nodes route to different destinations based on which option is picked",
@@ -140,7 +153,12 @@ var FEATURES = {
   },
   node_details: {
     name: "Details",
-    description: "Structured fields (name, email, phone, company) with consent checkboxes",
+    // Widened (#4338): the checkbox items are typed 'consent' (required,
+    // blocks submission until checked) or 'opt_in' (optional) - see
+    // CONSENT_TYPES in node-types.js and the viewer's Contact.tsx. Both are
+    // plain text checkboxes available to every creator with no gate; only
+    // attaching a PDF agreement document is gated (consent_documents, beta).
+    description: "Structured fields (name, email, phone, company) with consent and opt-in checkboxes",
     enabled: true,
     status: "live",
     category: "node-types"
@@ -201,18 +219,20 @@ var FEATURES = {
   },
   node_camera: {
     name: "Camera",
-    description: "Capture a photo from the device camera",
-    // Scaffolded disabled (#2097): code lands ready, but node.type's DB check
-    // constraint doesn't accept 'camera' yet - that's a separate parked
-    // holds-migration PR. Flip once the migration has merged (= applied to
-    // prod) and the apps have deployed.
+    // Description mirrors NODE_TYPES.camera.description (the node SSOT) - the
+    // node captures photo OR video (allowed_capture, #2759), not photo only.
+    description: "Capture a photo or video from the device camera",
+    // Dogfooding in live via NODE_COMPANY_ALLOWLIST.node_camera below. The DB
+    // node_type_check constraint already accepts 'camera' in prod (migration
+    // #2103 merged + applied 2026-07-17), so GA is now a pure app-config flip:
+    // set enabled true + status 'live' and follow feature-lifecycle.
     enabled: false,
     status: "planned",
     category: "node-types"
   },
   node_conditional: {
-    name: "Conditional",
-    description: "Route the flow to different branches based on Score",
+    name: "If / then",
+    description: "Route the flow to different branches based on a score, max score, or category variable.",
     // Scaffolded disabled (#4105, phase 1 of the #4104 variables engine): code
     // lands ready, but node.type's DB check constraint doesn't accept
     // 'conditional' yet - that's a separate parked holds-migration PR. Flip
@@ -288,10 +308,26 @@ var FEATURES = {
     status: "live",
     category: "responses"
   },
+  // Backfilled (#4338): the respondent-facing recorder (packages/media-recorder)
+  // already device-detects and adapts - mobile-first cover framing by default,
+  // front/back camera flip control shown only on mobile, iOS Safari getUserMedia
+  // quirks handled (browser-detection.ts) - so recording on a phone has always
+  // worked and been tuned for it. No enabled/status change, so no wentLiveAt.
+  mobile_recording: {
+    name: "Mobile-optimized recording",
+    description: "Respondents recording audio/video/photo on a phone get a mobile-first layout and a front/back camera flip control",
+    enabled: true,
+    status: "live",
+    category: "responses"
+  },
   // -- Analytics --
   analytics_overview: {
     name: "Analytics dashboard",
-    description: "Views, starts, completions with daily time series",
+    // Widened #4338: views/starts/completions update live (useInsightRealtime,
+    // apps/dashboard's analytics page) and NodeResultCard computes a per-node
+    // drop-off count (`total_views - answeredCount`, "N people dropped off"),
+    // not just an aggregate form-level funnel.
+    description: "Real-time views, starts, and completions with daily time series, plus per-question drop-off",
     enabled: true,
     status: "live",
     category: "analytics"
@@ -318,6 +354,35 @@ var FEATURES = {
     wentLiveAt: "2026-06-07",
     category: "analytics"
   },
+  // Backfilled (#4338): the Responses table's search box (DataSpreadsheet's
+  // globalFilter, TanStack default `includesString` across every visible
+  // column) already searches every node-response column's displayed value -
+  // for audio/video answers that value falls back to the transcription text
+  // (list_form_submissions / get_latest_responses_for_session's
+  // response_data->'transcription'->>'text', supabase/migrations
+  // 20260920190000_submission_grain_per_completion.sql) before the generic
+  // "Video/Audio response" label. So a transcribed response is genuinely
+  // full-text searchable today - this key just gives that existing behaviour
+  // a name marketing can cite. No enabled/status change (search has always
+  // been on), so deliberately no wentLiveAt.
+  //
+  // Scoped honestly (review follow-up, #4338): this is ONE form's Responses
+  // table, filtered client-side (TanStack's globalFilter over the rows
+  // already loaded for that form) - never cross-form, and a video/audio
+  // answer's transcript only becomes searchable once transcription finishes
+  // (checked: no write path ever sets response_data.display or .text on a
+  // media answer at submit time - only the async transcription pipeline
+  // adds `transcription.text` later, so nothing hides the transcript once it
+  // lands; transcription itself is not plan-gated, it runs on every
+  // audio/video response regardless of plan). It also never jumps playback
+  // to the matched moment in the recording - it only surfaces the row.
+  response_search: {
+    name: "Response search",
+    description: "Filter one form's responses table by keyword, including transcript text once transcription finishes - not cross-form, and does not jump to a moment in the recording",
+    enabled: true,
+    status: "live",
+    category: "analytics"
+  },
   tracked_links: {
     name: "Tracked links",
     description: "URL tracking and click-through analytics for shared form links",
@@ -406,10 +471,37 @@ var FEATURES = {
     status: "live",
     category: "sharing"
   },
+  // Backfilled (#4338): the public /templates gallery (apps/marketing/src/app/templates,
+  // apps/marketing/src/components/template-gallery) lets anyone browse and start
+  // from a real, live Clipform template - a curated core set, plus the rest
+  // (project_template_gallery_curated_core6). No enabled/status change, no wentLiveAt.
+  templates_gallery: {
+    name: "Template gallery",
+    description: "Browse and start a form from a real, prebuilt template",
+    enabled: true,
+    status: "live",
+    category: "sharing"
+  },
   // -- AI --
   ai_form_generation: {
     name: "AI form generation",
-    description: "Generate complete forms from a text prompt via MCP or dashboard",
+    // Corrected twice (#4338): not MCP-only (round 4 found the public
+    // web AI builder). In practice this mostly means the ChatGPT/Claude
+    // connector (chat_connectors) - leading with that per the user.
+    description: "Generate complete forms from a text prompt, primarily via the ChatGPT and Claude connectors (see chat_connectors); also the public web AI builder on marketing pages; no in-dashboard entry point",
+    enabled: true,
+    status: "live",
+    category: "ai"
+  },
+  // Confirmed live by the user 2026-09-27: both the ChatGPT App Directory and
+  // Claude Connectors Directory listings are live. Implementation is
+  // packages/mcp-server (the same MCP server surfaced as a connector in both
+  // directories - see #797 /
+  // #3681). No enabled/status change
+  // pending, so no wentLiveAt.
+  chat_connectors: {
+    name: "ChatGPT and Claude connectors",
+    description: "Build and edit forms from ChatGPT and Claude via the Clipform connector, listed in both the ChatGPT App Directory and the Claude Connectors Directory",
     enabled: true,
     status: "live",
     category: "ai"
@@ -548,7 +640,7 @@ var FEATURES = {
     name: "Google Sheets",
     description: "Sync form responses to a Google Sheet, one row per submission",
     enabled: false,
-    status: "planned",
+    status: "beta",
     category: "integrations"
   },
   notifications: {
@@ -1603,11 +1695,11 @@ var NODE_TYPES = {
   // branch is a node_options row (has_options:true); the branch edge is a
   // `jump` action anchored by the option's id (LogicAction.option_id).
   conditional: {
-    label: "Conditional",
+    label: "If / then",
     shorthand: "If",
     icon: "Split",
     color: "#E0E7FF",
-    description: "Route the flow based on Score",
+    description: "Route the flow to different branches based on a score, max score, or category variable.",
     category: "logic",
     sort_order: 6.7,
     has_options: true,
@@ -1621,6 +1713,10 @@ var NODE_TYPES = {
     supports_media: false,
     is_system: false,
     show_in_results: false,
+    // Logic/routing node - no respondent answer to render in a channel
+    // notification, same as the other control nodes (redirect, link_list,
+    // end_screen). Required by the #4154 notify_inline invariant.
+    notify_inline: false,
     default_config: {
       options: [
         { content: "Branch 1" },
@@ -3388,4 +3484,4 @@ export {
   getSessionContextWithAuth,
   getSessionContext
 };
-//# sourceMappingURL=chunk-ZHXMQ2PV.js.map
+//# sourceMappingURL=chunk-Z4ZGF6OV.js.map