olivercode-clilisted

# OliverCode CLI Design Canonical contract: `docs/OLIVERCODE_LAUNCHER.md`. Read that first — this skill adds design rationale and pitfalls on top of it. ## Current Surface Two thin, delegating launchers, both self-locating from `__file__`/script path — no hardcoded vault/home paths, no external runtime dependency: - **`runtime/control-plane/olivercode`** (bash shim) — resolves its own repo root two levels up, then `exec python3 "$OC_ROOT/scripts/olivercode" "$@"`. - **`scripts/olivercode`** (the actual Python CLI) — resolves `OC_ROOT` from its own file location, two levels up. Both run identically from cron, a container, or any working directory — nothing is hardcoded. Four commands: - `olivercode health` — checks `runtime/control-plane/OLIVERCODE_DEPENDENCY.md`'s declared paths resolve, checks core entrypoints exist, checks placement drift (SYS-2). Prints HEALTHY/DEGRADED with a pass/fail count. - `olivercode update` — `git -C <OC_ROOT> pull`, then runs `sync-hooks` (below) so a pull always converges hooks too. - `olivercode sync-hooks` — converges the pre-commit hook + `core.hooksPath` across every fleet repo and the vault (SYS-3). Also runs automatically at the end of `update`. - `olivercode skills [--grep TERM]` — lists OliverCode's own orchestration skills under `skills/`, reading name/description directly from each `SKILL.md`'s frontmatter (never from `skills/INDEX.md`'s prose tables, which are for human browsing and can drift). `--grep` filters case-insensitively