@sanity/ailf 4.6.0 → 5.0.0

package/dist/_vendor/ailf-core/examples/index.d.ts

@@ -185,11 +185,26 @@ export declare const exampleGroqBlogListingData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Uses the groq tagged template literal", "Fetches blog posts with title, slug, and publishedAt fields", "Orders results by publishedAt in descending order"];
+        readonly criteria: readonly [{
+            readonly id: "uses-groq-template-literal";
+            readonly text: "Uses the groq tagged template literal";
+        }, {
+            readonly id: "fetches-blog-fields";
+            readonly text: "Fetches blog posts with title, slug, and publishedAt fields";
+        }, {
+            readonly id: "orders-by-published-at";
+            readonly text: "Orders results by publishedAt in descending order";
+        }];
     }, {
         readonly type: "llm-rubric";
         readonly template: "code-correctness";
-        readonly criteria: readonly ["Uses createClient from @sanity/client or next-sanity", "Exports a valid Next.js page component"];
+        readonly criteria: readonly [{
+            readonly id: "uses-create-client";
+            readonly text: "Uses createClient from @sanity/client or next-sanity";
+        }, {
+            readonly id: "exports-nextjs-page";
+            readonly text: "Exports a valid Next.js page component";
+        }];
     }];
     readonly baseline: {
         readonly enabled: true;
@@ -198,9 +213,9 @@ export declare const exampleGroqBlogListingData: readonly [{
     readonly status: "draft";
 }];
 /** TypeScript task template for example-groq-blog-listing */
-export declare const exampleGroqBlogListingTs = "/**\n * Example Task: Blog listing with GROQ queries.\n *\n * This is a starter template \u2014 edit it for your own documentation.\n * Each task evaluates whether an AI coding agent can implement a feature\n * using your docs as context. Delete this file or replace it entirely.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * Full field reference:\n *   https://github.com/sanity-labs/ai-literacy-framework/blob/main/docs/contributing-tasks.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  // \u2500\u2500 Mode \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // \"literacy\" tests whether AI coding tools can implement features\n  // using your docs as context. Other modes: \"mcp-server\",\n  // \"knowledge-probe\", \"agent-harness\", \"custom\".\n  mode: \"literacy\",\n\n  // \u2500\u2500 Identity \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Unique identifier \u2014 lowercase alphanumeric with hyphens.\n  // Must be unique across all task files in .ailf/tasks/.\n  id: \"example-groq-blog-listing\",\n  title: \"Blog listing with GROQ queries\",\n  description: \"Example \u2014 tests GROQ blog listing implementation\",\n\n  // Feature area this task belongs to. Tasks with the same area are\n  // grouped together in score summaries.\n  area: \"groq\",\n\n  // \u2500\u2500 Documentation context \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Canonical doc references for this task. The pipeline fetches these\n  // from Sanity and injects them into the prompt for baseline evaluation.\n  //\n  // This example uses slug-based references \u2014 the simplest form.\n  // See the other example tasks for path, id, and perspective references.\n  context: {\n    docs: [\n      {\n        slug: \"groq-introduction\",\n        reason: \"Core GROQ syntax and query language reference\",\n      },\n      {\n        slug: \"how-queries-work\",\n        reason: \"Query execution model and best practices\",\n      },\n    ],\n  },\n\n  // When true, the pipeline auto-generates an additional rubric that\n  // checks whether the LLM's response actually used the provided docs.\n  docCoverage: true,\n\n  // Path to a gold-standard implementation, relative to canonical/.\n  // The grader uses this as a reference when scoring code correctness.\n  referenceSolution: \"canonical/example-groq-blog-listing.ts\",\n\n  // \u2500\u2500 Prompt \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // prompt.text \u2014 the implementation prompt given to the LLM.\n  // Write this as if you're asking a developer to build the feature.\n  // Be specific about requirements so the grader can evaluate clearly.\n  prompt: {\n    text: `Create a Next.js page component that lists blog posts from Sanity\nusing GROQ. The page should display the title, slug, and published\ndate for each post, sorted by most recent first. Use the Sanity\nclient to fetch data.`,\n  },\n\n  // \u2500\u2500 Assertions \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Grading assertions \u2014 how the LLM's response is scored.\n  //\n  // \"llm-rubric\" assertions use a grader LLM to score against criteria.\n  // The \"template\" references a rubric template (e.g. task-completion).\n  //\n  // Available templates:\n  //   task-completion   \u2014 did the LLM implement the feature? (weight: 0.50)\n  //   code-correctness  \u2014 is the code idiomatic and correct? (weight: 0.25)\n  //\n  // You can also use value-based assertions:\n  //   { type: \"contains\", value: \"client.fetch\" }\n  //   { type: \"contains-any\", value: [\"createClient\", \"sanityClient\"] }\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Uses the groq tagged template literal\",\n        \"Fetches blog posts with title, slug, and publishedAt fields\",\n        \"Orders results by publishedAt in descending order\",\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        \"Uses createClient from @sanity/client or next-sanity\",\n        \"Exports a valid Next.js page component\",\n      ],\n    },\n  ],\n\n  // \u2500\u2500 Baseline variant \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  //   enabled \u2014 set to false to skip this task entirely\n  //   rubric  \u2014 \"full\" (default), \"abbreviated\" (faster), or \"none\"\n  baseline: {\n    enabled: true,\n    rubric: \"full\",\n  },\n\n  // Example tasks ship as drafts so they don't run in production evals.\n  // Change to \"active\" (or remove this field) to activate.\n  status: \"draft\",\n})\n";
+export declare const exampleGroqBlogListingTs = "/**\n * Example Task: Blog listing with GROQ queries.\n *\n * This is a starter template \u2014 edit it for your own documentation.\n * Each task evaluates whether an AI coding agent can implement a feature\n * using your docs as context. Delete this file or replace it entirely.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * Full field reference:\n *   https://github.com/sanity-labs/ai-literacy-framework/blob/main/docs/contributing-tasks.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  // \u2500\u2500 Mode \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // \"literacy\" tests whether AI coding tools can implement features\n  // using your docs as context. Other modes: \"mcp-server\",\n  // \"knowledge-probe\", \"agent-harness\", \"custom\".\n  mode: \"literacy\",\n\n  // \u2500\u2500 Identity \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Unique identifier \u2014 lowercase alphanumeric with hyphens.\n  // Must be unique across all task files in .ailf/tasks/.\n  id: \"example-groq-blog-listing\",\n  title: \"Blog listing with GROQ queries\",\n  description: \"Example \u2014 tests GROQ blog listing implementation\",\n\n  // Feature area this task belongs to. Tasks with the same area are\n  // grouped together in score summaries.\n  area: \"groq\",\n\n  // \u2500\u2500 Documentation context \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Canonical doc references for this task. The pipeline fetches these\n  // from Sanity and injects them into the prompt for baseline evaluation.\n  //\n  // This example uses slug-based references \u2014 the simplest form.\n  // See the other example tasks for path, id, and perspective references.\n  context: {\n    docs: [\n      {\n        slug: \"groq-introduction\",\n        reason: \"Core GROQ syntax and query language reference\",\n      },\n      {\n        slug: \"how-queries-work\",\n        reason: \"Query execution model and best practices\",\n      },\n    ],\n  },\n\n  // When true, the pipeline auto-generates an additional rubric that\n  // checks whether the LLM's response actually used the provided docs.\n  docCoverage: true,\n\n  // Path to a gold-standard implementation, relative to canonical/.\n  // The grader uses this as a reference when scoring code correctness.\n  referenceSolution: \"canonical/example-groq-blog-listing.ts\",\n\n  // \u2500\u2500 Prompt \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // prompt.text \u2014 the implementation prompt given to the LLM.\n  // Write this as if you're asking a developer to build the feature.\n  // Be specific about requirements so the grader can evaluate clearly.\n  prompt: {\n    text: `Create a Next.js page component that lists blog posts from Sanity\nusing GROQ. The page should display the title, slug, and published\ndate for each post, sorted by most recent first. Use the Sanity\nclient to fetch data.`,\n  },\n\n  // \u2500\u2500 Assertions \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Grading assertions \u2014 how the LLM's response is scored.\n  //\n  // \"llm-rubric\" assertions use a grader LLM to score against criteria.\n  // The \"template\" references a rubric template (e.g. task-completion).\n  //\n  // Available templates:\n  //   task-completion   \u2014 did the LLM implement the feature? (weight: 0.50)\n  //   code-correctness  \u2014 is the code idiomatic and correct? (weight: 0.25)\n  //\n  // You can also use value-based assertions:\n  //   { type: \"contains\", value: \"client.fetch\" }\n  //   { type: \"contains-any\", value: [\"createClient\", \"sanityClient\"] }\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"uses-groq-template-literal\",\n          text: \"Uses the groq tagged template literal\",\n        },\n        {\n          id: \"fetches-blog-fields\",\n          text: \"Fetches blog posts with title, slug, and publishedAt fields\",\n        },\n        {\n          id: \"orders-by-published-at\",\n          text: \"Orders results by publishedAt in descending order\",\n        },\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        {\n          id: \"uses-create-client\",\n          text: \"Uses createClient from @sanity/client or next-sanity\",\n        },\n        {\n          id: \"exports-nextjs-page\",\n          text: \"Exports a valid Next.js page component\",\n        },\n      ],\n    },\n  ],\n\n  // \u2500\u2500 Baseline variant \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  //   enabled \u2014 set to false to skip this task entirely\n  //   rubric  \u2014 \"full\" (default), \"abbreviated\" (faster), or \"none\"\n  baseline: {\n    enabled: true,\n    rubric: \"full\",\n  },\n\n  // Example tasks ship as drafts so they don't run in production evals.\n  // Change to \"active\" (or remove this field) to activate.\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-groq-blog-listing (from parsed TS data) */
-export declare const exampleGroqBlogListingYaml = "- mode: literacy\n  id: example-groq-blog-listing\n  title: Blog listing with GROQ queries\n  description: Example \u2014 tests GROQ blog listing implementation\n  area: groq\n  context:\n    docs:\n      - slug: groq-introduction\n        reason: Core GROQ syntax and query language reference\n      - slug: how-queries-work\n        reason: Query execution model and best practices\n  docCoverage: true\n  referenceSolution: canonical/example-groq-blog-listing.ts\n  prompt:\n    text: |-\n      Create a Next.js page component that lists blog posts from Sanity\n      using GROQ. The page should display the title, slug, and published\n      date for each post, sorted by most recent first. Use the Sanity\n      client to fetch data.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Uses the groq tagged template literal\n        - Fetches blog posts with title, slug, and publishedAt fields\n        - Orders results by publishedAt in descending order\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - Uses createClient from @sanity/client or next-sanity\n        - Exports a valid Next.js page component\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
+export declare const exampleGroqBlogListingYaml = "- mode: literacy\n  id: example-groq-blog-listing\n  title: Blog listing with GROQ queries\n  description: Example \u2014 tests GROQ blog listing implementation\n  area: groq\n  context:\n    docs:\n      - slug: groq-introduction\n        reason: Core GROQ syntax and query language reference\n      - slug: how-queries-work\n        reason: Query execution model and best practices\n  docCoverage: true\n  referenceSolution: canonical/example-groq-blog-listing.ts\n  prompt:\n    text: |-\n      Create a Next.js page component that lists blog posts from Sanity\n      using GROQ. The page should display the title, slug, and published\n      date for each post, sorted by most recent first. Use the Sanity\n      client to fetch data.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: uses-groq-template-literal\n          text: Uses the groq tagged template literal\n        - id: fetches-blog-fields\n          text: Fetches blog posts with title, slug, and publishedAt fields\n        - id: orders-by-published-at\n          text: Orders results by publishedAt in descending order\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - id: uses-create-client\n          text: Uses createClient from @sanity/client or next-sanity\n        - id: exports-nextjs-page\n          text: Exports a valid Next.js page component\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
 /** Parsed task data for example-id-based-ref (JSON-safe) */
 export declare const exampleIdBasedRefData: readonly [{
     readonly mode: "literacy";
@@ -226,11 +241,26 @@ export declare const exampleIdBasedRefData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Explains GROQ availability across different Sanity contexts", "Describes custom GROQ function creation and usage", "Notes differences in GROQ support between contexts"];
+        readonly criteria: readonly [{
+            readonly id: "groq-availability";
+            readonly text: "Explains GROQ availability across different Sanity contexts";
+        }, {
+            readonly id: "custom-groq-functions";
+            readonly text: "Describes custom GROQ function creation and usage";
+        }, {
+            readonly id: "groq-context-differences";
+            readonly text: "Notes differences in GROQ support between contexts";
+        }];
     }, {
         readonly type: "llm-rubric";
         readonly template: "code-correctness";
-        readonly criteria: readonly ["GROQ examples use valid syntax", "Custom function examples follow the correct API pattern"];
+        readonly criteria: readonly [{
+            readonly id: "valid-groq-syntax";
+            readonly text: "GROQ examples use valid syntax";
+        }, {
+            readonly id: "correct-function-api";
+            readonly text: "Custom function examples follow the correct API pattern";
+        }];
     }];
     readonly baseline: {
         readonly enabled: true;
@@ -239,9 +269,9 @@ export declare const exampleIdBasedRefData: readonly [{
     readonly status: "draft";
 }];
 /** TypeScript task template for example-id-based-ref */
-export declare const exampleIdBasedRefTs = "/**\n * Example Task: Document ID-based canonical doc references.\n *\n * Demonstrates using `id` to reference canonical documentation by\n * Sanity document `_id`. This is useful for:\n *   - Draft documents that don't have a stable slug yet\n *   - Programmatic references from imports or migrations\n *   - Documents where you know the _id but not the slug\n *\n * The `id` ref type can also carry optional `slug` and `path` fields\n * as human-readable annotations \u2014 these are NOT used for resolution,\n * only for display in logs and reports.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-id-based-ref\",\n  title: \"GROQ feature support (ID-based doc references)\",\n  description: \"Example \u2014 demonstrates ID-based canonical doc references\",\n\n  area: \"groq\",\n\n  // ID-based canonical doc references.\n  //\n  // Use the Sanity document _id to reference articles directly.\n  // Optional slug/path annotations help humans reading the file\n  // but are NOT used for resolution \u2014 only the `id` field matters.\n  //\n  // These IDs reference real articles in the Sanity docs (next dataset):\n  //   0ba88f1b... = \"GROQ feature support across Sanity\"\n  //   5b9c2863... = \"Custom GROQ functions\"\n  context: {\n    docs: [\n      {\n        id: \"0ba88f1b-d1a7-418a-9267-2e343d01886a\",\n        slug: \"groq-feature-support-by-context\", // annotation only\n        reason: \"GROQ feature support across different Sanity contexts\",\n      },\n      {\n        id: \"5b9c2863-ef01-4565-af8e-ee54e081ee74\",\n        slug: \"custom-groq-functions\", // annotation only\n        reason: \"Custom GROQ functions and pipelines\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Explain how GROQ is used across different Sanity contexts.\nCover the following:\n1. Which GROQ features are available in each context (API queries,\n   webhooks, custom functions, access control)\n2. How to create and use custom GROQ functions\n3. Any differences in GROQ support between contexts\nProvide examples demonstrating context-specific GROQ patterns.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Explains GROQ availability across different Sanity contexts\",\n        \"Describes custom GROQ function creation and usage\",\n        \"Notes differences in GROQ support between contexts\",\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        \"GROQ examples use valid syntax\",\n        \"Custom function examples follow the correct API pattern\",\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
+export declare const exampleIdBasedRefTs = "/**\n * Example Task: Document ID-based canonical doc references.\n *\n * Demonstrates using `id` to reference canonical documentation by\n * Sanity document `_id`. This is useful for:\n *   - Draft documents that don't have a stable slug yet\n *   - Programmatic references from imports or migrations\n *   - Documents where you know the _id but not the slug\n *\n * The `id` ref type can also carry optional `slug` and `path` fields\n * as human-readable annotations \u2014 these are NOT used for resolution,\n * only for display in logs and reports.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-id-based-ref\",\n  title: \"GROQ feature support (ID-based doc references)\",\n  description: \"Example \u2014 demonstrates ID-based canonical doc references\",\n\n  area: \"groq\",\n\n  // ID-based canonical doc references.\n  //\n  // Use the Sanity document _id to reference articles directly.\n  // Optional slug/path annotations help humans reading the file\n  // but are NOT used for resolution \u2014 only the `id` field matters.\n  //\n  // These IDs reference real articles in the Sanity docs (next dataset):\n  //   0ba88f1b... = \"GROQ feature support across Sanity\"\n  //   5b9c2863... = \"Custom GROQ functions\"\n  context: {\n    docs: [\n      {\n        id: \"0ba88f1b-d1a7-418a-9267-2e343d01886a\",\n        slug: \"groq-feature-support-by-context\", // annotation only\n        reason: \"GROQ feature support across different Sanity contexts\",\n      },\n      {\n        id: \"5b9c2863-ef01-4565-af8e-ee54e081ee74\",\n        slug: \"custom-groq-functions\", // annotation only\n        reason: \"Custom GROQ functions and pipelines\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Explain how GROQ is used across different Sanity contexts.\nCover the following:\n1. Which GROQ features are available in each context (API queries,\n   webhooks, custom functions, access control)\n2. How to create and use custom GROQ functions\n3. Any differences in GROQ support between contexts\nProvide examples demonstrating context-specific GROQ patterns.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"groq-availability\",\n          text: \"Explains GROQ availability across different Sanity contexts\",\n        },\n        {\n          id: \"custom-groq-functions\",\n          text: \"Describes custom GROQ function creation and usage\",\n        },\n        {\n          id: \"groq-context-differences\",\n          text: \"Notes differences in GROQ support between contexts\",\n        },\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        { id: \"valid-groq-syntax\", text: \"GROQ examples use valid syntax\" },\n        {\n          id: \"correct-function-api\",\n          text: \"Custom function examples follow the correct API pattern\",\n        },\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-id-based-ref (from parsed TS data) */
-export declare const exampleIdBasedRefYaml = "- mode: literacy\n  id: example-id-based-ref\n  title: GROQ feature support (ID-based doc references)\n  description: Example \u2014 demonstrates ID-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - id: 0ba88f1b-d1a7-418a-9267-2e343d01886a\n        slug: groq-feature-support-by-context\n        reason: GROQ feature support across different Sanity contexts\n      - id: 5b9c2863-ef01-4565-af8e-ee54e081ee74\n        slug: custom-groq-functions\n        reason: Custom GROQ functions and pipelines\n  docCoverage: true\n  prompt:\n    text: |-\n      Explain how GROQ is used across different Sanity contexts.\n      Cover the following:\n      1. Which GROQ features are available in each context (API queries,\n         webhooks, custom functions, access control)\n      2. How to create and use custom GROQ functions\n      3. Any differences in GROQ support between contexts\n      Provide examples demonstrating context-specific GROQ patterns.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Explains GROQ availability across different Sanity contexts\n        - Describes custom GROQ function creation and usage\n        - Notes differences in GROQ support between contexts\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - GROQ examples use valid syntax\n        - Custom function examples follow the correct API pattern\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
+export declare const exampleIdBasedRefYaml = "- mode: literacy\n  id: example-id-based-ref\n  title: GROQ feature support (ID-based doc references)\n  description: Example \u2014 demonstrates ID-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - id: 0ba88f1b-d1a7-418a-9267-2e343d01886a\n        slug: groq-feature-support-by-context\n        reason: GROQ feature support across different Sanity contexts\n      - id: 5b9c2863-ef01-4565-af8e-ee54e081ee74\n        slug: custom-groq-functions\n        reason: Custom GROQ functions and pipelines\n  docCoverage: true\n  prompt:\n    text: |-\n      Explain how GROQ is used across different Sanity contexts.\n      Cover the following:\n      1. Which GROQ features are available in each context (API queries,\n         webhooks, custom functions, access control)\n      2. How to create and use custom GROQ functions\n      3. Any differences in GROQ support between contexts\n      Provide examples demonstrating context-specific GROQ patterns.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: groq-availability\n          text: Explains GROQ availability across different Sanity contexts\n        - id: custom-groq-functions\n          text: Describes custom GROQ function creation and usage\n        - id: groq-context-differences\n          text: Notes differences in GROQ support between contexts\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - id: valid-groq-syntax\n          text: GROQ examples use valid syntax\n        - id: correct-function-api\n          text: Custom function examples follow the correct API pattern\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
 /** Parsed task data for example-knowledge-probe (JSON-safe) */
 export declare const exampleKnowledgeProbeData: readonly [{
     readonly mode: "knowledge-probe";
@@ -255,14 +285,23 @@ export declare const exampleKnowledgeProbeData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Demonstrates understanding of GROQ query syntax", "Shows filtering and projection patterns", "Code examples use valid GROQ syntax"];
+        readonly criteria: readonly [{
+            readonly id: "understands-groq-syntax";
+            readonly text: "Demonstrates understanding of GROQ query syntax";
+        }, {
+            readonly id: "filter-projection-patterns";
+            readonly text: "Shows filtering and projection patterns";
+        }, {
+            readonly id: "valid-groq-examples";
+            readonly text: "Code examples use valid GROQ syntax";
+        }];
     }];
     readonly status: "draft";
 }];
 /** TypeScript task template for example-knowledge-probe */
-export declare const exampleKnowledgeProbeTs = "/**\n * Example Task: Knowledge probe baseline (DRAFT).\n *\n * Tests what the model knows about a topic without providing documentation.\n * Used to establish a baseline for comparison with literacy evaluations.\n * This task is a DRAFT \u2014 it won't run unless activated or explicitly targeted.\n *\n * To activate: change status to \"active\" or remove the status field.\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"knowledge-probe\",\n  id: \"example-knowledge-probe\",\n  title: \"Model knowledge of GROQ syntax\",\n  description: \"Example \u2014 probes baseline model knowledge (draft)\",\n  area: \"groq\",\n\n  prompt: {\n    text: `Explain the GROQ query language used by Sanity. Cover:\n1. Basic query syntax and projections\n2. How to filter and sort results\n3. Common patterns for fetching related documents\nProvide working code examples.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Demonstrates understanding of GROQ query syntax\",\n        \"Shows filtering and projection patterns\",\n        \"Code examples use valid GROQ syntax\",\n      ],\n    },\n  ],\n\n  status: \"draft\",\n})\n";
+export declare const exampleKnowledgeProbeTs = "/**\n * Example Task: Knowledge probe baseline (DRAFT).\n *\n * Tests what the model knows about a topic without providing documentation.\n * Used to establish a baseline for comparison with literacy evaluations.\n * This task is a DRAFT \u2014 it won't run unless activated or explicitly targeted.\n *\n * To activate: change status to \"active\" or remove the status field.\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"knowledge-probe\",\n  id: \"example-knowledge-probe\",\n  title: \"Model knowledge of GROQ syntax\",\n  description: \"Example \u2014 probes baseline model knowledge (draft)\",\n  area: \"groq\",\n\n  prompt: {\n    text: `Explain the GROQ query language used by Sanity. Cover:\n1. Basic query syntax and projections\n2. How to filter and sort results\n3. Common patterns for fetching related documents\nProvide working code examples.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"understands-groq-syntax\",\n          text: \"Demonstrates understanding of GROQ query syntax\",\n        },\n        {\n          id: \"filter-projection-patterns\",\n          text: \"Shows filtering and projection patterns\",\n        },\n        {\n          id: \"valid-groq-examples\",\n          text: \"Code examples use valid GROQ syntax\",\n        },\n      ],\n    },\n  ],\n\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-knowledge-probe (from parsed TS data) */
-export declare const exampleKnowledgeProbeYaml = "- mode: knowledge-probe\n  id: example-knowledge-probe\n  title: Model knowledge of GROQ syntax\n  description: Example \u2014 probes baseline model knowledge (draft)\n  area: groq\n  prompt:\n    text: |-\n      Explain the GROQ query language used by Sanity. Cover:\n      1. Basic query syntax and projections\n      2. How to filter and sort results\n      3. Common patterns for fetching related documents\n      Provide working code examples.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Demonstrates understanding of GROQ query syntax\n        - Shows filtering and projection patterns\n        - Code examples use valid GROQ syntax\n  status: draft\n";
+export declare const exampleKnowledgeProbeYaml = "- mode: knowledge-probe\n  id: example-knowledge-probe\n  title: Model knowledge of GROQ syntax\n  description: Example \u2014 probes baseline model knowledge (draft)\n  area: groq\n  prompt:\n    text: |-\n      Explain the GROQ query language used by Sanity. Cover:\n      1. Basic query syntax and projections\n      2. How to filter and sort results\n      3. Common patterns for fetching related documents\n      Provide working code examples.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: understands-groq-syntax\n          text: Demonstrates understanding of GROQ query syntax\n        - id: filter-projection-patterns\n          text: Shows filtering and projection patterns\n        - id: valid-groq-examples\n          text: Code examples use valid GROQ syntax\n  status: draft\n";
 /** Parsed task data for example-mcp-tool-usage (JSON-safe) */
 export declare const exampleMcpToolUsageData: readonly [{
     readonly mode: "mcp-server";
@@ -283,14 +322,23 @@ export declare const exampleMcpToolUsageData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "mcp-output-correctness";
-        readonly criteria: readonly ["Correctly discovers and selects the appropriate tool", "Passes valid arguments to the tool", "Interprets the tool response coherently"];
+        readonly criteria: readonly [{
+            readonly id: "discovers-correct-tool";
+            readonly text: "Correctly discovers and selects the appropriate tool";
+        }, {
+            readonly id: "passes-valid-arguments";
+            readonly text: "Passes valid arguments to the tool";
+        }, {
+            readonly id: "interprets-response";
+            readonly text: "Interprets the tool response coherently";
+        }];
     }];
     readonly status: "draft";
 }];
 /** TypeScript task template for example-mcp-tool-usage */
-export declare const exampleMcpToolUsageTs = "/**\n * Example Task: MCP Server tool-use evaluation (DRAFT).\n *\n * Tests whether an LLM can correctly discover and invoke tools from\n * an MCP server. Replace the placeholder serverConfig with your own\n * MCP server's URL and authentication details.\n *\n * Transports:\n *   - \"streamable-http\" / \"sse\" \u2014 remote servers (set url + optional headers)\n *   - \"stdio\" \u2014 local process (set command instead of url)\n *\n * Authentication:\n *   - `headers` \u2014 send arbitrary HTTP headers (e.g., Authorization)\n *   - `auth`    \u2014 structured auth config (bearer, basic, api_key, oauth)\n *   Values support {{env.VAR}} syntax so secrets stay out of source control.\n *\n * This task is a DRAFT \u2014 it won't run unless activated or explicitly targeted.\n * To activate: change status to \"active\" or remove the status field.\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"mcp-server\",\n  id: \"example-mcp-tool-usage\",\n  title: \"MCP tool discovery and invocation\",\n  description: \"Example \u2014 tests MCP server tool-use (draft)\",\n  area: \"mcp\",\n\n  // \u2500\u2500 Server configuration \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Replace the URL and headers below with your MCP server's details.\n  //\n  // For a local stdio server, use:\n  //   transport: \"stdio\",\n  //   command: \"node dist/my-mcp-server.js\",\n  serverConfig: {\n    transport: \"streamable-http\",\n    url: \"https://your-mcp-server.example.com\",\n    headers: {\n      Authorization: \"Bearer {{env.MCP_AUTH_TOKEN}}\",\n    },\n  },\n\n  // \u2500\u2500 Capabilities \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Restrict which MCP tools the model can call. If omitted, all\n  // tools discovered from the server are available.\n  // capabilities: [\"tool_a\", \"tool_b\"],\n\n  prompt: {\n    text: `Use the available MCP tools to complete the task.\nReplace this prompt with instructions specific to your MCP server.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"mcp-output-correctness\",\n      criteria: [\n        \"Correctly discovers and selects the appropriate tool\",\n        \"Passes valid arguments to the tool\",\n        \"Interprets the tool response coherently\",\n      ],\n    },\n  ],\n\n  status: \"draft\",\n})\n";
+export declare const exampleMcpToolUsageTs = "/**\n * Example Task: MCP Server tool-use evaluation (DRAFT).\n *\n * Tests whether an LLM can correctly discover and invoke tools from\n * an MCP server. Replace the placeholder serverConfig with your own\n * MCP server's URL and authentication details.\n *\n * Transports:\n *   - \"streamable-http\" / \"sse\" \u2014 remote servers (set url + optional headers)\n *   - \"stdio\" \u2014 local process (set command instead of url)\n *\n * Authentication:\n *   - `headers` \u2014 send arbitrary HTTP headers (e.g., Authorization)\n *   - `auth`    \u2014 structured auth config (bearer, basic, api_key, oauth)\n *   Values support {{env.VAR}} syntax so secrets stay out of source control.\n *\n * This task is a DRAFT \u2014 it won't run unless activated or explicitly targeted.\n * To activate: change status to \"active\" or remove the status field.\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"mcp-server\",\n  id: \"example-mcp-tool-usage\",\n  title: \"MCP tool discovery and invocation\",\n  description: \"Example \u2014 tests MCP server tool-use (draft)\",\n  area: \"mcp\",\n\n  // \u2500\u2500 Server configuration \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Replace the URL and headers below with your MCP server's details.\n  //\n  // For a local stdio server, use:\n  //   transport: \"stdio\",\n  //   command: \"node dist/my-mcp-server.js\",\n  serverConfig: {\n    transport: \"streamable-http\",\n    url: \"https://your-mcp-server.example.com\",\n    headers: {\n      Authorization: \"Bearer {{env.MCP_AUTH_TOKEN}}\",\n    },\n  },\n\n  // \u2500\u2500 Capabilities \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n  // Restrict which MCP tools the model can call. If omitted, all\n  // tools discovered from the server are available.\n  // capabilities: [\"tool_a\", \"tool_b\"],\n\n  prompt: {\n    text: `Use the available MCP tools to complete the task.\nReplace this prompt with instructions specific to your MCP server.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"mcp-output-correctness\",\n      criteria: [\n        {\n          id: \"discovers-correct-tool\",\n          text: \"Correctly discovers and selects the appropriate tool\",\n        },\n        {\n          id: \"passes-valid-arguments\",\n          text: \"Passes valid arguments to the tool\",\n        },\n        {\n          id: \"interprets-response\",\n          text: \"Interprets the tool response coherently\",\n        },\n      ],\n    },\n  ],\n\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-mcp-tool-usage (from parsed TS data) */
-export declare const exampleMcpToolUsageYaml = "- mode: mcp-server\n  id: example-mcp-tool-usage\n  title: MCP tool discovery and invocation\n  description: Example \u2014 tests MCP server tool-use (draft)\n  area: mcp\n  serverConfig:\n    transport: streamable-http\n    url: https://your-mcp-server.example.com\n    headers:\n      Authorization: Bearer {{env.MCP_AUTH_TOKEN}}\n  prompt:\n    text: |-\n      Use the available MCP tools to complete the task.\n      Replace this prompt with instructions specific to your MCP server.\n  assertions:\n    - type: llm-rubric\n      template: mcp-output-correctness\n      criteria:\n        - Correctly discovers and selects the appropriate tool\n        - Passes valid arguments to the tool\n        - Interprets the tool response coherently\n  status: draft\n";
+export declare const exampleMcpToolUsageYaml = "- mode: mcp-server\n  id: example-mcp-tool-usage\n  title: MCP tool discovery and invocation\n  description: Example \u2014 tests MCP server tool-use (draft)\n  area: mcp\n  serverConfig:\n    transport: streamable-http\n    url: https://your-mcp-server.example.com\n    headers:\n      Authorization: Bearer {{env.MCP_AUTH_TOKEN}}\n  prompt:\n    text: |-\n      Use the available MCP tools to complete the task.\n      Replace this prompt with instructions specific to your MCP server.\n  assertions:\n    - type: llm-rubric\n      template: mcp-output-correctness\n      criteria:\n        - id: discovers-correct-tool\n          text: Correctly discovers and selects the appropriate tool\n        - id: passes-valid-arguments\n          text: Passes valid arguments to the tool\n        - id: interprets-response\n          text: Interprets the tool response coherently\n  status: draft\n";
 /** Parsed task data for example-path-based-ref (JSON-safe) */
 export declare const examplePathBasedRefData: readonly [{
     readonly mode: "literacy";
@@ -314,11 +362,29 @@ export declare const examplePathBasedRefData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Explains create, createOrReplace, patch, and delete mutations", "Describes required document fields (_id, _type)", "Shows patch operations for field-level updates", "Includes practical code examples"];
+        readonly criteria: readonly [{
+            readonly id: "explains-mutations";
+            readonly text: "Explains create, createOrReplace, patch, and delete mutations";
+        }, {
+            readonly id: "required-document-fields";
+            readonly text: "Describes required document fields (_id, _type)";
+        }, {
+            readonly id: "patch-operations";
+            readonly text: "Shows patch operations for field-level updates";
+        }, {
+            readonly id: "practical-code-examples";
+            readonly text: "Includes practical code examples";
+        }];
     }, {
         readonly type: "llm-rubric";
         readonly template: "code-correctness";
-        readonly criteria: readonly ["Uses correct @sanity/client mutation API", "Patch operations use valid set/unset/inc syntax"];
+        readonly criteria: readonly [{
+            readonly id: "correct-mutation-api";
+            readonly text: "Uses correct @sanity/client mutation API";
+        }, {
+            readonly id: "valid-patch-syntax";
+            readonly text: "Patch operations use valid set/unset/inc syntax";
+        }];
     }];
     readonly baseline: {
         readonly enabled: true;
@@ -327,9 +393,9 @@ export declare const examplePathBasedRefData: readonly [{
     readonly status: "draft";
 }];
 /** TypeScript task template for example-path-based-ref */
-export declare const examplePathBasedRefTs = "/**\n * Example Task: Path-based canonical doc references.\n *\n * Demonstrates using `path` to reference canonical documentation.\n * Paths are the preferred reference type because they uniquely identify\n * an article across sections (unlike slugs, which can collide).\n *\n * Path format:\n *   - Simple:    \"webhooks\"                \u2192 resolves by slug lookup\n *   - Sectioned: \"content-lake/webhooks\"   \u2192 disambiguates by section + slug\n *\n * This example demonstrates why paths matter: the slug \"documents\"\n * exists in both the \"content-lake\" and \"cli-reference\" sections.\n * Using \"content-lake/documents\" ensures we get the right one.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-path-based-ref\",\n  title: \"GROQ mutations (path-based doc references)\",\n  description: \"Example \u2014 demonstrates path-based canonical doc references\",\n\n  area: \"groq\",\n\n  // Path-based canonical doc references.\n  //\n  // Use \"section/slug\" format to uniquely identify articles:\n  //   - \"content-lake/mutations-introduction\" \u2192 the mutations article\n  //   - \"content-lake/documents\" \u2192 the documents article in Content Lake\n  //     (not the CLI \"documents\" article in cli-reference section)\n  //\n  // The \"documents\" slug exists in two sections \u2014 this is exactly why\n  // path-based references are preferred over slug-based references.\n  context: {\n    docs: [\n      {\n        path: \"content-lake/mutations-introduction\",\n        reason: \"Introduction to document mutations in the Content Lake\",\n      },\n      {\n        path: \"content-lake/documents\",\n        reason:\n          \"Document structure and types (Content Lake, not CLI reference)\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Explain how to create, update, and delete documents in Sanity's\nContent Lake using mutations. Cover:\n1. The different mutation types (create, createOrReplace, patch, delete)\n2. Document structure and required fields (_id, _type)\n3. How to use patch operations to update specific fields\n4. Best practices for mutation patterns\nProvide working code examples using @sanity/client.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Explains create, createOrReplace, patch, and delete mutations\",\n        \"Describes required document fields (_id, _type)\",\n        \"Shows patch operations for field-level updates\",\n        \"Includes practical code examples\",\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        \"Uses correct @sanity/client mutation API\",\n        \"Patch operations use valid set/unset/inc syntax\",\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
+export declare const examplePathBasedRefTs = "/**\n * Example Task: Path-based canonical doc references.\n *\n * Demonstrates using `path` to reference canonical documentation.\n * Paths are the preferred reference type because they uniquely identify\n * an article across sections (unlike slugs, which can collide).\n *\n * Path format:\n *   - Simple:    \"webhooks\"                \u2192 resolves by slug lookup\n *   - Sectioned: \"content-lake/webhooks\"   \u2192 disambiguates by section + slug\n *\n * This example demonstrates why paths matter: the slug \"documents\"\n * exists in both the \"content-lake\" and \"cli-reference\" sections.\n * Using \"content-lake/documents\" ensures we get the right one.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-path-based-ref\",\n  title: \"GROQ mutations (path-based doc references)\",\n  description: \"Example \u2014 demonstrates path-based canonical doc references\",\n\n  area: \"groq\",\n\n  // Path-based canonical doc references.\n  //\n  // Use \"section/slug\" format to uniquely identify articles:\n  //   - \"content-lake/mutations-introduction\" \u2192 the mutations article\n  //   - \"content-lake/documents\" \u2192 the documents article in Content Lake\n  //     (not the CLI \"documents\" article in cli-reference section)\n  //\n  // The \"documents\" slug exists in two sections \u2014 this is exactly why\n  // path-based references are preferred over slug-based references.\n  context: {\n    docs: [\n      {\n        path: \"content-lake/mutations-introduction\",\n        reason: \"Introduction to document mutations in the Content Lake\",\n      },\n      {\n        path: \"content-lake/documents\",\n        reason:\n          \"Document structure and types (Content Lake, not CLI reference)\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Explain how to create, update, and delete documents in Sanity's\nContent Lake using mutations. Cover:\n1. The different mutation types (create, createOrReplace, patch, delete)\n2. Document structure and required fields (_id, _type)\n3. How to use patch operations to update specific fields\n4. Best practices for mutation patterns\nProvide working code examples using @sanity/client.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"explains-mutations\",\n          text: \"Explains create, createOrReplace, patch, and delete mutations\",\n        },\n        {\n          id: \"required-document-fields\",\n          text: \"Describes required document fields (_id, _type)\",\n        },\n        {\n          id: \"patch-operations\",\n          text: \"Shows patch operations for field-level updates\",\n        },\n        {\n          id: \"practical-code-examples\",\n          text: \"Includes practical code examples\",\n        },\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        {\n          id: \"correct-mutation-api\",\n          text: \"Uses correct @sanity/client mutation API\",\n        },\n        {\n          id: \"valid-patch-syntax\",\n          text: \"Patch operations use valid set/unset/inc syntax\",\n        },\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-path-based-ref (from parsed TS data) */
-export declare const examplePathBasedRefYaml = "- mode: literacy\n  id: example-path-based-ref\n  title: GROQ mutations (path-based doc references)\n  description: Example \u2014 demonstrates path-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - path: content-lake/mutations-introduction\n        reason: Introduction to document mutations in the Content Lake\n      - path: content-lake/documents\n        reason: Document structure and types (Content Lake, not CLI reference)\n  docCoverage: true\n  prompt:\n    text: |-\n      Explain how to create, update, and delete documents in Sanity's\n      Content Lake using mutations. Cover:\n      1. The different mutation types (create, createOrReplace, patch, delete)\n      2. Document structure and required fields (_id, _type)\n      3. How to use patch operations to update specific fields\n      4. Best practices for mutation patterns\n      Provide working code examples using @sanity/client.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Explains create, createOrReplace, patch, and delete mutations\n        - Describes required document fields (_id, _type)\n        - Shows patch operations for field-level updates\n        - Includes practical code examples\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - Uses correct @sanity/client mutation API\n        - Patch operations use valid set/unset/inc syntax\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
+export declare const examplePathBasedRefYaml = "- mode: literacy\n  id: example-path-based-ref\n  title: GROQ mutations (path-based doc references)\n  description: Example \u2014 demonstrates path-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - path: content-lake/mutations-introduction\n        reason: Introduction to document mutations in the Content Lake\n      - path: content-lake/documents\n        reason: Document structure and types (Content Lake, not CLI reference)\n  docCoverage: true\n  prompt:\n    text: |-\n      Explain how to create, update, and delete documents in Sanity's\n      Content Lake using mutations. Cover:\n      1. The different mutation types (create, createOrReplace, patch, delete)\n      2. Document structure and required fields (_id, _type)\n      3. How to use patch operations to update specific fields\n      4. Best practices for mutation patterns\n      Provide working code examples using @sanity/client.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: explains-mutations\n          text: Explains create, createOrReplace, patch, and delete mutations\n        - id: required-document-fields\n          text: Describes required document fields (_id, _type)\n        - id: patch-operations\n          text: Shows patch operations for field-level updates\n        - id: practical-code-examples\n          text: Includes practical code examples\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - id: correct-mutation-api\n          text: Uses correct @sanity/client mutation API\n        - id: valid-patch-syntax\n          text: Patch operations use valid set/unset/inc syntax\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
 /** Parsed task data for example-perspective-ref (JSON-safe) */
 export declare const examplePerspectiveRefData: readonly [{
     readonly mode: "literacy";
@@ -353,11 +419,26 @@ export declare const examplePerspectiveRefData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Demonstrates GROQ join syntax for cross-document queries", "Shows GROQ filter patterns for webhook configuration", "Includes practical query examples from cheat sheet patterns"];
+        readonly criteria: readonly [{
+            readonly id: "groq-join-syntax";
+            readonly text: "Demonstrates GROQ join syntax for cross-document queries";
+        }, {
+            readonly id: "groq-filter-patterns";
+            readonly text: "Shows GROQ filter patterns for webhook configuration";
+        }, {
+            readonly id: "practical-query-examples";
+            readonly text: "Includes practical query examples from cheat sheet patterns";
+        }];
     }, {
         readonly type: "llm-rubric";
         readonly template: "code-correctness";
-        readonly criteria: readonly ["All GROQ queries use valid syntax", "Reference joins use correct dereference operator (->)"];
+        readonly criteria: readonly [{
+            readonly id: "valid-groq-syntax";
+            readonly text: "All GROQ queries use valid syntax";
+        }, {
+            readonly id: "correct-dereference-operator";
+            readonly text: "Reference joins use correct dereference operator (->)";
+        }];
     }];
     readonly baseline: {
         readonly enabled: true;
@@ -366,9 +447,9 @@ export declare const examplePerspectiveRefData: readonly [{
     readonly status: "draft";
 }];
 /** TypeScript task template for example-perspective-ref */
-export declare const examplePerspectiveRefTs = "/**\n * Example Task: Perspective / content release doc references.\n *\n * Demonstrates using `perspective` to reference all documentation\n * articles within a content release. This is the key capability for\n * evaluating NEW feature documentation before it's published.\n *\n * How it works:\n *   - A perspective ref is one-to-many: the doc fetcher queries the\n *     named release and expands it to ALL articles versioned within it.\n *   - Downstream consumers see the same flat DocContext[] regardless\n *     of how docs were resolved.\n *   - When the release is published, the perspective entry becomes a\n *     no-op (articles are now in published). Migrate to explicit path\n *     or slug refs at your convenience.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-perspective-ref\",\n  title:\n    \"GROQ features from content release (perspective-based doc references)\",\n  description:\n    \"Example \u2014 demonstrates perspective-based canonical doc references\",\n\n  area: \"groq\",\n\n  // Perspective-based canonical doc reference.\n  //\n  // The perspective ID references a content release in the Sanity\n  // Content Lake. At evaluation time, the doc fetcher auto-discovers\n  // all articles versioned in this release and includes them as\n  // canonical documentation context.\n  //\n  // Release rE9TSJvR4 contains:\n  //   - \"GROQ-powered webhooks\" (webhooks)\n  //   - \"Query Cheat Sheet - GROQ\" (query-cheat-sheet)\n  //   - \"GROQ joins\" (groq-joins)\n  //\n  // You can combine perspective refs with explicit slug/path/id refs\n  // to include foundational published docs alongside release content.\n  // Here we add groq-data-types as a complementary published reference.\n  context: {\n    docs: [\n      {\n        perspective: \"rE9TSJvR4\",\n        reason: \"All GROQ documentation updates in the test content release\",\n      },\n      {\n        slug: \"groq-data-types\",\n        reason: \"GROQ data type reference (published, stable)\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Using GROQ, demonstrate advanced query patterns including:\n1. Joining data across document types using references\n2. Filtering webhook payloads with GROQ projections\n3. Using the query cheat sheet patterns for common operations\n4. Working with different GROQ data types in filters\nProvide working GROQ query examples for each pattern.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Demonstrates GROQ join syntax for cross-document queries\",\n        \"Shows GROQ filter patterns for webhook configuration\",\n        \"Includes practical query examples from cheat sheet patterns\",\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        \"All GROQ queries use valid syntax\",\n        \"Reference joins use correct dereference operator (->)\",\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
+export declare const examplePerspectiveRefTs = "/**\n * Example Task: Perspective / content release doc references.\n *\n * Demonstrates using `perspective` to reference all documentation\n * articles within a content release. This is the key capability for\n * evaluating NEW feature documentation before it's published.\n *\n * How it works:\n *   - A perspective ref is one-to-many: the doc fetcher queries the\n *     named release and expands it to ALL articles versioned within it.\n *   - Downstream consumers see the same flat DocContext[] regardless\n *     of how docs were resolved.\n *   - When the release is published, the perspective entry becomes a\n *     no-op (articles are now in published). Migrate to explicit path\n *     or slug refs at your convenience.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n *\n * @see docs/design-docs/canonical-doc-resolution.md\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-perspective-ref\",\n  title:\n    \"GROQ features from content release (perspective-based doc references)\",\n  description:\n    \"Example \u2014 demonstrates perspective-based canonical doc references\",\n\n  area: \"groq\",\n\n  // Perspective-based canonical doc reference.\n  //\n  // The perspective ID references a content release in the Sanity\n  // Content Lake. At evaluation time, the doc fetcher auto-discovers\n  // all articles versioned in this release and includes them as\n  // canonical documentation context.\n  //\n  // Release rE9TSJvR4 contains:\n  //   - \"GROQ-powered webhooks\" (webhooks)\n  //   - \"Query Cheat Sheet - GROQ\" (query-cheat-sheet)\n  //   - \"GROQ joins\" (groq-joins)\n  //\n  // You can combine perspective refs with explicit slug/path/id refs\n  // to include foundational published docs alongside release content.\n  // Here we add groq-data-types as a complementary published reference.\n  context: {\n    docs: [\n      {\n        perspective: \"rE9TSJvR4\",\n        reason: \"All GROQ documentation updates in the test content release\",\n      },\n      {\n        slug: \"groq-data-types\",\n        reason: \"GROQ data type reference (published, stable)\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n\n  prompt: {\n    text: `Using GROQ, demonstrate advanced query patterns including:\n1. Joining data across document types using references\n2. Filtering webhook payloads with GROQ projections\n3. Using the query cheat sheet patterns for common operations\n4. Working with different GROQ data types in filters\nProvide working GROQ query examples for each pattern.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"groq-join-syntax\",\n          text: \"Demonstrates GROQ join syntax for cross-document queries\",\n        },\n        {\n          id: \"groq-filter-patterns\",\n          text: \"Shows GROQ filter patterns for webhook configuration\",\n        },\n        {\n          id: \"practical-query-examples\",\n          text: \"Includes practical query examples from cheat sheet patterns\",\n        },\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        { id: \"valid-groq-syntax\", text: \"All GROQ queries use valid syntax\" },\n        {\n          id: \"correct-dereference-operator\",\n          text: \"Reference joins use correct dereference operator (->)\",\n        },\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-perspective-ref (from parsed TS data) */
-export declare const examplePerspectiveRefYaml = "- mode: literacy\n  id: example-perspective-ref\n  title: GROQ features from content release (perspective-based doc references)\n  description: Example \u2014 demonstrates perspective-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - perspective: rE9TSJvR4\n        reason: All GROQ documentation updates in the test content release\n      - slug: groq-data-types\n        reason: GROQ data type reference (published, stable)\n  docCoverage: true\n  prompt:\n    text: |-\n      Using GROQ, demonstrate advanced query patterns including:\n      1. Joining data across document types using references\n      2. Filtering webhook payloads with GROQ projections\n      3. Using the query cheat sheet patterns for common operations\n      4. Working with different GROQ data types in filters\n      Provide working GROQ query examples for each pattern.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Demonstrates GROQ join syntax for cross-document queries\n        - Shows GROQ filter patterns for webhook configuration\n        - Includes practical query examples from cheat sheet patterns\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - All GROQ queries use valid syntax\n        - Reference joins use correct dereference operator (->)\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
+export declare const examplePerspectiveRefYaml = "- mode: literacy\n  id: example-perspective-ref\n  title: GROQ features from content release (perspective-based doc references)\n  description: Example \u2014 demonstrates perspective-based canonical doc references\n  area: groq\n  context:\n    docs:\n      - perspective: rE9TSJvR4\n        reason: All GROQ documentation updates in the test content release\n      - slug: groq-data-types\n        reason: GROQ data type reference (published, stable)\n  docCoverage: true\n  prompt:\n    text: |-\n      Using GROQ, demonstrate advanced query patterns including:\n      1. Joining data across document types using references\n      2. Filtering webhook payloads with GROQ projections\n      3. Using the query cheat sheet patterns for common operations\n      4. Working with different GROQ data types in filters\n      Provide working GROQ query examples for each pattern.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: groq-join-syntax\n          text: Demonstrates GROQ join syntax for cross-document queries\n        - id: groq-filter-patterns\n          text: Shows GROQ filter patterns for webhook configuration\n        - id: practical-query-examples\n          text: Includes practical query examples from cheat sheet patterns\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - id: valid-groq-syntax\n          text: All GROQ queries use valid syntax\n        - id: correct-dereference-operator\n          text: Reference joins use correct dereference operator (->)\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
 /** Parsed task data for example-studio-custom-input (JSON-safe) */
 export declare const exampleStudioCustomInputData: readonly [{
     readonly mode: "literacy";
@@ -393,11 +474,29 @@ export declare const exampleStudioCustomInputData: readonly [{
     readonly assertions: readonly [{
         readonly type: "llm-rubric";
         readonly template: "task-completion";
-        readonly criteria: readonly ["Implements a React component that renders a text input", "Displays a live character count", "Reads maxLength from schema options", "Shows a visual warning when limit is exceeded"];
+        readonly criteria: readonly [{
+            readonly id: "renders-text-input";
+            readonly text: "Implements a React component that renders a text input";
+        }, {
+            readonly id: "displays-character-count";
+            readonly text: "Displays a live character count";
+        }, {
+            readonly id: "reads-max-length";
+            readonly text: "Reads maxLength from schema options";
+        }, {
+            readonly id: "shows-visual-warning";
+            readonly text: "Shows a visual warning when limit is exceeded";
+        }];
     }, {
         readonly type: "llm-rubric";
         readonly template: "code-correctness";
-        readonly criteria: readonly ["Uses the Sanity UI library for styling", "Calls onChange with patch operations"];
+        readonly criteria: readonly [{
+            readonly id: "uses-sanity-ui";
+            readonly text: "Uses the Sanity UI library for styling";
+        }, {
+            readonly id: "calls-onchange-patches";
+            readonly text: "Calls onChange with patch operations";
+        }];
     }];
     readonly baseline: {
         readonly enabled: true;
@@ -406,9 +505,9 @@ export declare const exampleStudioCustomInputData: readonly [{
     readonly status: "draft";
 }];
 /** TypeScript task template for example-studio-custom-input */
-export declare const exampleStudioCustomInputTs = "/**\n * Example Task: Custom input component in Sanity Studio.\n *\n * This is a starter template \u2014 edit it for your own documentation.\n * Delete this file or replace it with your own tasks.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-studio-custom-input\",\n  title: \"Custom input component in Sanity Studio\",\n  description: \"Example \u2014 tests Studio custom input implementation\",\n\n  area: \"studio\",\n\n  context: {\n    docs: [\n      {\n        slug: \"custom-input-widgets\",\n        reason: \"Guide for building custom form inputs in Sanity Studio\",\n      },\n      {\n        slug: \"form-components\",\n        reason: \"Form component API and customization patterns\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n  referenceSolution: \"canonical/example-studio-custom-input.ts\",\n\n  prompt: {\n    text: `Build a custom string input component for Sanity Studio that shows\na character count below the input field. The component should accept\na maxLength option from the field schema and display a warning when\nthe text exceeds the limit.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        \"Implements a React component that renders a text input\",\n        \"Displays a live character count\",\n        \"Reads maxLength from schema options\",\n        \"Shows a visual warning when limit is exceeded\",\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        \"Uses the Sanity UI library for styling\",\n        \"Calls onChange with patch operations\",\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
+export declare const exampleStudioCustomInputTs = "/**\n * Example Task: Custom input component in Sanity Studio.\n *\n * This is a starter template \u2014 edit it for your own documentation.\n * Delete this file or replace it with your own tasks.\n *\n * This example task ships as a DRAFT so it does not run in production\n * evaluations automatically. To activate it, change status to \"active\"\n * or remove the status field entirely (defaults to active).\n */\n\nimport { defineTask } from \"@sanity/ailf\"\n\nexport default defineTask({\n  mode: \"literacy\",\n  id: \"example-studio-custom-input\",\n  title: \"Custom input component in Sanity Studio\",\n  description: \"Example \u2014 tests Studio custom input implementation\",\n\n  area: \"studio\",\n\n  context: {\n    docs: [\n      {\n        slug: \"custom-input-widgets\",\n        reason: \"Guide for building custom form inputs in Sanity Studio\",\n      },\n      {\n        slug: \"form-components\",\n        reason: \"Form component API and customization patterns\",\n      },\n    ],\n  },\n\n  docCoverage: true,\n  referenceSolution: \"canonical/example-studio-custom-input.ts\",\n\n  prompt: {\n    text: `Build a custom string input component for Sanity Studio that shows\na character count below the input field. The component should accept\na maxLength option from the field schema and display a warning when\nthe text exceeds the limit.`,\n  },\n\n  assertions: [\n    {\n      type: \"llm-rubric\",\n      template: \"task-completion\",\n      criteria: [\n        {\n          id: \"renders-text-input\",\n          text: \"Implements a React component that renders a text input\",\n        },\n        {\n          id: \"displays-character-count\",\n          text: \"Displays a live character count\",\n        },\n        { id: \"reads-max-length\", text: \"Reads maxLength from schema options\" },\n        {\n          id: \"shows-visual-warning\",\n          text: \"Shows a visual warning when limit is exceeded\",\n        },\n      ],\n    },\n    {\n      type: \"llm-rubric\",\n      template: \"code-correctness\",\n      criteria: [\n        {\n          id: \"uses-sanity-ui\",\n          text: \"Uses the Sanity UI library for styling\",\n        },\n        {\n          id: \"calls-onchange-patches\",\n          text: \"Calls onChange with patch operations\",\n        },\n      ],\n    },\n  ],\n\n  baseline: { enabled: true, rubric: \"full\" },\n  status: \"draft\",\n})\n";
 /** Generated YAML for example-studio-custom-input (from parsed TS data) */
-export declare const exampleStudioCustomInputYaml = "- mode: literacy\n  id: example-studio-custom-input\n  title: Custom input component in Sanity Studio\n  description: Example \u2014 tests Studio custom input implementation\n  area: studio\n  context:\n    docs:\n      - slug: custom-input-widgets\n        reason: Guide for building custom form inputs in Sanity Studio\n      - slug: form-components\n        reason: Form component API and customization patterns\n  docCoverage: true\n  referenceSolution: canonical/example-studio-custom-input.ts\n  prompt:\n    text: |-\n      Build a custom string input component for Sanity Studio that shows\n      a character count below the input field. The component should accept\n      a maxLength option from the field schema and display a warning when\n      the text exceeds the limit.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - Implements a React component that renders a text input\n        - Displays a live character count\n        - Reads maxLength from schema options\n        - Shows a visual warning when limit is exceeded\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - Uses the Sanity UI library for styling\n        - Calls onChange with patch operations\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
+export declare const exampleStudioCustomInputYaml = "- mode: literacy\n  id: example-studio-custom-input\n  title: Custom input component in Sanity Studio\n  description: Example \u2014 tests Studio custom input implementation\n  area: studio\n  context:\n    docs:\n      - slug: custom-input-widgets\n        reason: Guide for building custom form inputs in Sanity Studio\n      - slug: form-components\n        reason: Form component API and customization patterns\n  docCoverage: true\n  referenceSolution: canonical/example-studio-custom-input.ts\n  prompt:\n    text: |-\n      Build a custom string input component for Sanity Studio that shows\n      a character count below the input field. The component should accept\n      a maxLength option from the field schema and display a warning when\n      the text exceeds the limit.\n  assertions:\n    - type: llm-rubric\n      template: task-completion\n      criteria:\n        - id: renders-text-input\n          text: Implements a React component that renders a text input\n        - id: displays-character-count\n          text: Displays a live character count\n        - id: reads-max-length\n          text: Reads maxLength from schema options\n        - id: shows-visual-warning\n          text: Shows a visual warning when limit is exceeded\n    - type: llm-rubric\n      template: code-correctness\n      criteria:\n        - id: uses-sanity-ui\n          text: Uses the Sanity UI library for styling\n        - id: calls-onchange-patches\n          text: Calls onChange with patch operations\n  baseline:\n    enabled: true\n    rubric: full\n  status: draft\n";
 /** All task example data as a flat array (JSON-safe) */
 export declare const allTaskData: readonly unknown[];
 /** Map of task ID (filename stem) → raw TypeScript source */