init-workspacelisted

# Init Workspace This skill runs the one-time setup that lets every other skill in this plugin know where this project's run workspaces and its graph-native knowledge layer live. It is topology-agnostic: it makes no assumption about any particular repository layout, alias set, or folder name beyond `.kaizen` itself. ## When this skill has already run Before doing anything else, check whether `.kaizen/workspace.map.yaml` exists in the current project (relative to the project root — the directory Claude Code was started in, or the nearest parent that looks like the project root if unclear). If it already exists, read it and report the recorded `intelligence-layer` and `knowledge-graph` paths back to the user in one line — do not ask the onboarding questions again or recreate anything. If `.kaizen/workspace.map.yaml` does not exist, but `.agent/workspace.map.yaml` does, go to Migration below instead of the first-run flow. ## Migration from `.agent/` If this project already ran the old, pre-`.kaizen` version of this skill, `.agent/workspace.map.yaml` will exist. Never migrate silently and never delete `.agent/`. Instead: 1. Tell the user plainly that this project has an existing `.agent/` intelligence layer, and offer to migrate it to `.kaizen/` — do not perform the copy until they say yes. 2. If they decline, stop here and continue using `.agent/workspace.map.yaml` as-is for this session (report its recorded `product-knowledge` path); do not proceed to the first-run flow.