@ascenda-one/claude-code-hooks 0.1.35 → 0.1.37

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/README.md CHANGED
@@ -74,6 +74,7 @@ npx @ascenda-one/claude-code-hooks uninstall # removes hooks and the binary
74
74
  | `--local [port]` | shorthand for a local [dev server](../ascenda-dev-server/) (default `4477`) |
75
75
  | `--tool-installation-id <id>` / `--token <t>` | reuse an existing pairing instead of creating one |
76
76
  | `--no-pair` | install the local half only: hooks work, nothing is sent |
77
+ | `--no-repo-keys` | GitHub repositories get a `repoKey` and, off the default branch, a `branchKey`, so a pull request can be matched to a session. They are unsalted digests, so anyone who guesses the names can recompute them. This turns both off, machine-wide. `--repo-keys` turns them back on |
77
78
  | `--event-log [path\|off]` | keep every event in a local JSONL file (default `~/.ascenda/events.jsonl`). On by default without a pairing; `off` stops it |
78
79
  | `--scope user\|project` | register in `~/.claude/settings.json` (default, every project) or in this project's `.claude/settings.local.json` |
79
80
  | `--project-dir <path>` | project root for `--scope project` (default cwd) |
@@ -100,6 +101,11 @@ rather than appending, hooks belonging to anyone else are left alone, and the
100
101
  file is backed up to `.ascenda-backup` before the first write. Settings that
101
102
  are not valid JSON abort the run rather than being overwritten.
102
103
 
104
+ With `CLAUDE_CONFIG_DIR` set, user-scope setup, `status` and `uninstall` use
105
+ `$CLAUDE_CONFIG_DIR/settings.json`. If another tool has added its own hook to
106
+ one of our groups, setup and `uninstall` take out only ours and leave theirs.
107
+ A symlinked settings file stays a symlink.
108
+
103
109
  #### Upgrading
104
110
 
105
111
  Re-run `setup` with the scope you installed with. It keeps your pairing, adds
@@ -107,7 +113,7 @@ the hooks this version registers, and prints what it added:
107
113
 
108
114
  ```text
109
115
  hooks ~/.claude/settings.json (13 events)
110
- upgraded: added SubagentStart, SubagentStop; hook set 2 → 3
116
+ upgraded: added PermissionRequest, PermissionDenied; hook set 3 → 4
111
117
  ```
112
118
 
113
119
  `status` prints the installed hook set and, when it's older, the command to
@@ -233,12 +239,14 @@ Optional environment:
233
239
  | `ASCENDA_EVENT_WRITE_TOKEN` | Only if you have no prior pairing to reuse — normally the token file supplies this |
234
240
  | `ASCENDA_EVENT_WRITE_TOKEN_FILE` | Override token file path (default `~/.ascenda/tokens/<toolInstallationId>`) |
235
241
  | `ASCENDA_SESSION_ID` | Stable session id across hooks |
242
+ | `ASCENDA_REPO_KEYS` | `off` leaves the repository and branch keys off every event. Wins over `setup --no-repo-keys` |
236
243
  | `ASCENDA_EVENT_LOG_FILE` | Local JSONL event log path, or `off`. Wins over `setup --event-log`. Without either, an unpaired install writes `~/.ascenda/events.jsonl` and a paired one writes nothing |
237
244
  | `ASCENDA_WORKSPACE_HASH` | Override only. By default the hook derives this from the payload's own `cwd`: a machine-salted hash of the checkout folder's basename (never the path itself) |
238
245
  | `ASCENDA_PROJECT_HASH` | Override only. Defaults to the salted hash of the canonical repository's basename — a git worktree folds into the repo it was created from |
239
246
  | `ASCENDA_STATE_FILE` | Override the send journal path (default `~/.ascenda/state/<toolInstallationId>.json`) |
240
247
  | `ASCENDA_OUTBOX_FILE` | Override the outbox path (default `~/.ascenda/state/<toolInstallationId>.outbox.jsonl`) |
241
- | `ASCENDA_OUTBOX_DRAIN` | `true` lets the next hook re-send queued events. **Off by default** until the ingest endpoint is confirmed to dedupe live events on `idempotencyKey`; see "When the collector cannot reach Ascenda" |
248
+ | `ASCENDA_HOOK_DELIVERY` | `inline` makes each hook send its own events and wait for the answer. By default a background sender does it; see "How events leave the machine" |
249
+ | `ASCENDA_OUTBOX_DRAIN` | `0` holds the outbox without sending it, and hooks send their own events inline. On by default |
242
250
  | `ASCENDA_DISABLE_FAILURE_NOTICE` | `true` silences the one-time in-session notice about a collector that has stopped delivering |
243
251
 
244
252
  On first run the CLI seeds `~/.ascenda/tokens/<toolInstallationId>` so
@@ -272,31 +280,43 @@ pair again before the 30 days are up and replace the token in the environment.
272
280
 
273
281
  ### Register hooks manually
274
282
 
275
- The plugin does this for you — this section is only for the standalone route.
276
- Merge [`examples/settings.local.json`](./examples/settings.local.json) into
277
- `.claude/settings.local.json` in a project, or into Claude Code's user settings
278
- for machine-wide coverage:
283
+ The plugin and `setup` both do this for you. Do it by hand only to put the
284
+ hooks in a file `setup` doesn't write, such as a project's shared
285
+ `.claude/settings.json`.
286
+
287
+ The commands run the launcher `setup` installs in `~/.ascenda/bin`, so run
288
+ `setup` first. Then move its entries into the file you want, using
289
+ [`examples/settings.local.json`](./examples/settings.local.json):
279
290
 
280
291
  ```json
281
292
  {
282
293
  "hooks": {
283
- "SessionStart": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks SessionStart", "timeout": 5 }] }],
284
- "UserPromptSubmit": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks UserPromptSubmit", "timeout": 5 }] }],
285
- "PreToolUse": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks PreToolUse", "timeout": 5 }] }],
286
- "PostToolUse": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks PostToolUse", "timeout": 5 }] }],
287
- "PostToolUseFailure": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks PostToolUseFailure", "timeout": 5 }] }],
288
- "PreCompact": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks PreCompact", "timeout": 5 }] }],
289
- "PostCompact": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks PostCompact", "timeout": 5 }] }],
290
- "Stop": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks Stop", "timeout": 5 }] }],
291
- "StopFailure": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks StopFailure", "timeout": 5 }] }],
292
- "Notification": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks Notification", "timeout": 5 }] }],
293
- "SessionEnd": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks SessionEnd", "timeout": 5 }] }],
294
- "SubagentStart": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks SubagentStart", "timeout": 5 }] }],
295
- "SubagentStop": [{ "hooks": [{ "type": "command", "command": "npx -y @ascenda-one/claude-code-hooks SubagentStop", "timeout": 5 }] }]
294
+ "SessionStart": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" SessionStart --hook-set 4", "timeout": 5 }] }],
295
+ "UserPromptSubmit": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" UserPromptSubmit --hook-set 4", "timeout": 5 }] }],
296
+ "PreToolUse": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PreToolUse --hook-set 4", "timeout": 5 }] }],
297
+ "PostToolUse": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PostToolUse --hook-set 4", "timeout": 5 }] }],
298
+ "PostToolUseFailure": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PostToolUseFailure --hook-set 4", "timeout": 5 }] }],
299
+ "PreCompact": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PreCompact --hook-set 4", "timeout": 5 }] }],
300
+ "PostCompact": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PostCompact --hook-set 4", "timeout": 5 }] }],
301
+ "Stop": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" Stop --hook-set 4", "timeout": 5 }] }],
302
+ "StopFailure": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" StopFailure --hook-set 4", "timeout": 5 }] }],
303
+ "Notification": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" Notification --hook-set 4", "timeout": 5 }] }],
304
+ "SessionEnd": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" SessionEnd --hook-set 4", "timeout": 5 }] }],
305
+ "SubagentStart": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" SubagentStart --hook-set 4", "timeout": 5 }] }],
306
+ "SubagentStop": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" SubagentStop --hook-set 4", "timeout": 5 }] }],
307
+ "PermissionRequest": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PermissionRequest --hook-set 4", "timeout": 5 }] }],
308
+ "PermissionDenied": [{ "hooks": [{ "type": "command", "command": "\"$HOME/.ascenda/bin/ascenda-claude-hook\" PermissionDenied --hook-set 4", "timeout": 5 }] }]
296
309
  }
297
310
  }
298
311
  ```
299
312
 
313
+ Keep them in one file: two copies run every event twice. Delete `setup`'s
314
+ entries from the file it wrote. `status` and `uninstall` only read your user
315
+ settings and a project's `settings.local.json`, so they won't see a copy in
316
+ `.claude/settings.json`. `setup --dry-run` prints the exact entries for this
317
+ machine. On Windows there's no launcher, so copy those instead: they name
318
+ Node and the bundle.
319
+
300
320
  Keep the timeouts. Without one Claude Code gives a hook up to 600s, and all
301
321
  SessionEnd hooks share 1.5s between them.
302
322
 
@@ -359,42 +379,46 @@ call, and never repeats until the collector has recovered and failed again.
359
379
  distinguish a dead token from a night's sleep, because both are "no events".
360
380
  Only the collector knows it tried and was refused.
361
381
 
362
- ### When the collector cannot reach Ascenda
382
+ ### How events leave the machine
363
383
 
364
- A send that fails without a verdict — the endpoint unreachable, a timeout, a
365
- `429` or `5xx` — is retried once after 250 ms and then **kept**, not dropped.
366
- The payload is appended to an outbox next to the journal:
384
+ A hook doesn't send anything itself. It appends its events to an outbox next
385
+ to the journal, starts a background sender, and hands control back to Claude
386
+ Code in a few milliseconds:
367
387
 
368
388
  ```
369
389
  ~/.ascenda/state/<toolInstallationId>.outbox.jsonl
370
390
  ```
371
391
 
372
- one JSON line per event, exactly as it would have gone on the wire, plus the
373
- time it was queued. Anything longer than a blip — a laptop waking from sleep,
374
- a VPN reconnecting, a captive portal, a slow network on a train — used to lose
375
- every event for its duration with no copy anywhere. Now it costs nothing but
376
- delay. A rejection *with* a verdict (`400`, `401`, `403`) is not queued:
377
- replaying it cannot change the answer.
378
-
379
- The next hook invocation drains the outbox, oldest first, one batch of up to
380
- 100 per invocation and never with a backoff loop — the hook is on your
381
- critical path, and the invocation after that is usually seconds away. An
382
- entry is deleted when the server answers `accepted` **or** `duplicate`; a
383
- duplicate means the server already had it, which is the point of the
384
- `idempotencyKey` every event carries. If the door refuses again, the pass stops
385
- with everything still on disk, and the live event joins the queue instead of
386
- knocking on a door that just said no.
387
-
388
- > **Sending from the outbox is off by default.** Set `ASCENDA_OUTBOX_DRAIN=true`
389
- > to enable it. A drain against an ingest endpoint that does not yet dedupe
390
- > live events on `idempotencyKey` would land every queued event a second
391
- > time — the exact double-count that blocked this queue until the key existed.
392
- > Until the deployed backend is confirmed to answer a replay with `duplicate`,
393
- > events are queued, bounded and reported, but not re-sent.
392
+ Each line is one event, exactly as it goes on the wire, plus the time it was
393
+ queued. The background sender is the same CLI run with `__flush-outbox`. It
394
+ sends the outbox oldest first, up to 100 events per request, until it's empty,
395
+ and exits. One sender runs at a time: a lock file next to the outbox
396
+ (`.flushing`) tells the next hook that one is already working.
397
+
398
+ So the network never sits between you and your agent. A slow connection, a
399
+ captive portal or an outage costs delay, not a stalled tool call. Each event's
400
+ time and `idempotencyKey` are set when the hook fires, so an event sent a few
401
+ seconds later keeps its time, and one sent twice comes back `duplicate`.
402
+
403
+ An entry is deleted when the server answers `accepted` or `duplicate`. If the
404
+ server can't be reached (a timeout, a `429` or `5xx`), the sender stops with
405
+ everything still on disk and journals the failure, and the next hook starts
406
+ another. A refusal with a verdict (`400`, `401`, `403`) isn't kept: replaying it
407
+ can't change the answer.
408
+
409
+ Two settings send from the hook itself, as earlier versions did:
410
+
411
+ - `ASCENDA_HOOK_DELIVERY=inline`. The hook sends each event and waits for the
412
+ answer. A failed send is retried once after 250 ms and then queued.
413
+ - `ASCENDA_OUTBOX_DRAIN=0`, which holds the outbox without sending it. The
414
+ hook still sends its own events inline, so nothing stops arriving.
415
+
416
+ A hosted session always sends inline. Its container goes when the session
417
+ does, and an outbox in it would go too.
394
418
 
395
419
  The outbox is bounded: 10,000 entries and 7 days. When a bound evicts, the
396
420
  discard is recorded in the journal as `"lastOutcome": "outbox_discarded"` with
397
- a cumulative `outboxDiscarded` block — how many, when, why, and how far back
421
+ a cumulative `outboxDiscarded` block: how many, when, why, and how far back
398
422
  the loss reaches. It survives every later success, because a gap that has
399
423
  since closed is still a gap in the data.
400
424
 
@@ -403,7 +427,8 @@ since closed is still a gap in the data.
403
427
  ```
404
428
  Outbox ~/.ascenda/state/claude_code_….outbox.jsonl
405
429
  Outbox depth 37 waiting — oldest queued 2026-09-03T01:12:08.114Z (3h 41m ago)
406
- Outbox drain off (queued events are kept and bounded, not sent) — ASCENDA_OUTBOX_DRAIN
430
+ Outbox drain on (queued events are replayed, oldest first) — ASCENDA_OUTBOX_DRAIN
431
+ Delivery background sender (the hook queues and returns)
407
432
  Outbox discarded 12 total; last 12 at 2026-09-02T… (12 age, reaching back to 2026-08-25T…)
408
433
  ```
409
434
 
@@ -411,11 +436,11 @@ A non-empty outbox is the honest health answer. `consecutiveFailures` resets
411
436
  on the first success after an outage; the outbox says events from that outage
412
437
  are still on this machine.
413
438
 
414
- Hooks overlap — Claude Code fires `PreToolUse` and `PostToolUse` from separate
415
- processes — so appends use `O_APPEND` (whole lines, never fragments) and a
416
- drain takes the file by renaming it out from under concurrent appenders. An
417
- entry is never deleted before the server has confirmed it; a drain that dies
418
- mid-way leaves a claim file that the next drain sweeps back in.
439
+ Hooks overlap, since Claude Code fires `PreToolUse` and `PostToolUse` from
440
+ separate processes. Appends use `O_APPEND` (whole lines, never fragments), and
441
+ a sender takes the file by renaming it out from under concurrent appenders. An
442
+ entry is never deleted before the server has confirmed it. A sender that dies
443
+ partway leaves a claim file that the next one sweeps back in.
419
444
 
420
445
  ## Build from source
421
446
 
@@ -459,6 +484,8 @@ Notification
459
484
  SessionEnd
460
485
  SubagentStart
461
486
  SubagentStop
487
+ PermissionRequest
488
+ PermissionDenied
462
489
  ```
463
490
 
464
491
  ## Ascenda event mappings
@@ -481,6 +508,8 @@ Notification -> supervision_interruption (interruptionKind only, never the
481
508
  SessionEnd -> recovery_offline_period (activity session_ended, sessionEndReason)
482
509
  SubagentStart -> subagent_started (subagentId, subagentClass)
483
510
  SubagentStop -> subagent_stopped (subagentId, subagentClass)
511
+ PermissionRequest -> permission_requested (toolName, autonomyMode)
512
+ PermissionDenied -> permission_denied (toolName, autonomyMode), auto mode only
484
513
  ```
485
514
 
486
515
  ## Privacy defaults
@@ -488,14 +517,21 @@ SubagentStop -> subagent_stopped (subagentId, subagentClass)
488
517
  Metadata-only telemetry. Does not send raw prompts, responses, code, file names, repository names, branch names, or terminal output.
489
518
 
490
519
  When the agent stops and waits for you, `Notification` records only which kind
491
- of wait it was — `permission_request`, `idle_prompt` or `other`. The
492
- notification's own wording is read to pick one of those three labels and is
493
- then discarded; it never leaves the hook process, and neither does anything you
520
+ of wait it was — `permission_request`, `input_request`, `idle_prompt` or
521
+ `other`. Claude Code's `notification_type` picks the label, and the
522
+ notification's own wording does it on a version that doesn't send one. The
523
+ wording is then discarded; it never leaves the hook process, and neither does anything you
494
524
  answer. `tests/interruptionContentGuard.test.mjs` fails the build if that
495
525
  changes.
496
526
 
497
- Repository and branch identity travel only as machine-salted digests, derived
498
- in the hook process and never as text: `workspaceHash` and `projectHash` from
527
+ `PermissionRequest` and `PermissionDenied` send the tool's name and the
528
+ permission posture, and nothing about what the tool was asked to do. The
529
+ request hook fires before you answer and no hook reports the answer, so a
530
+ request doesn't say whether it was granted. The denied hook only fires in auto
531
+ mode.
532
+
533
+ Repository and branch identity travel only as digests, derived in the hook
534
+ process and never as text. Most are machine-salted: `workspaceHash` and `projectHash` from
499
535
  the checkout's and repository's folder names, and `metadata.branchHash` from
500
536
  the branch the checkout is on. The salt is random per machine, stored at
501
537
  `~/.ascenda/salt`, and never transmitted — without it, a digest of a name from
@@ -505,6 +541,16 @@ lets work be grouped by branch on the other side without the name itself
505
541
  leaving the machine. On a detached HEAD, outside a checkout, or with no
506
542
  readable salt the key is omitted entirely rather than sent blank.
507
543
 
544
+ Two more digests are not salted, on purpose. `metadata.repoKey` and
545
+ `metadata.branchKey` use the recipe Ascenda's GitHub collector uses, which runs
546
+ where no salt exists, so a session and a pull request on the same repository
547
+ and branch carry the same pair. They go on events for github.com remotes only,
548
+ and `branchKey` is left off the default branch. Because they're unsalted,
549
+ anyone who guesses a repository or branch name can confirm it, and for a public
550
+ repository those names are public. Turn them off with `setup --no-repo-keys`
551
+ or `ASCENDA_REPO_KEYS=off`. `metadata.promptId` is Claude Code's own id for the
552
+ prompt a turn answers, and says nothing about its text.
553
+
508
554
  Correction detection uses local pattern matching on prompt text in the hook process only — classified metadata (`reason: repeated_reprompting`) is sent; raw prompt text is not.
509
555
 
510
556
  ## Compliance
@@ -1,4 +1,4 @@
1
- import { AscendaEventSender } from "@ascenda-one/tool-kit";
1
+ import { AscendaEventSender, runOutboxFlush } from "@ascenda-one/tool-kit";
2
2
  export { AscendaApiError as AscendaClientError } from "@ascenda-one/tool-kit";
3
3
  export class AscendaClient {
4
4
  sender;
@@ -28,6 +28,13 @@ export class AscendaClient {
28
28
  queue(mapped) {
29
29
  return this.sender.queue(mapped);
30
30
  }
31
+ outboxFilePath() {
32
+ return this.sender.outboxFilePath();
33
+ }
34
+ /** Drains the outbox until it's empty or the door refuses. What the background flusher runs. */
35
+ async flushOutbox() {
36
+ await runOutboxFlush(this.sender);
37
+ }
31
38
  async renewEventToken() {
32
39
  return this.sender.renewEventToken();
33
40
  }
@@ -1 +1 @@
1
- {"version":3,"file":"ascendaClient.js","sourceRoot":"","sources":["../src/ascendaClient.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAI3D,OAAO,EAAE,eAAe,IAAI,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE9E,MAAM,OAAO,aAAa;IACP,MAAM,CAAqB;IAE5C,YAAY,MAAyB;QACnC,IAAI,CAAC,MAAM,GAAG,IAAI,kBAAkB,CAAC;YACnC,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,kBAAkB,EAAE,MAAM,CAAC,kBAAkB;YAC7C,MAAM,EAAE,aAAa;YACrB,eAAe,EAAE,MAAM,CAAC,eAAe;YACvC,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,cAAc,EAAE,MAAM,CAAC,cAAc;YACrC,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,SAAS,EAAE,MAAM,CAAC,SAAS;YAC3B,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,WAAW,EAAE,MAAM,CAAC,WAAW;SAChC,CAAC,CAAC;IACL,CAAC;IAED,iEAAiE;IACjE,IAAI,KAAK;QACP,OAAO,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC;IAC3B,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,MAA0B;QACnC,OAAO,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IAClC,CAAC;IAED,qEAAqE;IACrE,KAAK,CAAC,MAA0B;QAC9B,OAAO,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;IACnC,CAAC;IAED,KAAK,CAAC,eAAe;QACnB,OAAO,IAAI,CAAC,MAAM,CAAC,eAAe,EAAE,CAAC;IACvC,CAAC;CACF"}
1
+ {"version":3,"file":"ascendaClient.js","sourceRoot":"","sources":["../src/ascendaClient.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,cAAc,EAAE,MAAM,uBAAuB,CAAC;AAI3E,OAAO,EAAE,eAAe,IAAI,kBAAkB,EAAE,MAAM,uBAAuB,CAAC;AAE9E,MAAM,OAAO,aAAa;IACP,MAAM,CAAqB;IAE5C,YAAY,MAAyB;QACnC,IAAI,CAAC,MAAM,GAAG,IAAI,kBAAkB,CAAC;YACnC,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,kBAAkB,EAAE,MAAM,CAAC,kBAAkB;YAC7C,MAAM,EAAE,aAAa;YACrB,eAAe,EAAE,MAAM,CAAC,eAAe;YACvC,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,cAAc,EAAE,MAAM,CAAC,cAAc;YACrC,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,SAAS,EAAE,MAAM,CAAC,SAAS;YAC3B,aAAa,EAAE,MAAM,CAAC,aAAa;YACnC,WAAW,EAAE,MAAM,CAAC,WAAW;SAChC,CAAC,CAAC;IACL,CAAC;IAED,iEAAiE;IACjE,IAAI,KAAK;QACP,OAAO,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC;IAC3B,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,MAA0B;QACnC,OAAO,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IAClC,CAAC;IAED,qEAAqE;IACrE,KAAK,CAAC,MAA0B;QAC9B,OAAO,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;IACnC,CAAC;IAED,cAAc;QACZ,OAAO,IAAI,CAAC,MAAM,CAAC,cAAc,EAAE,CAAC;IACtC,CAAC;IAED,gGAAgG;IAChG,KAAK,CAAC,WAAW;QACf,MAAM,cAAc,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACpC,CAAC;IAED,KAAK,CAAC,eAAe;QACnB,OAAO,IAAI,CAAC,MAAM,CAAC,eAAe,EAAE,CAAC;IACvC,CAAC;CACF"}