wingfoil 0.2.1

package/dist/core/index.d.ts

@@ -0,0 +1,388 @@
+import type { CoreModule } from './registry';
+/** This module's `dna.yaml` name (`core`) — the stable identifier surfaces and tests key it by. */
+export declare const MODULE_NAME: "core";
+export { DIRECTIVES_DIR_PATH, DNA_YAML_PATH, MEMORY_YAML_PATH, ROLES_YAML_PATH, loadDirectives, loadDirectivesAtHead, loadDnaYaml, loadDnaYamlAtHead, loadMemoryYaml, loadMemoryYamlAtHead, loadRolesYaml, loadRolesYamlAtHead, loadWorkflowsYaml, } from './loaders';
+export type { DirectiveFile, WorkflowsLoadResult } from './loaders';
+export { assembleExecutionContext, resolveRoleDirectives, selectDirectivesById } from './context';
+export { buildDirectiveListing, loadDirectiveListing, GLOBAL_ASSIGNMENT, UNASSIGNED_ASSIGNMENT, } from './directives-list';
+export type { DirectiveListEntry, DirectiveListing } from './directives-list';
+export type { DirectiveSelection, ExecutionContext, ExecutionContextElement, ExecutionContextInputs, RoleDirectiveResolution, } from './context';
+export * from './types';
+export * from './registry';
+export * from './exit-code';
+export * from './git-identity';
+export * from './approval-authority';
+export * from './require-reason';
+export * from './builtin-asset';
+export * from './confinement';
+export * from './usage-error';
+export { initWingfoilStorage, initWingfoilProject, WINGFOIL_ALREADY_INITIALIZED } from './init';
+export type { InitStorageValue, InitProjectValue } from './init';
+export { DEFAULT_CONTEXT_LIMITS, filterRelevantMemoryDocuments, NO_RELEVANT_MEMORY_NOTE, } from './relevance';
+export type { ContextLimits, RelevanceElementRef, RelevantMemoryDocument, RelevantMemoryResult, } from './relevance';
+export { commitMemoryTransition, prepareMemoryTransition, verifyCommittedScope } from './memory-transition';
+export type { PreparedMemoryTransition } from './memory-transition';
+export { resolveAddType } from './memory-add-type';
+export type { ResolvedAddType } from './memory-add-type';
+export { CONFIG_WRITE_CONTRACT, committedScopeError, requireAbsentTarget, requireUnmodifiedTarget, requireUnmodifiedTargets, undeclaredCommittedPaths, verifyCommittedPaths, } from './write-guard';
+export type { WriteTargetContract } from './write-guard';
+export { verifyBuiltinTemplates } from './builtin-integrity';
+export type { BuiltinIntegrityFailure, BuiltinTemplateKind, BuiltinTemplateSource } from './builtin-integrity';
+/** Params shared by every operation registered today — all of them are a bare pillar-config read. */
+export interface RootParams {
+    readonly root: string;
+}
+/**
+ * `wingfoil paths [category]` params (task-028-implement-paths-category) — the same generic seam
+ * `dnaShowFn` reads: `positional` is the bare CLI positional (`ParamsContext.positional`,
+ * `core/registry.ts` — task-026's single source of truth), interpreted here as the resource-path
+ * **category**; `list` is the parsed `--list` flag (`ParamsContext.flags.list`, spread into params by
+ * `buildParams`). `category`/`--list` are optional: an omitted category returns the whole `paths`
+ * node (what the MCP surface's mechanical zero-argument `wingfoil://paths` Resource gets — it has no
+ * per-request parameter, the same limitation `src/mcp/dna-resource.ts` documents for `dnaShow`).
+ * `--list` is accepted (spec-008/X_cli-cmds.md's "drill-down") but currently a no-op on the returned
+ * value: a DNA `paths` category is already a flat `string[]` with nothing coarser to collapse to, and
+ * spec-005-cli-command-contract §4's own worked example (`paths sources --format json` ->
+ * `{"category":"sources","paths":[...]}`) shows the full list without `--list` either — so there is
+ * no approved "collapsed" shape to switch away from. */
+export interface PathsParams {
+    readonly root: string;
+    readonly positional?: string;
+    readonly list?: boolean;
+}
+/** `wingfoil paths <category>` success shape — spec-005-cli-command-contract §4's worked example,
+ * verbatim (`{"category":"sources","paths":["src/cli","src/core"]}`). */
+export interface PathsShowResult {
+    readonly category: string;
+    readonly paths: readonly string[];
+}
+/**
+ * `dna set <path> --value <v>` params (P2.1, task-025-implement-dna-set) — the first mutating
+ * operation. `positionals` is the full CLI positional list (`ParamsContext.positionals`,
+ * `core/registry.ts`): `positionals[0]` is the dotted path and is the ONLY positional the verb reads.
+ *
+ * The value moved out of `positionals[1]` into `--value` in `task-093`, per
+ * `dl-082-cli-parameter-shape`: a positional carries the identity of the target, an option carries a
+ * named attribute of the action. The path is the target; the value was an attribute in positional
+ * clothing. See {@link DnaMutationParams} — the four verbs now share one parameter shape.
+ */
+export interface DnaSetParams {
+    readonly root: string;
+    readonly positionals?: readonly string[];
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * `dna add|remove|update` params (task-093). The **path** is `positionals[0]` — it identifies the
+ * target, and `dl-082-cli-parameter-shape` is the rule that puts a target in a positional. Everything
+ * else rides the value-bearing option seam `memory add --type … --title …` established
+ * (`ParamsContext.options`, `core/registry.ts`): `--value` is the payload, and every remaining option
+ * is a field of the entry the path names. Identical in shape to {@link DnaSetParams}, which is the
+ * point — all four DNA verbs state their parameters the same way, and the same way the other nine
+ * `memory`/`paths` commands already did (`dl-082` E2).
+ */
+export interface DnaMutationParams {
+    readonly root: string;
+    readonly positionals?: readonly string[];
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * The `--entry-<field>` namespace, re-exported from the DNA pillar (`src/dna/path.ts`), which owns it
+ * because it owns the derivation: the option set is read off `spec-002`'s entry schemas, and the
+ * refusal messages `src/dna/mutate.ts` writes have to spell those options the same way this module
+ * registers them. Re-exported rather than moved-and-forgotten so `src/core`'s public surface is
+ * unchanged (`spec-006` §1: the pillar is a leaf, and `src/core` is what both adapters import).
+ */
+export { DNA_ENTRY_OPTION_PREFIX, dnaEntryOptionName, dnaEntryFieldOfOption } from '../dna/path';
+/**
+ * `wingfoil memory add` params (P1.3, task-020-implement-memory-add) — the FIRST Memory-document
+ * mutation. `options` is the value-bearing-option seam this task establishes
+ * (`ParamsContext.options`, `core/registry.ts`), read as `--type`/`--title`/`--tags`. The MCP surface
+ * never populates it (task-030 wires the Tool input schema); a call with no options simply has all
+ * three absent, which the required checks below reject as usage errors.
+ */
+export interface MemoryAddParams {
+    readonly root: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * `wingfoil memory search [keyword]` params (P1.5, task-021-implement-memory-search) — reuses
+ * task-026's generic bare `ParamsContext.positional` seam for the free-text keyword (mirroring
+ * `dna show`'s `section`/`paths`'s `category`) and task-020's value-bearing `ParamsContext.options`
+ * seam for the `--tag`/`--status`/`--type` metadata filters (mirroring `memoryAdd`'s `--type`/
+ * `--title`/`--tags`). The MCP surface's mechanical zero-argument `wingfoil://memory/search` Resource
+ * (spec-006 §3) never populates either field (see `ParamsContext.positional`/`.options`'s own doc
+ * comments) — reading it degenerates to the "browse everything, no filter" call {@link memorySearchFn}
+ * already treats an omitted keyword as; see this task's Execution Notes for why that is the correct
+ * reading of spec-006's already-approved `memorySearch` row, not a workaround.
+ */
+export interface MemorySearchParams {
+    readonly root: string;
+    readonly positional?: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * One `wingfoil memory search` result entry — the fields a CLI/MCP consumer needs to identify and
+ * open the matched document, without re-reading the file (P1.5; spec-010-memory-frontmatter-schema's
+ * base fields). Deliberately drops `searchMemoryDocuments`'s internal `metadataMatch`/`bodyMatch`
+ * ranking flags: those exist to DRIVE this task's ordering (REQ-SYS-07), not to be part of its public
+ * result shape.
+ */
+export interface MemorySearchResultItem {
+    readonly path: string;
+    readonly id?: string;
+    readonly title?: string;
+    readonly type?: string;
+    readonly status?: string;
+    readonly tags: readonly string[];
+}
+/**
+ * `memory search` success shape: always the resolved `query` + the ranked `matches`, plus a `message`
+ * ONLY when `matches` is empty (P1.5 BDD "Error - query with no matches": zero results is still
+ * `coreOk` — exit 0, never a `CoreResult.error` — carrying the exact message "no documents matched the
+ * query"). A non-empty result carries no `message` field at all (not an empty string), so a
+ * `json`/`yaml` consumer can branch on its mere presence.
+ */
+export interface MemorySearchResult {
+    readonly query: string;
+    readonly matches: readonly MemorySearchResultItem[];
+    readonly message?: string;
+}
+/**
+ * `wingfoil memory history <id>` params (P1.10, task-049-memory-history). The document id rides the
+ * generic bare `ParamsContext.positional` seam (task-026) — spec-008-cli-grammar §7: a command whose
+ * noun already scopes the type takes the **bare `<id>`**, never a `<type>:<id>` element-ref, because
+ * ids are globally unique per `memory.yaml`'s `id_pattern`. Optional in the type only because the
+ * seam itself is: {@link memoryHistoryFn} rejects an absent id as a usage error (exit 2).
+ */
+export interface MemoryHistoryParams {
+    readonly root: string;
+    readonly positional?: string;
+}
+/**
+ * One entry of a document's audit trail as `wingfoil memory history` renders it — exactly the four
+ * things `P1.10-memory-history.feature` requires of every entry ("author, ISO-8601 timestamp, state
+ * change, and reason"), plus the `sha`/`subject`/`operation` that identify the commit it came from.
+ *
+ * Every field is derived, never stored: `author`/`timestamp` come from git's own `%an`/`%ae`/`%aI`
+ * (ADR-007 / P1.2 — the commit supplies the date, never file content), `from`/`to` from the
+ * document's own frontmatter `status:` at each commit, and `approver`/`reason` from the commit body's
+ * CLAUDE.md §5.1 trailers. `author` and `approver` are rendered in that same trailer notation
+ * (`Name <email>`, `Name <email> (role)`) because P1.10 exists to read exactly that convention back.
+ *
+ * Two independently-nullable fields, and neither is ever filled in by inference:
+ *
+ * - `approver` is `null` unless the commit carries a well-formed `Approver:` line — so it is null on
+ *   `add`/`submit` (subject-only by convention) and on `deprecate` (not an approval gate).
+ * - `reason` is `null` unless the commit carries a `Reason:` line, read independently of `Approver:`
+ *   (`parseCommitReason`) so a `deprecate` reason is not lost with the missing approver.
+ *
+ * `from` is `null` only on the element's creation entry (no prior state to name) — which is what
+ * "1 entry describing the creation" in the feature's edge scenario looks like. `to` is `null` only
+ * when the commit genuinely has no document to read — before the element's creation, or after a
+ * deletion. It used to be `null` at every commit older than a rename too, which was
+ * `bug-080-read-status-at-reads-the-current-path-at-pre-rename-commits` and is fixed: the walk now
+ * carries each commit's own path and `reconstructMemoryTransitions` reads at it.
+ */
+export interface MemoryHistoryEntryView {
+    readonly sha: string;
+    /** `Name <email>` — git's own author identity for this commit (`%an`/`%ae`). */
+    readonly author: string;
+    /** ISO-8601 author date (`%aI`), sourced from git, never from the document. */
+    readonly timestamp: string;
+    /** The CLAUDE.md §5.1 verb this commit's subject declares, or `null` if the subject is not in that shape. */
+    readonly operation: string | null;
+    /** The state before this commit; `null` on the creation entry. */
+    readonly from: string | null;
+    /** The state this commit put the document in, read from its frontmatter at that commit. */
+    readonly to: string | null;
+    /** `Name <email> (role)` from the commit's `Approver:` line, or `null` when it carries none. */
+    readonly approver: string | null;
+    /** The commit's `Reason:` line, or `null` when it carries none. */
+    readonly reason: string | null;
+    readonly subject: string;
+}
+/** `memory history` success shape: the resolved document (`id` + root-relative `path`) and its full
+ * audit trail, oldest first ("the output lists N entries in chronological order"). */
+export interface MemoryHistoryResult {
+    readonly id: string;
+    readonly path: string;
+    readonly entries: readonly MemoryHistoryEntryView[];
+}
+/**
+ * `wingfoil memory submit <id>` params (P1.6, task-045-memory-submit). The document id rides the bare
+ * `ParamsContext.positional` seam, per spec-008-cli-grammar §7 (a command whose noun scopes the type
+ * takes the bare `<id>`). Optional only because the seam is; an absent id is a usage error.
+ */
+export interface MemorySubmitParams {
+    readonly root: string;
+    readonly positional?: string;
+}
+/** `memory submit` success shape: the document and the transition it went through. */
+export interface MemorySubmitResult {
+    readonly id: string;
+    /** Root-relative path of the submitted document. */
+    readonly path: string;
+    readonly from: string;
+    readonly to: string;
+}
+/**
+ * `wingfoil memory approve <id> --reason <text>` params (P1.7, task-046-memory-approve). The document
+ * id rides the bare `ParamsContext.positional` seam (spec-008-cli-grammar §7) and `--reason` the
+ * value-bearing `options` seam (`./registry.ts`), the same one `memory add` reads `--type`/`--title`
+ * from. Both are optional only because the seams are; {@link memoryApproveFn} refuses either absent.
+ */
+export interface MemoryApproveParams {
+    readonly root: string;
+    readonly positional?: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/** `memory approve` success shape: the document and the transition it went through. */
+export interface MemoryApproveResult {
+    readonly id: string;
+    /** Root-relative path of the approved document. */
+    readonly path: string;
+    readonly from: string;
+    readonly to: string;
+}
+/**
+ * `wingfoil memory reject <id> --reason <text>` params (P1.8, task-047-memory-reject). The id rides
+ * the bare `ParamsContext.positional` seam (spec-008-cli-grammar §7 names
+ * `memory reject <id> --reason ...` explicitly); the reason rides task-020's value-bearing
+ * `ParamsContext.options` seam, exactly as `memory add`'s `--type`/`--title` do. Both are optional
+ * here only because the seams are — {@link memoryRejectFn} refuses either absence as a usage error
+ * (exit `2`).
+ */
+export interface MemoryRejectParams {
+    readonly root: string;
+    readonly positional?: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/** `memory reject` success shape: the document, the transition it went through, and the reason recorded. */
+export interface MemoryRejectResult {
+    readonly id: string;
+    /** Root-relative path of the rejected document. */
+    readonly path: string;
+    readonly from: string;
+    readonly to: string;
+    /** The `--reason` text, exactly as given — the same string written to frontmatter and to the commit body. */
+    readonly reason: string;
+}
+/**
+ * `wingfoil memory deprecate <id> [--reason <text>]` params (P1.9, task-048-memory-deprecate). The id
+ * rides the bare `ParamsContext.positional` seam (`spec-008-cli-grammar` §7 names
+ * `memory deprecate <id>` explicitly); the reason rides task-020's value-bearing
+ * `ParamsContext.options` seam. Unlike `memory reject`'s, this `--reason` is genuinely OPTIONAL —
+ * `spec-008` §2 ("optional elsewhere (e.g. `memory deprecate`)") and
+ * `dl-027-req-sec-04-deprecate-reason-scope` option (a), which narrowed REQ-SEC-04 to the approval
+ * gates — so {@link memoryDeprecateFn} reads it directly and never calls `requireReason`.
+ */
+export interface MemoryDeprecateParams {
+    readonly root: string;
+    readonly positional?: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/** `memory deprecate` success shape: the document, the edge it took, and the reason if one was given. */
+export interface MemoryDeprecateResult {
+    readonly id: string;
+    /** Root-relative path of the deprecated document — still present in the repository (P1.9 sc.1). */
+    readonly path: string;
+    readonly from: string;
+    readonly to: string;
+    /** The `--reason` text exactly as given, or `undefined` when the optional flag was omitted. */
+    readonly reason?: string;
+}
+/**
+ * `wingfoil directive create --name <name>` params (P3.1, task-050-directive-create). The name rides
+ * task-020's value-bearing `ParamsContext.options` seam (`core/registry.ts`), read as `--name` —
+ * NOT the bare positional seam: `X_cli-cmds.md` and the P3.1 BDD both spell the invocation
+ * `wingfoil directive create --name <NAME>`. `options` is optional only because the seam itself is;
+ * {@link directiveCreateFn} rejects an absent `--name` as a usage error (exit 2).
+ */
+export interface DirectiveCreateParams {
+    readonly root: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * `wingfoil directives list [--role <role>]` params (P3.4, task-053-directives-list). Reuses
+ * task-020's value-bearing `ParamsContext.options` seam for the optional `--role` filter, exactly as
+ * `memorySearch`'s `--tag`/`--status`/`--type` do. The MCP surface's mechanical zero-argument
+ * `wingfoil://directives/list` Resource never populates it (see `ParamsContext.options`), which
+ * degenerates to the unfiltered listing — the right default for a Resource that has no per-request
+ * parameter.
+ */
+export interface DirectivesListParams {
+    readonly root: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * `wingfoil directive assign --directive <id>[,<id>...] --role <role>` params (P3.2,
+ * task-051-directive-assign; the comma-separated list is P3.7,
+ * task-056-role-based-directive-assignment). Both values ride the value-bearing
+ * `ParamsContext.options` seam, as `directive create`'s `--name` does — the list travels *inside* the
+ * `--directive` value rather than as a repeated flag, because that seam carries one `string` per
+ * option name; {@link directiveAssignFn} rejects an absent or id-less one as a usage error (exit 2).
+ */
+export interface DirectiveAssignParams {
+    readonly root: string;
+    readonly options?: Readonly<Record<string, string>>;
+}
+/**
+ * `directive assign` success shape: the binding requested and the role's resulting assignment list.
+ *
+ * `directives` is always a **list** — the ids `--directive` named, trimmed, de-duplicated, in
+ * argument order — even for a single-id request. It was `directive: string` while only P3.2 existed
+ * (task-051); P3.7 (task-056) widened it rather than varying the payload's shape with the number of
+ * ids, which would be hostile to `--format json` consumers and to REQ-SYS-07's "output is a pure
+ * function of the input". `[AUTHORING]`: no spec pins this payload — spec-006 §3's row names the
+ * operation, not its result type.
+ */
+export interface DirectiveAssignResult {
+    readonly directives: readonly string[];
+    readonly role: string;
+    readonly assignments: readonly string[];
+}
+/**
+ * `wingfoil directive remove <name>` params (P3.3, task-052-directive-remove). Unlike `directive
+ * create`/`directive assign`, the name rides the generic bare `positional` seam (task-026's
+ * `ParamsContext.positional`), not `--name`: `X_cli-cmds.md` and the P3.3 BDD both spell the
+ * invocation `wingfoil directive remove <NAME>`, and spec-008-cli-grammar §7's bare-`<id>` rule
+ * applies — the noun already scopes what the argument is.
+ */
+export interface DirectiveRemoveParams {
+    readonly root: string;
+    readonly positional?: string;
+}
+/** `directive remove` success shape: the name removed and the root-relative path that was deleted. */
+export interface DirectiveRemoveResult {
+    readonly name: string;
+    readonly path: string;
+}
+/**
+ * The production `CoreModule` registry (spec-006 §2, §4). `src/cli`'s command registrar and
+ * `src/mcp`'s Tool/Resource registrar both import this exact array — see spec-006 §4.1: "no
+ * duplicated or hand-copied operation list in either surface module".
+ *
+ * SCOPE (task-006-dual-interface-shared-core, see the task's Execution Notes for the full
+ * rationale): only the core functions that already legitimately exist are wired in here today —
+ * task-004's three read-only per-pillar loaders that have a natural spec-006 §3 counterpart
+ * (`dnaShow`, `directivesList`, `workflowList` — all `mutates: false`), plus
+ * task-028-implement-paths-category's `paths` (P2.5, `wingfoil paths [category]`) — the first FLAT,
+ * no-verb command (`deriveVerb('paths', 'paths') === ''`, spec-008-cli-grammar §1) and the first to
+ * declare a `--list` flag (`CoreOperation.flags`, `./registry.ts`); its `category` rides the same
+ * generic bare-positional seam `dna show`'s `section` does (task-026's `ParamsContext.positional`),
+ * so no per-operation positional metadata is needed here. `loadMemoryYaml`
+ * is deliberately NOT registered as a `memory` module operation: it loads the Memory *pillar's own
+ * config* (`memory.yaml`'s types/state-machines), a different concept from spec-006 §3's `memory`
+ * module (which operates on Memory *documents* — `memoryAdd`, `memorySearch`, ...); registering it
+ * under a `memoryXxx` name would misrepresent it as the latter. As of
+ * task-025-implement-dna-set the registry has its FIRST mutating operation — `dna.dnaSet`
+ * (`mutates: true`, P2.1); `memory.memoryAdd` (P1.3, task-020), `directive.directiveCreate`
+ * (P3.1, task-050), `directive.directiveAssign` (P3.2, task-051) and `memory.memorySubmit` (P1.6,
+ * task-045) have since joined it, and the remaining spec-006 §3 mutating functions
+ * (`memoryApprove`, `directiveRemove`, `workflowStart`, ...) are still later tasks' scope. The
+ * REQ-SYS-05 parity test in `test/core/parity.test.ts` runs against this exact array, so it is now a
+ * live regression guard: each of those mutating ops must appear as both a CLI command and an MCP
+ * Tool, or the diff fails.
+ */
+export declare const CORE_MODULES: readonly CoreModule[];
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/core/index.ts"],"names":[],"mappings":"AAmFA,OAAO,KAAK,EAAU,UAAU,EAAc,MAAM,YAAY,CAAC;AAIjE,mGAAmG;AACnG,eAAO,MAAM,WAAW,EAAG,MAAe,CAAC;AAE3C,OAAO,EACL,mBAAmB,EACnB,aAAa,EACb,gBAAgB,EAChB,eAAe,EACf,cAAc,EAId,oBAAoB,EACpB,WAAW,EACX,iBAAiB,EACjB,cAAc,EACd,oBAAoB,EACpB,aAAa,EACb,mBAAmB,EACnB,iBAAiB,GAClB,MAAM,WAAW,CAAC;AACnB,YAAY,EAAE,aAAa,EAAE,mBAAmB,EAAE,MAAM,WAAW,CAAC;AACpE,OAAO,EAAE,wBAAwB,EAAE,qBAAqB,EAAE,oBAAoB,EAAE,MAAM,WAAW,CAAC;AAClG,OAAO,EACL,qBAAqB,EACrB,oBAAoB,EACpB,iBAAiB,EACjB,qBAAqB,GACtB,MAAM,mBAAmB,CAAC;AAC3B,YAAY,EAAE,kBAAkB,EAAE,gBAAgB,EAAE,MAAM,mBAAmB,CAAC;AAC9E,YAAY,EACV,kBAAkB,EAClB,gBAAgB,EAChB,uBAAuB,EACvB,sBAAsB,EACtB,uBAAuB,GACxB,MAAM,WAAW,CAAC;AACnB,cAAc,SAAS,CAAC;AACxB,cAAc,YAAY,CAAC;AAC3B,cAAc,aAAa,CAAC;AAC5B,cAAc,gBAAgB,CAAC;AAC/B,cAAc,sBAAsB,CAAC;AACrC,cAAc,kBAAkB,CAAC;AACjC,cAAc,iBAAiB,CAAC;AAChC,cAAc,eAAe,CAAC;AAC9B,cAAc,eAAe,CAAC;AAC9B,OAAO,EAAE,mBAAmB,EAAE,mBAAmB,EAAE,4BAA4B,EAAE,MAAM,QAAQ,CAAC;AAChG,YAAY,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,MAAM,QAAQ,CAAC;AACjE,OAAO,EACL,sBAAsB,EACtB,6BAA6B,EAC7B,uBAAuB,GACxB,MAAM,aAAa,CAAC;AACrB,YAAY,EACV,aAAa,EACb,mBAAmB,EACnB,sBAAsB,EACtB,oBAAoB,GACrB,MAAM,aAAa,CAAC;AACrB,OAAO,EAAE,sBAAsB,EAAE,uBAAuB,EAAE,oBAAoB,EAAE,MAAM,qBAAqB,CAAC;AAC5G,YAAY,EAAE,wBAAwB,EAAE,MAAM,qBAAqB,CAAC;AACpE,OAAO,EAAE,cAAc,EAAE,MAAM,mBAAmB,CAAC;AACnD,YAAY,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACzD,OAAO,EACL,qBAAqB,EACrB,mBAAmB,EACnB,mBAAmB,EACnB,uBAAuB,EACvB,wBAAwB,EACxB,wBAAwB,EACxB,oBAAoB,GACrB,MAAM,eAAe,CAAC;AACvB,YAAY,EAAE,mBAAmB,EAAE,MAAM,eAAe,CAAC;AACzD,OAAO,EAAE,sBAAsB,EAAE,MAAM,qBAAqB,CAAC;AAC7D,YAAY,EAAE,uBAAuB,EAAE,mBAAmB,EAAE,qBAAqB,EAAE,MAAM,qBAAqB,CAAC;AAE/G,qGAAqG;AACrG,MAAM,WAAW,UAAU;IACzB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAkCD;;;;;;;;;;;;wDAYwD;AACxD,MAAM,WAAW,WAAW;IAC1B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,IAAI,CAAC,EAAE,OAAO,CAAC;CACzB;AAED;yEACyE;AACzE,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,KAAK,EAAE,SAAS,MAAM,EAAE,CAAC;CACnC;AA2DD;;;;;;;;;GASG;AACH,MAAM,WAAW,YAAY;IAC3B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACzC,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAwLD;;;;;;;;GAQG;AACH,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACzC,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAkDD;;;;;;GAMG;AACH,OAAO,EAAE,uBAAuB,EAAE,kBAAkB,EAAE,qBAAqB,EAAE,MAAM,aAAa,CAAC;AA4BjG;;;;;;GAMG;AACH,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AA2FD;;;;;;;;;;GAUG;AACH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED;;;;;;GAMG;AACH,MAAM,WAAW,sBAAsB;IACrC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,CAAC,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,IAAI,EAAE,SAAS,MAAM,EAAE,CAAC;CAClC;AAED;;;;;;GAMG;AACH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,OAAO,EAAE,SAAS,sBAAsB,EAAE,CAAC;IACpD,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;CAC3B;AAqED;;;;;;GAMG;AACH,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;CAC9B;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,MAAM,WAAW,sBAAsB;IACrC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,gFAAgF;IAChF,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,+EAA+E;IAC/E,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,6GAA6G;IAC7G,QAAQ,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IAClC,kEAAkE;IAClE,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,2FAA2F;IAC3F,QAAQ,CAAC,EAAE,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,gGAAgG;IAChG,QAAQ,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,mEAAmE;IACnE,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IAC/B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED;sFACsF;AACtF,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,SAAS,sBAAsB,EAAE,CAAC;CACrD;AA6DD;;;;GAIG;AACH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;CAC9B;AAED,sFAAsF;AACtF,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,oDAAoD;IACpD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;CACrB;AAmDD;;;;;GAKG;AACH,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED,uFAAuF;AACvF,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,mDAAmD;IACnD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;CACrB;AAqED;;;;;;;GAOG;AACH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED,4GAA4G;AAC5G,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,mDAAmD;IACnD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,6GAA6G;IAC7G,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAoED;;;;;;;;GAQG;AACH,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED,yGAAyG;AACzG,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,mGAAmG;IACnG,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,+FAA+F;IAC/F,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;CAC1B;AAoED;;;;;;GAMG;AACH,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AA6DD;;;;;;;GAOG;AACH,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACrD;AAED;;;;;;;;;GASG;AACH,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,UAAU,EAAE,SAAS,MAAM,EAAE,CAAC;IACvC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,WAAW,EAAE,SAAS,MAAM,EAAE,CAAC;CACzC;AAmDD;;;;;;GAMG;AACH,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;CAC9B;AAED,sGAAsG;AACtG,MAAM,WAAW,qBAAqB;IACpC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AA2HD;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,eAAO,MAAM,YAAY,EAAE,SAAS,UAAU,EA4K7C,CAAC"}