garelier-control-projectlisted

# Garelier Project Control This skill turns the **currently running AI** into the manager of one canonical Garelier control namespace. It uses full Garelier's persistent storage and artifact formats without enabling roles, branches, worktrees, lanes, or driver. `garelier-control-project` plus `garelier-control-library` is the standalone **Garelier Control** management plane. It can remain lightweight indefinitely or later gain full Garelier execution without changing its durable management data. ## Activation 1. Read `../garelier-core/control_contract.md`. 2. Resolve the managed `pm_id`: - use the id explicitly named by the user; - otherwise use the sole evident `__garelier/<pm_id>/control/control.toml`; - if multiple control namespaces exist, list them and ask which one to manage; never silently choose `_workshop` or the first match; - otherwise default to single-user id `_workshop`. 3. Treat that namespace as the management authority for this session. 4. Read `control/control.toml`, `control/project_dashboard/README.md`, then only the relevant dashboard/artifact files. `_workshop` is preferred over `_workspace`: `workspace` is a deprecated Garelier alias for `runtime` and would make the control/runtime boundary ambiguous. This selection rule also applies after full Garelier is running: a separately launched AI can use `garelier-control-project` against any full or control-only namespace. ## Initialize When the namespace is absent, run the matching