litmus-cli 1.4.21 → 1.4.24

package/README.md

@@ -51,6 +51,22 @@ Run this from inside your assessment folder when you're done. It packages your w
 
 Use `litmus submit --yes` to skip the confirmation prompt.
 
+### If your assessment runs in a Litmus workspace
+
+Some assessments give you a hosted workspace instead of a local folder — you open
+it in the browser or connect to it with `litmus connect`. There is nothing local
+to package there, so `litmus submit` does not apply and will tell you so. Submit
+with:
+
+```bash
+litmus push
+```
+
+Run it in the workspace terminal, where it needs no token, or on your own machine
+as `litmus push <token>` with the token from your assessment page. Either way it
+captures the workspace exactly as it stands, so there is nothing to commit or push
+first. The Submit button on your assessment page does the same thing.
+
 ## How it works
 
 1. `litmus init <token>` — sets up your workspace and starts the clock

package/dist/commands/connect.d.ts

@@ -84,6 +84,144 @@ export declare function buildControlPathBlock(alias: string, p: ParsedSsh): stri
 export declare function upsertSshConfigContent(existing: string, alias: string, block: string, controlBlock?: string): string;
 /** Short, stable alias from the workspace hostname (or token as a fallback). */
 export declare function aliasFor(sshHostname: string | null | undefined, token: string): string;
+/**
+ * The native editors `litmus connect` can drive, and everything about them that is
+ * not shared. Both are VS Code-family, so one set of helpers serves both: the CLI
+ * argument grammar (`--remote ssh-remote+<alias>`, `--list-extensions`,
+ * `--install-extension … --force`) is identical. What is NOT identical is the
+ * Remote-SSH extension, and that is the part worth stating.
+ *
+ * ENG-1950. MEASURED against a real Cursor (3.17.19, darwin arm64) rather than assumed
+ * from VS Code, because a fork is exactly where this silently differs:
+ *
+ *   - `cursor --list-extensions` reports `anysphere.remote-ssh`, whose manifest
+ *     activates on `onResolveRemoteAuthority:ssh-remote` — i.e. it is the resolver that
+ *     `--remote ssh-remote+<alias>` needs, the same role `ms-vscode-remote.remote-ssh`
+ *     plays in VS Code. Microsoft's extension is licensed to VS Code and cannot be
+ *     installed into Cursor at all, so reusing the VS Code id here would install
+ *     nothing and leave the candidate in a dead remote window — the one failure this
+ *     check exists to prevent.
+ *   - `--install-extension <ext-id>` / `--force` / `--list-extensions` are all
+ *     documented in `cursor --help`, with VS Code's spelling.
+ *   - `--remote` is absent from `cursor --help`, as it is from `code --help`: in both
+ *     bundles the option table carries `remote:{type:"string",allowEmptyValue:true}`
+ *     with no help category, so it is hidden rather than missing. `code --remote` is
+ *     already proven in production here; Cursor parses the same grammar.
+ *
+ * ENG-2152 adds `banner`, and it is the field that makes the rest of this record safe to
+ * use. `bin` is a NAME ON PATH, not an identity: Cursor's own CLI is shipped as
+ * `Cursor.app/Contents/Resources/app/bin/code`, so a machine where Cursor is the daily
+ * driver can easily have `code` resolve to it — which is how a teammate whose default
+ * editor is Cursor, choosing VS Code, got Cursor (reported by Elena, 2026-09-03).
+ * Everything below then ran against the wrong editor:
+ * `--list-extensions` does not report the Microsoft id, so we "install" it and announce
+ * "Installed the VS Code Remote-SSH extension", and `--remote` opens Cursor while we say
+ * we are opening VS Code. The candidate is then on Cursor's capture lane having never
+ * been shown the full-quit notice that lane depends on (ENG-1728), which is silent zero
+ * capture.
+ *
+ * MEASURED 2026-09-04 on darwin arm64, VS Code 1.136.1 and Cursor 3.18.25, with a `code`
+ * symlinked to Cursor's CLI to reproduce the report:
+ *
+ *   - `--version` CANNOT tell them apart. Both print exactly three lines — version,
+ *     commit, arch — with no product name anywhere ("3.18.25" from the `code` that was
+ *     Cursor). So `hasEditorCli`'s probe is not merely unchecked, it has nothing to
+ *     check, and the version numbers (1.x vs 3.x) are a coincidence, not a contract.
+ *   - `--help` line 1 IS the product name: "Visual Studio Code 1.136.1" against
+ *     "Cursor 3.18.25", on STDOUT (stderr empty), exit 0, no window, instant. It is
+ *     `product.json`'s `nameLong`, which is why the patterns below are anchored prefixes
+ *     — VS Code Insiders prints "Visual Studio Code - Insiders", and matching the whole
+ *     line would refuse it.
+ *   - The body of `--help` names BOTH editors ("ps aux | grep code | cursor -"), so the
+ *     identity is read off the first non-empty line and never scanned for.
+ *   - Cursor 3.18.25 does not even fail loudly on the wrong extension: it answers
+ *     `--install-extension ms-vscode-remote.remote-ssh --force` with "already installed",
+ *     exit 0, mapping the Microsoft id onto its own `anysphere.remote-ssh`. So the dead
+ *     remote window is version-dependent and the FALSE success line is not.
+ */
+export type NativeIde = "vscode" | "cursor";
+export interface NativeEditor {
+    /** Which choice this record IS, so a record is self-describing once resolved. */
+    ide: NativeIde;
+    /** CLI binary we expect on PATH. */
+    bin: string;
+    /**
+     * What `<bin> --help` announces on its FIRST non-empty line when `bin` really is this
+     * editor. Anchored prefix, never the whole line and never the body — see the block
+     * comment above for the measurement and for why both of those matter.
+     */
+    banner: RegExp;
+    /** What the candidate calls it — used verbatim in our output. */
+    label: string;
+    /**
+     * The client-side extension that resolves `ssh-remote+…`. Without it the editor
+     * silently opens a dead remote window ("Extension 'Remote - SSH' is required").
+     * Per-editor, never shared — see the block comment above.
+     */
+    remoteSshExt: string;
+    /** The palette command that puts `bin` on PATH, for the no-CLI fallback. */
+    shellCommand: string;
+}
+/**
+ * ENG-2152 — what the editor CLI we are about to drive says it IS.
+ *
+ * `hasEditorCli` above answers "does this command exist", which is a different and much
+ * weaker question, and treating the answer as an identity is the whole of this bug: the
+ * `code` on a Cursor user's PATH can be Cursor's own CLI, which is literally installed
+ * under that name inside `Cursor.app`. The measurement behind `banner` is in the
+ * `NATIVE_EDITORS` block comment; the three verdicts are what the caller may conclude.
+ *
+ * `unverified` is deliberately NOT a refusal, and the direction it fails in is the point.
+ * The only thing we can positively assert is "this banner is an editor we know", so an
+ * unrecognised one — VSCodium, a WSL or devcontainer `code` wrapper, a future rename, a
+ * platform where `--help` prints something else — may only move the answer towards
+ * "unknown", never towards naming an editor. Refusing there would break candidates for
+ * whom connect works today, in exchange for a claim we cannot make; proceeding leaves
+ * them exactly where they were before this check existed. What it can never do is
+ * silently open the OTHER editor, because that verdict requires recognising it.
+ */
+export type EditorIdentity = {
+    kind: "match";
+} | {
+    kind: "mismatch";
+    actual: NativeIde;
+} | {
+    kind: "unverified";
+};
+/**
+ * Map `--help` output to an editor we know, or null.
+ *
+ * FIRST NON-EMPTY LINE ONLY. The body of `--help` names both editors — Cursor's own
+ * usage example is `ps aux | grep code | cursor -` — so anything that scans the whole
+ * output identifies whichever pattern it happens to try first, on either editor.
+ */
+export declare function identifyEditorBanner(helpOutput: string): NativeIde | null;
+/** How the identity probe reaches the binary. Injected so the verdicts are testable. */
+export type EditorHelpRunner = (bin: string) => string | null;
+export declare function identifyEditorCli(ed: NativeEditor, run?: EditorHelpRunner): EditorIdentity;
+/**
+ * ENG-2152 — the refusal, when the command the candidate's PATH answers with is the
+ * other editor.
+ *
+ * Two routes, and the one that WORKS RIGHT NOW comes first: on a machine where `code` is
+ * Cursor, Cursor is almost certainly the daily driver and VS Code may not be installed at
+ * all, so leading with "fix your PATH" leads with the thing that may be impossible.
+ * That ordering is the same one `announceCursorFullQuit` documents — what a candidate can
+ * act on immediately is what they read first.
+ *
+ * The offered command carries the token already inlined, for the reason `CursorReentry`
+ * gives: a `litmus connect <token>` a candidate has to repair themselves is worse than no
+ * command at all.
+ *
+ * When the editor that answered is Cursor, the quit requirement rides along. It is the
+ * headline only, not the whole ENG-1728 notice, because the command being offered prints
+ * that notice in full at selection time before anything opens — this is a FORWARD
+ * reference to output the candidate is about to see, not ENG-2145's back-reference to
+ * output that has scrolled away. Restating the whole block here would also have to
+ * restate its "this command is still running and will open Cursor for you", which on
+ * this path is false.
+ */
+export declare function editorMismatchLines(chosen: NativeEditor, actual: NativeEditor, reentry?: CursorReentry): string[];
 export type IdeChoice = "vscode" | "cursor" | "browser" | "ssh";
 /**
  * Resolve which editor to open: an explicit --ide flag wins; otherwise prompt.
@@ -94,11 +232,75 @@ export type IdeChoice = "vscode" | "cursor" | "browser" | "ssh";
  * selection path rather than by reading a string constant. A warning that is never
  * reached is precisely the bug this ticket is fixing, so a test that cannot see whether
  * it was printed is not a test of it.
+ *
+ * `reentry` is the way back in, and it is threaded from `runConnect` rather than
+ * rebuilt here because only the caller holds the token and the resolved base. When it
+ * is absent (a test, a scripted call) the notice degrades to the placeholder form
+ * rather than dropping the route — see `cursorReentryLines`.
  */
-export declare function resolveIde(flag: string | undefined, log?: (line: string) => void): Promise<{
+export declare function resolveIde(flag: string | undefined, log?: (line: string) => void, reentry?: CursorReentry): Promise<{
     ide: IdeChoice;
     chosen: boolean;
 }>;
+/**
+ * The candidate's own assessment page.
+ *
+ * **The slug is the ASSESSMENT ID, never the token**, and getting that wrong fails in
+ * the most misleading way available. `app/candidate/[slug]/layout.tsx` tolerates a
+ * token-shaped slug as a fallback, so the shell renders and the URL looks right — but
+ * `page.tsx` then fetches `/api/candidates/<email>/assessments/<slug>`, whose store
+ * lookup (`getAssessmentForCandidate`) matches on `assessment.id` alone. A token 404s
+ * there, and the candidate gets "Assessment Not Found. If you were invited under a
+ * different email, sign out and try that address" — a page telling them the problem is
+ * their account, at the moment they were promised a way back into their workspace.
+ * `/auth-redirect` resolves the token through `/api/assessments/by-token` and pushes
+ * exactly this shape, which is why it is the one to reproduce.
+ *
+ * ONE helper because this module prints the page twice for two different reasons (the
+ * disclosure refusal and ENG-2145's re-entry route) and both were the broken spelling.
+ * `connect-cursor-option.test.ts` asserts over the module's source that no `/candidate/`
+ * URL is built any other way — the mistake is invisible to a behavioural test, since
+ * both spellings are well-formed URLs that render a page.
+ */
+export declare function candidatePageUrl(apiBase: string, assessmentId: string): string;
+/**
+ * The way back into a workspace, as the two things a candidate can act on.
+ *
+ * `command` is the pasteable form with the token already inlined; a bare
+ * `litmus connect <token>` a candidate has to repair themselves is worse than no
+ * command at all, which is the same line `showPauseControl` draws on the portal.
+ * `pageUrl` is their assessment page, which is the only route that survives losing
+ * the terminal as well — see `cursorReentryLines`.
+ */
+export interface CursorReentry {
+    command: string;
+    pageUrl: string | null;
+}
+/**
+ * ENG-2145 — how to get back in, said in the same breath as "quit".
+ *
+ * Elena, 2026-09-04, after two people who know the product could not work it out:
+ * "it prompts you to quit cursor and come back in but it's not quite intuitive how
+ * we're going to get back in."
+ *
+ * The notice used to offer exactly one route — "let this command reopen it" — and that
+ * is the one route the instruction above it destroys. A candidate told to quit Cursor is
+ * very likely reading the instruction IN CURSOR'S OWN INTEGRATED TERMINAL, because that
+ * is where they have a shell; `Cmd+Q` then takes `litmus connect` with it. What is left
+ * on screen is a quit editor, no running command, and nothing anywhere naming the way
+ * back. On the clock, that reads as the workspace being gone.
+ *
+ * So the route is stated as an instruction rather than as a promise about a process that
+ * may no longer exist, and the terminal it must be run from is named: a candidate who
+ * has just been told to quit an application cannot be told to use that application's
+ * terminal. The assessment page comes second and is the one that survives closing the
+ * tab AND losing the terminal, which is the state Elena was actually in.
+ *
+ * Both routes reopen the SAME workspace — `litmus connect` re-registers this machine's
+ * key and wakes a parked container through the ENG-2005 machinery, and the portal's own
+ * card does the same — so the reassurance is a fact about the platform, not a hope.
+ */
+export declare function cursorReentryLines(reentry?: CursorReentry): string[];
 /**
  * ENG-1950 — the one thing a Cursor candidate has to be told, and the only place we can
  * reliably tell them.
@@ -116,8 +318,15 @@ export declare function resolveIde(flag: string | undefined, log?: (line: string
  *
  * So the copy is written for a candidate, not for us: what to do, and what it costs if
  * they don't. No "hooks", no "capture lane". The mechanism is our problem.
+ *
+ * ENG-2145 adds the second half of that sentence: what to do is now "quit, THEN run
+ * this", because an instruction to quit with no stated way back is what sent two people
+ * who know the product looking for their workspace. The order is deliberate — the cost
+ * of skipping the quit still comes last, so the thing a candidate acts on immediately is
+ * the thing they read first, and `cursorReentryLines` sits between them rather than
+ * after the whole notice where it would scroll.
  */
-export declare function announceCursorFullQuit(log?: (line: string) => void): void;
+export declare function announceCursorFullQuit(log?: (line: string) => void, reentry?: CursorReentry): void;
 /**
  * Map a menu answer to an editor. (ENG-1667 item 3; Cursor added by ENG-1950.)
  *
@@ -155,6 +364,26 @@ export declare function ideMenuLines(): string[];
  *     EditorChatConfigResult.
  */
 export declare function chatConfigAction(ide: IdeChoice, state: "configured" | "unconfigured" | "unavailable"): "write" | "remove" | "none";
+/**
+ * ENG-2152 — the same question, once the editor CLI's identity is known.
+ *
+ * A mismatch is refused before anything opens, so a refused connect drives NO editor and
+ * may not WRITE: the entry would leave a live `lwt_` bearer token in an editor we then
+ * declined to drive, from an attempt that failed.
+ *
+ * The obvious spelling — keep `chatConfigAction` and pass it "the editor that actually
+ * answered" — reads more obviously correct than it is, and is wrong in the direction
+ * nobody pictures. Greptile caught it on #2134. Choose VS Code on a machine where `code`
+ * is Cursor and it suppresses the write, correctly. Choose CURSOR on a machine where
+ * `cursor` is VS Code and it ENABLES a write that the unpatched code suppressed: the very
+ * check added to stop the wrong editor being driven would be what plants the credential.
+ * So the typed choice stays the input and the mismatch only ever REMOVES an action.
+ *
+ * `remove` survives a mismatch and must: yesterday's dead token is in that file however
+ * today's connect ends, and `writeChatModelConfig` refuses to create a file that was
+ * never there, so on a machine that never ran the VS Code path it touches nothing.
+ */
+export declare function chatConfigActionForIdentity(ide: IdeChoice, state: "configured" | "unconfigured" | "unavailable", identity: EditorIdentity): "write" | "remove" | "none";
 /**
  * What to do when the browser IDE was selected. (Greptile on #1713.)
  *

package/dist/commands/connect.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"connect.d.ts","sourceRoot":"","sources":["../../src/commands/connect.ts"],"names":[],"mappings":"AAyCA,MAAM,WAAW,SAAS;IACxB,IAAI,EAAE,MAAM,CAAA;IACZ,IAAI,EAAE,MAAM,CAAA;IACZ,IAAI,CAAC,EAAE,MAAM,CAAA;IACb,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAA;CAClB;AAQD;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,SAAS,CAwBtD;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,CAAC,EAAE,SAAS,GAAG,MAAM,CAkCxF;AAMD;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE,MAAM,EAAE,CAAC,EAAE,SAAS,GAAG,MAAM,CAUzE;AAiCD;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,sBAAsB,CACpC,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,KAAK,EAAE,MAAM,EACb,YAAY,CAAC,EAAE,MAAM,GACpB,MAAM,CAKR;AAED,gFAAgF;AAChF,wBAAgB,QAAQ,CAAC,WAAW,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,CAItF;AAiID,MAAM,MAAM,SAAS,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,GAAG,KAAK,CAAA;AAE/D;;;;;;;;;GASG;AACH,wBAAsB,UAAU,CAC9B,IAAI,EAAE,MAAM,GAAG,SAAS,EACxB,GAAG,GAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAkB,GACxC,OAAO,CAAC;IAAE,GAAG,EAAE,SAAS,CAAC;IAAC,MAAM,EAAE,OAAO,CAAA;CAAE,CAAC,CAc9C;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,sBAAsB,CAAC,GAAG,GAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAkB,GAAG,IAAI,CAYtF;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,YAAY,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,CAMtD;AAED;;;;GAIG;AACH,wBAAgB,YAAY,IAAI,MAAM,EAAE,CASvC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,gBAAgB,CAC9B,GAAG,EAAE,SAAS,EACd,KAAK,EAAE,YAAY,GAAG,cAAc,GAAG,aAAa,GACnD,OAAO,GAAG,QAAQ,GAAG,MAAM,CAI7B;AA+ED;;;;;;GAMG;AACH,wBAAgB,eAAe,CAC7B,MAAM,EAAE,OAAO,EACf,YAAY,EAAE,OAAO,GACpB,SAAS,GAAG,QAAQ,GAAG,aAAa,CAGtC;AAED,wBAAsB,UAAU,CAAC,KAAK,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAwQ9E"}
+{"version":3,"file":"connect.d.ts","sourceRoot":"","sources":["../../src/commands/connect.ts"],"names":[],"mappings":"AA2CA,MAAM,WAAW,SAAS;IACxB,IAAI,EAAE,MAAM,CAAA;IACZ,IAAI,EAAE,MAAM,CAAA;IACZ,IAAI,CAAC,EAAE,MAAM,CAAA;IACb,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAA;CAClB;AAQD;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,SAAS,CAwBtD;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,CAAC,EAAE,SAAS,GAAG,MAAM,CAkCxF;AAMD;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE,MAAM,EAAE,CAAC,EAAE,SAAS,GAAG,MAAM,CAUzE;AAiCD;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,sBAAsB,CACpC,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,KAAK,EAAE,MAAM,EACb,YAAY,CAAC,EAAE,MAAM,GACpB,MAAM,CAKR;AAED,gFAAgF;AAChF,wBAAgB,QAAQ,CAAC,WAAW,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,CAItF;AAwBD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AACH,MAAM,MAAM,SAAS,GAAG,QAAQ,GAAG,QAAQ,CAAA;AAE3C,MAAM,WAAW,YAAY;IAC3B,iFAAiF;IACjF,GAAG,EAAE,SAAS,CAAA;IACd,oCAAoC;IACpC,GAAG,EAAE,MAAM,CAAA;IACX;;;;OAIG;IACH,MAAM,EAAE,MAAM,CAAA;IACd,iEAAiE;IACjE,KAAK,EAAE,MAAM,CAAA;IACb;;;;OAIG;IACH,YAAY,EAAE,MAAM,CAAA;IACpB,4EAA4E;IAC5E,YAAY,EAAE,MAAM,CAAA;CACrB;AA8BD;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,MAAM,cAAc,GACtB;IAAE,IAAI,EAAE,OAAO,CAAA;CAAE,GACjB;IAAE,IAAI,EAAE,UAAU,CAAC;IAAC,MAAM,EAAE,SAAS,CAAA;CAAE,GACvC;IAAE,IAAI,EAAE,YAAY,CAAA;CAAE,CAAA;AAE1B;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,UAAU,EAAE,MAAM,GAAG,SAAS,GAAG,IAAI,CAUzE;AAED,wFAAwF;AACxF,MAAM,MAAM,gBAAgB,GAAG,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,GAAG,IAAI,CAAA;AAmC7D,wBAAgB,iBAAiB,CAAC,EAAE,EAAE,YAAY,EAAE,GAAG,GAAE,gBAAgC,GAAG,cAAc,CAMzG;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,mBAAmB,CACjC,MAAM,EAAE,YAAY,EACpB,MAAM,EAAE,YAAY,EACpB,OAAO,GAAE,aAAuC,GAC/C,MAAM,EAAE,CA2BV;AA0CD,MAAM,MAAM,SAAS,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,GAAG,KAAK,CAAA;AAE/D;;;;;;;;;;;;;;GAcG;AACH,wBAAsB,UAAU,CAC9B,IAAI,EAAE,MAAM,GAAG,SAAS,EACxB,GAAG,GAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAkB,EACzC,OAAO,CAAC,EAAE,aAAa,GACtB,OAAO,CAAC;IAAE,GAAG,EAAE,SAAS,CAAC;IAAC,MAAM,EAAE,OAAO,CAAA;CAAE,CAAC,CAc9C;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,GAAG,MAAM,CAE9E;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,MAAM,CAAA;IACf,OAAO,EAAE,MAAM,GAAG,IAAI,CAAA;CACvB;AAKD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,kBAAkB,CAAC,OAAO,GAAE,aAAuC,GAAG,MAAM,EAAE,CAsB7F;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,sBAAsB,CACpC,GAAG,GAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAkB,EACzC,OAAO,GAAE,aAAuC,GAC/C,IAAI,CAiBN;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,YAAY,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,CAMtD;AAED;;;;GAIG;AACH,wBAAgB,YAAY,IAAI,MAAM,EAAE,CASvC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,gBAAgB,CAC9B,GAAG,EAAE,SAAS,EACd,KAAK,EAAE,YAAY,GAAG,cAAc,GAAG,aAAa,GACnD,OAAO,GAAG,QAAQ,GAAG,MAAM,CAI7B;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,2BAA2B,CACzC,GAAG,EAAE,SAAS,EACd,KAAK,EAAE,YAAY,GAAG,cAAc,GAAG,aAAa,EACpD,QAAQ,EAAE,cAAc,GACvB,OAAO,GAAG,QAAQ,GAAG,MAAM,CAI7B;AA+ED;;;;;;GAMG;AACH,wBAAgB,eAAe,CAC7B,MAAM,EAAE,OAAO,EACf,YAAY,EAAE,OAAO,GACpB,SAAS,GAAG,QAAQ,GAAG,aAAa,CAGtC;AAED,wBAAsB,UAAU,CAAC,KAAK,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAwU9E"}