@case-framework/survey-assistant 0.2.2 → 0.3.0

package/dist/references/expressions.md

@@ -1,6 +1,7 @@
 # Expressions, Conditions, Validations, Prefills
 
 Use `survey_expression` for expression work. It is the expression capability bundle:
+
 - `action: "context"` returns available response refs and optional existing expression locations.
 - `action: "prepare"` validates expression refs/return types and registers a candidate change set.
 - Prefer this tool over hand-written raw JSON Patch for expression-bearing locations.
@@ -21,6 +22,7 @@ Optional `editorConfig` can contain `usedTemplate`, `label`, and `description`.
 ## Response Values And Variables
 
 Response values are typed objects:
+
 - string: `{ "type": "string", "value": "abc" }`
 - number: `{ "type": "number", "value": 42 }`
 - boolean: `{ "type": "boolean", "value": true }`
@@ -33,6 +35,7 @@ Response variable refs use this exact string format:
 `<itemId>...<method>...<slotId>`
 
 Methods:
+
 - `get`: returns the current slot value.
 - `isDefined`: returns boolean true when a response exists.
 
@@ -40,15 +43,17 @@ Never invent response refs. Use the current context response-slots scope or item
 This rule is item-type independent: preserve every item id, slot id, component/validation key,
 prefill id, template key, and reference constant exactly as inspected. Never humanize an identifier
 for display or explanation; if a coding key exists, show that exact key, otherwise show the exact id.
-The live snapshot is immutable for the whole assistant response. `survey_change` validates and
-registers a candidate; it does not change what later tools can inspect. The browser applies authorized change sets
-only after the response completes successfully. A validated candidate is intended for apply if the turn succeeds;
-it is not a dry run. For a
-request that creates dependent items, plan the complete structure first, put the source create
-operation before its dependents, and embed each dependent expression directly in its
-`create-item.item` object in one `survey_change` call. Do not create the items with
-`survey_change` and then call `survey_expression`: live inspection cannot see unapplied items
-during the same turn.
+The submitted snapshot is the immutable apply baseline, but successful mutation calls materialize
+in one request-scoped draft. Later inspection and mutation tools can see and target items,
+translations, assets, and response slots introduced earlier in the same turn. The browser applies
+the authorized cumulative draft only after the response completes successfully; a validated
+candidate is intended for apply if the turn succeeds and is not a dry run.
+
+For a request that creates dependent items, prefer planning the complete structure first, putting
+the source create operation before its dependents, and embedding each dependent expression directly
+in its `create-item.item` object in one `survey_change` call. When a genuine dependency requires
+separate calls, inspect the updated request-scoped draft and use `survey_expression` against the
+newly available ids and response slots.
 
 Each response slot defined by a source item's config is available as
 `<sourceItemId>...get...<slotId>`, with a boolean presence check at
@@ -56,6 +61,7 @@ Each response slot defined by a source item's config is available as
 function and constant. For example, a single-choice `reference` slot uses `eq` with a
 `reference` const; this is only one typed case, not a restriction on source item types.
 Always check the response slot value type before choosing a function:
+
 - Single-choice choice items return `reference`; compare them with `eq` and a `reference` const.
 - Multiple-choice choice items return `reference[]`; check selected options with `list_contains` and a `reference` const.
 - `list_contains` must receive `string[]` + `string` or `reference[]` + `reference`. Never use it with a single `reference` response.
@@ -279,11 +285,13 @@ Prefill shape:
 ```
 
 Targets:
+
 - `{ "type": "itemResponse" }`
 - `{ "type": "field", "fieldId": "<fieldId>" }`
 - `{ "type": "embeddedField", "optionId": "<optionId>", "fieldId": "<fieldId>" }`
 
 Sources:
+
 - `static`: direct ResponseValue.
 - `expression`: JsonExpression.
 - `templateValue`: `{ "key": "<templateValueKey>" }`.

package/dist/references/fair-by-design.md

@@ -0,0 +1,80 @@
+# FAIR-by-design survey authoring
+
+Use this reference when a request concerns FAIR or born-FAIR data, interoperability, reuse,
+standardization, harmonization, comparability across studies or waves, codebooks or export,
+stable identifiers and codes, missing-value semantics, metadata or provenance, standard
+instruments, or controlled vocabularies and formats.
+
+FAIR means Findable, Accessible, Interoperable, and Reusable. In Survey Editor authoring, the
+most relevant concerns are machine-readable identifiers and codes, sufficient metadata, and
+stable semantics that survive translation, rewording, export, and reuse. FAIR is decision context,
+not a universal override of the user's request or an established survey convention.
+
+## Keep the three layers separate
+
+1. **Presentation:** respondent-visible questions, instructions, and answer labels. These are
+   localized content and may be reworded.
+2. **Stored identifiers and codes:** stable item and option identifiers, coding keys, typed values,
+   and standard formats. These are for machines and should not depend on display language.
+3. **Metadata:** definitions, labels for codes, units, data types, missing-value meanings, versions,
+   provenance, and mappings to standards. Meaning belongs here rather than being packed into a
+   short identifier.
+
+Do not use a respondent-visible label as though it were a stable stored code. Do not expose a raw
+identifier as respondent wording. In CASE, visible item, option, field, and validation text belongs
+in locale translations; ids, keys, option values, and response-slot references remain exact data.
+
+## Identifiers and coding keys
+
+- Preserve stable internal ids and existing keys unless the user asks to change them. Never
+  silently repurpose an existing identifier when meaning changes.
+- When FAIR item-key naming is relevant, start with a letter; use lowercase ASCII letters, digits,
+  and underscores; use `snake_case`; stay at or below 32 characters; avoid programming and
+  database reserved words; prefer a stable, language-neutral English concept name; reuse the same
+  concept name across waves and studies; use established instrument prefixes and sortable item
+  numbers when applicable; and distinguish raw from derived variables.
+- A name is a stable handle, not a sentence. Put the complete question meaning in content and
+  metadata.
+- For a standard instrument, preserve its established identity and predictable structure, such as
+  an instrument prefix plus a zero-padded item number, rather than inventing unrelated names.
+- Choice option ids, keys, and values should be stable and coding-friendly. Their localized labels
+  remain separate translations.
+- Follow an explicit user-supplied identifier or established local convention when FAIR naming was
+  not requested. If a FAIR alternative would materially help, explain the tradeoff rather than
+  silently imposing it.
+
+## Answers, value sets, and missingness
+
+- Prefer defined coded value sets over storing localized display text as the primary answer.
+- Keep the coding scheme consistent across equivalent questions. Every code needs a documented
+  label and meaning.
+- Reuse established code lists and formats when the task calls for interoperability: ISO 8601 for
+  dates, ISO 3166 for countries, ISO 639 for languages, UCUM for units, and appropriate domain
+  vocabularies such as LOINC or SNOMED CT when supported and relevant.
+- Treat not applicable, skipped by routing, do not know, refused, and not asked as distinct missing
+  reasons. Never invent an ordinary numeric value such as `99` or `-9` that could be analyzed as a
+  real response unless the surrounding data model explicitly declares and documents it as missing.
+- Do not invent CASE fields or ad hoc codes to simulate missing-value semantics that the installed
+  editor capabilities do not support. Explain the capability gap instead.
+
+## Metadata, reuse, and versioning
+
+- Capture useful metadata already implied by authoring: question text, localized labels, answer
+  choices, types, constraints, units, definitions, provenance, and standard mappings.
+- Reuse a validated standard question or instrument definition when available instead of creating a
+  near-duplicate merely from wording.
+- Keep raw collected values separate from derived values and document how derivations are made.
+- Treat content changes, mappings, and instrument updates as versioned changes. Do not rename or
+  repurpose an existing identifier merely to change its meaning.
+- Dataset-level persistent identifiers, licences, publication metadata, DDI/FHIR exports, and other
+  repository or export guarantees are platform concerns unless the current capability manifest
+  exposes them. Explain that boundary rather than claiming the survey edit alone makes the final
+  dataset FAIR.
+
+## Applying this reference
+
+Use only supported survey structures and operations. Inspect the current survey and relevant
+capabilities before changing existing identifiers, codes, values, or metadata. Do not proactively
+rewrite a survey merely because this reference was loaded. Apply the parts material to the user's
+goal, state important tradeoffs, and identify platform-level FAIR requirements that remain outside
+the editor.

package/dist/references/item-types.md

@@ -83,9 +83,10 @@ Embedded option forms:
 - There is no `allowOther` flag in the current choice item model. Do not use `allowOther` to create free-text "Other" inputs.
 - CRITICAL — exact key name: the field on the option object is `embeddedForm` (singular, one object). It is NEVER `embeddedForms` (plural) and NEVER an array. The option's recognized keys are only: `id`, `key`, `label`, `hasDisplayCondition`, `embeddedFormItemId`, `embeddedForm`. Any other key (including a typo'd/pluralized `embeddedForms`) is silently dropped during validation — no error is raised, the field simply never appears, and you must not report the change as successful if you are not certain you used the exact singular key.
 - CRITICAL — exact shape: `embeddedForm` fields are never listed directly as `embeddedForm.fields`. They must be nested inside `embeddedForm.fieldGroups`, an array of groups, each with its own `fields` array: `{ "id": "...", "fieldGroups": [ { "id": "...", "fields": [ { "id": "...", "type": "input", "controller": { "type": "input", ... } } ] } ] }`. A top-level `fields` array with no `fieldGroups` wrapper will not render anything.
-- CRITICAL — `embeddedForm` is a FLAT object with exactly two meaningful keys: `id` and `fieldGroups`. Do NOT invent an envelope like `{ "itemType": "formItem", "config": { "fields": [...] } }` — that is not a real shape, it is not schema-validated so it fails silently (no error, no visible field, the option just behaves as if it had no embedded form at all). There is no `itemType`/`config` wrapper anywhere inside `embeddedForm`; `fieldGroups` sits directly on the `embeddedForm` object itself.
+- CRITICAL — `embeddedForm` is a FLAT object with `id`, `authoringMode`, and `fieldGroups`. Do NOT invent an envelope like `{ "itemType": "formItem", "config": { "fields": [...] } }`. There is no `itemType`/`config` wrapper anywhere inside `embeddedForm`; `fieldGroups` sits directly on the `embeddedForm` object itself.
 - CRITICAL — always set an explicit `id` on any option that will have an `embeddedForm` (e.g. `"id": "other"`, lowercase, coding-friendly). If you omit `id`, one is auto-generated from `label` and PRESERVES THE EXACT CASE of the label text (e.g. label "Other" auto-generates id "Other", not "other") — you cannot reliably predict it, and every embedded-form translation content key (`embeddedForms.<optionId>...`) and response slot (`embedded.<optionId>...`) must match that exact generated id, including case. Setting an explicit lowercase `id` yourself removes this guesswork entirely.
-- To attach input controls to a choice option, put an `embeddedForm` on that option. It uses the same `FormItemConfig` shape as a `formItem` (`id` + `fieldGroups`), but it is embedded directly on the option object — it is never a separate `formItem` sibling and never uses `embeddedFormItemId` unless you are intentionally referencing a shared/reusable form item defined elsewhere (rare; prefer inline `embeddedForm`).
+- To attach input controls to a choice option, put an `embeddedForm` on that option. It uses the same `FormItemConfig` shape as a `formItem` (`id` + `authoringMode` + `fieldGroups`), but it is embedded directly on the option object — it is never a separate `formItem` sibling and never uses `embeddedFormItemId` unless you are intentionally referencing a shared/reusable form item defined elsewhere (rare; prefer inline `embeddedForm`).
+- Use `authoringMode: "simple"` only for one internal group containing exactly one field. Use `custom` for a blank or multi-field follow-up. Adding, removing, moving, retyping, or rekeying fields, or changing groups/layouts, is a one-way transition to `custom`; preserve the existing field and translations during that transition.
 - The embedded form renders only while that option is selected. When the option is deselected, existing embedded responses are cleared after user confirmation.
 - Embedded form translation keys are prefixed with `embeddedForms.<optionId>`; for example `embeddedForms.other.fields.other_text.label`. Note this translation content-key prefix IS plural (`embeddedForms`) even though the config field on the option is singular (`embeddedForm`) — these are two different things; do not confuse them.
 - Embedded form response slots are `embedded.<optionId>.<fieldKey>`; for example `embedded.other.other_text`.
@@ -100,6 +101,7 @@ Example "Other, please specify" option:
   "key": "other",
   "embeddedForm": {
     "id": "other",
+    "authoringMode": "simple",
     "fieldGroups": [
       {
         "id": "other_details",
@@ -160,6 +162,7 @@ One `create-item` operation carries the whole item plus every translation it nee
           "key": "other",
           "embeddedForm": {
             "id": "other",
+            "authoringMode": "simple",
             "fieldGroups": [
               {
                 "id": "other_details",
@@ -242,6 +245,7 @@ Interactive form question:
   "itemType": "formItem",
   "config": {
     "id": "<itemId>",
+    "authoringMode": "custom",
     "fieldGroups": [
       {
         "id": "main",
@@ -253,7 +257,18 @@ Interactive form question:
 }
 ```
 
-CRITICAL — the item's `config` object has exactly two meaningful keys: `id` and `fieldGroups`. `fieldGroups` sits directly on `config` — never nest it under another wrapper, and never put a top-level `fields` array directly on `config` (fields must be inside a `fieldGroups` entry). Fields need at least one non-empty `fieldGroups` entry with an actual `fields` array to be useful; an empty `fieldGroups: [{ "fields": [] }]` is only a starting scaffold, not a finished item.
+The item's config has `id`, `authoringMode`, and `fieldGroups`. `fieldGroups` sits directly on config — never nest it under another wrapper, and never put a top-level `fields` array directly on config.
+
+Authoring modes and Add item presets:
+
+- `Text` → `input`, `Long text` → `textarea`, `Number` → `number`, `Slider` → `slider`, `Dropdown` → `select`, `Date` → `datepicker`, and `Switch` → `switch`.
+- These seven presets use `authoringMode: "simple"` with exactly one internal field group containing exactly one field. The field group remains part of persisted/runtime data; hiding it is only an editor abstraction.
+- `Blank form` uses `authoringMode: "custom"`. Any finished multi-field/group form also uses custom mode.
+- Simple mode exposes the existing field's label, description, required state, and compatible controller settings. It does not expose groups, layouts, field reordering, field keys, or field-type switching.
+- Adding/removing/moving fields or groups, changing layout, or changing the sole field's key/type is a one-way transition to custom. Preserve the existing field and every translation. Never leave a multi-field, empty, or multi-group structure marked simple.
+- If a stored simple form lacks its sole first field, treat it as custom without deleting any remaining data.
+
+Fields normally need at least one non-empty group to be useful. An explicit `authoringMode: "custom"` with one empty group is the supported Blank form starting preset.
 
 Field group config:
 
@@ -357,6 +372,7 @@ MANDATORY: every `select` option needs a matching `fields.<fieldId>.options.<opt
     "itemType": "formItem",
     "config": {
       "id": "form_1",
+      "authoringMode": "custom",
       "fieldGroups": [
         {
           "id": "main",

package/dist/references/localization.md

@@ -5,17 +5,19 @@ Use this reference when the user asks to translate, localize, add a language, or
 ## 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.
+- An unqualified request to "add a German localization", "add German", or translate/localize the survey means make the existing respondent-facing content available in that language. Registering an empty locale does not complete that request.
+- Use `add-survey-locale` only when the user explicitly wants the language registered before it has translated content. It rejects blank and already-present locale codes.
 - Use the target locale code directly in typed translation operations. The first applied translation creates the locale branch while preserving every existing locale.
 - To remove an existing survey language, load the `remove-survey-locale` operation contract and use that typed operation with the exact locale code. Do not delete translations one item at a time or remove the locale branch with raw JSON Patch.
-- Removing a locale deletes all respondent-facing survey and item translations stored under it. The final remaining locale cannot be removed.
+- Removing a locale deletes all respondent-facing survey and item translations stored under it.
 - 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.
+1. Use `survey_inspect` with `action: "localization"`, the source locale, and the target locale. Page until `nextCursor` is absent; this covers existing respondent-visible item and survey translation surfaces without one item-details call per item.
+2. Inspect item configuration separately only when the localization surface result or an audit indicates that the source survey itself is missing a visible content key. This includes choice-option labels, form-field labels, select-option labels, embedded-form labels, and validation copy.
 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.
@@ -23,5 +25,6 @@ Use this reference when the user asks to translate, localize, add a language, or
 ## 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.
+- Split only an oversized localization into independent, coherent chunks by section or item set. Each successful chunk updates the request-scoped draft for the next inspection.
+- After each chunk, call the localization inspection again with `missingOnly: true` and no cursor, because a draft change invalidates offsets into the previous missing-only result. Completion means it returns no remaining source surfaces for the target locale.
 - 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/source-material-surveys.md

@@ -18,16 +18,17 @@ Use this reference when the user asks to implement, recreate, convert, import, o
 - 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 bounded mutation calls rather than omitting details. Each successful call automatically extends the same turn draft.
+- Preserve question order, numbering intent, and section structure. For long sources, use multiple bounded mutation calls rather than omitting details. Bounded applies to each call, not the whole assistant turn; each successful call automatically extends the same turn draft.
 - 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.
+- On a later continuation turn, load the original stored attachment before conversational recall. When the relevant location is known, request the exact one-based PDF page range and a short section/question focus; the complete original remains authoritative.
+- 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 in the same assistant turn while capacity remains instead of constructing one very large call or stopping to restate the plan. Task size alone is not a blocker.
 
 ## 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 a simple `formItem` preset for a single text, long-text, number, slider, dropdown, date, or switch response. Use custom form mode for grouped personal data, tables, repeated inputs, contact details, or unsupported compound controls.
 - Prefer the supported semantic field type for the respondent value instead of copying the paper
   form's box layout. Use one `datepicker` with mode `year-month-day` for an ordinary full calendar
   date; use separate day/month/year fields only when the source measures those components
@@ -65,4 +66,5 @@ Use this reference when the user asks to implement, recreate, convert, import, o
 - 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.
+- 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 continue with the next chunk in the same turn. State what remains only if a concrete blocker or reported execution limit prevents further work.
+- When a successful change says verification is required, inspect the exact affected targets or run the deterministic audit before claiming completion. Validation proves the operation contract, not complete fidelity to the supplied source.

package/dist/{request-context-BBzU3VdG.mjs → request-context-BEjnaaFr.mjs}

@@ -1,5 +1,5 @@
-import { B as surveyDocumentVersionSchema, L as surveyAssistantSnapshotPayloadSchema } from "./protocol-DpCYmCjr.mjs";
-import { Q as createSurveyAssistantEngineContext } from "./engine-0AJrv0hI.mjs";
+import { H as surveyDocumentVersionSchema, o as surveyAssistantApplyOutcomeSchema, z as surveyAssistantSnapshotPayloadSchema } from "./protocol-DATvkr1S.mjs";
+import { Q as createSurveyAssistantEngineContext } from "./engine-CWTuN3o2.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
@@ -11,6 +11,10 @@ const parseSurveyAssistantPreviousSettledVersion = (value) => {
 	if (value === void 0 || value === null) return null;
 	return surveyDocumentVersionSchema.parse(value);
 };
+const parseSurveyAssistantPreviousApplyOutcome = (value) => {
+	if (value === void 0 || value === null) return null;
+	return surveyAssistantApplyOutcomeSchema.parse(value);
+};
 const deriveSurveyAssistantDocumentTransition = ({ current, previous }) => {
 	if (!current) return void 0;
 	if (!previous) return { status: "no-baseline" };
@@ -38,7 +42,7 @@ const deriveSurveyAssistantDocumentTransition = ({ current, previous }) => {
 		capabilitiesChanged
 	};
 };
-const buildSurveyAssistantRequestContext = ({ turnDraft, identity, snapshot, previousSettledVersion = null, trustedCapabilities = defaultSurveyAssistantCapabilitySet, attachmentAccess, modelAttachments = [], modelSelection }) => {
+const buildSurveyAssistantRequestContext = ({ turnDraft, identity, snapshot, previousSettledVersion = null, trustedCapabilities = defaultSurveyAssistantCapabilitySet, attachmentAccess, modelAttachments = [], modelSelection, previousApplyOutcome }) => {
 	const requestContext = new RequestContext();
 	requestContext.set("invocation", { kind: "chat" });
 	requestContext.set("turnId", turnDraft.turnId);
@@ -58,6 +62,7 @@ const buildSurveyAssistantRequestContext = ({ turnDraft, identity, snapshot, pre
 	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 (previousApplyOutcome) requestContext.set("previousApplyOutcome", previousApplyOutcome);
 	if (!snapshot) return requestContext;
 	const engineContext = createSurveyAssistantEngineContext(snapshot, trustedCapabilities);
 	turnDraft.initialize(engineContext);
@@ -81,6 +86,6 @@ const requireSurveyAssistantTurnState = (requestContext) => {
 	};
 };
 //#endregion
-export { parseSurveyAssistantSnapshot as a, parseSurveyAssistantPreviousSettledVersion as i, deriveSurveyAssistantDocumentTransition as n, requireSurveyAssistantTurnState as o, getSurveyAssistantEngineContext as r, buildSurveyAssistantRequestContext as t };
+export { parseSurveyAssistantPreviousSettledVersion as a, parseSurveyAssistantPreviousApplyOutcome as i, deriveSurveyAssistantDocumentTransition as n, parseSurveyAssistantSnapshot as o, getSurveyAssistantEngineContext as r, requireSurveyAssistantTurnState as s, buildSurveyAssistantRequestContext as t };
 
-//# sourceMappingURL=request-context-BBzU3VdG.mjs.map
+//# sourceMappingURL=request-context-BEjnaaFr.mjs.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"request-context-BEjnaaFr.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 type { OpenAICompatibleConfig } from \"@mastra/core/llm\";\nimport {\n  surveyAssistantSnapshotPayloadSchema,\n  surveyAssistantApplyOutcomeSchema,\n  surveyDocumentVersionSchema,\n  type SurveyAssistantApplyOutcome,\n  type SurveyDocumentSnapshot,\n  type SurveyDocumentVersion,\n} from \"../protocol\";\nimport {\n  createSurveyAssistantEngineContext,\n  TurnSurveyDraft,\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  surveyId?: string;\n  threadId: string;\n}\n\nexport interface SurveyAssistantModelSelection {\n  id: string;\n  model: string | OpenAICompatibleConfig;\n}\n\nexport type SurveyAssistantDocumentTransition =\n  | { status: \"no-baseline\" }\n  | {\n      status: \"session-changed\";\n      previousHistoryIndex: number;\n      currentHistoryIndex: number;\n    }\n  | {\n      status: \"unchanged\";\n      previousHistoryIndex: number;\n      currentHistoryIndex: number;\n      capabilitiesChanged: boolean;\n    }\n  | {\n      status: \"changed\";\n      previousHistoryIndex: number;\n      currentHistoryIndex: number;\n      historyDirection: \"backward\" | \"forward\" | \"same-index\";\n      recordedSources: Array<\"user\" | \"system\" | \"assistant\">;\n      capabilitiesChanged: boolean;\n    };\n\nexport interface SurveyAssistantRequestContext {\n  invocation: SurveyAssistantInvocationContext;\n  turnId: string;\n  turnDraft: TurnSurveyDraft;\n  identity: SurveyAssistantIdentityContext;\n  authenticatedResourceId?: string;\n  authorizedThreadId?: string;\n  applyPolicy?: \"auto\" | \"review\" | \"deny\";\n  mastra__resourceId?: string;\n  mastra__threadId?: string;\n  documentTransition?: SurveyAssistantDocumentTransition;\n  engineContext?: SurveyAssistantEngineContext;\n  documentSnapshot?: SurveyDocumentSnapshot;\n  modelAttachments?: SurveyAssistantModelAttachment[];\n  attachmentAccess?: SurveyAssistantAttachmentAccess;\n  modelSelection?: SurveyAssistantModelSelection;\n  previousApplyOutcome?: SurveyAssistantApplyOutcome;\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 parseSurveyAssistantPreviousSettledVersion = (\n  value: unknown,\n): SurveyDocumentVersion | null => {\n  if (value === undefined || value === null) {\n    return null;\n  }\n\n  return surveyDocumentVersionSchema.parse(value);\n};\n\nexport const parseSurveyAssistantPreviousApplyOutcome = (\n  value: unknown,\n): SurveyAssistantApplyOutcome | null => {\n  if (value === undefined || value === null) {\n    return null;\n  }\n\n  return surveyAssistantApplyOutcomeSchema.parse(value);\n};\n\nexport const deriveSurveyAssistantDocumentTransition = ({\n  current,\n  previous,\n}: {\n  current: SurveyDocumentSnapshot | null;\n  previous: SurveyDocumentVersion | null;\n}): SurveyAssistantDocumentTransition | undefined => {\n  if (!current) return undefined;\n  if (!previous) return { status: \"no-baseline\" };\n\n  const previousHistoryIndex = previous.historyIndex;\n  const currentHistoryIndex = current.version.historyIndex;\n  if (previous.sessionId !== current.version.sessionId) {\n    return {\n      status: \"session-changed\",\n      previousHistoryIndex,\n      currentHistoryIndex,\n    };\n  }\n\n  const capabilitiesChanged = previous.capabilityDigest !== current.version.capabilityDigest;\n  if (previous.contentHash === current.version.contentHash) {\n    return {\n      status: \"unchanged\",\n      previousHistoryIndex,\n      currentHistoryIndex,\n      capabilitiesChanged,\n    };\n  }\n\n  const historyDirection =\n    currentHistoryIndex > previousHistoryIndex\n      ? \"forward\"\n      : currentHistoryIndex < previousHistoryIndex\n        ? \"backward\"\n        : \"same-index\";\n  const recordedSources =\n    historyDirection === \"forward\"\n      ? [\n          ...new Set(\n            (current.ui.history?.recent ?? [])\n              .filter(\n                (entry) => entry.index > previousHistoryIndex && entry.index <= currentHistoryIndex,\n              )\n              .flatMap((entry) => (entry.source ? [entry.source] : [])),\n          ),\n        ]\n      : [];\n\n  return {\n    status: \"changed\",\n    previousHistoryIndex,\n    currentHistoryIndex,\n    historyDirection,\n    recordedSources,\n    capabilitiesChanged,\n  };\n};\n\nexport const buildSurveyAssistantRequestContext = ({\n  turnDraft,\n  identity,\n  snapshot,\n  previousSettledVersion = null,\n  trustedCapabilities = defaultSurveyAssistantCapabilitySet,\n  attachmentAccess,\n  modelAttachments = [],\n  modelSelection,\n  previousApplyOutcome,\n}: {\n  turnDraft: TurnSurveyDraft;\n  identity: SurveyAssistantIdentityContext;\n  snapshot: SurveyDocumentSnapshot | null;\n  previousSettledVersion?: SurveyDocumentVersion | null;\n  trustedCapabilities?: SurveyAssistantCapabilitySet;\n  attachmentAccess?: SurveyAssistantAttachmentAccess;\n  modelAttachments?: SurveyAssistantModelAttachment[];\n  modelSelection?: SurveyAssistantModelSelection;\n  previousApplyOutcome?: SurveyAssistantApplyOutcome | null;\n}): RequestContext<SurveyAssistantRequestContext> => {\n  const requestContext = new RequestContext<SurveyAssistantRequestContext>();\n\n  requestContext.set(\"invocation\", { kind: \"chat\" });\n  requestContext.set(\"turnId\", turnDraft.turnId);\n  requestContext.set(\"turnDraft\", turnDraft);\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  const documentTransition = deriveSurveyAssistantDocumentTransition({\n    current: snapshot,\n    previous: previousSettledVersion,\n  });\n  if (documentTransition) {\n    requestContext.set(\"documentTransition\", documentTransition);\n  }\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  if (previousApplyOutcome) {\n    requestContext.set(\"previousApplyOutcome\", previousApplyOutcome);\n  }\n\n  if (!snapshot) {\n    return requestContext;\n  }\n\n  const engineContext = createSurveyAssistantEngineContext(snapshot, trustedCapabilities);\n  turnDraft.initialize(engineContext);\n  requestContext.set(\"documentSnapshot\", snapshot);\n  requestContext.set(\"engineContext\", engineContext);\n\n  return requestContext;\n};\n\n/**\n * Returns the materialized request-local survey state. The immutable\n * engineContext remains available as the turn baseline, while every tool uses\n * this accessor so successful same-turn mutations are immediately visible.\n */\nexport const getSurveyAssistantEngineContext = (\n  requestContext: RequestContext<SurveyAssistantRequestContext> | undefined,\n): SurveyAssistantEngineContext | undefined =>\n  requestContext?.get(\"turnDraft\")?.context ?? requestContext?.get(\"engineContext\");\n\nexport const requireSurveyAssistantTurnState = (\n  requestContext: RequestContext<SurveyAssistantRequestContext> | undefined,\n) => {\n  const turnId = requestContext?.get(\"turnId\");\n  const turnDraft = requestContext?.get(\"turnDraft\");\n  if (!turnId || !turnDraft || turnDraft.turnId !== turnId) {\n    throw new Error(\"Survey assistant turn context is unavailable or inconsistent.\");\n  }\n\n  return { turnId, turnDraft };\n};\n"],"mappings":";;;;;AAmFA,MAAa,gCAAgC,UAAkD;AAC7F,KAAI,UAAU,KAAA,KAAa,UAAU,KACnC,QAAO;AAGT,QAAO,qCAAqC,MAAM,MAAM;;AAG1D,MAAa,8CACX,UACiC;AACjC,KAAI,UAAU,KAAA,KAAa,UAAU,KACnC,QAAO;AAGT,QAAO,4BAA4B,MAAM,MAAM;;AAGjD,MAAa,4CACX,UACuC;AACvC,KAAI,UAAU,KAAA,KAAa,UAAU,KACnC,QAAO;AAGT,QAAO,kCAAkC,MAAM,MAAM;;AAGvD,MAAa,2CAA2C,EACtD,SACA,eAImD;AACnD,KAAI,CAAC,QAAS,QAAO,KAAA;AACrB,KAAI,CAAC,SAAU,QAAO,EAAE,QAAQ,eAAe;CAE/C,MAAM,uBAAuB,SAAS;CACtC,MAAM,sBAAsB,QAAQ,QAAQ;AAC5C,KAAI,SAAS,cAAc,QAAQ,QAAQ,UACzC,QAAO;EACL,QAAQ;EACR;EACA;EACD;CAGH,MAAM,sBAAsB,SAAS,qBAAqB,QAAQ,QAAQ;AAC1E,KAAI,SAAS,gBAAgB,QAAQ,QAAQ,YAC3C,QAAO;EACL,QAAQ;EACR;EACA;EACA;EACD;CAGH,MAAM,mBACJ,sBAAsB,uBAClB,YACA,sBAAsB,uBACpB,aACA;AAcR,QAAO;EACL,QAAQ;EACR;EACA;EACA;EACA,iBAjBA,qBAAqB,YACjB,CACE,GAAG,IAAI,KACJ,QAAQ,GAAG,SAAS,UAAU,EAAE,EAC9B,QACE,UAAU,MAAM,QAAQ,wBAAwB,MAAM,SAAS,oBACjE,CACA,SAAS,UAAW,MAAM,SAAS,CAAC,MAAM,OAAO,GAAG,EAAE,CAAE,CAC5D,CACF,GACD,EAAE;EAQN;EACD;;AAGH,MAAa,sCAAsC,EACjD,WACA,UACA,UACA,yBAAyB,MACzB,sBAAsB,qCACtB,kBACA,mBAAmB,EAAE,EACrB,gBACA,2BAWmD;CACnD,MAAM,iBAAiB,IAAI,gBAA+C;AAE1E,gBAAe,IAAI,cAAc,EAAE,MAAM,QAAQ,CAAC;AAClD,gBAAe,IAAI,UAAU,UAAU,OAAO;AAC9C,gBAAe,IAAI,aAAa,UAAU;AAC1C,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;CAC3D,MAAM,qBAAqB,wCAAwC;EACjE,SAAS;EACT,UAAU;EACX,CAAC;AACF,KAAI,mBACF,gBAAe,IAAI,sBAAsB,mBAAmB;AAE9D,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;AAEtD,KAAI,qBACF,gBAAe,IAAI,wBAAwB,qBAAqB;AAGlE,KAAI,CAAC,SACH,QAAO;CAGT,MAAM,gBAAgB,mCAAmC,UAAU,oBAAoB;AACvF,WAAU,WAAW,cAAc;AACnC,gBAAe,IAAI,oBAAoB,SAAS;AAChD,gBAAe,IAAI,iBAAiB,cAAc;AAElD,QAAO;;;;;;;AAQT,MAAa,mCACX,mBAEA,gBAAgB,IAAI,YAAY,EAAE,WAAW,gBAAgB,IAAI,gBAAgB;AAEnF,MAAa,mCACX,mBACG;CACH,MAAM,SAAS,gBAAgB,IAAI,SAAS;CAC5C,MAAM,YAAY,gBAAgB,IAAI,YAAY;AAClD,KAAI,CAAC,UAAU,CAAC,aAAa,UAAU,WAAW,OAChD,OAAM,IAAI,MAAM,gEAAgE;AAGlF,QAAO;EAAE;EAAQ;EAAW"}

package/dist/server-agent.d.mts

@@ -1,5 +1,6 @@
-import { o as SurveyAssistantRequestContext, t as SURVEY_ASSISTANT_AGENT_ID } from "./constants-D-5m_KGB.mjs";
-import { n as surveyAssistantTools } from "./index-BcyfBeDj.mjs";
+import { g as SurveyChangeSetShape } from "./lifecycle-DWv5CiSu.mjs";
+import { o as SurveyAssistantRequestContext, t as SURVEY_ASSISTANT_AGENT_ID } from "./constants-DrGZXtQf.mjs";
+import { n as surveyAssistantTools } from "./index-DZk20e3k.mjs";
 import * as _$_mastra_core_agent0 from "@mastra/core/agent";
 import { Agent, AgentConfig } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
@@ -36,22 +37,13 @@ declare const createSurveyAssistantAgent: ({
   observationalMemory
 }: CreateSurveyAssistantAgentOptions) => Agent<"survey-assistant-agent", Readonly<{
   survey_inspect: _$_mastra_core_tools0.Tool<{
-    action: "current-context" | "search-items" | "item-details" | "assets" | "raw-json";
-    reason: unknown;
-    scopes: unknown;
-    query: unknown;
-    itemRef: unknown;
-    cursor: unknown;
-    outlineMode: unknown;
-    paths: unknown;
-    includeChildren: unknown;
-    includeItemConfig: unknown;
-    limit: unknown;
-  } | {
-    action: "current-context" | "search-items" | "item-details" | "assets" | "raw-json";
+    action: "current-context" | "search-items" | "item-details" | "localization" | "assets" | "raw-json";
     reason?: string | undefined;
     scopes?: ("summary" | "selected-item" | "outline" | "response-slots" | "ui-context" | "history")[] | undefined;
     query?: string | undefined;
+    sourceLocale?: string | undefined;
+    targetLocale?: string | undefined;
+    missingOnly?: boolean | undefined;
     itemRef?: string | undefined;
     cursor?: string | undefined;
     outlineMode?: "full" | "focused" | "children" | undefined;
@@ -61,7 +53,7 @@ declare const createSurveyAssistantAgent: ({
     limit?: number | undefined;
   }, {
     ok: boolean;
-    action: "current-context" | "search-items" | "item-details" | "assets" | "raw-json";
+    action: "current-context" | "search-items" | "item-details" | "localization" | "assets" | "raw-json";
     modelSummary: string;
     reason?: string | undefined;
     result?: unknown;
@@ -69,12 +61,12 @@ declare const createSurveyAssistantAgent: ({
   survey_change: _$_mastra_core_tools0.Tool<{
     summary: string;
     operations: unknown[];
-  }, unknown, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_change", unknown>;
+  }, SurveyChangeSetShape, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_change", unknown>;
   survey_authoring_reference: _$_mastra_core_tools0.Tool<{
     topic: string;
     itemType?: string | undefined;
     operationKind?: string | undefined;
-    detail?: "compact" | "full" | undefined;
+    detail?: "full" | "compact" | undefined;
     reason?: string | undefined;
   }, {
     ok: boolean;
@@ -83,7 +75,7 @@ declare const createSurveyAssistantAgent: ({
     content: string;
     itemType?: string | undefined;
     operationKind?: string | undefined;
-    detail?: "compact" | "full" | undefined;
+    detail?: "full" | "compact" | undefined;
   }, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_authoring_reference", unknown>;
   survey_expression: _$_mastra_core_tools0.Tool<{
     action: "context" | "prepare";
@@ -92,15 +84,45 @@ declare const createSurveyAssistantAgent: ({
     includeRawLocations?: boolean | undefined;
     summary?: string | undefined;
     mutations?: Record<string, unknown>[] | undefined;
-  }, unknown, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_expression", unknown>;
+  }, SurveyChangeSetShape | {
+    ok: boolean;
+    action: "context";
+    modelSummary: string;
+    listOrdering: Record<string, string>;
+    responseSlots: {
+      ref: string;
+      valueType?: string | undefined;
+    }[];
+    expressionLocations?: {
+      itemId: string;
+      key: string;
+      itemType: string;
+      rawIndex: number;
+      locations: string[];
+    }[] | undefined;
+  }, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_expression", unknown>;
   survey_attachment: _$_mastra_core_tools0.Tool<{
-    documentIds: string[];
+    documentIds?: string[] | undefined;
+    documentRequests?: {
+      documentId: string;
+      pages?: {
+        start: number;
+        end: number;
+      } | undefined;
+      focus?: string | undefined;
+    }[] | undefined;
   }, {
     loaded: {
       id: string;
       filename: string;
       mediaType: string;
+      pages?: {
+        start: number;
+        end: number;
+      } | undefined;
+      focus?: string | undefined;
     }[];
+    warnings?: string[] | undefined;
   }, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_attachment", unknown>;
   survey_audit: _$_mastra_core_tools0.Tool<{
     sourceLocale?: string | undefined;
@@ -120,7 +142,7 @@ declare const createSurveyAssistantAgent: ({
     name?: string | null | undefined;
     filename?: string | null | undefined;
     alt?: string | null | undefined;
-  }, unknown, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_asset", unknown>;
+  }, SurveyChangeSetShape, unknown, unknown, _$_mastra_core_tools0.ToolExecutionContext<unknown, unknown, unknown>, "survey_asset", unknown>;
 }>, undefined, SurveyAssistantRequestContext, _$_mastra_core_agent0.AgentEditorConfig | undefined>;
 //#endregion
 export { CreateSurveyAssistantAgentOptions, SURVEY_ASSISTANT_OBSERVATIONAL_MEMORY_DEFAULTS, SurveyAssistantObservationalMemoryOptions, createSurveyAssistantAgent, createSurveyAssistantObservationalMemoryOptions, surveyAssistantThreadAttachmentProcessor };

package/dist/server-agent.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"server-agent.d.mts","names":[],"sources":["../src/server/agent.ts"],"mappings":";;;;;;;;;cAuBa,wCAAA,EAA0C,cAAA;AAAA,KAqPlD,0BAAA,GAA6B,WAAA,QACzB,yBAAA,SACA,oBAAA,aAEP,6BAAA;AAAA,KAGG,4BAAA,GAA+B,WAAA,CAClC,WAAA,CAAY,qBAAA,QAA6B,MAAA;AAAA,KAyC/B,yCAAA,GAA4C,OAAA,CACtD,4BAAA;AAAA,KAIG,8CAAA,GAAiD,OAAA,CACpD,IAAA,CAAK,yCAAA;EAEL,KAAA,EAAO,WAAA,CAAY,yCAAA;AAAA;AAAA,cAGR,8CAAA;EAAA;;;;cAMA,+CAAA;EAAmD,KAAA;EAAA,WAAA;EAAA,UAAA;EAAA,GAAA;AAAA,GAK7D,8CAAA,KAAiD,yCAAA;AAAA,UAkCnC,iCAAA;EACf,KAAA,EAAO,0BAAA;EACP,MAAA,GAAS,0BAAA;EACT,mBAAA,GAAsB,yCAAA;AAAA;AAAA,cAGX,0BAAA;EAA8B,MAAA;EAAA,KAAA;EAAA;AAAA,GAIxC,iCAAA,KAAiC,KAAA,2BAAA,QAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uBAAA,qBAAA,CAAA,oBAAA"}
+{"version":3,"file":"server-agent.d.mts","names":[],"sources":["../src/server/agent.ts"],"mappings":";;;;;;;;;;cAwBa,wCAAA,EAA0C,cAAA;AAAA,KA4SlD,0BAAA,GAA6B,WAAA,QACzB,yBAAA,SACA,oBAAA,aAEP,6BAAA;AAAA,KAGG,4BAAA,GAA+B,WAAA,CAClC,WAAA,CAAY,qBAAA,QAA6B,MAAA;AAAA,KA8E/B,yCAAA,GAA4C,OAAA,CACtD,4BAAA;AAAA,KAIG,8CAAA,GAAiD,OAAA,CACpD,IAAA,CAAK,yCAAA;EAEL,KAAA,EAAO,WAAA,CAAY,yCAAA;AAAA;AAAA,cAGR,8CAAA;EAAA;;;;cAMA,+CAAA;EAAmD,KAAA;EAAA,WAAA;EAAA,UAAA;EAAA,GAAA;AAAA,GAK7D,8CAAA,KAAiD,yCAAA;AAAA,UAkCnC,iCAAA;EACf,KAAA,EAAO,0BAAA;EACP,MAAA,GAAS,0BAAA;EACT,mBAAA,GAAsB,yCAAA;AAAA;AAAA,cAGX,0BAAA;EAA8B,MAAA;EAAA,KAAA;EAAA;AAAA,GAIxC,iCAAA,KAAiC,KAAA,2BAAA,QAAA;;;;;;;;;;;;;;;;;;;;;;uBAAA,qBAAA,CAAA,oBAAA"}