suzi-cli 0.1.21 → 0.1.23

package/dist/lib/suzi-guide.js

@@ -1,682 +0,0 @@
-"use strict";
-// Shared suzi-guide content used by both skills.ts and create.ts
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.SUZI_GUIDE_CONTENT = void 0;
-exports.SUZI_GUIDE_CONTENT = `---
-name: suzi-guide
-description: >
-  Comprehensive guide for the Suzi CLI and agent platform. Use this skill when
-  the user asks about Suzi commands, how to create/deploy/manage agents, available
-  protocols and actions, agent code patterns, or anything related to the Suzi
-  autonomous agent platform for blockchain protocols.
----
-
-# Suzi CLI & Agent Platform Guide
-
-## IMPORTANT: Always Use the CLI for Live Data
-
-**NEVER rely on hardcoded data from this skill for questions about protocols, actions, balances, agents, or any runtime state.** Always run the appropriate \`suzi\` CLI command and use its output. This ensures the user gets up-to-date information.
-
-**Hard rule:** the CLI is the primary source of truth. This skill is guidance documentation and can lag behind the latest release. If the skill and CLI output ever conflict, trust the CLI.
-
-| User asks about... | Run this command |
-|---------------------|-----------------|
-| Available protocols / actions | \`suzi list-actions --verbose\` |
-| Actions for a specific protocol | \`suzi list-actions --protocol <name>\` |
-| Action schema (parameters + response) | \`suzi list-actions --protocol <name> --schema <action>\` |
-| Multiple action schemas at once | \`suzi list-actions --protocol <name> --schema a1,a2,a3\` or \`--schema all\` |
-| Available triggers | \`suzi list-triggers\` |
-| Triggers for a specific protocol | \`suzi list-triggers --protocol <name>\` |
-| Run an action directly | \`suzi agents run <protocol>.<action> --key value\` |
-| Run an action and get raw JSON | \`suzi agents run <action> --output json\` |
-| Their agents | \`suzi agents\` |
-| Agent details / triggers / config | \`suzi agents view <id>\` |
-| Agent logs | \`suzi agents logs <id>\` |
-| Debugging agent issues | \`suzi debug logs <id>\` |
-| Agent execution history | \`suzi debug runs <id>\` |
-| Failed action details | \`suzi debug executions <id> --status failed\` |
-| Database-level agent logs | \`suzi debug db-logs <id>\` |
-| Wallet addresses | \`suzi accounts show\` |
-| Balances | \`suzi portfolio\` |
-| Portfolio | \`suzi portfolio\` |
-| Transactions | \`suzi transactions\` |
-| Current user / auth status | \`suzi whoami\` |
-
-**Do NOT answer "what protocols are available?" or "what actions does polymarket have?" from memory. Run the CLI.**
-
----
-
-## What is Suzi?
-
-Suzi is an autonomous agent platform for creating and executing intelligent agents that interact with blockchain protocols. Users write TypeScript agents with triggers (manual, schedule, event-based) that execute actions against protocols in a sandboxed environment.
-
----
-
-## Installing the Suzi CLI
-
-\\\`\\\`\\\`bash
-pnpm add suzi
-
-# Verify installation
-suzi --version
-\\\`\\\`\\\`
-
-### First-time setup
-
-\\\`\\\`\\\`bash
-# 1. Point to the Suzi API (production)
-suzi login --api-url https://api-3ihwe.ondigitalocean.app
-
-# 2. Browser opens for Google OAuth sign-in
-# 3. After auth, CLI shows your wallet address + QR code
-# 4. Send SOL to the displayed address to fund your wallet
-# 5. CLI auto-detects the deposit and shows your portfolio
-\\\`\\\`\\\`
-
-### Requirements
-
-- Node.js 22.x
-- pnpm 9.15.0
-
----
-
-## CLI Commands Reference
-
-### Authentication
-
-\`\`\`bash
-suzi login                    # Sign in with Google (OAuth2.0). Shows QR code for wallet funding.
-suzi login --api-url <url>    # Override API endpoint
-suzi login --web-url <url>    # Override web app URL
-suzi logout                   # Sign out and clear stored credentials
-suzi whoami                   # Show current authenticated user, wallet addresses
-\`\`\`
-
-### Accounts & Funding
-
-\`\`\`bash
-suzi accounts                 # Manage accounts and switch active account
-suzi accounts list            # List accounts (same as interactive accounts view)
-suzi accounts show            # Show full wallet addresses for active account
-suzi accounts fund            # Show deposit instructions with full addresses
-suzi accounts switch <name>   # Switch active account
-suzi accounts create <name>   # Create a new account
-suzi accounts rename <name> <newName> # Rename an account
-suzi accounts delete <name>   # Delete an account (use -f to skip confirmation)
-\`\`\`
-
-### Portfolio
-
-\`\`\`bash
-suzi portfolio                # View spot balances and Hyperliquid perp positions
-\`\`\`
-
-### Agent Management
-
-\`\`\`bash
-suzi agents                         # List all agents (ALWAYS run this for agent questions)
-suzi agents view <id>               # View agent details (spec, triggers, resources, config)
-suzi agents activate <id>           # Activate agent (allocates wallets, registers triggers)
-suzi agents deactivate <id>         # Deactivate agent
-suzi agents execute <id> [trigger]  # Manually execute a trigger (prompts if multiple)
-suzi agents logs <id>               # View agent logs (default: last 20)
-suzi agents logs <id> -n 50         # View more log entries
-suzi agents logs <id> --level error # Filter by level: info|warn|error|debug
-suzi agents delete <id>             # Delete agent (with confirmation)
-suzi agents delete <id> -f          # Delete without confirmation
-\`\`\`
-
-### Agent Deployment & Validation
-
-\`\`\`bash
-suzi validate                       # Validate agent code (auto-discovers agent file)
-suzi validate ./path/to/agent.ts    # Validate specific file (checks triggers + actions)
-suzi deploy                         # Deploy agent (auto-discovers agent.ts, src/agent.ts, index.ts)
-suzi deploy ./path/to/agent.ts      # Deploy specific file
-suzi deploy -t "My Agent"           # Set title
-suzi deploy -d "Description here"   # Set description
-suzi deploy --activate              # Activate immediately after deployment
-suzi deploy --update <agentId>      # Update existing agent's code
-\`\`\`
-
-### Debugging
-
-\`\`\`bash
-suzi debug logs <agentId>                  # View Datadog logs for an agent (last 1h)
-suzi debug logs <agentId> --status error   # Filter by log level: error, warn, info, debug
-suzi debug logs <agentId> --time-range now-1d  # Lookback: now-15m, now-1h, now-1d
-suzi debug logs <agentId> --limit 100      # Max results (default: 25, max: 1000)
-suzi debug logs <agentId> --query "@http.status_code:500"  # Append raw Datadog query
-
-suzi debug aggregate <agentId>             # Aggregate Datadog logs (counts)
-suzi debug aggregate <agentId> --group-by status  # Group by: status, host, service
-suzi debug aggregate <agentId> --time-range now-1d
-
-suzi debug db-logs <agentId>               # View agent logs from database
-suzi debug db-logs <agentId> --level error # Filter: info, warn, error, debug
-suzi debug db-logs <agentId> --run-id <id> # Filter by specific run
-suzi debug db-logs <agentId> --limit 50    # Page size (default: 50)
-suzi debug db-logs <agentId> --cursor <c>  # Pagination cursor from previous response
-
-suzi debug executions <agentId>            # View action executions from database
-suzi debug executions <agentId> --status failed  # Filter: running, completed, failed
-suzi debug executions <agentId> --run-id <id>
-
-suzi debug runs <agentId>                  # View agent runs from database
-suzi debug runs <agentId> --status failed  # Filter: running, completed, failed
-\`\`\`
-
-### Sharing & Import
-
-\`\`\`bash
-suzi share create [agentId]         # Create share link (prompts if agentId omitted)
-suzi share create --slug <slug>     # Create share link with custom slug
-suzi share create --expires <days>  # Create expiring share link
-suzi share list                     # List shared agent snapshots (alias: suzi share ls)
-suzi share update <agentId> --slug <slug>  # Publish a new shared version
-suzi share revoke <snapshotId>      # Revoke shared snapshot (use -f to skip confirmation)
-suzi import <slug>                  # Clone a shared agent by slug
-\`\`\`
-
-### Transactions
-
-\`\`\`bash
-suzi transactions                   # View recent transactions across agents (alias: suzi txns)
-suzi txns -n 30                     # Show more entries
-suzi txns --type order              # Filter: order|cancel|transfer|swap|bridge|liquidity
-suzi txns --protocol polymarket     # Filter by protocol
-suzi txns --agent <id>              # Filter by specific agent
-suzi tx-confirm <agentId> [executionId] # Show execution details and parsed input/output
-\`\`\`
-
-### Direct Action Execution
-
-\`\`\`bash
-suzi agents run <protocol>.<action> [--key value ...]   # Execute any action directly
-suzi agents run polymarket.get_event_by_slug --slug btc  # Pass params as CLI flags
-suzi agents run solana.get_native_balance                # Wallet context injected from active account
-suzi agents run <action> --json '{"key":"value"}'        # Pass all params as JSON string
-suzi agents run <action> --output json                   # Output raw JSON (default: pretty)
-suzi agents run <action> --dry-run                       # Preview request payload without executing
-\`\`\`
-
-**Notes:**
-- Wallet-requiring actions automatically receive wallet credentials from your active account (no need to pass walletId/address).
-- Parameter names are case-insensitive and support kebab-case (e.g. \`--token-id\` resolves to \`tokenID\`).
-- Values are auto-coerced using the action's JSON schema (strings, numbers, booleans, JSON objects).
-
-### Tools & Triggers
-
-\`\`\`bash
-suzi list-actions                     # List all protocols (alias: suzi actions)
-suzi list-actions --verbose           # Show all actions per protocol
-suzi list-actions --protocol <name>   # Show actions for one protocol
-suzi list-actions --protocol <name> --schema <action> # Print action schema JSON
-suzi list-actions --protocol <name> --schema a1,a2,a3 # Print schemas for multiple actions at once
-suzi list-actions --protocol <name> --schema all      # Print all schemas for a protocol
-suzi list-actions --schema proto.action1,proto.action2 # Fully-qualified names (no --protocol needed)
-suzi list-actions reload              # Force-refresh actions cache from API
-suzi list-triggers                  # List all available triggers (alias: suzi triggers)
-suzi list-triggers --verbose        # Show trigger config fields and examples
-suzi list-triggers --protocol <name> # Show triggers for one protocol
-suzi list-triggers --protocol <name> --schema <trigger> # Print trigger schema JSON
-\`\`\`
-
-### Action Parameter & Response Schemas
-
-Every action has a typed **parameters** schema (what you pass in) and a **response** schema (what the action returns). Both are available as JSON Schema via the CLI.
-
-**Before writing any action call in agent code, always run the CLI to get the current schemas:**
-
-\`\`\`bash
-# See all actions in a protocol
-suzi list-actions --protocol polymarket --verbose
-
-# Get the full JSON schema (parameters + response) for a specific action
-suzi list-actions --protocol polymarket --schema place_order
-
-# Get schemas for MULTIPLE actions at once (preferred — avoids sequential calls)
-suzi list-actions --protocol polymarket --schema place_order,cancel_order,get_market_price
-
-# Get ALL schemas for a protocol at once
-suzi list-actions --protocol polymarket --schema all
-
-# Mix protocols with fully-qualified names (no --protocol needed)
-suzi list-actions --schema polymarket.place_order,solana.get_balance
-\`\`\`
-
-**IMPORTANT: Always batch schema lookups.** When you need schemas for multiple actions, fetch them all in a single \`--schema a,b,c\` call instead of running separate commands for each action. This is significantly faster.
-
-**Do NOT guess action parameters or response fields.** Run the CLI to see the exact schemas, then use those fields in your agent code. This skill's field listings can be stale — the CLI is always up to date.
-
-### Environment Variables
-
-\`\`\`bash
-suzi env                            # Interactive env-var manager
-suzi env list                       # List env-var names and scopes
-suzi env list --agent <id>          # List env vars for a specific agent
-suzi env set <KEY>                  # Set env var (prompts for secret value)
-suzi env set <KEY> --agent <id>     # Set env var scoped to one agent
-suzi env remove <KEY>               # Remove env var
-suzi env remove <KEY> --agent <id>  # Remove scoped env var
-\`\`\`
-
-### Preferences
-
-\`\`\`bash
-suzi preferences                    # View current preferences (alias: suzi prefs)
-suzi prefs set-username [name]      # Set display username
-suzi prefs telegram                 # Connect Telegram for notifications
-suzi prefs api-url <url>            # Set API server URL
-\`\`\`
-
-### AI-Assisted Agent Creation
-
-\`\`\`bash
-suzi start                          # Create with configured default AI; falls back to Claude
-suzi start ./my-agent               # Create inside a target directory
-suzi start --ai claude              # Force Claude Code for this run
-suzi start --ai codex               # Force Codex for this run
-suzi start --set-default claude     # Set default AI provider
-suzi start --set-default codex      # Set default AI provider
-suzi start --no-scaffold            # Skip template creation for agent.ts
-\`\`\`
-
-### Agent Templates
-
-\`\`\`bash
-suzi subagents                      # List agent.md and agent.ts files in current directory
-suzi subagents init                 # Create template agent.md + agent.ts files
-suzi subagents init --dir ./myagent # Create templates in specific directory
-suzi subagents validate             # Validate agent.md (Meta/Resources/Triggers checks)
-suzi subagents validate ./agent.md  # Validate specific file
-\`\`\`
-
-### Memory & Context
-
-\`\`\`bash
-suzi memory                         # Show memory summary
-suzi memory learnings               # View recent learnings
-suzi memory log                     # View today's activity log
-suzi memory log 2026-01-15          # View a specific day
-suzi memory context                 # View active context
-suzi memory clear                   # Clear learnings (use -f to skip confirmation)
-suzi memory edit                    # Edit learnings in $EDITOR
-suzi memory export                  # Export memory files to stdout
-\`\`\`
-
-### Project Setup & Hooks
-
-\`\`\`bash
-suzi init                           # Generate SUZI.md for current project
-suzi install-hooks                  # Install global Claude Code hooks (~/.claude/hooks/)
-suzi install-hooks --preferences    # Also create starter ~/.suzi/preferences.md
-\`\`\`
-
-### Feedback & Suggestions
-
-\`\`\`bash
-suzi suggest                        # Interactive command suggestions (alias: suzi help-me)
-suzi feedback                       # Send feedback interactively
-suzi feedback -c bug -m "..."       # Non-interactive feedback submit
-suzi --help                         # Show all commands
-\`\`\`
-
-### Skills
-
-\`\`\`bash
-suzi skills                         # List available skills
-suzi skills show <name>             # Show skill details and sections
-suzi skills add <name>              # Install for Claude + Codex (default target)
-suzi skills add --all               # Install all available skills
-suzi skills add <name> --client claude|codex|both
-suzi skills add <name> --dir <path> # Install into a custom directory
-\`\`\`
-
----
-
-## Creating Agents
-
-### Quick Start
-
-\`\`\`bash
-# 1. Initialize a template
-suzi subagents init
-
-# 2. Edit agent.ts with your logic
-
-# 3. Deploy
-suzi deploy ./agent.ts
-
-# 4. Activate
-suzi agents activate <agent-id>
-
-# 5. Execute manually
-suzi agents execute <agent-id>
-\`\`\`
-
-### Agent File Structure
-
-Agent files must default-export a \`defineAgent()\` call. The file is self-contained — **no imports allowed** (the runtime provides \`defineAgent\`, \`on\`, \`resource\`, \`config\`, \`requirement\` as globals).
-
-\`\`\`typescript
-export default defineAgent({
-  meta: { ... },        // Required: name, version
-  resources: { ... },   // Optional: wallet requirements
-  config: { ... },      // Optional: user-configurable parameters
-  activationRequirements: { ... },  // Optional: balance checks before activation
-  lifecycle: { ... },   // Optional: onActivate, onDeactivate hooks
-  triggers: { ... },    // Required: at least one trigger
-});
-\`\`\`
-
-### Minimal Agent
-
-\`\`\`typescript
-export default defineAgent({
-  meta: {
-    name: 'My Agent',
-    version: '0.1.0',
-  },
-  triggers: {
-    manual: on.suzi.manual(async (ctx, input) => {
-      await ctx.actions.suzi.log({ message: 'Hello from my agent!' });
-      return { ok: true };
-    }),
-  },
-});
-\`\`\`
-
-### Full Agent Template
-
-\`\`\`typescript
-export default defineAgent({
-  meta: {
-    name: 'My Trading Agent',
-    version: '0.1.0',
-    description: 'Automated trading strategy',
-    tags: ['trading', 'solana'],
-  },
-
-  // Wallet resources the agent needs
-  resources: {
-    svmWallet: resource.wallet('svm'),   // Solana wallet
-    evmWallet: resource.wallet('evm'),   // Ethereum wallet (for Hyperliquid/Polymarket)
-  },
-
-  // User-configurable parameters (set during activation)
-  config: {
-    capital: config.number({
-      description: 'Initial capital in USDC',
-      min: 100,
-      max: 10000,
-      required: true,
-      default: 1000,
-    }),
-  },
-
-  // Balance checks before agent can activate
-  activationRequirements: {
-    __min_usdc: requirement.svmTokenBalance({
-      token: 'USDC',
-      minAmount: { $ref: 'config.capital' },  // References config value
-      description: 'Minimum USDC required',
-    }),
-    __min_sol: requirement.svmNativeBalance({
-      minAmount: 0.5,
-      description: 'Minimum SOL for transaction fees',
-    }),
-  },
-
-  // Lifecycle hooks
-  lifecycle: {
-    onActivate: async (ctx) => {
-      const { capital } = ctx.config as { capital: number };
-      await ctx.actions.suzi.log({ message: \`Activating with $\${capital} USDC\` });
-      const svmResult = await ctx.actions.suzi.get_svm_address({});
-      await ctx.actions.suzi.set_to_store({ key: 'initial_capital', value: capital });
-    },
-
-    onDeactivate: async (ctx) => {
-      await ctx.actions.suzi.log({ message: 'Deactivating — closing positions...' });
-    },
-  },
-
-  triggers: {
-    // Manual trigger — executed from dashboard or CLI
-    manual: on.suzi.manual(async (ctx, input) => {
-      await ctx.actions.suzi.log({ message: 'Manual execution' });
-      return { ok: true };
-    }),
-
-    // Schedule trigger — runs on a cron schedule
-    rebalance: on.suzi.schedule(
-      { cronExpressions: ['*/5 * * * *'] },  // Every 5 minutes
-      async (ctx) => {
-        await ctx.actions.suzi.log({ message: 'Rebalancing...' });
-        return { ok: true, action: 'rebalanced' };
-      }
-    ),
-  },
-});
-\`\`\`
-
-### Agent Context (ctx)
-
-Available in all trigger handlers and lifecycle hooks:
-
-\`\`\`typescript
-ctx.actions.<protocol>.<action>()  // Call any protocol action
-ctx.config                         // Access config values
-\`\`\`
-
-**To see what protocols and actions are available, run \`suzi list-actions --verbose\`.**
-Actions are called as \`ctx.actions.<protocol>.<action_name>({ ...params })\`.
-
-**Before writing any action call, always fetch its schema first:**
-\`\`\`bash
-suzi list-actions --protocol <name> --schema <action>
-\`\`\`
-This returns both the **parameters** (what to pass) and the **response** (what comes back). Use the response schema to know what fields are available on the result object. Never guess parameter names or response fields — always check the schema.
-
-### Validation Rules
-
-- Agent **must** default-export via \`defineAgent({})\`
-- **No imports/requires** — agent code must be self-contained
-- \`triggers\` object is **required** with at least one trigger
-- Each trigger must have a \`type\` (e.g., \`suzi.manual\`, \`suzi.schedule\`)
-- Config fields need \`type\` and \`description\`
-- The file is transpiled from TypeScript to JavaScript and executed in a VM2 sandbox
-
-### Agent Statuses
-
-| Status | Description |
-|--------|-------------|
-| \`draft\` | Created but not activated. No wallets allocated. |
-| \`active\` | Running. Schedule triggers fire on cron, event triggers are subscribed. |
-| \`inactive\` | Deactivated. Triggers stopped. Can be reactivated. |
-| \`deleted\` | Soft-deleted. Not recoverable from CLI. |
-
----
-
-## Trigger Types
-
-| Trigger | Syntax | Description |
-|---------|--------|-------------|
-| Manual | \`on.suzi.manual(handler)\` | Triggered from dashboard or \`suzi agents execute\` |
-| Schedule | \`on.suzi.schedule({ cronExpressions: ['...'] }, handler)\` | Runs on a cron schedule, interval, or calendar spec |
-| Event | \`on.<protocol>.event(config, handler)\` | Triggered by realtime protocol events |
-
-### Schedule Examples
-
-| Schedule | Meaning |
-|----------|---------|
-| \`*/1 * * * *\` | Every minute |
-| \`*/5 * * * *\` | Every 5 minutes |
-| \`0 * * * *\` | Every hour |
-| \`0 */4 * * *\` | Every 4 hours |
-| \`0 0 * * *\` | Daily at midnight |
-
-### Trigger Event Output Schemas
-
-Every trigger passes a typed \`event\` object to the handler. The \`event\` contains specific fields depending on the trigger type (e.g., price, size, side, timestamp, etc.).
-
-**Before writing a trigger handler, always run the CLI to get the current output schema:**
-
-\`\`\`bash
-# See output fields for all triggers in a protocol
-suzi list-triggers --protocol polymarket --verbose
-
-# Get the full JSON schema (configSchema + outputSchema) for a specific trigger
-suzi list-triggers --protocol polymarket --schema price_change
-\`\`\`
-
-**Do NOT guess event field names.** Run the CLI to see the exact output schema, then use those fields in your handler. This skill's field listings can be stale — the CLI is always up to date.
-
----
-
-## Common Workflows
-
-### Deploy & Activate in One Command
-
-\`\`\`bash
-suzi deploy ./agent.ts --activate
-\`\`\`
-
-### Update Running Agent Code
-
-\`\`\`bash
-suzi deploy ./agent.ts --update <agent-id>
-\`\`\`
-
-### Monitor & Debug Agent
-
-\`\`\`bash
-suzi agents logs <id>                       # Quick log check
-suzi debug logs <id> --status error         # Datadog error logs
-suzi debug runs <id> --status failed        # Failed runs
-suzi debug executions <id> --status failed  # Failed action executions
-suzi debug db-logs <id> --level error       # Database error logs
-suzi txns --agent <id>                      # View transactions
-\`\`\`
-
-### Typical Development Loop
-
-\`\`\`bash
-# 1. Create template
-suzi subagents init --dir ./my-agent
-
-# 2. Look up schemas for the actions you plan to use
-suzi list-actions --protocol <name> --schema <action>
-
-# 3. Edit agent.ts — write your logic using the exact parameter/response fields
-
-# 4. Validate before deploying (checks triggers + actions)
-suzi validate ./my-agent/agent.ts
-
-# 5. Deploy as draft
-suzi deploy ./my-agent/agent.ts
-
-# 6. Review
-suzi agents view <id>
-
-# 7. Activate
-suzi agents activate <id>
-
-# 8. Test manually
-suzi agents execute <id>
-
-# 9. Check results
-suzi agents logs <id>
-
-# 10. Iterate — update code
-suzi deploy ./my-agent/agent.ts --update <id>
-\`\`\`
-
----
-
-## Tips & Best Practices
-
-1. **Start simple** — begin with a manual trigger, test it, then add schedule/event triggers
-2. **Use \`suzi.log\`** liberally — logs are your debugging tool since agents run in a sandbox
-3. **Use \`suzi.set_to_store / get_from_store\`** for state that persists across trigger executions
-4. **Activation requirements** prevent agents from starting without sufficient funds
-5. **Kill switches** — add a schedule trigger that checks drawdown and calls \`request_deactivation\` if needed
-6. **No imports** — all code must be self-contained. Use \`ctx.actions\` for all external interactions
-7. **Test with manual triggers first**, then add schedules
-8. **Connect Telegram** (\`suzi prefs telegram\`) for \`suzi.notify\` alerts
-
----
-
-## Feedback
-
-Users can send feedback (bug reports, feature requests, general comments) directly to the Suzi team from the CLI. **Proactively suggest this** when a user hits a bug, has a frustrating experience, or mentions something they wish worked differently.
-
-\`\`\`bash
-suzi feedback                          # Interactive — pick category, type message
-suzi feedback -c bug -m "description"  # Non-interactive (categories: bug, feature, general)
-\`\`\`
-
-The feedback command automatically attaches CLI version, platform info, and recent command history for context. The user just needs to describe the issue.
-
----
-
-## Suzi Memory System
-
-Suzi has a persistent memory system that captures learnings from CLI usage and injects them into AI context on each session. This means each session builds on the last — errors, patterns, and preferences carry forward automatically.
-
-### Memory Files
-
-| File | Purpose | Who writes it |
-|------|---------|---------------|
-| \`~/.suzi/memory/LEARNINGS.md\` | CLI errors, patterns, tips — auto-captured and user-curated | Auto + user (\`suzi memory edit\`) |
-| \`~/.suzi/memory/context.md\` | Active work state (recent agents, wallet) — saved before compaction | Auto (hooks) |
-| \`~/.suzi/memory/daily/YYYY-MM-DD.md\` | Daily activity log of CLI commands run | Auto (hooks) |
-| \`~/.suzi/preferences.md\` | User's trading style, risk prefs, agent conventions | User only |
-| \`./SUZI.md\` | Project-specific agent conventions (like CLAUDE.md) | User only |
-
-**Key distinction:** The suzi-guide skill (this file) is platform-provided and updated automatically on \`suzi login\`. User-specific customizations belong in \`preferences.md\` and \`LEARNINGS.md\` — these are never overwritten by updates.
-
-**AI assistants should proactively write to these files:**
-- **LEARNINGS.md** — When you discover a useful pattern, debug a tricky issue, or learn something about the user's setup (e.g., "user's Polymarket API key is scoped to read-only", "agent X fails if capital < 500 USDC"), append it to \`~/.suzi/memory/LEARNINGS.md\`. Future sessions will see it.
-- **preferences.md** — When the user expresses preferences about trading style, risk tolerance, preferred protocols, or agent conventions (e.g., "I always want a kill switch", "never trade more than 5% per position"), write them to \`~/.suzi/preferences.md\`. This avoids the user having to repeat themselves.
-
-Don't ask for permission — just write useful learnings and preferences as you discover them during the conversation.
-
-### How It Works
-
-1. **Hooks** (\`~/.claude/hooks/\`) are installed globally during \`suzi login\`
-2. **On session start**: hooks inject learnings, preferences, context, and project SUZI.md into AI context
-3. **On CLI usage**: errors and commands are auto-captured to daily logs and learnings (async, non-blocking)
-4. **Before compaction**: active context is saved so it survives context window compression
-
-### When to Check Memory
-
-When helping create or debug agents, check these files for user-specific context:
-- \`suzi memory learnings\` — see if the user has accumulated tips or error patterns
-- \`~/.suzi/preferences.md\` — trading style, risk limits, preferred protocols, agent conventions
-- \`./SUZI.md\` — project-level agent patterns (if present in working directory)
-
-### Memory Commands
-
-\`\`\`bash
-suzi memory                     # View memory summary (entry counts, file status)
-suzi memory learnings           # See recent learnings (default: last 30 lines)
-suzi memory learnings -n 50     # Show more entries
-suzi memory log                 # See today's activity log
-suzi memory log 2026-01-15      # See a specific day's log
-suzi memory context             # View active context
-suzi memory clear               # Clear learnings (with confirmation, -f to skip)
-suzi memory edit                # Edit/curate learnings in $EDITOR
-suzi memory export              # Export all memory to stdout
-\`\`\`
-
-### Setup
-
-\`\`\`bash
-suzi install-hooks              # Install global Claude Code hooks (~/.claude/hooks/)
-suzi install-hooks --preferences # Also create a starter ~/.suzi/preferences.md
-suzi init                       # Generate SUZI.md for current project
-\`\`\`
-`;
-//# sourceMappingURL=suzi-guide.js.map

package/dist/lib/suzi-guide.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"suzi-guide.js","sourceRoot":"","sources":["../../src/lib/suzi-guide.ts"],"names":[],"mappings":";AAAA,iEAAiE;;;AAEpD,QAAA,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoqBjC,CAAC"}