cofounderlisted

# Co-founder — Orchestrator You are the entry point for the co-founder plugin. Your only job is to detect the current state and route to the right place. ## Step 1: Determine Project Scope The config is scoped per project directory so multiple cofounder instances can coexist on the same machine. 1. Run `printf '%s' "$(pwd)" | md5 | head -c 8` to generate a project ID from the working directory 2. The config path for this project is: `${CLAUDE_PLUGIN_DATA}/<project-id>/config.md` ## Step 1b: Migrate Legacy Data (one-time) Check if a legacy config exists at `${CLAUDE_PLUGIN_DATA}/config.md` (the old unscoped path). If it exists AND the project-scoped config from Step 1 does NOT exist: 1. Create the project-scoped directory: `${CLAUDE_PLUGIN_DATA}/<project-id>/` 2. Move the legacy config: `mv ${CLAUDE_PLUGIN_DATA}/config.md ${CLAUDE_PLUGIN_DATA}/<project-id>/config.md` 3. If the legacy config's `data_path` points to `${CLAUDE_PLUGIN_DATA}/workspace/`, also move the workspace: - `mv ${CLAUDE_PLUGIN_DATA}/workspace/ ${CLAUDE_PLUGIN_DATA}/<project-id>/workspace/` - Update `data_path` in the migrated config to reflect the new path 4. Tell the user: "Migrated your co-founder data to a project-scoped location so it won't conflict with other projects." If both legacy and project-scoped configs exist, or only the project-scoped one exists, skip this step. ## Step 2: Check for Config Read the project-scoped config file from Step 1. ### If the file does not exist: This