initialize-workspacelisted

# Initialize Workspace Create the smallest Git-backed home in which the user's adopted Skills and scenario Workflows can become the local run truth. ## Apply 1. Confirm or infer one target directory and path-safe Workspace id. Inspect existing contents before writing; preserve unrelated user files and stop before any destructive cleanup. 2. Locate the user's maintained Agent Skill Library as the first-priority upstream. Record its current local path and, when available, Git remote and commit in the human-readable Profile. Do not copy or install its domain Skills yet. 3. Create this minimal identity file: ```yaml apiVersion: asl-wep/v0.2.0-draft.1 kind: WorkspaceManifest metadata: id: <workspace-id> spec: {} ``` 4. Create `PROFILE.md` with only known long-term goals, audience, preferences, boundaries, and the first-priority Library source. Mark unknowns as unknown; do not force a long interview before useful work can begin. 5. Create `skills/`, `workflows/`, `candidates/`, `trials/`, `feedback/`, and `archive/` as empty lifecycle areas. Do not add registries, lockfiles, caches, logs, runtime state, or placeholder Skill packages. 6. Initialize Git at the Workspace root if it is not already inside the intended repository. Keep secrets and host-generated state out of Git. Show the exact initialization diff before making the first traceable commit. 7. Validate the Workspace with the installed Harness. An empty Workspace is valid; host projection waits u