feat: updade workspace

packages/casan-control-panel/README.md

@@ -38,6 +38,17 @@ Settings management:
   permission; calls `rbac-check.py` before `control-plane-settings.py set`.
 - `POST /api/v1/settings/rollback` — governed rollback through the same core CLI.
 
+Goal workspace context:
+
+- `GET /api/v1/goals/projects` — lists active project IDs and context roots from the
+  harness-owned project registry after RBAC filtering; browser-supplied paths are never accepted.
+- `POST /api/v1/goals` requires `{ goal, projectId }`. H1 resolves the registry again,
+  produces a size-limited redacted manifest/snapshot, and gives the exact same snapshot to
+  local and cloud models. Account-model CLIs remain inside an empty temporary sandbox.
+- Goals requesting workspace side effects create a tenant-scoped
+  `goal.workspace.execute` approval proposal and finish as `requires_approval`; this flow
+  does not write source files or execute a coding action.
+
 Local management headers: `x-casan-actor`, `x-casan-role`, `x-casan-project`,
 `x-casan-tenant`. Missing role defaults to `viewer`, so writes fail closed.