loudmouth-ai 0.1.0 → 0.2.0

package/extensions/nostr/src/types.test.ts

@@ -1,161 +0,0 @@
-import { describe, expect, it } from "vitest";
-import {
-  listNostrAccountIds,
-  resolveDefaultNostrAccountId,
-  resolveNostrAccount,
-} from "./types.js";
-
-const TEST_PRIVATE_KEY = "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef";
-
-describe("listNostrAccountIds", () => {
-  it("returns empty array when not configured", () => {
-    const cfg = { channels: {} };
-    expect(listNostrAccountIds(cfg)).toEqual([]);
-  });
-
-  it("returns empty array when nostr section exists but no privateKey", () => {
-    const cfg = { channels: { nostr: { enabled: true } } };
-    expect(listNostrAccountIds(cfg)).toEqual([]);
-  });
-
-  it("returns default when privateKey is configured", () => {
-    const cfg = {
-      channels: {
-        nostr: { privateKey: TEST_PRIVATE_KEY },
-      },
-    };
-    expect(listNostrAccountIds(cfg)).toEqual(["default"]);
-  });
-});
-
-describe("resolveDefaultNostrAccountId", () => {
-  it("returns default when configured", () => {
-    const cfg = {
-      channels: {
-        nostr: { privateKey: TEST_PRIVATE_KEY },
-      },
-    };
-    expect(resolveDefaultNostrAccountId(cfg)).toBe("default");
-  });
-
-  it("returns default when not configured", () => {
-    const cfg = { channels: {} };
-    expect(resolveDefaultNostrAccountId(cfg)).toBe("default");
-  });
-});
-
-describe("resolveNostrAccount", () => {
-  it("resolves configured account", () => {
-    const cfg = {
-      channels: {
-        nostr: {
-          privateKey: TEST_PRIVATE_KEY,
-          name: "Test Bot",
-          relays: ["wss://test.relay"],
-          dmPolicy: "pairing" as const,
-        },
-      },
-    };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.accountId).toBe("default");
-    expect(account.name).toBe("Test Bot");
-    expect(account.enabled).toBe(true);
-    expect(account.configured).toBe(true);
-    expect(account.privateKey).toBe(TEST_PRIVATE_KEY);
-    expect(account.publicKey).toMatch(/^[0-9a-f]{64}$/);
-    expect(account.relays).toEqual(["wss://test.relay"]);
-  });
-
-  it("resolves unconfigured account with defaults", () => {
-    const cfg = { channels: {} };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.accountId).toBe("default");
-    expect(account.enabled).toBe(true);
-    expect(account.configured).toBe(false);
-    expect(account.privateKey).toBe("");
-    expect(account.publicKey).toBe("");
-    expect(account.relays).toContain("wss://relay.damus.io");
-    expect(account.relays).toContain("wss://nos.lol");
-  });
-
-  it("handles disabled channel", () => {
-    const cfg = {
-      channels: {
-        nostr: {
-          enabled: false,
-          privateKey: TEST_PRIVATE_KEY,
-        },
-      },
-    };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.enabled).toBe(false);
-    expect(account.configured).toBe(true);
-  });
-
-  it("handles custom accountId parameter", () => {
-    const cfg = {
-      channels: {
-        nostr: { privateKey: TEST_PRIVATE_KEY },
-      },
-    };
-    const account = resolveNostrAccount({ cfg, accountId: "custom" });
-
-    expect(account.accountId).toBe("custom");
-  });
-
-  it("handles allowFrom config", () => {
-    const cfg = {
-      channels: {
-        nostr: {
-          privateKey: TEST_PRIVATE_KEY,
-          allowFrom: ["npub1test", "0123456789abcdef"],
-        },
-      },
-    };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.config.allowFrom).toEqual(["npub1test", "0123456789abcdef"]);
-  });
-
-  it("handles invalid private key gracefully", () => {
-    const cfg = {
-      channels: {
-        nostr: {
-          privateKey: "invalid-key",
-        },
-      },
-    };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.configured).toBe(true); // key is present
-    expect(account.publicKey).toBe(""); // but can't derive pubkey
-  });
-
-  it("preserves all config options", () => {
-    const cfg = {
-      channels: {
-        nostr: {
-          privateKey: TEST_PRIVATE_KEY,
-          name: "Bot",
-          enabled: true,
-          relays: ["wss://relay1", "wss://relay2"],
-          dmPolicy: "allowlist" as const,
-          allowFrom: ["pubkey1", "pubkey2"],
-        },
-      },
-    };
-    const account = resolveNostrAccount({ cfg });
-
-    expect(account.config).toEqual({
-      privateKey: TEST_PRIVATE_KEY,
-      name: "Bot",
-      enabled: true,
-      relays: ["wss://relay1", "wss://relay2"],
-      dmPolicy: "allowlist",
-      allowFrom: ["pubkey1", "pubkey2"],
-    });
-  });
-});

package/extensions/nostr/src/types.ts

@@ -1,99 +0,0 @@
-import type { ClawdbotConfig } from "clawdbot/plugin-sdk";
-import { getPublicKeyFromPrivate } from "./nostr-bus.js";
-import { DEFAULT_RELAYS } from "./nostr-bus.js";
-import type { NostrProfile } from "./config-schema.js";
-
-export interface NostrAccountConfig {
-  enabled?: boolean;
-  name?: string;
-  privateKey?: string;
-  relays?: string[];
-  dmPolicy?: "pairing" | "allowlist" | "open" | "disabled";
-  allowFrom?: Array<string | number>;
-  profile?: NostrProfile;
-}
-
-export interface ResolvedNostrAccount {
-  accountId: string;
-  name?: string;
-  enabled: boolean;
-  configured: boolean;
-  privateKey: string;
-  publicKey: string;
-  relays: string[];
-  profile?: NostrProfile;
-  config: NostrAccountConfig;
-}
-
-const DEFAULT_ACCOUNT_ID = "default";
-
-/**
- * List all configured Nostr account IDs
- */
-export function listNostrAccountIds(cfg: ClawdbotConfig): string[] {
-  const nostrCfg = (cfg.channels as Record<string, unknown> | undefined)?.nostr as
-    | NostrAccountConfig
-    | undefined;
-
-  // If privateKey is configured at top level, we have a default account
-  if (nostrCfg?.privateKey) {
-    return [DEFAULT_ACCOUNT_ID];
-  }
-
-  return [];
-}
-
-/**
- * Get the default account ID
- */
-export function resolveDefaultNostrAccountId(cfg: ClawdbotConfig): string {
-  const ids = listNostrAccountIds(cfg);
-  if (ids.includes(DEFAULT_ACCOUNT_ID)) return DEFAULT_ACCOUNT_ID;
-  return ids[0] ?? DEFAULT_ACCOUNT_ID;
-}
-
-/**
- * Resolve a Nostr account from config
- */
-export function resolveNostrAccount(opts: {
-  cfg: ClawdbotConfig;
-  accountId?: string | null;
-}): ResolvedNostrAccount {
-  const accountId = opts.accountId ?? DEFAULT_ACCOUNT_ID;
-  const nostrCfg = (opts.cfg.channels as Record<string, unknown> | undefined)?.nostr as
-    | NostrAccountConfig
-    | undefined;
-
-  const baseEnabled = nostrCfg?.enabled !== false;
-  const privateKey = nostrCfg?.privateKey ?? "";
-  const configured = Boolean(privateKey.trim());
-
-  let publicKey = "";
-  if (configured) {
-    try {
-      publicKey = getPublicKeyFromPrivate(privateKey);
-    } catch {
-      // Invalid key - leave publicKey empty, configured will indicate issues
-    }
-  }
-
-  return {
-    accountId,
-    name: nostrCfg?.name?.trim() || undefined,
-    enabled: baseEnabled,
-    configured,
-    privateKey,
-    publicKey,
-    relays: nostrCfg?.relays ?? DEFAULT_RELAYS,
-    profile: nostrCfg?.profile,
-    config: {
-      enabled: nostrCfg?.enabled,
-      name: nostrCfg?.name,
-      privateKey: nostrCfg?.privateKey,
-      relays: nostrCfg?.relays,
-      dmPolicy: nostrCfg?.dmPolicy,
-      allowFrom: nostrCfg?.allowFrom,
-      profile: nostrCfg?.profile,
-    },
-  };
-}

package/extensions/nostr/test/setup.ts

@@ -1,5 +0,0 @@
-// Test setup file for nostr extension
-import { vi } from "vitest";
-
-// Mock console.error to suppress noise in tests
-vi.spyOn(console, "error").mockImplementation(() => {});

package/extensions/open-prose/README.md

@@ -1,25 +0,0 @@
-# OpenProse (plugin)
-
-Adds the OpenProse skill pack and `/prose` slash command.
-
-## Enable
-
-Bundled plugins are disabled by default. Enable this one:
-
-```json
-{
-  "plugins": {
-    "entries": {
-      "open-prose": { "enabled": true }
-    }
-  }
-}
-```
-
-Restart the Gateway after enabling.
-
-## What you get
-
-- `/prose` slash command (user-invocable skill)
-- OpenProse VM semantics (`.prose` programs + multi-agent orchestration)
-- Telemetry support (best-effort, per OpenProse spec)

package/extensions/open-prose/clawdbot.plugin.json

@@ -1,11 +0,0 @@
-{
-  "id": "open-prose",
-  "name": "OpenProse",
-  "description": "OpenProse VM skill pack with a /prose slash command.",
-  "skills": ["./skills"],
-  "configSchema": {
-    "type": "object",
-    "additionalProperties": false,
-    "properties": {}
-  }
-}

package/extensions/open-prose/index.ts

@@ -1,5 +0,0 @@
-import type { ClawdbotPluginApi } from "../../src/plugins/types.js";
-
-export default function register(_api: ClawdbotPluginApi) {
-  // OpenProse is delivered via plugin-shipped skills.
-}

package/extensions/open-prose/package.json

@@ -1,11 +0,0 @@
-{
-  "name": "@clawdbot/open-prose",
-  "version": "2026.1.25",
-  "type": "module",
-  "description": "OpenProse VM skill pack plugin (slash command + telemetry).",
-  "clawdbot": {
-    "extensions": [
-      "./index.ts"
-    ]
-  }
-}

package/extensions/open-prose/skills/prose/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 OpenProse
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/extensions/open-prose/skills/prose/SKILL.md

@@ -1,318 +0,0 @@
----
-name: prose
-description: OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
-metadata: {"clawdbot":{"emoji":"🪶","homepage":"https://www.prose.md"}}
----
-
-# OpenProse Skill
-
-OpenProse is a programming language for AI sessions. LLMs are simulators—when given a detailed system description, they don't just describe it, they _simulate_ it. The `prose.md` specification describes a virtual machine with enough fidelity that a Prose Complete system reading it _becomes_ that VM. Simulation with sufficient fidelity is implementation. **You are the Prose Complete system.**
-
-## Clawdbot Runtime Mapping
-
-- **Task tool** in the upstream spec == Clawdbot `sessions_spawn`
-- **File I/O** == Clawdbot `read`/`write`
-- **Remote fetch** == Clawdbot `web_fetch` (or `exec` with curl when POST is required)
-
-## When to Activate
-
-Activate this skill when the user:
-
-- **Uses ANY `prose` command** (e.g., `prose boot`, `prose run`, `prose compile`, `prose update`, `prose help`, etc.)
-- Asks to run a `.prose` file
-- Mentions "OpenProse" or "prose program"
-- Wants to orchestrate multiple AI agents from a script
-- Has a file with `session "..."` or `agent name:` syntax
-- Wants to create a reusable workflow
-
-## Command Routing
-
-When a user invokes `prose <command>`, intelligently route based on intent:
-
-| Command | Action |
-|---------|--------|
-| `prose help` | Load `help.md`, guide user to what they need |
-| `prose run <file>` | Load VM (`prose.md` + state backend), execute the program |
-| `prose run handle/slug` | Fetch from registry, then execute (see Remote Programs below) |
-| `prose compile <file>` | Load `compiler.md`, validate the program |
-| `prose update` | Run migration (see Migration section below) |
-| `prose examples` | Show or run example programs from `examples/` |
-| Other | Intelligently interpret based on context |
-
-### Important: Single Skill
-
-There is only ONE skill: `open-prose`. There are NO separate skills like `prose-run`, `prose-compile`, or `prose-boot`. All `prose` commands route through this single skill.
-
-### Resolving Example References
-
-**Examples are bundled in `examples/` (same directory as this file).** When users reference examples by name (e.g., "run the gastown example"):
-
-1. Read `examples/` to list available files
-2. Match by partial name, keyword, or number
-3. Run with: `prose run examples/28-gas-town.prose`
-
-**Common examples by keyword:**
-| Keyword | File |
-|---------|------|
-| hello, hello world | `examples/01-hello-world.prose` |
-| gas town, gastown | `examples/28-gas-town.prose` |
-| captain, chair | `examples/29-captains-chair.prose` |
-| forge, browser | `examples/37-the-forge.prose` |
-| parallel | `examples/16-parallel-reviews.prose` |
-| pipeline | `examples/21-pipeline-operations.prose` |
-| error, retry | `examples/22-error-handling.prose` |
-
-### Remote Programs
-
-You can run any `.prose` program from a URL or registry reference:
-
-```bash
-# Direct URL — any fetchable URL works
-prose run https://raw.githubusercontent.com/openprose/prose/main/skills/open-prose/examples/48-habit-miner.prose
-
-# Registry shorthand — handle/slug resolves to p.prose.md
-prose run irl-danb/habit-miner
-prose run alice/code-review
-```
-
-**Resolution rules:**
-
-| Input | Resolution |
-|-------|------------|
-| Starts with `http://` or `https://` | Fetch directly from URL |
-| Contains `/` but no protocol | Resolve to `https://p.prose.md/{path}` |
-| Otherwise | Treat as local file path |
-
-**Steps for remote programs:**
-
-1. Apply resolution rules above
-2. Fetch the `.prose` content
-3. Load the VM and execute as normal
-
-This same resolution applies to `use` statements inside `.prose` files:
-
-```prose
-use "https://example.com/my-program.prose"  # Direct URL
-use "alice/research" as research             # Registry shorthand
-```
-
----
-
-## File Locations
-
-**Do NOT search for OpenProse documentation files.** All skill files are co-located with this SKILL.md file:
-
-| File                      | Location                    | Purpose                                   |
-| ------------------------- | --------------------------- | ----------------------------------------- |
-| `prose.md`                | Same directory as this file | VM semantics (load to run programs)       |
-| `help.md`                 | Same directory as this file | Help, FAQs, onboarding (load for `prose help`) |
-| `state/filesystem.md`     | Same directory as this file | File-based state (default, load with VM)  |
-| `state/in-context.md`     | Same directory as this file | In-context state (on request)             |
-| `state/sqlite.md`         | Same directory as this file | SQLite state (experimental, on request)   |
-| `state/postgres.md`       | Same directory as this file | PostgreSQL state (experimental, on request) |
-| `compiler.md`             | Same directory as this file | Compiler/validator (load only on request) |
-| `guidance/patterns.md`    | Same directory as this file | Best practices (load when writing .prose) |
-| `guidance/antipatterns.md`| Same directory as this file | What to avoid (load when writing .prose)  |
-| `examples/`               | Same directory as this file | 37 example programs                       |
-
-**User workspace files** (these ARE in the user's project):
-
-| File/Directory   | Location                 | Purpose                             |
-| ---------------- | ------------------------ | ----------------------------------- |
-| `.prose/.env`    | User's working directory | Config (key=value format) |
-| `.prose/runs/`   | User's working directory | Runtime state for file-based mode   |
-| `.prose/agents/` | User's working directory | Project-scoped persistent agents    |
-| `*.prose` files  | User's project           | User-created programs to execute    |
-
-**User-level files** (in user's home directory, shared across all projects):
-
-| File/Directory    | Location         | Purpose                                  |
-| ----------------- | ---------------- | ---------------------------------------- |
-| `~/.prose/agents/`| User's home dir  | User-scoped persistent agents (cross-project) |
-
-When you need to read `prose.md` or `compiler.md`, read them from the same directory where you found this SKILL.md file. Never search the user's workspace for these files.
-
----
-
-## Core Documentation
-
-| File                  | Purpose              | When to Load                                   |
-| --------------------- | -------------------- | ---------------------------------------------- |
-| `prose.md`            | VM / Interpreter     | Always load to run programs                    |
-| `state/filesystem.md` | File-based state     | Load with VM (default)                         |
-| `state/in-context.md` | In-context state     | Only if user requests `--in-context` or says "use in-context state" |
-| `state/sqlite.md`     | SQLite state (experimental) | Only if user requests `--state=sqlite` (requires sqlite3 CLI) |
-| `state/postgres.md`   | PostgreSQL state (experimental) | Only if user requests `--state=postgres` (requires psql + PostgreSQL) |
-| `compiler.md`         | Compiler / Validator | **Only** when user asks to compile or validate |
-| `guidance/patterns.md` | Best practices      | Load when **writing** new .prose files         |
-| `guidance/antipatterns.md` | What to avoid  | Load when **writing** new .prose files         |
-
-### Authoring Guidance
-
-When the user asks you to **write or create** a new `.prose` file, load the guidance files:
-- `guidance/patterns.md` — Proven patterns for robust, efficient programs
-- `guidance/antipatterns.md` — Common mistakes to avoid
-
-Do **not** load these when running or compiling—they're for authoring only.
-
-### State Modes
-
-OpenProse supports three state management approaches:
-
-| Mode | When to Use | State Location |
-|------|-------------|----------------|
-| **filesystem** (default) | Complex programs, resumption needed, debugging | `.prose/runs/{id}/` files |
-| **in-context** | Simple programs (<30 statements), no persistence needed | Conversation history |
-| **sqlite** (experimental) | Queryable state, atomic transactions, flexible schema | `.prose/runs/{id}/state.db` |
-| **postgres** (experimental) | True concurrent writes, external integrations, team collaboration | PostgreSQL database |
-
-**Default behavior:** When loading `prose.md`, also load `state/filesystem.md`. This is the recommended mode for most programs.
-
-**Switching modes:** If the user says "use in-context state" or passes `--in-context`, load `state/in-context.md` instead.
-
-**Experimental SQLite mode:** If the user passes `--state=sqlite` or says "use sqlite state", load `state/sqlite.md`. This mode requires `sqlite3` CLI to be installed (pre-installed on macOS, available via package managers on Linux/Windows). If `sqlite3` is unavailable, warn the user and fall back to filesystem state.
-
-**Experimental PostgreSQL mode:** If the user passes `--state=postgres` or says "use postgres state":
-
-**⚠️ Security Note:** Database credentials in `OPENPROSE_POSTGRES_URL` are passed to subagent sessions and visible in logs. Advise users to use a dedicated database with limited-privilege credentials. See `state/postgres.md` for secure setup guidance.
-
-1. **Check for connection configuration first:**
-   ```bash
-   # Check .prose/.env for OPENPROSE_POSTGRES_URL
-   cat .prose/.env 2>/dev/null | grep OPENPROSE_POSTGRES_URL
-   # Or check environment variable
-   echo $OPENPROSE_POSTGRES_URL
-   ```
-
-2. **If connection string exists, verify connectivity:**
-   ```bash
-   psql "$OPENPROSE_POSTGRES_URL" -c "SELECT 1" 2>&1
-   ```
-
-3. **If not configured or connection fails, advise the user:**
-   ```
-   ⚠️  PostgreSQL state requires a connection URL.
-
-   To configure:
-   1. Set up a PostgreSQL database (Docker, local, or cloud)
-   2. Add connection string to .prose/.env:
-
-      echo "OPENPROSE_POSTGRES_URL=postgresql://user:pass@localhost:5432/prose" >> .prose/.env
-
-   Quick Docker setup:
-      docker run -d --name prose-pg -e POSTGRES_DB=prose -e POSTGRES_HOST_AUTH_METHOD=trust -p 5432:5432 postgres:16
-      echo "OPENPROSE_POSTGRES_URL=postgresql://postgres@localhost:5432/prose" >> .prose/.env
-
-   See state/postgres.md for detailed setup options.
-   ```
-
-4. **Only after successful connection check, load `state/postgres.md`**
-
-This mode requires both `psql` CLI and a running PostgreSQL server. If either is unavailable, warn and offer fallback to filesystem state.
-
-**Context warning:** `compiler.md` is large. Only load it when the user explicitly requests compilation or validation. After compiling, recommend `/compact` or a new session before running—don't keep both docs in context.
-
-## Examples
-
-The `examples/` directory contains 37 example programs:
-
-- **01-08**: Basics (hello world, research, code review, debugging)
-- **09-12**: Agents and skills
-- **13-15**: Variables and composition
-- **16-19**: Parallel execution
-- **20-21**: Loops and pipelines
-- **22-23**: Error handling
-- **24-27**: Advanced (choice, conditionals, blocks, interpolation)
-- **28**: Gas Town (multi-agent orchestration)
-- **29-31**: Captain's chair pattern (persistent orchestrator)
-- **33-36**: Production workflows (PR auto-fix, content pipeline, feature factory, bug hunter)
-- **37**: The Forge (build a browser from scratch)
-
-Start with `01-hello-world.prose` or try `37-the-forge.prose` to watch AI build a web browser.
-
-## Execution
-
-When first invoking the OpenProse VM in a session, display this banner:
-
-```
-┌─────────────────────────────────────┐
-│         ◇ OpenProse VM ◇            │
-│       A new kind of computer        │
-└─────────────────────────────────────┘
-```
-
-To execute a `.prose` file, you become the OpenProse VM:
-
-1. **Read `prose.md`** — this document defines how you embody the VM
-2. **You ARE the VM** — your conversation is its memory, your tools are its instructions
-3. **Spawn sessions** — each `session` statement triggers a Task tool call
-4. **Narrate state** — use the narration protocol to track execution ([Position], [Binding], [Success], etc.)
-5. **Evaluate intelligently** — `**...**` markers require your judgment
-
-## Help & FAQs
-
-For syntax reference, FAQs, and getting started guidance, load `help.md`.
-
----
-
-## Migration (`prose update`)
-
-When a user invokes `prose update`, check for legacy file structures and migrate them to the current format.
-
-### Legacy Paths to Check
-
-| Legacy Path | Current Path | Notes |
-|-------------|--------------|-------|
-| `.prose/state.json` | `.prose/.env` | Convert JSON to key=value format |
-| `.prose/execution/` | `.prose/runs/` | Rename directory |
-
-### Migration Steps
-
-1. **Check for `.prose/state.json`**
-   - If exists, read the JSON content
-   - Convert to `.env` format:
-     ```json
-     {"OPENPROSE_TELEMETRY": "enabled", "USER_ID": "user-xxx", "SESSION_ID": "sess-xxx"}
-     ```
-     becomes:
-     ```env
-     OPENPROSE_TELEMETRY=enabled
-     USER_ID=user-xxx
-     SESSION_ID=sess-xxx
-     ```
-   - Write to `.prose/.env`
-   - Delete `.prose/state.json`
-
-2. **Check for `.prose/execution/`**
-   - If exists, rename to `.prose/runs/`
-   - The internal structure of run directories may also have changed; migration of individual run state is best-effort
-
-3. **Create `.prose/agents/` if missing**
-   - This is a new directory for project-scoped persistent agents
-
-### Migration Output
-
-```
-🔄 Migrating OpenProse workspace...
-  ✓ Converted .prose/state.json → .prose/.env
-  ✓ Renamed .prose/execution/ → .prose/runs/
-  ✓ Created .prose/agents/
-✅ Migration complete. Your workspace is up to date.
-```
-
-If no legacy files are found:
-```
-✅ Workspace already up to date. No migration needed.
-```
-
-### Skill File References (for maintainers)
-
-These documentation files were renamed in the skill itself (not user workspace):
-
-| Legacy Name | Current Name |
-|-------------|--------------|
-| `docs.md` | `compiler.md` |
-| `patterns.md` | `guidance/patterns.md` |
-| `antipatterns.md` | `guidance/antipatterns.md` |
-
-If you encounter references to the old names in user prompts or external docs, map them to the current paths.