agent-recall-core 3.4.46 → 3.4.48
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/helpers/handoff.d.ts.map +1 -1
- package/dist/helpers/handoff.js +17 -9
- package/dist/helpers/handoff.js.map +1 -1
- package/dist/helpers/journal-files.d.ts +24 -1
- package/dist/helpers/journal-files.d.ts.map +1 -1
- package/dist/helpers/journal-files.js +29 -10
- package/dist/helpers/journal-files.js.map +1 -1
- package/dist/helpers/journal-filter.d.ts +25 -0
- package/dist/helpers/journal-filter.d.ts.map +1 -1
- package/dist/helpers/journal-filter.js +12 -1
- package/dist/helpers/journal-filter.js.map +1 -1
- package/dist/index.d.ts +18 -9
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +45 -6
- package/dist/index.js.map +1 -1
- package/dist/retrieval/candidates.d.ts +339 -0
- package/dist/retrieval/candidates.d.ts.map +1 -0
- package/dist/retrieval/candidates.js +473 -0
- package/dist/retrieval/candidates.js.map +1 -0
- package/dist/retrieval/contradiction.d.ts +284 -0
- package/dist/retrieval/contradiction.d.ts.map +1 -0
- package/dist/retrieval/contradiction.js +343 -0
- package/dist/retrieval/contradiction.js.map +1 -0
- package/dist/retrieval/query-memory.d.ts +464 -0
- package/dist/retrieval/query-memory.d.ts.map +1 -0
- package/dist/retrieval/query-memory.js +1189 -0
- package/dist/retrieval/query-memory.js.map +1 -0
- package/dist/retrieval/scope.d.ts +75 -0
- package/dist/retrieval/scope.d.ts.map +1 -0
- package/dist/retrieval/scope.js +91 -0
- package/dist/retrieval/scope.js.map +1 -0
- package/dist/storage/corrections.d.ts +163 -2
- package/dist/storage/corrections.d.ts.map +1 -1
- package/dist/storage/corrections.js +147 -3
- package/dist/storage/corrections.js.map +1 -1
- package/dist/storage/lifecycle-telemetry.d.ts +20 -5
- package/dist/storage/lifecycle-telemetry.d.ts.map +1 -1
- package/dist/storage/lifecycle-telemetry.js +16 -5
- package/dist/storage/lifecycle-telemetry.js.map +1 -1
- package/dist/storage/session.d.ts +28 -1
- package/dist/storage/session.d.ts.map +1 -1
- package/dist/storage/session.js +41 -8
- package/dist/storage/session.js.map +1 -1
- package/dist/supabase/recall-backend.d.ts +26 -2
- package/dist/supabase/recall-backend.d.ts.map +1 -1
- package/dist/supabase/recall-backend.js +233 -27
- package/dist/supabase/recall-backend.js.map +1 -1
- package/dist/supabase/sync.d.ts +41 -0
- package/dist/supabase/sync.d.ts.map +1 -1
- package/dist/supabase/sync.js +46 -0
- package/dist/supabase/sync.js.map +1 -1
- package/dist/tools-logic/check.d.ts.map +1 -1
- package/dist/tools-logic/check.js +62 -36
- package/dist/tools-logic/check.js.map +1 -1
- package/dist/tools-logic/drill-down.d.ts +24 -0
- package/dist/tools-logic/drill-down.d.ts.map +1 -1
- package/dist/tools-logic/drill-down.js +36 -0
- package/dist/tools-logic/drill-down.js.map +1 -1
- package/dist/tools-logic/journal-cold-start.d.ts.map +1 -1
- package/dist/tools-logic/journal-cold-start.js +48 -9
- package/dist/tools-logic/journal-cold-start.js.map +1 -1
- package/dist/tools-logic/journal-list.d.ts +42 -0
- package/dist/tools-logic/journal-list.d.ts.map +1 -1
- package/dist/tools-logic/journal-list.js +60 -10
- package/dist/tools-logic/journal-list.js.map +1 -1
- package/dist/tools-logic/journal-read.d.ts.map +1 -1
- package/dist/tools-logic/journal-read.js +22 -13
- package/dist/tools-logic/journal-read.js.map +1 -1
- package/dist/tools-logic/journal-search.d.ts +58 -0
- package/dist/tools-logic/journal-search.d.ts.map +1 -1
- package/dist/tools-logic/journal-search.js +123 -92
- package/dist/tools-logic/journal-search.js.map +1 -1
- package/dist/tools-logic/palace-search.d.ts.map +1 -1
- package/dist/tools-logic/palace-search.js +30 -11
- package/dist/tools-logic/palace-search.js.map +1 -1
- package/dist/tools-logic/palace-walk.d.ts +10 -0
- package/dist/tools-logic/palace-walk.d.ts.map +1 -1
- package/dist/tools-logic/palace-walk.js +25 -16
- package/dist/tools-logic/palace-walk.js.map +1 -1
- package/dist/tools-logic/recall-insight.d.ts +20 -0
- package/dist/tools-logic/recall-insight.d.ts.map +1 -1
- package/dist/tools-logic/recall-insight.js +12 -1
- package/dist/tools-logic/recall-insight.js.map +1 -1
- package/dist/tools-logic/session-end.d.ts.map +1 -1
- package/dist/tools-logic/session-end.js +23 -7
- package/dist/tools-logic/session-end.js.map +1 -1
- package/dist/tools-logic/session-start.d.ts +85 -0
- package/dist/tools-logic/session-start.d.ts.map +1 -1
- package/dist/tools-logic/session-start.js +245 -108
- package/dist/tools-logic/session-start.js.map +1 -1
- package/dist/tools-logic/smart-recall.d.ts +87 -62
- package/dist/tools-logic/smart-recall.d.ts.map +1 -1
- package/dist/tools-logic/smart-recall.js +183 -508
- package/dist/tools-logic/smart-recall.js.map +1 -1
- package/dist/tools-logic/supersession.d.ts +63 -2
- package/dist/tools-logic/supersession.d.ts.map +1 -1
- package/dist/tools-logic/supersession.js +153 -48
- package/dist/tools-logic/supersession.js.map +1 -1
- package/dist/types.d.ts +12 -1
- package/dist/types.d.ts.map +1 -1
- package/dist/types.js +1 -1
- package/package.json +1 -1
|
@@ -1,6 +1,34 @@
|
|
|
1
1
|
/**
|
|
2
2
|
* smart_recall — unified cross-store search. v3.3.14
|
|
3
3
|
*
|
|
4
|
+
* ── WAVE 2 (2026-08-29/30, plywood SOP ecbd4351) ────────────────────────────
|
|
5
|
+
* Internals migrated onto the shared retrieval pipeline
|
|
6
|
+
* (`retrieval/query-memory.ts`'s `queryMemory()`). EXTERNAL CONTRACT
|
|
7
|
+
* UNCHANGED: same `SmartRecallInput`/`SmartRecallResult` shape, same
|
|
8
|
+
* feedback-rating footer, same archive-fallback/bridge/graph-walk behavior.
|
|
9
|
+
* The composition that used to live directly in this file — journalSearch +
|
|
10
|
+
* palaceSearch + recallInsight + archiveSearch, plus the 5 scattered scoring
|
|
11
|
+
* formulas below and the two-stage RRF fusion — now lives in
|
|
12
|
+
* `retrieval/query-memory.ts` as MANDATORY PIPELINE STAGES (fetch ->
|
|
13
|
+
* trust-filter -> tokenize+score -> scope -> rank/fuse -> fence). See that
|
|
14
|
+
* file's header comment for the full CHALLENGE-by-CHALLENGE design reasoning
|
|
15
|
+
* (why scoring stays per-tier/pluggable rather than unified into one formula;
|
|
16
|
+
* how the Wave-1 candidate superset is handled per source; why FENCE is not
|
|
17
|
+
* applied to this surface's per-item fields). This file now owns exactly the
|
|
18
|
+
* smart_recall-SPECIFIC post-pipeline concerns that do not generalize to
|
|
19
|
+
* other future `queryMemory()` consumers: confidence calibration
|
|
20
|
+
* (`calibratedConfidence`), the Beta-feedback multiplier + feedback log, the
|
|
21
|
+
* remote/local backend race + degraded-timeout handling, the Bridge
|
|
22
|
+
* drilldown, and the F4 archive-fallback's confidence GATE (the policy
|
|
23
|
+
* decision of *when* to call `queryArchiveFallback` — its fetch/score logic
|
|
24
|
+
* itself moved to query-memory.ts).
|
|
25
|
+
*
|
|
26
|
+
* The formulas described below (Fix 1-5b) are UNCHANGED in substance — they
|
|
27
|
+
* are simply now implemented in query-memory.ts's per-tier scoring functions
|
|
28
|
+
* and RANK/FUSE stage instead of inline here. Kept as historical/design
|
|
29
|
+
* documentation because the RATIONALE is still exactly why those formulas
|
|
30
|
+
* are what they are.
|
|
31
|
+
*
|
|
4
32
|
* ## Scoring Architecture (why it works this way)
|
|
5
33
|
*
|
|
6
34
|
* ### Problem with the old approach (< v3.3.14): Linear Score Fusion
|
|
@@ -25,7 +53,6 @@
|
|
|
25
53
|
* Formula: R(t) = e^(-t/S), where S = memory strength (days).
|
|
26
54
|
* Different memory types have different S values based on psychological research:
|
|
27
55
|
* - Journal (episodic, low meaning): S = 2 → 60% retained after 1 day
|
|
28
|
-
* - Knowledge/bug-fix (procedural): S = 180 → 99.4% retained after 1 day
|
|
29
56
|
* - Palace/decisions (semantic): S = 9999 → barely decays
|
|
30
57
|
* - Insight (conceptual): not time-based; uses confirmation count instead
|
|
31
58
|
* This replaces the uniform 0.95^days that treated all memory equally.
|
|
@@ -59,46 +86,22 @@
|
|
|
59
86
|
* duplicates (same id) could. A later "dedup by excerpt" pass then silently
|
|
60
87
|
* collapsed same-excerpt entries by first-inserted-wins, DISCARDING the other
|
|
61
88
|
* source's score entirely instead of summing it in.
|
|
62
|
-
* Fix: fusion is now TWO stages. Stage 1 (applyRRF,
|
|
63
|
-
*
|
|
64
|
-
*
|
|
65
|
-
*
|
|
66
|
-
*
|
|
67
|
-
*
|
|
68
|
-
*
|
|
69
|
-
* then re-keys those already-consolidated per-document entries by NORMALIZED
|
|
70
|
-
* EXCERPT CONTENT — the same identity notion the old post-hoc dedup pass
|
|
71
|
-
* already used to decide "same memory". Two per-document entries from
|
|
72
|
-
* different sources whose representative excerpt matches now land in the
|
|
73
|
-
* SAME canonical entry, so cross-source accumulation happens. Provenance
|
|
74
|
-
* from every contributing source is preserved via `alsoFoundIn` on the fused
|
|
75
|
-
* item (primary/display source is whichever source ran first — unchanged),
|
|
76
|
-
* rather than being dropped.
|
|
89
|
+
* Fix: fusion is now TWO stages. Stage 1 (applyRRF, keyed by `item.id`) still
|
|
90
|
+
* consolidates multiple hits from the SAME source document. Stage 2
|
|
91
|
+
* (fuseCanonical) then re-keys those already-consolidated per-document
|
|
92
|
+
* entries by NORMALIZED EXCERPT CONTENT. Provenance from every contributing
|
|
93
|
+
* source is preserved via `alsoFoundIn` on the fused item, rather than being
|
|
94
|
+
* dropped. (Both stages live in query-memory.ts now — see that file's
|
|
95
|
+
* `applyRRF`/`fuseCanonical`.)
|
|
77
96
|
*
|
|
78
97
|
* ### Fix 5b: insight excerpt is too low-entropy to be a fusion identity
|
|
79
98
|
* Stage 2's "normalized excerpt content" identity assumption (Fix 5) is
|
|
80
99
|
* sound for palace/journal, whose `excerpt` is a real matched text snippet.
|
|
81
100
|
* It was broken for the insight source: its excerpt was synthesized from
|
|
82
|
-
* ONLY `severity` + `applies_when
|
|
83
|
-
*
|
|
84
|
-
* insights sharing a severity + tag set produced byte-identical excerpts and
|
|
85
|
-
* silently fused into one — one insight vanished from results, and the
|
|
86
|
-
* survivor's score absorbed the other's RRF contribution with zero trace
|
|
87
|
-
* (same-source collisions don't show up in `alsoFoundIn`, which only records
|
|
88
|
-
* source NAMES). Fix: insight items now carry a separate `fusionKey`
|
|
101
|
+
* ONLY `severity` + `applies_when`, omitting the insight's own distinguishing
|
|
102
|
+
* `title` entirely. Fix: insight items now carry a separate `fusionKey`
|
|
89
103
|
* (`${title} [severity] tags`) that fuseCanonical() and the defensive dedup
|
|
90
|
-
* pass key on INSTEAD of `excerpt` when present
|
|
91
|
-
* comment on `SmartRecallResultItem`). The displayed `excerpt` stays terse —
|
|
92
|
-
* embedding `title` into it would duplicate title text in every consumer
|
|
93
|
-
* that reads `excerpt` directly (recall.ts's display line, the CLI's
|
|
94
|
-
* ambient-injection word-overlap scorer, consistency/conflict-scan's
|
|
95
|
-
* `title + excerpt` concatenation), which for the word-overlap scorer would
|
|
96
|
-
* also double-count title tokens and inflate insight relevance versus other
|
|
97
|
-
* sources. Palace/journal items leave `fusionKey` unset (falls back to
|
|
98
|
-
* `excerpt`, unchanged from Fix 5) — insights are a distinct "confirmed
|
|
99
|
-
* pattern" memory type that isn't expected to share literal content with a
|
|
100
|
-
* journal/palace excerpt, so this doesn't reopen the cross-source fusion
|
|
101
|
-
* Fix 5 was built for; it only stops insights colliding WITH EACH OTHER.
|
|
104
|
+
* pass key on INSTEAD of `excerpt` when present.
|
|
102
105
|
*/
|
|
103
106
|
import { type VerbatimKey } from "./drill-down.js";
|
|
104
107
|
export interface RecallFeedback {
|
|
@@ -125,9 +128,10 @@ export interface SmartRecallResultItem {
|
|
|
125
128
|
* canonical entry first (palace, then journal, then insight). Kept
|
|
126
129
|
* singular for backward compatibility with existing consumers.
|
|
127
130
|
* "archive" (F4, 2026-07-31) is DIFFERENT from the other three: it never
|
|
128
|
-
* competes inside
|
|
129
|
-
*
|
|
130
|
-
* palace/journal/insight is below medium (see
|
|
131
|
+
* competes inside the RRF fusion — it is appended separately by
|
|
132
|
+
* smartRecall() only when the fused top confidence from
|
|
133
|
+
* palace/journal/insight is below medium (see the archive-fallback gate
|
|
134
|
+
* below). */
|
|
131
135
|
source: "palace" | "journal" | "insight" | "archive";
|
|
132
136
|
/** Other sources that ALSO matched this same canonical memory (same
|
|
133
137
|
* normalized excerpt) during RRF fusion. Present only when the item was
|
|
@@ -136,25 +140,6 @@ export interface SmartRecallResultItem {
|
|
|
136
140
|
alsoFoundIn?: Array<"palace" | "journal" | "insight" | "archive">;
|
|
137
141
|
title: string;
|
|
138
142
|
excerpt: string;
|
|
139
|
-
/** Cross-source fusion identity override (Fix 5b). When present, fusion
|
|
140
|
-
* (fuseCanonical() + the defensive dedup pass) keys on THIS instead of
|
|
141
|
-
* `excerpt`. Needed for the insight source: its displayed `excerpt` is a
|
|
142
|
-
* terse `[severity] tags` summary — good for compact display, but too
|
|
143
|
-
* low-entropy to serve as a "same conceptual memory" signal, since two
|
|
144
|
-
* genuinely UNRELATED insights sharing a severity + applies_when tag set
|
|
145
|
-
* produce byte-identical excerpts. `fusionKey` embeds the insight's own
|
|
146
|
-
* distinguishing content (its `title`) so it can't collide with another
|
|
147
|
-
* insight's identity, WITHOUT duplicating that title into the displayed
|
|
148
|
-
* `excerpt` (which recall.ts, the CLI's ambient-injection word-overlap
|
|
149
|
-
* scorer, and consistency/conflict-scan's `title + excerpt` concatenation
|
|
150
|
-
* all consume directly — embedding title there would double-count title
|
|
151
|
-
* tokens for insights only, and would push `[severity] tags` out of the
|
|
152
|
-
* 80-char display truncation in recall.ts's formatResults()). Palace and
|
|
153
|
-
* journal items leave this unset — their raw excerpt is already a strong,
|
|
154
|
-
* content-derived identity signal (Fix 5's original design), and forcing
|
|
155
|
-
* a synthetic fusionKey there would risk breaking their genuine
|
|
156
|
-
* cross-source matches. */
|
|
157
|
-
fusionKey?: string;
|
|
158
143
|
score: number;
|
|
159
144
|
/** Human-readable confidence: "high", "medium", "low", "weak" */
|
|
160
145
|
confidence: string;
|
|
@@ -166,6 +151,32 @@ export interface SmartRecallResultItem {
|
|
|
166
151
|
room?: string;
|
|
167
152
|
date?: string;
|
|
168
153
|
severity?: string;
|
|
154
|
+
/**
|
|
155
|
+
* CONTRADICTION stage (Wave 5a, `retrieval/contradiction.ts`) — set ONLY
|
|
156
|
+
* when this item was detected as the STALE side of a same-tier version-
|
|
157
|
+
* token conflict with a sibling this result set could confidently order
|
|
158
|
+
* as more current. Holds the CURRENT sibling's `id`. Additive: absent on
|
|
159
|
+
* every item unaffected by the stage. W5a salvage (2026-08-31, HIGH-3):
|
|
160
|
+
* this field is threaded straight through from `QueryMemoryItem` by
|
|
161
|
+
* `localRecallSearch` below — previously computed but silently dropped by
|
|
162
|
+
* this interface's field-list map, making the annotation invisible to any
|
|
163
|
+
* agent reading `smart_recall`'s JSON output.
|
|
164
|
+
*
|
|
165
|
+
* ANNOTATE-ONLY (pre-ship red-team fix, STEP 4a, 2026-09-01): a
|
|
166
|
+
* `supersededBy` item's `score`/rank is NEVER changed by the contradiction
|
|
167
|
+
* stage — see `retrieval/query-memory.ts`'s `applyContradictionStage` for
|
|
168
|
+
* why the original down-rank was removed (a false-positive grammar match
|
|
169
|
+
* used to actively INVERT ranking; now it is, at worst, a harmless extra
|
|
170
|
+
* annotation).
|
|
171
|
+
*/
|
|
172
|
+
supersededBy?: string;
|
|
173
|
+
/**
|
|
174
|
+
* CONTRADICTION stage (Wave 5a) — the `id`s of every sibling this item's
|
|
175
|
+
* text grammar-conflicts with, regardless of whether a stale direction
|
|
176
|
+
* could be resolved. Additive; see `supersededBy`'s doc comment for the
|
|
177
|
+
* W5a salvage visibility fix this field shares.
|
|
178
|
+
*/
|
|
179
|
+
conflictsWith?: string[];
|
|
169
180
|
}
|
|
170
181
|
/** A verbatim source attached when a low-confidence top hit was drilled into. */
|
|
171
182
|
export interface BridgedSource {
|
|
@@ -202,12 +213,26 @@ export interface SmartRecallResult {
|
|
|
202
213
|
}
|
|
203
214
|
/**
|
|
204
215
|
* localRecallSearch — the core local search logic (palace + journal + insight).
|
|
205
|
-
* Performs three parallel searches, scores internally, merges via RRF,
|
|
206
|
-
* applies hot-window recency boost, and deduplicates.
|
|
207
216
|
*
|
|
208
|
-
*
|
|
209
|
-
*
|
|
210
|
-
*
|
|
217
|
+
* WAVE 2: delegates FETCH/TRUST-FILTER/TOKENIZE+SCORE/RANK-FUSE entirely to
|
|
218
|
+
* `retrieval/query-memory.ts`'s `queryMemory()` — see this file's header.
|
|
219
|
+
* This function's own remaining job: resolve `project` (queryMemory()
|
|
220
|
+
* requires an already-resolved slug, matching Wave 1's `readTierCandidates`
|
|
221
|
+
* convention — previously this resolution happened independently 3x, inside
|
|
222
|
+
* journalSearch/palaceSearch/nowhere-for-insight; now once, here — a
|
|
223
|
+
* characterized simplification, not a behavior change for any caller passing
|
|
224
|
+
* an already-valid explicit slug, which is every existing test and the
|
|
225
|
+
* common real-world case), label each fused item with a calibrated
|
|
226
|
+
* confidence (rrf-local scale, matching the original dedup loop exactly),
|
|
227
|
+
* reconstruct `verbatimKey`, run the graph-walk 1-hop related-room surfacing
|
|
228
|
+
* (smart_recall-specific; no other Wave-3 migration target has this), and
|
|
229
|
+
* attach the raw-candidate-count side channel.
|
|
230
|
+
*
|
|
231
|
+
* Called by LocalRecallBackend.search() in recall-backend.ts, and directly
|
|
232
|
+
* by helpers/associative-link.ts and (in tests) by
|
|
233
|
+
* audit-retrieval-accounting.test.mjs — its signature and the RAW_CANDIDATE_COUNTS
|
|
234
|
+
* side-channel contract are UNCHANGED, since those are real, direct external
|
|
235
|
+
* callers, not just smartRecall()'s own internals.
|
|
211
236
|
*/
|
|
212
237
|
export declare function localRecallSearch(query: string, project: string | undefined, limit: number, since?: string): Promise<SmartRecallResultItem[]>;
|
|
213
238
|
export declare function smartRecall(input: SmartRecallInput): Promise<SmartRecallResult>;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"smart-recall.d.ts","sourceRoot":"","sources":["../../src/tools-logic/smart-recall.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"smart-recall.d.ts","sourceRoot":"","sources":["../../src/tools-logic/smart-recall.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwGG;AAWH,OAAO,EAAiB,KAAK,WAAW,EAAE,MAAM,iBAAiB,CAAC;AAQlE,MAAM,WAAW,cAAc;IAC7B,EAAE,CAAC,EAAE,MAAM,CAAC;IACZ,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,OAAO,CAAC;CACjB;AAED,MAAM,WAAW,gBAAgB;IAC/B,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,CAAC,EAAE,cAAc,EAAE,CAAC;IAC5B;;qDAEiD;IACjD,KAAK,CAAC,EAAE,MAAM,CAAC;IACf;wBACoB;IACpB,SAAS,CAAC,EAAE,OAAO,CAAC;CACrB;AAED,MAAM,WAAW,qBAAqB;IACpC,EAAE,EAAE,MAAM,CAAC;IACX;;;;;;;kBAOc;IACd,MAAM,EAAE,QAAQ,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,CAAC;IACrD;;;yEAGqE;IACrE,WAAW,CAAC,EAAE,KAAK,CAAC,QAAQ,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,CAAC,CAAC;IAClE,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,EAAE,MAAM,CAAC;IACd,iEAAiE;IACjE,UAAU,EAAE,MAAM,CAAC;IACnB;yEACqE;IACrE,UAAU,EAAE,MAAM,CAAC;IACnB,mFAAmF;IACnF,WAAW,CAAC,EAAE,WAAW,CAAC;IAC1B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB;;;;;;;;;;;;;;;;;OAiBG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;;;OAKG;IACH,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;CAC1B;AAED,iFAAiF;AACjF,MAAM,WAAW,aAAa;IAC5B,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;CAClB;AAQD,MAAM,WAAW,mBAAmB;IAGlC,MAAM,EAAE,SAAS,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;CACjB;AAED;+EAC+E;AAC/E,MAAM,WAAW,kBAAkB;IACjC,MAAM,EAAE,MAAM,CAAC;IACf,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,iBAAiB;IAChC,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,qBAAqB,EAAE,CAAC;IACjC,cAAc,EAAE,MAAM,CAAC;IACvB,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,sFAAsF;IACtF,QAAQ,CAAC,EAAE,mBAAmB,CAAC;IAC/B,6EAA6E;IAC7E,OAAO,CAAC,EAAE,aAAa,EAAE,CAAC;IAC1B;;;gEAG4D;IAC5D,oBAAoB,CAAC,EAAE,kBAAkB,CAAC;CAC3C;AAkID;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAsB,iBAAiB,CACrC,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,GAAG,SAAS,EAC3B,KAAK,EAAE,MAAM,EACb,KAAK,CAAC,EAAE,MAAM,GACb,OAAO,CAAC,qBAAqB,EAAE,CAAC,CA2FlC;AAkCD,wBAAsB,WAAW,CAAC,KAAK,EAAE,gBAAgB,GAAG,OAAO,CAAC,iBAAiB,CAAC,CAgNrF"}
|