@case-framework/survey-assistant 0.1.0

package/dist/references/localization.md

@@ -0,0 +1,25 @@
+# Survey Localization
+
+Use this reference when the user asks to translate, localize, add a language, or make all/some survey content available in another language.
+
+## Locale Lifecycle
+
+- A target locale may be absent. That is a normal starting state, not an error and not a reason to inspect a nonexistent translation branch.
+- Use the target locale code directly in typed translation operations. The first applied translation creates the locale branch while preserving every existing locale.
+- Never create a temporary item, placeholder text, blank title, or dummy translation merely to introduce a locale. Introduce it only through the real respondent-visible translations requested by the user.
+- Never put target-language respondent text into an existing source-language locale just because that locale already exists.
+- Coding keys and editor-only item labels are not respondent translations. Translate them only when the user explicitly asks.
+
+## Scope A Complete Localization Correctly
+
+1. Inspect the complete outline. Page it when needed; do not assume a compact outline is the entire survey.
+2. Inspect each relevant item type/configuration to discover every respondent-visible content key. This includes question titles/subtitles/info copy, choice-option labels, form-field labels, select-option labels, embedded-form labels, validation copy, and respondent-facing navigation/card copy when present.
+3. Preserve the source language while writing each target-language value under the target locale. Do not replace source content or translation containers.
+4. Use `update-item-translation` for ordinary item content. Use typed choice operations only when also changing the choice structure. Use a focused raw patch only for a supported survey-level translation surface that has no typed operation.
+5. Before proposing, check that every visible label implied by the inspected item configuration has a target-locale translation. A title alone is not a complete localization of a choice or form item.
+
+## Bounded Execution
+
+- Prefer one atomic proposal for a coherent localization when it fits the advertised operation limit. The limit is a hard safety bound, not a target chunk size.
+- Split only an oversized localization into independent, coherent chunks by section or item set. Independent localization chunks may be prepared in the same turn; do not make a later chunk depend on an unapplied structural change.
+- If live inspection or a source translation cannot determine a phrase accurately, ask a focused clarification rather than inventing domain-specific wording.

package/dist/references/rich-text-content.md

@@ -0,0 +1,193 @@
+# Rich Text Content
+
+Formatted survey text uses `{ "type": "richText", "version": 1, "doc": ... }`.
+Do not use markdown syntax for formatting; `md` content is displayed as plain text.
+
+Use typed `update-item-translation` and `create-item.translations[].content` for formatted text. Prefer `plainText` for all unformatted text, including a simple title, label, or one-paragraph info item. Use richText only when formatting carries meaning or structure. Use `survey-json-patch` for rich text only when you need to edit raw paths that typed translation operations cannot address.
+
+For `survey_change`, compact `richTextBlocks` shorthand is accepted and normalized before validation. This is useful for source-document imports:
+
+```json
+{
+  "locale": "en",
+  "contentKey": "content",
+  "richTextBlocks": [
+    { "type": "heading", "level": 2, "text": "How should I complete this survey?" },
+    { "type": "paragraph", "text": "Read each question carefully before answering." },
+    { "type": "bulletList", "items": ["Select the answer that applies to you.", "Enter the requested information."] },
+    { "type": "footnote", "text": "* Complete the survey using the information for the intended participant." }
+  ]
+}
+```
+
+The shorthand also supports inline runs through `children`. Use it when a paragraph or question title contains a link, bold/italic/underlined words, or a mix of styles:
+
+```json
+{
+  "locale": "en",
+  "contentKey": "title",
+  "richTextBlocks": [
+    {
+      "type": "paragraph",
+      "children": [
+        { "type": "text", "text": "Read the ", "style": { "weight": "strong" } },
+        { "type": "text", "text": "guidance" },
+        { "type": "text", "text": " at " },
+        { "type": "link", "href": "https://example.org/help", "text": "example.org/help" }
+      ]
+    }
+  ]
+}
+```
+
+For an email address, use `href: "mailto:contact@example.org"`. Do not put a visible URL or email address into a plain-text block when the source intends it to be clickable.
+
+## Inline Nodes
+
+```json
+{ "type": "text", "text": "Important", "style": { "weight": "strong" } }
+{ "type": "text", "text": "accented", "style": { "color": "accent" } }
+{ "type": "template", "key": "participantName" }
+{ "type": "lineBreak" }
+{
+  "type": "link",
+  "href": "https://example.com",
+  "children": [{ "type": "text", "text": "Read more" }]
+}
+```
+
+Important:
+- `template` inline nodes render template-variable tokens such as `{participantName}`. They are not respondent inputs and must not be used to simulate cloze blanks or inline answer fields.
+- The current editor/player path ignores generic `inlineExtension` nodes. Do not invent custom inline node types unless the registry explicitly supports them.
+
+Style values:
+- `weight`: `strong` or `normal`
+- `italic`: `italic` or `normal`
+- `underline`: `underline` or `none`
+- `color`: `primary`, `accent`, or `default`
+
+## Block Nodes
+
+```json
+{
+  "type": "richText",
+  "version": 1,
+  "doc": {
+    "type": "doc",
+    "blocks": [
+      {
+        "type": "heading",
+        "level": 2,
+        "children": [{ "type": "text", "text": "Before you start" }]
+      },
+      {
+        "type": "paragraph",
+        "children": [
+          { "type": "text", "text": "Read this " },
+          { "type": "text", "text": "carefully", "style": { "weight": "strong" } },
+          { "type": "text", "text": " before continuing." }
+        ]
+      },
+      {
+        "type": "bulletList",
+        "items": [
+          {
+            "type": "listItem",
+            "children": [
+              { "type": "paragraph", "children": [{ "type": "text", "text": "First point" }] }
+            ]
+          }
+        ]
+      },
+      {
+        "type": "infoBox",
+        "tone": "info",
+        "title": [{ "type": "text", "text": "Note" }],
+        "collapsible": true,
+        "defaultOpen": true,
+        "children": [
+          { "type": "paragraph", "children": [{ "type": "text", "text": "Helpful detail." }] }
+        ]
+      }
+    ]
+  }
+}
+```
+
+Supported block types:
+- `paragraph`
+- `heading` with `level` 1 for section headings or `level` 2 for subsection headings. Do not author levels 3 through 6; the player offsets/clamps these stored levels to semantic page headings.
+- `bulletList` with `listItem` entries
+- `image` with `source: { "type": "asset", "assetId": "..." }` or `source: { "type": "external", "url": "..." }`
+- `infoBox` with `tone: "info"` or `"warning"`
+- `separator`: use only between two substantive blocks within the same content surface. Never use it as the first or last block, or to decorate/mark the boundary of a survey item, page, or section; the survey layout already provides those boundaries.
+
+## Where Rich Text Is Used
+
+- Info items: content key `content`; full block editor with paragraphs, headings, bullet lists, images, separators, and info boxes.
+- Choice item `topContent` / `bottomContent`: block rich text with paragraphs, headings, bullet lists, images, separators, and info boxes.
+- Form item `topContent` / `bottomContent`: block rich text with paragraphs, bullet lists, images, and separators only. Do not use headings or info boxes there.
+- Question `title` and `cardFooter`: compact rich text with paragraph blocks only. Inline styles may use bold, italic, underline, and color.
+- Question `subtitle`: compact rich text with paragraph blocks only. Inline styles may use bold, underline, and color. Do not rely on italic in subtitles.
+- If the user asks for unsupported formatting on a surface, explain the limitation briefly and use the nearest supported representation.
+
+## Updating Existing Rich Text
+
+Inspect the item first, then use `update-item-translation` with a rich text `content` value:
+
+```json
+{
+  "kind": "update-item-translation",
+  "itemId": "info_1",
+  "locale": "en",
+  "contentKey": "content",
+  "content": {
+    "type": "richText",
+    "version": 1,
+    "doc": {
+      "type": "doc",
+      "blocks": [
+        { "type": "heading", "level": 2, "children": [{ "type": "text", "text": "Instructions" }] },
+        { "type": "paragraph", "children": [{ "type": "text", "text": "Please read carefully.", "style": { "weight": "strong" } }] }
+      ]
+    }
+  }
+}
+```
+
+This replaces that translation key for the target locale. Preserve existing blocks you still want; do not send only the new block unless the user asked to replace the whole content.
+
+## Creating A Formatted Info Item
+
+For a new formatted info item, use one typed `create-item` operation with a rich text `content` translation:
+
+```json
+{
+  "kind": "create-item",
+  "target": { "parentItemId": "<root-group-id-or-key>", "index": 0 },
+  "item": { "id": "info_intro", "key": "intro", "itemType": "infoItem", "config": {} },
+  "translations": [
+    {
+      "locale": "en",
+      "contentKey": "content",
+      "content": {
+        "type": "richText",
+        "version": 1,
+        "doc": {
+          "type": "doc",
+          "blocks": [
+            { "type": "heading", "level": 2, "children": [{ "type": "text", "text": "Before you start" }] },
+            { "type": "paragraph", "children": [{ "type": "text", "text": "This survey asks about your preferences." }] }
+          ]
+        }
+      }
+    }
+  ]
+}
+```
+
+The raw item can still be minimal:
+
+```json
+{ "id": "info_intro", "key": "intro", "itemType": "infoItem", "config": {} }
+```

package/dist/references/source-material-surveys.md

@@ -0,0 +1,60 @@
+# Source-Material Survey Implementation
+
+Use this reference when the user asks to implement, recreate, convert, import, or continue a survey from a PDF, document, image/OCR text, pasted questionnaire, table, form, protocol, or supplied question list.
+
+## Language
+
+- Respond to the user in the language of their current message unless they explicitly request another reply language.
+- Write respondent-visible survey text in the language of the supplied source material or supplied questions. If no source language is clear, use the language requested by the user.
+- If the needed locale is missing, introduce it through the created/updated translations. Do not put Dutch/German/French/etc. survey text under `en` just because `en` exists.
+- Preserve source-language answer labels and field labels unless the user asks for translation or localization.
+
+## Fidelity And Completeness
+
+- First classify source elements as respondent survey content, respondent input, study/admin metadata, print-only logistics, examples, or decorative layout. Preserve respondent content and inputs; adapt or omit print-only/admin/decorative elements unless the user explicitly asks for a literal archive copy.
+- Implement every distinct question, instruction, answer option, section heading, and respondent input implied by the source unless the user explicitly asks for a summary.
+- Do not collapse multiple real questions into one text field. A text field is appropriate only when the source asks for open-ended text, an unsupported structured response cannot be represented more precisely, or the user explicitly asks for a free-text capture.
+- If the questionnaire body asks the respondent to record information, the digital survey must include an input control for it. Do not leave respondent-entered information as static text.
+- Empty lines, blanks, underscores, table cells intended for handwriting, parenthetical "specify" prompts, and inline write-in areas in actual questions imply an input field. Model them as form fields or embedded option forms as appropriate.
+- Do not create respondent questions for front-cover study identifiers, barcodes, prefilled participant names, prefilled dates of birth, page numbers, institutional logos, or duplicate administrative fields when those values should come from digital participant metadata or are asked later as real survey questions.
+- Printed examples that demonstrate how to fill in a paper form should be preserved as instructional text when useful, not converted into real inputs.
+- Preserve question order, numbering intent, and section structure. For long sources, use multiple validated change proposals rather than omitting details. Omit `continuationMode` only on the first mutation call; use `continuationMode: "append"` on every later independent chunk so all chunks are retained.
+- Do not use representative sampling, "and similar items", broad paraphrase, or shortened tables for source-derived surveys unless the user explicitly asks for an abbreviated version. Repeated rows, repeated follow-ups, and long option sets still need to be modeled.
+- If the source is too long to hold comfortably in context, work by source/page/section chunks. For each chunk, make a complete implementation decision for every respondent-facing element before moving on.
+- Keep each source-import `survey_change` payload bounded. A good chunk is one source page/section or about 4-8 respondent items, including their options, fields, footnotes, and conditions. Continue with additional chunks instead of constructing one very large tool call.
+
+## Item Mapping
+
+- Map supported item types directly. Use `choiceItem` for single choice, multiple choice, and scale-like questions until a dedicated scale item exists.
+- For scale questions, create an ordered `choiceItem` with stable option ids/keys and labels that preserve the endpoints and intermediate labels. Include the scale instruction in `subtitle` or `topContent` when it is not part of the actual question.
+- Use `formItem` for grouped personal data, tables of fields, repeated short inputs, dates, numbers, contact details, or unsupported compound controls.
+- Use choice option embedded forms for choices that include an open field, such as "Other, specify", "Yes, explain", or an option-specific quantity/date/text input.
+- Preserve option-level parenthetical instructions, side notes, and footnote markers. If the current choice option UI has no separate option-description surface, fold short option notes into the visible option label, for example `Uitgenodigde persoon zelf (zie hiervoor de naam op de brief en/of geboortedatum op de voorkant van de vragenlijst)`, and keep markers such as `Iemand anders*`.
+- For sentence-completion options with an embedded input, put the completion cue on the embedded field label, not twice. Source text like `Iemand anders*, namelijk ____`, `Andere bedrijfstak, namelijk ____`, or `Other, please specify ____` should become option label `Iemand anders*` / `Andere bedrijfstak` / `Other` and embedded field label `Namelijk` / `Please specify`.
+- Use info items for non-interactive section introductions, explanations, consent/instruction text, and visible page/section headings. Keep a simple one-paragraph info item as plainText. Use richText only when the source requires headings, lists, links, separators, or meaningful emphasis.
+- Preserve major chapters/sections as survey structure. If page boundaries matter, use available page-break structure and/or a heading info item so respondents see the section break.
+- Include respondent-facing "before you begin", "how to complete this survey", consent, eligibility, safety, and contact/help sections as info items when still relevant digitally. Rewrite or omit paper-only return/postage instructions unless the user wants a literal reproduction.
+
+## Conditions And Follow-Ups
+
+- Implement implied conditions, branching, conditional follow-up questions, conditional option visibility, and skip logic when the source text clearly implies them. Do not skip conditions just because they require extra work.
+- If newly created items depend on other newly created items, place displayConditions/disabledConditions/validations/prefills directly on the created item objects in the same survey_change call when possible.
+- Load the expressions reference and use the expression tool for complex expression work or existing/applied items.
+
+## Text Shaping
+
+- Rephrase only enough to make the digital survey clear and grammatically coherent. Preserve measurement meaning, recall periods, answer scales, and eligibility wording.
+- Split source text into the right visible content keys: concise question in `title`; instructions like "multiple answers possible" or recall-period guidance in `subtitle` or `topContent`; explanations after the control in `bottomContent`; non-question prose in info item `content`.
+- Use plainText for ordinary unformatted prose. Use richText, not plainText, only when info item content has headings, subheadings, boxed sections, bullet/list structure, examples, emphasized phrases, separators, footnotes, URLs, email links, or mixed inline formatting. Preserve the hierarchy with heading blocks, paragraph blocks, bullet lists, info boxes, or separators as supported.
+- Preserve meaningful inline source formatting, not only block layout. A URL or email address that is intended as a destination must be a richText `link` node with a canonical `href`; do not rely on automatic link detection. If source text emphasizes or highlights individual words in a question title, subtitle, option, or info text, author that content key as richText with styled inline runs instead of flattening it to plainText. Use emphasis only where it carries source meaning or scanning value.
+- For source-import info items, you may use the compact `richTextBlocks` shorthand in a translation; `survey_change` normalizes it to strict richText. A paragraph or heading can use `children` for mixed inline text, links, and styles. Example blocks: `{ "type": "heading", "level": 2, "text": "Before you begin" }`, `{ "type": "paragraph", "children": [{ "type": "text", "text": "More information: " }, { "type": "link", "href": "https://example.org/help", "text": "example.org/help" }] }`, `{ "type": "paragraph", "children": [{ "type": "text", "text": "Important", "bold": true }, { "type": "text", "text": " wording" }] }`, `{ "type": "bulletList", "items": ["...", "..."] }`, `{ "type": "footnote", "text": "* ..." }`, `{ "type": "separator" }`.
+- Preserve footnote markers and footnote text when they change interpretation, eligibility, instructions, privacy, or coding. If a question/option has `*`, keep the marker in the visible title/option text and place the note in `subtitle`, `topContent`, `bottomContent`, or a following info item close to the referenced question. Do not silently drop source footnotes.
+- Do not put respondent-visible option labels, form field labels, dropdown option labels, validation messages, or embedded-form labels only in config. They need translation entries.
+
+## Workflow
+
+- For complex source implementation, load item-types and assistant-operations before preparing create-item operations; load rich-text-content before formatted info items; load expressions before complex branching.
+- Use survey_inspect for the root group and long-survey insertion points. Use full outline paging or children lookup; do not guess append indexes from truncated context.
+- Before calling survey_change for a source-derived chunk, do a quick fidelity pass against the source: every question title, option label, option parenthetical, blank/input, section heading, footnote marker, and footnote text in that chunk should either be represented digitally or intentionally omitted as print-only/admin material.
+- If the fidelity pass finds missing details, fix the operations before calling survey_change. Do not knowingly leave cleanup for the user when the source gives enough information to implement it now.
+- Prefer complete, coherent chunks over one enormous proposal. Each chunk should be valid, ordered, and usable on its own. If a page/section is too large for one bounded chunk, split it at a natural subsection boundary and say what remains to continue.

package/dist/references/survey-data-model.md

@@ -0,0 +1,109 @@
+# Survey Data Model
+
+## RawSurvey
+
+A survey JSON object has this shape:
+
+```json
+{
+  "$schema": "https://github.com/case-framework/case-survey-toolkit/packages/survey-core/schemas/survey-schema.json",
+  "maxItemsPerPage": { "large": 1, "small": 1 },
+  "surveyItems": [],
+  "assets": {},
+  "metadata": {},
+  "templateValues": {},
+  "translations": {}
+}
+```
+
+Required fields:
+- `$schema`: keep the current schema string; never remove or edit it.
+- `surveyItems`: array of raw survey items.
+
+Optional fields:
+- `maxItemsPerPage`: object with numeric `large` and `small` page-size limits.
+- `metadata`: survey-level string map.
+- `templateValues`: reusable expression values; see expressions.md.
+- `assets`: image assets keyed by asset id.
+- `translations`: locale-keyed translated content.
+
+## RawSurveyItem
+
+Minimal item shape:
+
+```json
+{
+  "id": "stable-unique-id",
+  "key": "coding_key",
+  "itemType": "choiceItem"
+}
+```
+
+Conventions:
+- `id` is globally unique and is the durable reference used by groups, translations, response slots, expressions, and patches.
+- `key` is the coding key shown in fullKey paths. Sibling keys must be unique and use letters, numbers, underscores, or hyphens.
+- `itemType` must exist in the current editor registry.
+
+Optional fields:
+- `metadata`: string map. `metadata.itemLabel` is the internal editor label, not respondent-visible text. `metadata.editorItemColor` stores the editor item color as a hex string such as `#0369a1`.
+- `config`: item-type-specific configuration. Many item types need config; simple structural/content items can be sparse.
+- `validations`: map of validation key to `JsonExpression`.
+- `displayConditions`: item/root and component display expressions.
+- `disabledConditions`: component disabled expressions.
+- `prefills`: configured prefill rules; see expressions.md.
+
+## Tree Structure
+
+There must be exactly one root group:
+
+```json
+{
+  "itemType": "group",
+  "config": { "isRoot": true, "items": [], "shuffleItems": false }
+}
+```
+
+Groups order children by id in `config.items`. To reorder survey items, patch the parent group item at `/surveyItems/<groupIndex>/config/items`.
+
+## Translations And Content
+
+Visible text is stored under translations, not usually in item config:
+
+```json
+{
+  "translations": {
+    "en": {
+      "itemTranslations": {
+        "<itemId>": {
+          "title": { "type": "md", "content": "Question text" }
+        }
+      },
+      "surveyCardContent": {},
+      "navigationContent": {},
+      "validationMessages": {}
+    }
+  }
+}
+```
+
+Content values may be:
+- `{ "type": "md", "content": "Text" }`
+- `{ "type": "plain", "content": "Plain text" }`
+- `{ "type": "richText", "version": 1, "doc": { "type": "doc", "blocks": [...] } }`
+
+Important:
+- `md` and `plain` content are rendered as plain text with line breaks. Markdown syntax such as `# Heading`, `**bold**`, or `- item` is not parsed into formatting.
+- For unformatted text, use typed translation operations with `plainText`.
+- For formatted content, use typed translation operations with a `content` value whose type is `richText`; see rich-text-content.md.
+- If the user asks for another language or the source material is clearly in another language, write respondent-visible translations under that locale code. A translation operation may introduce a missing locale; do not store Dutch, German, French, etc. text under `en` just because `en` exists.
+
+Common item content keys:
+- `title`: question title or group/page title.
+- `subtitle`: question subtitle.
+- `topContent`: content before the response controls.
+- `bottomContent`: content after the response controls.
+- `cardFooter`: footer inside the question card.
+- `content`: info item body.
+
+JSON Patch paths are relative to the survey document root. Do not prefix paths with `/survey`.
+Escape JSON Pointer segments: `/` becomes `~1`, `~` becomes `~0`.

package/dist/references/survey-quality.md

@@ -0,0 +1,23 @@
+# Survey quality review
+
+Use this reference for qualitative feedback on a questionnaire. Separate deterministic technical defects from judgment about research quality. A clean technical audit does not establish reliability, validity, absence of bias, or fitness for a scientific or regulatory purpose.
+
+## Review frame
+
+1. **Purpose and coverage.** Identify the survey's intended decisions, population, constructs, and mode. Check that every question contributes to an objective and that important constructs are not omitted.
+2. **Cognitive response process.** Consider how respondents comprehend the question, retrieve relevant information, form a judgment, and map it to the offered response. Flag vague concepts, hidden assumptions, unrealistic recall, and response options that do not fit likely answers.
+3. **Wording.** Prefer plain, specific, neutral language. Flag double-barrelled questions, leading or loaded wording, double negatives, unexplained terms, absolutes, presuppositions, and questions respondents may not be able or willing to answer accurately.
+4. **Response design.** Check that categories are mutually exclusive and sufficiently exhaustive, scales are balanced and consistently oriented, anchors are clear, ranges do not overlap, and `Other`, `Not applicable`, or `Prefer not to answer` are available where justified.
+5. **Order and burden.** Look for a logical progression, useful grouping, adequate transitions, and placement effects. Estimate burden from length, repetition, open-text effort, matrix density, and branching—not item count alone.
+6. **Routing and requiredness.** Verify that skip logic and validation match eligibility and that required questions do not force fabricated answers. Check whether respondents can recover from an accidental choice.
+7. **Sensitivity, privacy, and inclusion.** Ask only for data that is necessary. Review respectful phrasing, answer granularity, voluntariness, confidentiality context, accessibility, and risks to vulnerable groups.
+8. **Localization.** Evaluate conceptual and cultural equivalence, not only literal completeness. Recommend expert review, back-translation or team reconciliation, and testing with target-language respondents where stakes warrant it.
+9. **Testing and evidence.** Recommend expert review, cognitive interviewing, usability/accessibility testing, a pilot, and analysis of missingness, timing, distributions, reliability, and validity as appropriate to the claimed use.
+
+## How to report feedback
+
+- State assumptions about purpose, audience, mode, and locale.
+- Prioritize findings by likely effect on measurement quality or respondent harm.
+- Quote or identify the exact item, explain the risk, and suggest a concrete revision.
+- Distinguish defects from choices that require domain or ethics input.
+- Avoid claiming that wording alone makes an instrument scientifically validated.

package/dist/request-context-jcmXT_Q2.mjs

@@ -0,0 +1,44 @@
+import { I as surveyAssistantSnapshotPayloadSchema } from "./protocol-DV0ka9WT.mjs";
+import { Q as createSurveyAssistantEngineContext } from "./engine-sPvuixWg.mjs";
+import { defaultSurveyAssistantCapabilitySet } from "./capabilities-default.mjs";
+import { MASTRA_RESOURCE_ID_KEY, MASTRA_THREAD_ID_KEY, RequestContext } from "@mastra/core/request-context";
+//#region src/server/request-context.ts
+const parseSurveyAssistantSnapshot = (value) => {
+	if (value === void 0 || value === null) return null;
+	return surveyAssistantSnapshotPayloadSchema.parse(value);
+};
+const buildSurveyAssistantRequestContext = ({ changeCollector, identity, snapshot, snapshotSource = snapshot ? "full" : "missing", trustedCapabilities = defaultSurveyAssistantCapabilitySet, attachmentAccess, modelAttachments = [], modelSelection }) => {
+	const requestContext = new RequestContext();
+	requestContext.set("invocation", { kind: "chat" });
+	requestContext.set("turnId", changeCollector.turnId);
+	requestContext.set("changeCollector", changeCollector);
+	requestContext.set("identity", identity);
+	if (identity.authority === "authenticated-host") {
+		requestContext.set("authenticatedResourceId", identity.resourceId);
+		requestContext.set("authorizedThreadId", identity.threadId);
+	}
+	requestContext.set(MASTRA_RESOURCE_ID_KEY, identity.resourceId);
+	requestContext.set(MASTRA_THREAD_ID_KEY, identity.threadId);
+	requestContext.set("snapshotSource", snapshotSource);
+	if (attachmentAccess && attachmentAccess.documents.length > 0) requestContext.set("attachmentAccess", attachmentAccess);
+	if (modelAttachments.length > 0) requestContext.set("modelAttachments", modelAttachments);
+	if (modelSelection) requestContext.set("modelSelection", modelSelection);
+	if (!snapshot) return requestContext;
+	const engineContext = createSurveyAssistantEngineContext(snapshot, trustedCapabilities);
+	requestContext.set("documentSnapshot", snapshot);
+	requestContext.set("engineContext", engineContext);
+	return requestContext;
+};
+const requireSurveyAssistantTurnState = (requestContext) => {
+	const turnId = requestContext?.get("turnId");
+	const changeCollector = requestContext?.get("changeCollector");
+	if (!turnId || !changeCollector || changeCollector.turnId !== turnId) throw new Error("Survey assistant turn context is unavailable or inconsistent.");
+	return {
+		turnId,
+		changeCollector
+	};
+};
+//#endregion
+export { parseSurveyAssistantSnapshot as n, requireSurveyAssistantTurnState as r, buildSurveyAssistantRequestContext as t };
+
+//# sourceMappingURL=request-context-jcmXT_Q2.mjs.map

package/dist/request-context-jcmXT_Q2.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"request-context-jcmXT_Q2.mjs","names":[],"sources":["../src/server/request-context.ts"],"sourcesContent":["import {\n  MASTRA_RESOURCE_ID_KEY,\n  MASTRA_THREAD_ID_KEY,\n  RequestContext,\n} from \"@mastra/core/request-context\";\nimport { surveyAssistantSnapshotPayloadSchema, type SurveyDocumentSnapshot } from \"../protocol\";\nimport {\n  createSurveyAssistantEngineContext,\n  TurnChangeCollector,\n  type SurveyAssistantCapabilitySet,\n  type SurveyAssistantEngineContext,\n} from \"../engine\";\nimport { defaultSurveyAssistantCapabilitySet } from \"../capabilities/default\";\nimport type {\n  SurveyAssistantAttachmentAccess,\n  SurveyAssistantModelAttachment,\n} from \"./thread-documents\";\n\nexport interface SurveyAssistantInvocationContext {\n  kind: \"chat\";\n}\n\nexport interface SurveyAssistantIdentityContext {\n  authority: \"experimental-client-request\" | \"authenticated-host\";\n  resourceId: string;\n  threadId: string;\n}\n\nexport interface SurveyAssistantModelSelection {\n  id: string;\n  model: string;\n}\n\nexport type SurveyAssistantSnapshotSource = \"full\" | \"missing\";\n\nexport interface SurveyAssistantRequestContext {\n  invocation: SurveyAssistantInvocationContext;\n  turnId: string;\n  changeCollector: TurnChangeCollector;\n  identity: SurveyAssistantIdentityContext;\n  authenticatedResourceId?: string;\n  authorizedThreadId?: string;\n  applyPolicy?: \"auto\" | \"review\" | \"deny\";\n  mastra__resourceId?: string;\n  mastra__threadId?: string;\n  snapshotSource?: SurveyAssistantSnapshotSource;\n  engineContext?: SurveyAssistantEngineContext;\n  documentSnapshot?: SurveyDocumentSnapshot;\n  modelAttachments?: SurveyAssistantModelAttachment[];\n  attachmentAccess?: SurveyAssistantAttachmentAccess;\n  modelSelection?: SurveyAssistantModelSelection;\n}\n\nexport const parseSurveyAssistantSnapshot = (value: unknown): SurveyDocumentSnapshot | null => {\n  if (value === undefined || value === null) {\n    return null;\n  }\n\n  return surveyAssistantSnapshotPayloadSchema.parse(value);\n};\n\nexport const buildSurveyAssistantRequestContext = ({\n  changeCollector,\n  identity,\n  snapshot,\n  snapshotSource = snapshot ? \"full\" : \"missing\",\n  trustedCapabilities = defaultSurveyAssistantCapabilitySet,\n  attachmentAccess,\n  modelAttachments = [],\n  modelSelection,\n}: {\n  changeCollector: TurnChangeCollector;\n  identity: SurveyAssistantIdentityContext;\n  snapshot: SurveyDocumentSnapshot | null;\n  snapshotSource?: SurveyAssistantSnapshotSource;\n  trustedCapabilities?: SurveyAssistantCapabilitySet;\n  attachmentAccess?: SurveyAssistantAttachmentAccess;\n  modelAttachments?: SurveyAssistantModelAttachment[];\n  modelSelection?: SurveyAssistantModelSelection;\n}): RequestContext<SurveyAssistantRequestContext> => {\n  const requestContext = new RequestContext<SurveyAssistantRequestContext>();\n\n  requestContext.set(\"invocation\", { kind: \"chat\" });\n  requestContext.set(\"turnId\", changeCollector.turnId);\n  requestContext.set(\"changeCollector\", changeCollector);\n  requestContext.set(\"identity\", identity);\n  if (identity.authority === \"authenticated-host\") {\n    requestContext.set(\"authenticatedResourceId\", identity.resourceId);\n    requestContext.set(\"authorizedThreadId\", identity.threadId);\n  }\n  requestContext.set(MASTRA_RESOURCE_ID_KEY, identity.resourceId);\n  requestContext.set(MASTRA_THREAD_ID_KEY, identity.threadId);\n  requestContext.set(\"snapshotSource\", snapshotSource);\n  if (attachmentAccess && attachmentAccess.documents.length > 0) {\n    requestContext.set(\"attachmentAccess\", attachmentAccess);\n  }\n  if (modelAttachments.length > 0) {\n    requestContext.set(\"modelAttachments\", modelAttachments);\n  }\n  if (modelSelection) {\n    requestContext.set(\"modelSelection\", modelSelection);\n  }\n\n  if (!snapshot) {\n    return requestContext;\n  }\n\n  const engineContext = createSurveyAssistantEngineContext(snapshot, trustedCapabilities);\n  requestContext.set(\"documentSnapshot\", snapshot);\n  requestContext.set(\"engineContext\", engineContext);\n\n  return requestContext;\n};\n\nexport const requireSurveyAssistantTurnState = (\n  requestContext: RequestContext<SurveyAssistantRequestContext> | undefined,\n) => {\n  const turnId = requestContext?.get(\"turnId\");\n  const changeCollector = requestContext?.get(\"changeCollector\");\n  if (!turnId || !changeCollector || changeCollector.turnId !== turnId) {\n    throw new Error(\"Survey assistant turn context is unavailable or inconsistent.\");\n  }\n\n  return { turnId, changeCollector };\n};\n"],"mappings":";;;;;AAqDA,MAAa,gCAAgC,UAAkD;AAC7F,KAAI,UAAU,KAAA,KAAa,UAAU,KACnC,QAAO;AAGT,QAAO,qCAAqC,MAAM,MAAM;;AAG1D,MAAa,sCAAsC,EACjD,iBACA,UACA,UACA,iBAAiB,WAAW,SAAS,WACrC,sBAAsB,qCACtB,kBACA,mBAAmB,EAAE,EACrB,qBAUmD;CACnD,MAAM,iBAAiB,IAAI,gBAA+C;AAE1E,gBAAe,IAAI,cAAc,EAAE,MAAM,QAAQ,CAAC;AAClD,gBAAe,IAAI,UAAU,gBAAgB,OAAO;AACpD,gBAAe,IAAI,mBAAmB,gBAAgB;AACtD,gBAAe,IAAI,YAAY,SAAS;AACxC,KAAI,SAAS,cAAc,sBAAsB;AAC/C,iBAAe,IAAI,2BAA2B,SAAS,WAAW;AAClE,iBAAe,IAAI,sBAAsB,SAAS,SAAS;;AAE7D,gBAAe,IAAI,wBAAwB,SAAS,WAAW;AAC/D,gBAAe,IAAI,sBAAsB,SAAS,SAAS;AAC3D,gBAAe,IAAI,kBAAkB,eAAe;AACpD,KAAI,oBAAoB,iBAAiB,UAAU,SAAS,EAC1D,gBAAe,IAAI,oBAAoB,iBAAiB;AAE1D,KAAI,iBAAiB,SAAS,EAC5B,gBAAe,IAAI,oBAAoB,iBAAiB;AAE1D,KAAI,eACF,gBAAe,IAAI,kBAAkB,eAAe;AAGtD,KAAI,CAAC,SACH,QAAO;CAGT,MAAM,gBAAgB,mCAAmC,UAAU,oBAAoB;AACvF,gBAAe,IAAI,oBAAoB,SAAS;AAChD,gBAAe,IAAI,iBAAiB,cAAc;AAElD,QAAO;;AAGT,MAAa,mCACX,mBACG;CACH,MAAM,SAAS,gBAAgB,IAAI,SAAS;CAC5C,MAAM,kBAAkB,gBAAgB,IAAI,kBAAkB;AAC9D,KAAI,CAAC,UAAU,CAAC,mBAAmB,gBAAgB,WAAW,OAC5D,OAAM,IAAI,MAAM,gEAAgE;AAGlF,QAAO;EAAE;EAAQ;EAAiB"}

package/dist/request-guardrails-C59IWnH8.mjs

@@ -0,0 +1,73 @@
+//#region src/server/request-guardrails.ts
+const SURVEY_ASSISTANT_MAX_REQUEST_BYTES = 20 * 1024 * 1024;
+const SURVEY_ASSISTANT_MAX_MESSAGES = 32;
+const SURVEY_ASSISTANT_MAX_ATTACHMENTS = 4;
+const SURVEY_ASSISTANT_MAX_ATTACHMENT_BYTES = 5 * 1024 * 1024;
+const SURVEY_ASSISTANT_MAX_TOTAL_ATTACHMENT_BYTES = 12 * 1024 * 1024;
+const SURVEY_ASSISTANT_MAX_TEXT_PART_CHARS = 64e3;
+const SURVEY_ASSISTANT_ACCEPTED_ATTACHMENT_TYPES = new Set([
+	"application/pdf",
+	"image/gif",
+	"image/jpeg",
+	"image/png",
+	"image/webp"
+]);
+var SurveyAssistantRequestError = class extends Error {
+	status;
+	constructor(message, status = 400) {
+		super(message);
+		this.name = "SurveyAssistantRequestError";
+		this.status = status;
+	}
+};
+const getDataUrlBytes = (url, expectedMediaType) => {
+	const match = /^data:([^;,]+);base64,([A-Za-z0-9+/]*={0,2})$/.exec(url);
+	if (!match) throw new SurveyAssistantRequestError("Attachments must be base64 data URLs.");
+	if (match[1]?.toLowerCase() !== expectedMediaType.toLowerCase()) throw new SurveyAssistantRequestError("Attachment media type does not match its data URL.");
+	const payload = match[2] ?? "";
+	const padding = payload.endsWith("==") ? 2 : payload.endsWith("=") ? 1 : 0;
+	return Math.max(0, Math.floor(payload.length * 3 / 4) - padding);
+};
+const validateSurveyAssistantMessages = (value) => {
+	if (!Array.isArray(value) || value.length === 0) throw new SurveyAssistantRequestError("A survey assistant message is required.");
+	if (value.length > 32) throw new SurveyAssistantRequestError("The survey assistant request contains too many messages.");
+	if (value.length !== 1 || value[0]?.role !== "user") throw new SurveyAssistantRequestError("The survey assistant request must contain only the current user message.");
+	let attachmentCount = 0;
+	let totalAttachmentBytes = 0;
+	for (const message of value) {
+		if (!message || typeof message !== "object" || !Array.isArray(message.parts)) throw new SurveyAssistantRequestError("The survey assistant messages are malformed.");
+		for (const part of message.parts) {
+			if (!part || typeof part !== "object" || typeof part.type !== "string") throw new SurveyAssistantRequestError("A survey assistant message part is malformed.");
+			if (part.type === "text") {
+				if (typeof part.text !== "string") throw new SurveyAssistantRequestError("A survey assistant text part is malformed.");
+				if (part.text.length > 64e3) throw new SurveyAssistantRequestError("A survey assistant message is too long.");
+				continue;
+			}
+			if (part.type !== "file") throw new SurveyAssistantRequestError("The survey assistant message part is not supported.");
+			attachmentCount += 1;
+			if (attachmentCount > 4) throw new SurveyAssistantRequestError("The survey assistant request has too many attachments.");
+			if (typeof part.mediaType !== "string" || !SURVEY_ASSISTANT_ACCEPTED_ATTACHMENT_TYPES.has(part.mediaType.toLowerCase())) throw new SurveyAssistantRequestError("The survey assistant attachment type is not supported.");
+			if (typeof part.url !== "string") throw new SurveyAssistantRequestError("The survey assistant attachment is malformed.");
+			const bytes = getDataUrlBytes(part.url, part.mediaType);
+			if (bytes > 5242880) throw new SurveyAssistantRequestError("A survey assistant attachment is too large.");
+			totalAttachmentBytes += bytes;
+			if (totalAttachmentBytes > 12582912) throw new SurveyAssistantRequestError("The survey assistant attachments are too large in total.");
+		}
+	}
+	return value;
+};
+const readSurveyAssistantRequestJson = async (request) => {
+	const declaredLength = Number(request.headers.get("content-length"));
+	if (Number.isFinite(declaredLength) && declaredLength > 20971520) throw new SurveyAssistantRequestError("The survey assistant request is too large.", 413);
+	const text = await request.text();
+	if (new TextEncoder().encode(text).byteLength > 20971520) throw new SurveyAssistantRequestError("The survey assistant request is too large.", 413);
+	try {
+		return JSON.parse(text);
+	} catch {
+		throw new SurveyAssistantRequestError("The survey assistant request is not valid JSON.");
+	}
+};
+//#endregion
+export { SURVEY_ASSISTANT_MAX_REQUEST_BYTES as a, SurveyAssistantRequestError as c, SURVEY_ASSISTANT_MAX_MESSAGES as i, readSurveyAssistantRequestJson as l, SURVEY_ASSISTANT_MAX_ATTACHMENTS as n, SURVEY_ASSISTANT_MAX_TEXT_PART_CHARS as o, SURVEY_ASSISTANT_MAX_ATTACHMENT_BYTES as r, SURVEY_ASSISTANT_MAX_TOTAL_ATTACHMENT_BYTES as s, SURVEY_ASSISTANT_ACCEPTED_ATTACHMENT_TYPES as t, validateSurveyAssistantMessages as u };
+
+//# sourceMappingURL=request-guardrails-C59IWnH8.mjs.map

package/dist/request-guardrails-C59IWnH8.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"request-guardrails-C59IWnH8.mjs","names":[],"sources":["../src/server/request-guardrails.ts"],"sourcesContent":["import type { UIMessage } from \"ai\";\n\nexport const SURVEY_ASSISTANT_MAX_REQUEST_BYTES = 20 * 1024 * 1024;\nexport const SURVEY_ASSISTANT_MAX_MESSAGES = 32;\nexport const SURVEY_ASSISTANT_MAX_ATTACHMENTS = 4;\nexport const SURVEY_ASSISTANT_MAX_ATTACHMENT_BYTES = 5 * 1024 * 1024;\nexport const SURVEY_ASSISTANT_MAX_TOTAL_ATTACHMENT_BYTES = 12 * 1024 * 1024;\nexport const SURVEY_ASSISTANT_MAX_TEXT_PART_CHARS = 64_000;\n\nexport const SURVEY_ASSISTANT_ACCEPTED_ATTACHMENT_TYPES = new Set([\n  \"application/pdf\",\n  \"image/gif\",\n  \"image/jpeg\",\n  \"image/png\",\n  \"image/webp\",\n]);\n\nexport class SurveyAssistantRequestError extends Error {\n  readonly status: number;\n\n  constructor(message: string, status = 400) {\n    super(message);\n    this.name = \"SurveyAssistantRequestError\";\n    this.status = status;\n  }\n}\n\nconst getDataUrlBytes = (url: string, expectedMediaType: string): number => {\n  const match = /^data:([^;,]+);base64,([A-Za-z0-9+/]*={0,2})$/.exec(url);\n  if (!match) {\n    throw new SurveyAssistantRequestError(\"Attachments must be base64 data URLs.\");\n  }\n  if (match[1]?.toLowerCase() !== expectedMediaType.toLowerCase()) {\n    throw new SurveyAssistantRequestError(\"Attachment media type does not match its data URL.\");\n  }\n\n  const payload = match[2] ?? \"\";\n  const padding = payload.endsWith(\"==\") ? 2 : payload.endsWith(\"=\") ? 1 : 0;\n  return Math.max(0, Math.floor((payload.length * 3) / 4) - padding);\n};\n\nexport const validateSurveyAssistantMessages = (value: unknown): UIMessage[] => {\n  if (!Array.isArray(value) || value.length === 0) {\n    throw new SurveyAssistantRequestError(\"A survey assistant message is required.\");\n  }\n  if (value.length > SURVEY_ASSISTANT_MAX_MESSAGES) {\n    throw new SurveyAssistantRequestError(\n      \"The survey assistant request contains too many messages.\",\n    );\n  }\n  if (value.length !== 1 || value[0]?.role !== \"user\") {\n    throw new SurveyAssistantRequestError(\n      \"The survey assistant request must contain only the current user message.\",\n    );\n  }\n\n  let attachmentCount = 0;\n  let totalAttachmentBytes = 0;\n  for (const message of value) {\n    if (!message || typeof message !== \"object\" || !Array.isArray(message.parts)) {\n      throw new SurveyAssistantRequestError(\"The survey assistant messages are malformed.\");\n    }\n\n    for (const part of message.parts) {\n      if (!part || typeof part !== \"object\" || typeof part.type !== \"string\") {\n        throw new SurveyAssistantRequestError(\"A survey assistant message part is malformed.\");\n      }\n      if (part.type === \"text\") {\n        if (typeof part.text !== \"string\") {\n          throw new SurveyAssistantRequestError(\"A survey assistant text part is malformed.\");\n        }\n        if (part.text.length > SURVEY_ASSISTANT_MAX_TEXT_PART_CHARS) {\n          throw new SurveyAssistantRequestError(\"A survey assistant message is too long.\");\n        }\n        continue;\n      }\n      if (part.type !== \"file\") {\n        throw new SurveyAssistantRequestError(\n          \"The survey assistant message part is not supported.\",\n        );\n      }\n\n      attachmentCount += 1;\n      if (attachmentCount > SURVEY_ASSISTANT_MAX_ATTACHMENTS) {\n        throw new SurveyAssistantRequestError(\n          \"The survey assistant request has too many attachments.\",\n        );\n      }\n      if (\n        typeof part.mediaType !== \"string\" ||\n        !SURVEY_ASSISTANT_ACCEPTED_ATTACHMENT_TYPES.has(part.mediaType.toLowerCase())\n      ) {\n        throw new SurveyAssistantRequestError(\n          \"The survey assistant attachment type is not supported.\",\n        );\n      }\n      if (typeof part.url !== \"string\") {\n        throw new SurveyAssistantRequestError(\"The survey assistant attachment is malformed.\");\n      }\n\n      const bytes = getDataUrlBytes(part.url, part.mediaType);\n      if (bytes > SURVEY_ASSISTANT_MAX_ATTACHMENT_BYTES) {\n        throw new SurveyAssistantRequestError(\"A survey assistant attachment is too large.\");\n      }\n      totalAttachmentBytes += bytes;\n      if (totalAttachmentBytes > SURVEY_ASSISTANT_MAX_TOTAL_ATTACHMENT_BYTES) {\n        throw new SurveyAssistantRequestError(\n          \"The survey assistant attachments are too large in total.\",\n        );\n      }\n    }\n  }\n\n  return value as UIMessage[];\n};\n\nexport const readSurveyAssistantRequestJson = async (request: Request): Promise<unknown> => {\n  const declaredLength = Number(request.headers.get(\"content-length\"));\n  if (Number.isFinite(declaredLength) && declaredLength > SURVEY_ASSISTANT_MAX_REQUEST_BYTES) {\n    throw new SurveyAssistantRequestError(\"The survey assistant request is too large.\", 413);\n  }\n\n  const text = await request.text();\n  if (new TextEncoder().encode(text).byteLength > SURVEY_ASSISTANT_MAX_REQUEST_BYTES) {\n    throw new SurveyAssistantRequestError(\"The survey assistant request is too large.\", 413);\n  }\n\n  try {\n    return JSON.parse(text) as unknown;\n  } catch {\n    throw new SurveyAssistantRequestError(\"The survey assistant request is not valid JSON.\");\n  }\n};\n"],"mappings":";AAEA,MAAa,qCAAqC,KAAK,OAAO;AAC9D,MAAa,gCAAgC;AAC7C,MAAa,mCAAmC;AAChD,MAAa,wCAAwC,IAAI,OAAO;AAChE,MAAa,8CAA8C,KAAK,OAAO;AACvE,MAAa,uCAAuC;AAEpD,MAAa,6CAA6C,IAAI,IAAI;CAChE;CACA;CACA;CACA;CACA;CACD,CAAC;AAEF,IAAa,8BAAb,cAAiD,MAAM;CACrD;CAEA,YAAY,SAAiB,SAAS,KAAK;AACzC,QAAM,QAAQ;AACd,OAAK,OAAO;AACZ,OAAK,SAAS;;;AAIlB,MAAM,mBAAmB,KAAa,sBAAsC;CAC1E,MAAM,QAAQ,gDAAgD,KAAK,IAAI;AACvE,KAAI,CAAC,MACH,OAAM,IAAI,4BAA4B,wCAAwC;AAEhF,KAAI,MAAM,IAAI,aAAa,KAAK,kBAAkB,aAAa,CAC7D,OAAM,IAAI,4BAA4B,qDAAqD;CAG7F,MAAM,UAAU,MAAM,MAAM;CAC5B,MAAM,UAAU,QAAQ,SAAS,KAAK,GAAG,IAAI,QAAQ,SAAS,IAAI,GAAG,IAAI;AACzE,QAAO,KAAK,IAAI,GAAG,KAAK,MAAO,QAAQ,SAAS,IAAK,EAAE,GAAG,QAAQ;;AAGpE,MAAa,mCAAmC,UAAgC;AAC9E,KAAI,CAAC,MAAM,QAAQ,MAAM,IAAI,MAAM,WAAW,EAC5C,OAAM,IAAI,4BAA4B,0CAA0C;AAElF,KAAI,MAAM,SAAA,GACR,OAAM,IAAI,4BACR,2DACD;AAEH,KAAI,MAAM,WAAW,KAAK,MAAM,IAAI,SAAS,OAC3C,OAAM,IAAI,4BACR,2EACD;CAGH,IAAI,kBAAkB;CACtB,IAAI,uBAAuB;AAC3B,MAAK,MAAM,WAAW,OAAO;AAC3B,MAAI,CAAC,WAAW,OAAO,YAAY,YAAY,CAAC,MAAM,QAAQ,QAAQ,MAAM,CAC1E,OAAM,IAAI,4BAA4B,+CAA+C;AAGvF,OAAK,MAAM,QAAQ,QAAQ,OAAO;AAChC,OAAI,CAAC,QAAQ,OAAO,SAAS,YAAY,OAAO,KAAK,SAAS,SAC5D,OAAM,IAAI,4BAA4B,gDAAgD;AAExF,OAAI,KAAK,SAAS,QAAQ;AACxB,QAAI,OAAO,KAAK,SAAS,SACvB,OAAM,IAAI,4BAA4B,6CAA6C;AAErF,QAAI,KAAK,KAAK,SAAA,KACZ,OAAM,IAAI,4BAA4B,0CAA0C;AAElF;;AAEF,OAAI,KAAK,SAAS,OAChB,OAAM,IAAI,4BACR,sDACD;AAGH,sBAAmB;AACnB,OAAI,kBAAA,EACF,OAAM,IAAI,4BACR,yDACD;AAEH,OACE,OAAO,KAAK,cAAc,YAC1B,CAAC,2CAA2C,IAAI,KAAK,UAAU,aAAa,CAAC,CAE7E,OAAM,IAAI,4BACR,yDACD;AAEH,OAAI,OAAO,KAAK,QAAQ,SACtB,OAAM,IAAI,4BAA4B,gDAAgD;GAGxF,MAAM,QAAQ,gBAAgB,KAAK,KAAK,KAAK,UAAU;AACvD,OAAI,QAAA,QACF,OAAM,IAAI,4BAA4B,8CAA8C;AAEtF,2BAAwB;AACxB,OAAI,uBAAA,SACF,OAAM,IAAI,4BACR,2DACD;;;AAKP,QAAO;;AAGT,MAAa,iCAAiC,OAAO,YAAuC;CAC1F,MAAM,iBAAiB,OAAO,QAAQ,QAAQ,IAAI,iBAAiB,CAAC;AACpE,KAAI,OAAO,SAAS,eAAe,IAAI,iBAAA,SACrC,OAAM,IAAI,4BAA4B,8CAA8C,IAAI;CAG1F,MAAM,OAAO,MAAM,QAAQ,MAAM;AACjC,KAAI,IAAI,aAAa,CAAC,OAAO,KAAK,CAAC,aAAA,SACjC,OAAM,IAAI,4BAA4B,8CAA8C,IAAI;AAG1F,KAAI;AACF,SAAO,KAAK,MAAM,KAAK;SACjB;AACN,QAAM,IAAI,4BAA4B,kDAAkD"}