wingfoil 0.2.1 → 0.3.0

package/dist/core/context.d.ts

@@ -1,33 +1,9 @@
-/**
- * Agent execution context assembly (task-037-role-task-scoped-context, REQ-STATE-05) — the
- * `directive-loader` + a minimal `context-builder` slice of
- * `spec-012-context-loader-relevance-filtering` (§1 "placement & responsibilities", §5 "Directive
- * resolution"). Satisfies REQ-STATE-05's Fit Criterion, verbatim: "The assembled context object
- * exposes separate `dna`, `memory`, `directives` sections; it contains 100% of the role's assigned
- * directives and 0 directives of other roles."
- *
- * **Archived elements are excluded** (REQ-STATE-06, the `{deprecated, superseded}` set ratified by
- * `dl-028-archived-states-excluded-from-context`): {@link assembleExecutionContext} drops a resolved
- * element whose `status` is archived, through the shared `isArchivedStatus` primitive rather than any
- * local notion of "archived". This closed `bug-010-deprecated-reaches-agent-context` — which this
- * header previously recorded as an open gap — together with the `wingfoil://memory/{type}` collection
- * Resource, the other surface that bug covered (`task-069-fix-archived-excluded-from-agent-context`).
- *
- * Still deliberately NOT the full spec-012 pipeline: no `ContextRequest`/`stateRef` pinning, no tiered
- * (T1–T4) Memory relevance ranking, no bounding caps, and no canonical byte-for-byte Markdown
- * serialization (§7). Those are split across sibling Wave-1 v0.2 tasks
- * (task-035-bounded-context-relevance REQ-PERF-05, task-038-deprecated-excluded-from-context
- * REQ-STATE-06) and v0.3 (`REQ-SYS-07`, `REQ-PERF-01`, `REQ-STATE-09`, the real `agent execute`
- * CLI/MCP surface) — see this task's Execution Notes for the full scope decision. This module wraps
- * only existing, already-shipped primitives: `loadDirectives`/`loadRolesYaml` (`./loaders`),
- * `findMemoryDocumentByTypeAndId` and `isArchivedStatus` (`../memory`, task-011/task-035) — no
- * scan/parse logic and no second status predicate is reimplemented here.
- */
-import { type MemoryDocumentSummary } from '../memory';
-import type { MemoryYaml } from '../memory/schema';
 import type { RolesYaml } from '../directives/schema';
-import type { DnaYaml } from '../dna/schema';
-import type { DirectiveFile } from './loaders';
+import type { Module, Paths, Project, Stacks, Team } from '../dna/schema';
+import { type MemoryDocumentSummary } from '../memory';
+import { type DirectiveFile } from './loaders';
+import { type ContextLimits, type RelevantMemoryDocument } from './relevance';
+import { type CoreResult } from './types';
 /**
  * The outcome of {@link resolveRoleDirectives}: the resolved directive files **and** any operator
  * diagnostics produced while resolving them.
@@ -98,90 +74,166 @@ export declare function selectDirectivesById(directiveFiles: readonly DirectiveF
  * `assignments`, the resolved sets are disjoint too (100% of one role's directives, 0% of the other's).
  */
 export declare function resolveRoleDirectives(directiveFiles: readonly DirectiveFile[], rolesYaml: RolesYaml, role: string): RoleDirectiveResolution;
-/** The active Memory element an execution context is scoped to (spec-012 §2 `ContextRequest.element`,
- * narrowed here to just `type`/`id` — this task does not implement the full `ContextRequest` shape). */
+/** The active Memory element a context is built for (`spec-012` §2 `ContextRequest.element`). */
 export interface ExecutionContextElement {
     readonly type: string;
     readonly id: string;
 }
 /**
- * The assembled execution context (REQ-STATE-05 Fit Criterion, P5.4.4 "a context object containing
- * distinct DNA, Memory, and Directives sections", "each section is individually addressable"): three
- * plain, independently-readable properties — `context.dna`, `context.memory`,
- * `context.directives` — never merged into one flat structure.
+ * `spec-012` §2's `ContextRequest`: everything a context is a function of. Nothing else is read — no
+ * clock, no environment, no working tree.
+ */
+export interface ContextRequest {
+    /** The role the agent executes under (`roles.yaml` binding, §5). */
+    readonly role: string;
+    /** The element the context is built for, usually a `task`. */
+    readonly element: ExecutionContextElement;
+    /** The revision every read is pinned to — a sha, or any name of one commit (`HEAD`, a branch). It is
+     * resolved once; the payload records the full sha. */
+    readonly stateRef: string;
+    /** Memory caps (§6); {@link DEFAULT_CONTEXT_LIMITS} when omitted. */
+    readonly limits?: ContextLimits;
+}
+/** The subject element as `stateRef` holds it (§3 stage 1, `resolve-element`). */
+export interface ContextElementDocument extends MemoryDocumentSummary {
+    readonly type: string;
+    readonly id: string;
+    /** As the document wrote it: a timestamp value is a {@link WrittenTimestamp} (its text as written), never a `Date`. */
+    readonly frontmatter: Record<string, unknown>;
+}
+/**
+ * The DNA sections `spec-012` §4 selects. Its own keys are inserted in `dna.yaml`'s declared order, and
+ * that order is the order §7 emits them in.
+ */
+export interface DnaSelection {
+    readonly project?: Project;
+    /** The element's `modules:`/`scope:` entries, or every module when it declares neither. */
+    readonly modules: readonly Module[];
+    /** Whole, technologies and methodologies (`dl-151` option A). */
+    readonly stacks?: Stacks;
+    readonly team?: Team;
+    /** Every category, `runs` included. */
+    readonly paths?: Paths;
+}
+/** A resolved directive and its Markdown body, which §7 carries verbatim. */
+export interface ContextDirective extends DirectiveFile {
+    readonly body: string;
+}
+/**
+ * The assembled execution context (P5.4.4 sc. 1: "distinct DNA, Memory, and Directives sections",
+ * "each section is individually addressable"; REQ-STATE-05). Each section is its own property, checked
+ * by {@link validateExecutionContext} before {@link serializeExecutionContext} renders it.
  */
 export interface ExecutionContext {
-    /** The full parsed `dna.yaml` (P5.4.4: DNA section — this task does not sub-select DNA sections by
-     * scope, unlike spec-012 §4's full `dna-loader`; that selection logic is out of this task's scope). */
-    readonly dna: DnaYaml;
-    /** This role's assigned directives + global, resolved by {@link resolveRoleDirectives}. */
-    readonly directives: readonly DirectiveFile[];
-    /** Memory relevant to `element` — today, exactly the element's own document (0 or 1 entries), and
-     * empty when that document is archived (REQ-STATE-06; see {@link assembleExecutionContext}); the
-     * full T1–T4 tiered relevance expansion is task-035/038/v0.3's scope (see the module doc comment). */
-    readonly memory: readonly MemoryDocumentSummary[];
-    /** Operator diagnostics gathered during assembly — currently only
-     * {@link RoleDirectiveResolution.warnings}: no-assignments (dl-029), dangling binding (dl-042 D),
-     * shadowed directive (dl-037 B.1). Diagnostics *about* the context, not content
-     * *of* it: spec-012 §7's canonical envelope has no warnings section, so this never enters the
-     * serialized payload. */
+    readonly role: string;
+    /** The full sha `ContextRequest.stateRef` resolved to. */
+    readonly stateRef: string;
+    /** §7 `## 1. Task`. */
+    readonly element: ContextElementDocument;
+    /** §7 `## 2. Project DNA`. */
+    readonly dna: DnaSelection;
+    /** §7 `## 3. Directives`: the role's directives and the globals, ascending by id ({@link resolveRoleDirectives}). */
+    readonly directives: readonly ContextDirective[];
+    /** §7 `## 4. Relevant Memory`, in §6 order and within the request's limits. Each `frontmatter` is as
+     * the document wrote it: a timestamp value is a {@link WrittenTimestamp} (its text as written), never a `Date`. */
+    readonly memory: readonly RelevantMemoryDocument[];
+    /** {@link RoleDirectiveResolution.warnings}: §5.1's three kinds in their fixed order. Diagnostics
+     * *about* the context, never part of the payload (dl-050, dl-051). */
     readonly warnings: readonly string[];
 }
-/** Inputs to {@link assembleExecutionContext} — every pillar's config, already loaded by its own
- * loader (`./loaders.ts`), plus the `role`/`element` the context is being assembled for. Nothing here
- * reads the filesystem itself beyond resolving `element` via `findMemoryDocumentByTypeAndId`. */
-export interface ExecutionContextInputs {
-    /** Project root the Memory element lookup resolves against (same root the pillar loaders were
-     * called with). */
-    readonly root: string;
-    readonly dna: DnaYaml;
-    readonly memoryYaml: MemoryYaml;
-    readonly directiveFiles: readonly DirectiveFile[];
-    readonly rolesYaml: RolesYaml;
-    readonly role: string;
-    readonly element: ExecutionContextElement;
+/** What {@link assembleExecutionContext} returns: the context, its §7 bytes, and the notes recorded
+ * while building it — diagnostics, kept out of `payload` like `context.warnings`. */
+export interface AssembledExecutionContext {
+    readonly context: ExecutionContext;
+    /** The canonical §7 payload: UTF-8, LF-only, exactly one trailing `\n`. */
+    readonly payload: string;
+    /** In §3 stage order: `no module matches the element's modules:/scope: (…); all modules included`
+     * when the element names modules and none matches (§4, ruling D3), then `no relevant Memory found
+     * for task` when nothing passed the relevance threshold (P5.3.3 sc. 3). */
+    readonly notes: readonly string[];
+}
+/**
+ * Validate an assembled context before anything uses it (P5.4.4 sc. 3). The first section that is
+ * absent, or not of its section's shape, refuses the context with `VALIDATION` and the scenario's
+ * message, verbatim: `invalid execution context: missing '<section>' section`. Sections are checked in
+ * §7 order — `element`, `dna`, `directives`, `memory` — so the refusal is deterministic.
+ */
+export declare function validateExecutionContext(candidate: unknown): CoreResult<ExecutionContext>;
+/**
+ * The payload's format version (`dl-150` option B, the `dl-149` format key): the first field of the
+ * header comment. A change to the bytes §7 pins is a new format.
+ */
+export declare const CONTEXT_PAYLOAD_FORMAT = 1;
+/**
+ * A YAML timestamp scalar exactly as its document wrote it (`bug-232`, review F1 of task-255): the
+ * frontmatter the payload carries holds one of these where js-yaml's default schema would hold a
+ * `Date`, so `2026-10-05`, `2026-10-05T00:00:00Z` and `2026-10-05 10:00:00 +02:00` are re-emitted
+ * unchanged rather than normalized to an instant.
+ */
+export declare class WrittenTimestamp {
+    /** The scalar's text, as written. */
+    readonly text: string;
+    constructor(
+    /** The scalar's text, as written. */
+    text: string);
+    /** The text as written, so `JSON.stringify` of a context renders the timestamp as the document did. */
+    toJSON(): string;
 }
 /**
- * Assemble a role- and task-scoped {@link ExecutionContext} (REQ-STATE-05) from already-loaded pillar
- * config. Given the same inputs and unchanged on-disk Memory content, the output is deep-equal across
- * calls: the function itself introduces no wall-clock, randomness, or unordered iteration
- * (REQ-SYS-07's discipline, applied to this narrower slice per REQ-STATE-05's own rationale "crisp,
- * low-noise context; determinism"), and `directives` is totally ordered by
- * {@link resolveRoleDirectives}.
+ * Render a context as `spec-012` §7's canonical Markdown payload, format {@link CONTEXT_PAYLOAD_FORMAT}
+ * (`dl-150` option B) — the bytes §8 holds identical across builds. Fixed headings in a fixed order,
+ * one blank line between blocks; frontmatter and DNA sections as fenced YAML with sorted keys; every
+ * directive and document body verbatim between `<!-- begin:<key> -->`/`<!-- end:<key> -->` markers
+ * (`<type>:<id>` for the element and Memory, `directive:<id>` for a directive), so a body's own
+ * headings never pass for §7's; ids rather than paths; the header names only the format, role, element
+ * and the resolved sha. `warnings` are not rendered.
+ *
+ * @throws Error `invalid execution context: missing '<section>' section` when `context` does not
+ *   validate ({@link validateExecutionContext}): a partial payload is never rendered. Error `invalid
+ *   role …` (or `element type`/`element id`/`directive id`) when a header field or a directive id holds
+ *   a control character or `-->`; `invalid Memory document <path>: …` for a document it cannot name;
+ *   `… cannot enter an execution context: its body holds the line … that closes it` for a body that
+ *   holds its own end marker.
+ */
+export declare function serializeExecutionContext(context: ExecutionContext): string;
+/**
+ * Build the execution context for `request` — `spec-012`'s single public entry (§1), the context
+ * `agent execute` (task-218) and the `{role}-session` Prompt (task-195) hand an agent.
+ *
+ * The §3 pipeline, every read at the one commit `request.stateRef` resolves to:
  *
- * `memory` resolves `element` via `findMemoryDocumentByTypeAndId`
- * (`task-011-mcp-resources-read-only`). Two properties of that primitive are inherited here and are
- * worth stating plainly:
+ * 1. **resolve-element**: every Memory document at that commit is read once
+ *    (`loadMemoryDocumentsAtRev`); the element is found in that snapshot. Absent → `NOT_FOUND`;
+ *    archived (`isArchivedStatus`) → `VALIDATION`, since an archived document never enters a context
+ *    (REQ-STATE-06). A `draft` element assembles.
+ * 2. **load-dna** (§4): see `selectDnaSections`; modules match by name or path (ruling D3, `bug-233`).
+ * 3. **load-directives** (§5): {@link resolveRoleDirectives} over the directives and `roles.yaml` at the
+ *    commit; its warnings become `context.warnings`.
+ * 4. **filter-memory** (§6): `selectRelevantMemoryDocuments` over the same snapshot, within
+ *    `request.limits`, among the documents §7 can carry (`dl-150` B, `payloadCandidates`): one with
+ *    no nameable `type` and `id` is left out, and reported only when it would have been relevant; one
+ *    whose body holds its own end marker is left out and reported. Both reports are
+ *    `W_MEMORY_UNREADABLE` lines on the success warnings, after the scan's own, in path order.
+ * 5. **validate** (P5.4.4 sc. 3) and **serialize** (§7).
  *
- * - It is **not** a single addressed read. It walks the Memory document paths derived from
- *   `memoryYaml` in sorted order and YAML-parses each document's frontmatter until one matches
- *   `element.type`/`element.id`, so cost grows with the size of the Memory tree (bounding that is
- *   `task-035-bounded-context-relevance`'s REQ-PERF-05 scope, not this task's).
- * - It therefore **can throw**. An `element` that matches nothing yields an empty `memory` array
- *   rather than an error — an unresolvable element is the caller's concern to surface — but a
- *   `ValidationError` (`E_YAML_PARSE_ERROR`) propagates out of assembly if any document visited
- *   during that walk has unparseable frontmatter. This function adds no `try`/`catch` of its own.
+ * A pillar file the commit does not hold leaves its section unset, and step 5 refuses the context:
+ * no `roles.yaml` → `missing 'directives'`, no `dna.yaml` → `missing 'dna'`, no `memory.yaml` →
+ * `missing 'element'`; the refusal's `details.cause` names the file (`no .wingfoil/roles.yaml at <sha>`).
+ * Before any read, a role or element field holding a control character or `-->`, or limits that are
+ * not positive integers, are refused as `VALIDATION`. After the reads, an element or directive body
+ * that holds its own end marker, or a directive id holding a control character or `-->`, refuses the
+ * context as `VALIDATION`: neither may be dropped (§5 never truncates a directive).
  *
- * `memory` **is** filtered by document status, in one direction only: a resolved element whose
- * `status` is archived — `{deprecated, superseded}`, per the shared {@link isArchivedStatus}
- * (`../memory`, the set ratified by `dl-028-archived-states-excluded-from-context`) — is dropped,
- * leaving `memory` empty. That is REQ-STATE-06's Fit Criterion as amended: "a `deprecated` or
- * `superseded` document never appears in an assembled agent context". The filter is applied to the
- * lookup's *result* rather than pushed into `findMemoryDocumentByTypeAndId`, because that same
- * primitive also serves `wingfoil://memory/{type}/{id}`, where explicit retrieval of archived content
- * must keep working.
+ * A subject the commit holds in a `format:` newer than this build reads is refused as `VALIDATION` with
+ * the `dl-149` `E_INVALID_FORMAT` text (task-195, `bug-263`), not reported as absent.
  *
- * `draft` is deliberately **not** excluded here, unlike in `./relevance.ts`. That module filters
- * *candidate* documents for relevance (spec-012 §6, which does bar `draft` from a context); this
- * function resolves the **subject** element the context is being assembled for (spec-012 §3's
- * `resolve-element` stage), and blanking the context for a task still in `draft` would defeat the
- * point of assembling it. dl-028 ratified the archived set as `{deprecated, superseded}` and did not
- * put `draft` in it.
+ * A Memory document that does not parse is left out and reported (task-171): as a `W_MEMORY_UNREADABLE`
+ * line in the result's `warnings` on success, and in `details.unreadable` of a `NOT_FOUND` refusal, so
+ * a subject that does not parse is not reported as merely absent. Neither reaches the payload.
  *
- * An archived element produces no warning: {@link ExecutionContext.warnings} carries
- * directive-resolution diagnostics only (dl-029, dl-037, dl-042), and adding an unratified entry would change a payload
- * REQ-SYS-07 governs. An archived element is therefore indistinguishable here from an unresolvable
- * one — both yield `memory: []`.
+ * Expected failures are returned, never thrown: a `stateRef` that is malformed or names no commit is
+ * the `RevisionError`'s own `CoreError`. A pillar file (`dna.yaml`, `roles.yaml`, a directive) that
+ * does not parse still throws `ValidationError`, as its loader does.
  */
-export declare function assembleExecutionContext(inputs: ExecutionContextInputs): ExecutionContext;
+export declare function assembleExecutionContext(root: string, request: ContextRequest): CoreResult<AssembledExecutionContext>;
 //# sourceMappingURL=context.d.ts.map

package/dist/core/context.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../../src/core/context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,OAAO,EAAmD,KAAK,qBAAqB,EAAE,MAAM,WAAW,CAAC;AACxG,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AACnD,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AAG7C,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAC;AAE/C;;;;;;;;;GASG;AACH,MAAM,WAAW,uBAAuB;IACtC,mGAAmG;IACnG,QAAQ,CAAC,UAAU,EAAE,SAAS,aAAa,EAAE,CAAC;IAC9C,+FAA+F;IAC/F,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAWD;;;GAGG;AACH,MAAM,WAAW,kBAAkB;IACjC,+EAA+E;IAC/E,QAAQ,CAAC,IAAI,EAAE,WAAW,CAAC,MAAM,EAAE,aAAa,CAAC,CAAC;IAClD,2GAA2G;IAC3G,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAoBD;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAClC,cAAc,EAAE,SAAS,aAAa,EAAE,EACxC,GAAG,CAAC,EAAE,WAAW,CAAC,MAAM,CAAC,GACxB,kBAAkB,CAuBpB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,qBAAqB,CACnC,cAAc,EAAE,SAAS,aAAa,EAAE,EACxC,SAAS,EAAE,SAAS,EACpB,IAAI,EAAE,MAAM,GACX,uBAAuB,CAczB;AAED;wGACwG;AACxG,MAAM,WAAW,uBAAuB;IACtC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;CACrB;AAED;;;;;GAKG;AACH,MAAM,WAAW,gBAAgB;IAC/B;2GACuG;IACvG,QAAQ,CAAC,GAAG,EAAE,OAAO,CAAC;IACtB,2FAA2F;IAC3F,QAAQ,CAAC,UAAU,EAAE,SAAS,aAAa,EAAE,CAAC;IAC9C;;0GAEsG;IACtG,QAAQ,CAAC,MAAM,EAAE,SAAS,qBAAqB,EAAE,CAAC;IAClD;;;;6BAIyB;IACzB,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAED;;iGAEiG;AACjG,MAAM,WAAW,sBAAsB;IACrC;uBACmB;IACnB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,GAAG,EAAE,OAAO,CAAC;IACtB,QAAQ,CAAC,UAAU,EAAE,UAAU,CAAC;IAChC,QAAQ,CAAC,cAAc,EAAE,SAAS,aAAa,EAAE,CAAC;IAClD,QAAQ,CAAC,SAAS,EAAE,SAAS,CAAC;IAC9B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,uBAAuB,CAAC;CAC3C;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyCG;AACH,wBAAgB,wBAAwB,CAAC,MAAM,EAAE,sBAAsB,GAAG,gBAAgB,CASzF"}
+{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../../src/core/context.ts"],"names":[],"mappings":"AAoBA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,KAAK,EAAW,MAAM,EAAE,KAAK,EAAE,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,eAAe,CAAC;AACnF,OAAO,EAKL,KAAK,qBAAqB,EAC3B,MAAM,WAAW,CAAC;AAMnB,OAAO,EAQL,KAAK,aAAa,EACnB,MAAM,WAAW,CAAC;AACnB,OAAO,EAGL,KAAK,aAAa,EAElB,KAAK,sBAAsB,EAC5B,MAAM,aAAa,CAAC;AAErB,OAAO,EAAmC,KAAK,UAAU,EAAE,MAAM,SAAS,CAAC;AAE3E;;;;;;;;;GASG;AACH,MAAM,WAAW,uBAAuB;IACtC,mGAAmG;IACnG,QAAQ,CAAC,UAAU,EAAE,SAAS,aAAa,EAAE,CAAC;IAC9C,+FAA+F;IAC/F,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAWD;;;GAGG;AACH,MAAM,WAAW,kBAAkB;IACjC,+EAA+E;IAC/E,QAAQ,CAAC,IAAI,EAAE,WAAW,CAAC,MAAM,EAAE,aAAa,CAAC,CAAC;IAClD,2GAA2G;IAC3G,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAoBD;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAClC,cAAc,EAAE,SAAS,aAAa,EAAE,EACxC,GAAG,CAAC,EAAE,WAAW,CAAC,MAAM,CAAC,GACxB,kBAAkB,CAuBpB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,qBAAqB,CACnC,cAAc,EAAE,SAAS,aAAa,EAAE,EACxC,SAAS,EAAE,SAAS,EACpB,IAAI,EAAE,MAAM,GACX,uBAAuB,CAczB;AAID,iGAAiG;AACjG,MAAM,WAAW,uBAAuB;IACtC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,MAAM,WAAW,cAAc;IAC7B,oEAAoE;IACpE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,8DAA8D;IAC9D,QAAQ,CAAC,OAAO,EAAE,uBAAuB,CAAC;IAC1C;0DACsD;IACtD,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,qEAAqE;IACrE,QAAQ,CAAC,MAAM,CAAC,EAAE,aAAa,CAAC;CACjC;AAED,kFAAkF;AAClF,MAAM,WAAW,sBAAuB,SAAQ,qBAAqB;IACnE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,uHAAuH;IACvH,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC/C;AAED;;;GAGG;AACH,MAAM,WAAW,YAAY;IAC3B,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,CAAC;IAC3B,2FAA2F;IAC3F,QAAQ,CAAC,OAAO,EAAE,SAAS,MAAM,EAAE,CAAC;IACpC,iEAAiE;IACjE,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,IAAI,CAAC,EAAE,IAAI,CAAC;IACrB,uCAAuC;IACvC,QAAQ,CAAC,KAAK,CAAC,EAAE,KAAK,CAAC;CACxB;AAED,6EAA6E;AAC7E,MAAM,WAAW,gBAAiB,SAAQ,aAAa;IACrD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAED;;;;GAIG;AACH,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,0DAA0D;IAC1D,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,uBAAuB;IACvB,QAAQ,CAAC,OAAO,EAAE,sBAAsB,CAAC;IACzC,8BAA8B;IAC9B,QAAQ,CAAC,GAAG,EAAE,YAAY,CAAC;IAC3B,qHAAqH;IACrH,QAAQ,CAAC,UAAU,EAAE,SAAS,gBAAgB,EAAE,CAAC;IACjD;uHACmH;IACnH,QAAQ,CAAC,MAAM,EAAE,SAAS,sBAAsB,EAAE,CAAC;IACnD;0EACsE;IACtE,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;CACtC;AAED;qFACqF;AACrF,MAAM,WAAW,yBAAyB;IACxC,QAAQ,CAAC,OAAO,EAAE,gBAAgB,CAAC;IACnC,2EAA2E;IAC3E,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB;;+EAE2E;IAC3E,QAAQ,CAAC,KAAK,EAAE,SAAS,MAAM,EAAE,CAAC;CACnC;AAqBD;;;;;GAKG;AACH,wBAAgB,wBAAwB,CAAC,SAAS,EAAE,OAAO,GAAG,UAAU,CAAC,gBAAgB,CAAC,CAMzF;AAED;;;GAGG;AACH,eAAO,MAAM,sBAAsB,IAAI,CAAC;AAExC;;;;;GAKG;AACH,qBAAa,gBAAgB;IAEzB,qCAAqC;IACrC,QAAQ,CAAC,IAAI,EAAE,MAAM;;IADrB,qCAAqC;IAC5B,IAAI,EAAE,MAAM;IAGvB,uGAAuG;IACvG,MAAM,IAAI,MAAM;CAGjB;AAgJD;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,yBAAyB,CAAC,OAAO,EAAE,gBAAgB,GAAG,MAAM,CAwC3E;AAsND;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AACH,wBAAgB,wBAAwB,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,cAAc,GAAG,UAAU,CAAC,yBAAyB,CAAC,CAwGrH"}