@mrclrchtr/supi-insights 1.3.1 → 1.4.0

package/README.md

@@ -1,234 +1,107 @@
 # @mrclrchtr/supi-insights
 
-> Usage insights and analytics for [pi](https://pi.dev) sessions. Inspired by Claude Code's `/insights` command, rebuilt for pi's extension architecture.
+Adds a `/supi-insights` command to the [pi coding agent](https://github.com/earendil-works/pi) that analyzes your historical pi sessions and writes a shareable HTML report.
 
-Generate rich, shareable HTML reports analyzing your PI coding sessions — what you work on, how you interact with the agent, what works well, where friction happens, and what to try next.
-
-## What you get
-
-Running `/supi-insights` produces a report with:
-
-- **At a Glance** — high-level summary of what's working, what's hindering you, quick wins, and ambitious workflows for future models
-- **What You Work On** — project areas with session counts and descriptions
-- **How You Use PI** — narrative analysis of your interaction style and key patterns
-- **Impressive Things You Did** — notable workflows and accomplishments
-- **Where Things Go Wrong** — friction categories with concrete examples
-- **Charts & Stats** — tool usage, languages, session types, outcomes, satisfaction, response times, time-of-day patterns, tool errors, multi-session usage
-- **Suggestions** — CLAUDE.md additions, features to try, new usage patterns
-- **On the Horizon** — ambitious workflows to prepare for as models improve
-
-Reports are saved as self-contained HTML files you can open in any browser.
-
-## Installation
+## Install
 
 ```bash
 pi install npm:@mrclrchtr/supi-insights
 ```
 
-> **🧪 Beta package** — not included in the `@mrclrchtr/supi` meta-package.
-> Install directly when you need session analytics.
+This is a **beta** package. It is not bundled in `@mrclrchtr/supi`.
 
-Or install from a local checkout with `pi install /path/to/packages/supi-insights`.
+For local development:
 
-## Usage
-
-Type `/supi-insights` in the pi editor and press Enter.
-
-```
-/supi-insights
+```bash
+pi install ./packages/supi-insights
 ```
 
-The extension will:
-
-1. **Scan** all historical pi sessions across projects
-2. **Extract metadata** — tool counts, languages, git activity, lines changed, response times, errors (cached for future runs)
-3. **Extract qualitative facets** — goals, outcomes, satisfaction, friction via LLM analysis (cached)
-4. **Generate narrative insights** — coaching-style analysis in 7 parallel sections
-5. **Render an HTML report** — saved to `~/.pi/agent/supi/insights/report-{timestamp}.html`
-6. **Show a summary** — in the PI chat with a link to the full report
+After editing the source, run `/reload`.
 
-### First run
-
-The first run may take a minute or two if you have many sessions, because it:
-- Parses all session JSONL files
-- Extracts metadata for each session
-- Runs ~50 LLM facet extractions (batched, 50 concurrent)
-- Generates ~8 LLM insight sections
-
-Subsequent runs are fast — cached metadata and facets are reused.
+## What you get
 
-## Configuration
+After install, pi gets one command:
 
-If your install surface includes `/supi-settings` (for example when also installing the `@mrclrchtr/supi` meta-package), this package contributes an **Insights** section there. You can also edit `~/.pi/agent/supi/config.json` directly:
+- `/supi-insights` — scan session history, generate metrics and narrative insights, and save an HTML report
 
-| Setting | Description | Default |
-|---------|-------------|---------|
-| `enabled` | Enable or disable insights generation | `on` |
-| `maxSessions` | Maximum sessions to fully parse and analyze | `200` |
-| `maxFacets` | Maximum per-session LLM facet extractions | `50` |
+The command pipeline is:
 
-Example config:
+1. list historical sessions with `SessionManager.listAll()`
+2. parse session files and extract metadata such as message counts, tools, languages, git activity, lines changed, response times, and tool errors
+3. run LLM-based facet extraction on a bounded set of sessions
+4. aggregate the results across sessions
+5. generate an HTML report and post a short in-chat summary with the saved file path
 
-```json
-{
-  "insights": {
-    "enabled": true,
-    "maxSessions": 200,
-    "maxFacets": 50
-  }
-}
-```
+## What the report covers
 
-## Architecture
+The generated report can include:
 
-```
-packages/supi-insights/src/
-├── insights.ts       # Extension factory — registers /supi-insights and settings
-├── scanner.ts        # Session discovery via SessionManager.listAll()
-├── parser.ts         # JSONL parsing, transcript extraction, tool stat aggregation
-├── extractor.ts      # LLM facet extraction via @earendil-works/pi-ai/complete()
-├── aggregator.ts     # Pure data aggregation + multi-clauding detection
-├── generator.ts      # Parallel narrative insight generation (7 sections)
-├── html.ts           # HTML report renderer with CSS bar charts
-├── cache.ts          # Facet and metadata caching
-├── utils.ts          # Chart helpers, label mappings, text utilities
-└── types.ts          # Shared TypeScript types
-```
+- at-a-glance summary
+- project areas
+- interaction style
+- what works well
+- friction analysis
+- suggestions
+- future opportunities
+- charts and aggregate stats for tools, languages, outcomes, satisfaction, response times, time of day, and multi-session overlap
 
-### Data flow
+## Output and caching
 
-```
-SessionManager.listAll()
-       │
-       ▼
-┌─────────────┐     ┌─────────────┐     ┌─────────────┐
-│  scanner    │────▶│   parser    │────▶│   cache     │
-└─────────────┘     └─────────────┘     └─────────────┘
-       │                                    │
-       │         ┌─────────────┐            │
-       └────────▶│  extractor  │◀───────────┘
-                 │ (LLM facets)│
-                 └─────────────┘
-                        │
-                        ▼
-               ┌─────────────┐
-               │  aggregator │
-               └─────────────┘
-                        │
-                        ▼
-               ┌─────────────┐
-               │  generator  │
-               │ (insights)  │
-               └─────────────┘
-                        │
-                        ▼
-               ┌─────────────┐
-               │    html     │
-               │   report    │
-               └─────────────┘
-```
+Reports are written under pi's agent directory (typically `~/.pi/agent/`):
 
-### Key design decisions
+- reports: `~/.pi/agent/supi/insights/report-*.html`
+- metadata cache: `~/.pi/agent/supi/insights/meta/*.json`
+- facet cache: `~/.pi/agent/supi/insights/facets/*.json`
 
-**Direct LLM access** — Uses `@earendil-works/pi-ai/complete()` and `ctx.modelRegistry.getApiKeyAndHeaders()` to make API calls with the user's already-configured keys. No external SDK needed.
+The cache key includes:
 
-**Aggressive caching** — Session metadata and LLM-extracted facets are cached in `~/.pi/agent/supi/insights/`. Cache keys include the session file path and modified timestamp, so branch files do not collide and resumed sessions are reprocessed.
+- session id
+- session file path hash
+- modified timestamp hash
 
-**Branch deduplication** — pi session files are append-only trees. The extension analyzes the active branch path, then keeps only the branch/file with the most user messages per session ID to avoid double-counting.
+That keeps branched or resumed session files from colliding.
 
-**Substantive filtering** — Sessions with fewer than 2 user messages or lasting under 1 minute are skipped, as are sessions where the only goal is `warmup_minimal`.
+## Important limits
 
-**Parallel processing** — Facet extractions run in batches of 50 concurrent LLM calls. Insight sections run in parallel too, with `atAGlance` generated last (it consumes outputs from all other sections).
+Built-in defaults:
 
-## Caching
+- `maxSessions`: `200`
+- `maxFacets`: `50`
 
-Cached data lives in `~/.pi/agent/supi/insights/`:
+Filtering in the current implementation:
 
-```
-~/.pi/agent/supi/insights/
-├── meta/
-│   ├── {session-id}_{path-hash}_{modified-hash}.json    # Extracted metadata
-│   └── ...
-├── facets/
-│   ├── {session-id}_{path-hash}_{modified-hash}.json    # LLM-extracted facets
-│   └── ...
-└── report-{timestamp}.html    # Generated HTML reports
-```
+- sessions with fewer than 2 user messages are skipped from the final analysis set
+- sessions shorter than 1 minute are skipped from the final analysis set
+- sessions whose only facet category is `warmup_minimal` are dropped after facet extraction
 
-- **Metadata cache** includes: tool counts, languages, git activity, tokens, lines changed, response times, errors, feature flags
-- **Facet cache** includes: goals, outcomes, satisfaction, friction, success factors, brief summaries
+## Settings
 
-To force a full re-analysis, delete the cache directory:
+This package registers an **Insights** section in `/supi-settings`.
 
-```bash
-rm -rf ~/.pi/agent/supi/insights/meta ~/.pi/agent/supi/insights/facets
-```
+Available settings:
 
-## Multi-session detection
-
-The extension detects when you run multiple pi sessions simultaneously ("multi-clauding") using a sliding-window algorithm:
-
-- Collects all user message timestamps across sessions
-- Looks for the pattern `sessionA → sessionB → sessionA` within a 30-minute window
-- Reports overlap events, sessions involved, and percentage of messages during overlaps
-
-## Statistics tracked
-
-### Per-session
-- Tool usage counts
-- Programming languages used (from file paths in edit/write tool calls)
-- Git commits and pushes
-- Input/output tokens
-- Lines added/removed (via diff)
-- Files modified
-- User response times (time between assistant message and next user message)
-- Tool errors with categorization (Command Failed, Edit Failed, User Rejected, etc.)
-- User interruptions
-- Feature usage (task agents, MCP, web search, web fetch)
-- Message timestamps for time-of-day analysis
-
-### Aggregated
-- Total sessions, messages, duration, tokens
-- Days active, messages per day
-- Top tools, languages, goals, outcomes
-- Satisfaction and helpfulness distributions
-- Friction types and success factors
-- Response time histograms
-- Time-of-day patterns
-- Multi-session overlap events
-
-## Compared to Claude Code `/insights`
-
-| Feature | Claude Code | /supi-insights |
-|---------|-------------|---------------|
-| Session discovery | Manual filesystem scan | `SessionManager.listAll()` |
-| LLM access | Internal `queryWithModel()` | `@earendil-works/pi-ai/complete()` |
-| Output | HTML report + browser | HTML report + browser |
-| Caching | Custom `~/.claude/usage-data/` | `~/.pi/agent/supi/insights/` |
-| Multi-clauding | ✅ | ✅ |
-| Remote host collection | ✅ (ant-only, SCP) | ❌ (not applicable) |
-| Team feedback (ant-only) | ✅ | ❌ |
-| TUI dashboard | ❌ | Planned |
-| Live tracking | ❌ | Planned |
-
-## Development
+- `enabled` — turn the command on or off
+- `maxSessions` — maximum sessions to fully analyze
+- `maxFacets` — maximum LLM facet extractions
 
-```bash
-# Typecheck
-pnpm exec tsc --noEmit -p packages/supi-insights/tsconfig.json
+Defaults:
 
-# Test
-pnpm vitest run packages/supi-insights/
+```json
+{
+  "insights": {
+    "enabled": true,
+    "maxSessions": 200,
+    "maxFacets": 50
+  }
+}
 ```
 
-## Roadmap
-
-- [ ] **Live tracking** — accumulate stats via `tool_call`, `turn_end`, `model_select` events instead of only scanning historical sessions
-- [ ] **TUI overlay dashboard** — native PI terminal UI with ASCII bar charts, keyboard-navigable sections
-- [ ] **Export formats** — Markdown, JSON, CSV
-- [ ] **Trend comparison** — compare current report with previous reports
-- [ ] **Session drill-down** — `/supi-insights --session <id>` to analyze a specific session
-
-## License
+## Source
 
-MIT
+- `src/insights.ts` — command, settings, and end-to-end report generation
+- `src/scanner.ts` — session discovery
+- `src/parser.ts` — session parsing and metadata extraction
+- `src/aggregator.ts` — aggregated statistics and multi-session overlap detection
+- `src/generator.ts` — narrative insight generation
+- `src/html.ts` — HTML report output
+- `src/cache.ts` — metadata and facet caching

package/node_modules/@mrclrchtr/supi-core/README.md

@@ -1,65 +1,78 @@
 # @mrclrchtr/supi-core
 
-Shared infrastructure for SuPi packages.
+Shared infrastructure for SuPi extensions.
+
+This package is mainly for extension authors. It gives you a common config system, settings plumbing, context helpers, registries, and a small extension surface that registers `/supi-settings`.
 
 ## Install
 
-Use it as a dependency in another extension package:
+### As a dependency for another extension
 
 ```bash
 pnpm add @mrclrchtr/supi-core
 ```
 
-## Package role
-
-`@mrclrchtr/supi-core` now has two explicit surfaces:
+### As a pi package
 
-- `@mrclrchtr/supi-core/api` — shared library helpers for other SuPi packages
-- `@mrclrchtr/supi-core/extension` — a minimal pi extension that registers `/supi-settings`
-
-`pi.extensions` still points at the real file path `./src/extension.ts` inside the package. The `/api` and `/extension` paths are consumer-facing package exports, not manifest aliases.
+```bash
+pi install npm:@mrclrchtr/supi-core
+```
 
-## What it provides
+Installing it as a pi package adds the minimal `/supi-settings` extension surface.
 
-Current exports cover:
+## Package surfaces
 
-- shared config loading, scoped reads, writes, and key removal
-- config-backed settings registration helpers for `/supi-settings`
-- the shared settings registry, overlay UI, and `registerSettingsCommand()` helper
-- XML `<extension-context>` wrapping plus context-message utilities
-- context-provider and debug-event registries reused across SuPi packages
-- project root and path helpers reused by packages such as `supi-lsp`
+- `@mrclrchtr/supi-core/api` — reusable helpers for other packages and extensions
+- `@mrclrchtr/supi-core/extension` — minimal pi extension that registers `/supi-settings`
 
-## Config system
+## What you get from the API
 
-Config resolution order:
+### Config helpers
 
-```text
-defaults <- global <- project
-```
+- `loadSupiConfig()` — merged config with resolution order `defaults <- global <- project`
+- `loadSupiConfigForScope()` — load one scope at a time for settings UIs
+- `writeSupiConfig()` — persist values
+- `removeSupiConfigKey()` — remove a key or override
 
 Config file locations:
 
 - global: `~/.pi/agent/supi/config.json`
 - project: `.pi/supi/config.json`
 
-Main helpers:
+### Settings helpers
+
+- `registerSettings()` — register an arbitrary settings section
+- `registerConfigSettings()` — register a config-backed settings section with scoped persistence helpers
+- `registerSettingsCommand()` — register `/supi-settings`
+- `openSettingsOverlay()` — open the shared settings UI directly
+- `createInputSubmenu()` — helper for simple text-entry submenus
+
+The built-in settings UI supports:
 
-- `loadSupiConfig()` — effective merged config (`defaults <- global <- project`)
-- `loadSupiConfigForScope()` — raw single-scope config for settings UIs (`defaults <- selected scope`)
-- `writeSupiConfig()`
-- `removeSupiConfigKey()`
-- `registerConfigSettings()`
+- project/global scope toggle
+- grouped extension sections
+- searchable setting lists
 
-## Context and settings helpers
+### Context helpers
 
-- `wrapExtensionContext()`
+- `wrapExtensionContext()` — wrap injected text in SuPi's `<extension-context>` tag
 - `findLastUserMessageIndex()`
 - `getContextToken()`
+- `getPromptContent()`
 - `pruneAndReorderContextMessages()`
-- `registerSettings()`
-- `registerSettingsCommand()`
-- `openSettingsOverlay()`
+- `restorePromptContent()`
+
+### Shared registries
+
+- context-provider registry for `/supi-context`
+- debug-event registry for producers that want shared debug capture
+- settings registry used by `/supi-settings`
+
+### Project and session helpers
+
+- project-root detection and directory walking helpers such as `findProjectRoot()` and `walkProject()`
+- active-branch session helper: `getActiveBranchEntries()`
+- terminal helpers such as `formatTitle()`, `signalWaiting()`, and `signalDone()`
 
 ## Example
 
@@ -80,17 +93,15 @@ registerConfigSettings({
 });
 
 const message = wrapExtensionContext("my-extension", "hello", {
-  turn: 1,
   file: "CLAUDE.md",
+  turn: 1,
 });
 ```
 
-## Requirements
-
-- `@earendil-works/pi-coding-agent`
-- `@earendil-works/pi-tui`
-
 ## Source
 
-- Library surface: `src/api.ts`
-- Extension surface: `src/extension.ts`
+- `src/api.ts` — exported library surface
+- `src/extension.ts` — minimal `/supi-settings` entrypoint
+- `src/config.ts` — shared config loading and writing
+- `src/config-settings.ts` — config-backed settings registration helper
+- `src/settings-ui.ts` — shared settings overlay

package/node_modules/@mrclrchtr/supi-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mrclrchtr/supi-core",
-  "version": "1.3.1",
+  "version": "1.4.0",
   "description": "SuPi core — shared infrastructure for SuPi extensions (XML context tags, config system)",
   "license": "MIT",
   "repository": {

package/node_modules/@mrclrchtr/supi-core/src/api.ts

@@ -2,30 +2,30 @@
 // Provides XML context tag wrapping, unified config system, context-message utilities,
 // and settings registry for supi-wide TUI settings.
 
-export type { SupiConfigLocation, SupiConfigOptions } from "./config.ts";
+export type { SupiConfigLocation, SupiConfigOptions } from "./config/config.ts";
 export {
   loadSupiConfig,
   loadSupiConfigForScope,
   removeSupiConfigKey,
   writeSupiConfig,
-} from "./config.ts";
-export type { ConfigSettingsHelpers, ConfigSettingsOptions } from "./config-settings.ts";
-export { registerConfigSettings } from "./config-settings.ts";
-export type { ContextMessageLike } from "./context-messages.ts";
+} from "./config/config.ts";
+export type { ConfigSettingsHelpers, ConfigSettingsOptions } from "./config/config-settings.ts";
+export { registerConfigSettings } from "./config/config-settings.ts";
+export type { ContextMessageLike } from "./context/context-messages.ts";
 export {
   findLastUserMessageIndex,
   getContextToken,
   getPromptContent,
   pruneAndReorderContextMessages,
   restorePromptContent,
-} from "./context-messages.ts";
-export type { ContextProvider } from "./context-provider-registry.ts";
+} from "./context/context-messages.ts";
+export type { ContextProvider } from "./context/context-provider-registry.ts";
 export {
   clearRegisteredContextProviders,
   getRegisteredContextProviders,
   registerContextProvider,
-} from "./context-provider-registry.ts";
-export { wrapExtensionContext } from "./context-tag.ts";
+} from "./context/context-provider-registry.ts";
+export { wrapExtensionContext } from "./context/context-tag.ts";
 export type {
   DebugAgentAccess,
   DebugEvent,
@@ -64,14 +64,14 @@ export {
   walkProject,
 } from "./project-roots.ts";
 export { getActiveBranchEntries } from "./session-utils.ts";
-export { registerSettingsCommand } from "./settings-command.ts";
-export type { SettingsScope, SettingsSection } from "./settings-registry.ts";
+export { registerSettingsCommand } from "./settings/settings-command.ts";
+export type { SettingsScope, SettingsSection } from "./settings/settings-registry.ts";
 export {
   clearRegisteredSettings,
   getRegisteredSettings,
   registerSettings,
-} from "./settings-registry.ts";
-export { createInputSubmenu, openSettingsOverlay } from "./settings-ui.ts";
+} from "./settings/settings-registry.ts";
+export { createInputSubmenu, openSettingsOverlay } from "./settings/settings-ui.ts";
 export type { TitleTarget } from "./terminal.ts";
 export {
   DONE_SYMBOL,

package/node_modules/@mrclrchtr/supi-core/src/{config-settings.ts → config/config-settings.ts}

@@ -2,9 +2,9 @@
 // Wraps registerSettings() and centralizes selected-scope loading + scoped persistence.
 
 import type { SettingItem } from "@earendil-works/pi-tui";
+import type { SettingsScope } from "../settings/settings-registry.ts";
+import { registerSettings } from "../settings/settings-registry.ts";
 import { loadSupiConfigForScope, removeSupiConfigKey, writeSupiConfig } from "./config.ts";
-import type { SettingsScope } from "./settings-registry.ts";
-import { registerSettings } from "./settings-registry.ts";
 
 export interface ConfigSettingsHelpers {
   /** Write a key to the selected scope's config section. */

package/node_modules/@mrclrchtr/supi-core/src/{context-provider-registry.ts → context/context-provider-registry.ts}

@@ -3,7 +3,7 @@
 // Extensions declare context data providers via `registerContextProvider()` during their
 // factory function. The `/supi-context` command reads them via `getRegisteredContextProviders()`.
 
-import { createRegistry } from "./registry-utils.ts";
+import { createRegistry } from "../registry-utils.ts";
 
 export interface ContextProvider {
   /** Unique identifier — e.g. "rtk" */

package/node_modules/@mrclrchtr/supi-core/src/extension.ts

@@ -1 +1 @@
-export { registerSettingsCommand as default } from "./settings-command.ts";
+export { registerSettingsCommand as default } from "./settings/settings-command.ts";

package/node_modules/@mrclrchtr/supi-core/src/index.ts

@@ -2,30 +2,30 @@
 // Provides XML context tag wrapping, unified config system, context-message utilities,
 // and settings registry for supi-wide TUI settings.
 
-export type { SupiConfigLocation, SupiConfigOptions } from "./config.ts";
+export type { SupiConfigLocation, SupiConfigOptions } from "./config/config.ts";
 export {
   loadSupiConfig,
   loadSupiConfigForScope,
   removeSupiConfigKey,
   writeSupiConfig,
-} from "./config.ts";
-export type { ConfigSettingsHelpers, ConfigSettingsOptions } from "./config-settings.ts";
-export { registerConfigSettings } from "./config-settings.ts";
-export type { ContextMessageLike } from "./context-messages.ts";
+} from "./config/config.ts";
+export type { ConfigSettingsHelpers, ConfigSettingsOptions } from "./config/config-settings.ts";
+export { registerConfigSettings } from "./config/config-settings.ts";
+export type { ContextMessageLike } from "./context/context-messages.ts";
 export {
   findLastUserMessageIndex,
   getContextToken,
   getPromptContent,
   pruneAndReorderContextMessages,
   restorePromptContent,
-} from "./context-messages.ts";
-export type { ContextProvider } from "./context-provider-registry.ts";
+} from "./context/context-messages.ts";
+export type { ContextProvider } from "./context/context-provider-registry.ts";
 export {
   clearRegisteredContextProviders,
   getRegisteredContextProviders,
   registerContextProvider,
-} from "./context-provider-registry.ts";
-export { wrapExtensionContext } from "./context-tag.ts";
+} from "./context/context-provider-registry.ts";
+export { wrapExtensionContext } from "./context/context-tag.ts";
 export type {
   DebugAgentAccess,
   DebugEvent,
@@ -64,14 +64,14 @@ export {
   walkProject,
 } from "./project-roots.ts";
 export { getActiveBranchEntries } from "./session-utils.ts";
-export { registerSettingsCommand } from "./settings-command.ts";
-export type { SettingsScope, SettingsSection } from "./settings-registry.ts";
+export { registerSettingsCommand } from "./settings/settings-command.ts";
+export type { SettingsScope, SettingsSection } from "./settings/settings-registry.ts";
 export {
   clearRegisteredSettings,
   getRegisteredSettings,
   registerSettings,
-} from "./settings-registry.ts";
-export { createInputSubmenu, openSettingsOverlay } from "./settings-ui.ts";
+} from "./settings/settings-registry.ts";
+export { createInputSubmenu, openSettingsOverlay } from "./settings/settings-ui.ts";
 export type { TitleTarget } from "./terminal.ts";
 export {
   DONE_SYMBOL,

package/node_modules/@mrclrchtr/supi-core/src/{settings-registry.ts → settings/settings-registry.ts}

@@ -4,7 +4,7 @@
 // factory function. The generic settings UI reads them via `getRegisteredSettings()`.
 
 import type { SettingItem } from "@earendil-works/pi-tui";
-import { createRegistry } from "./registry-utils.ts";
+import { createRegistry } from "../registry-utils.ts";
 
 export type SettingsScope = "project" | "global";
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mrclrchtr/supi-insights",
-  "version": "1.3.1",
+  "version": "1.4.0",
   "description": "SuPi Insights extension — generate usage reports analyzing your PI sessions",
   "license": "MIT",
   "repository": {
@@ -17,14 +17,14 @@
   ],
   "files": [
     "src/**/*.ts",
-    "!src/__tests__/**",
+    "!__tests__/**",
     "src/report.css",
     "src/report.js",
     "README.md"
   ],
   "dependencies": {
     "diff": "^9.0.0",
-    "@mrclrchtr/supi-core": "1.3.1"
+    "@mrclrchtr/supi-core": "1.4.0"
   },
   "bundledDependencies": [
     "@mrclrchtr/supi-core"