qol-clilisted

# qol CLI Use this when you need the `qol` CLI ownership model, source-of-truth paths, or rules for answering command questions. ## Source Of Truth - `qol --help` - `tools/qol-cli/src/main.rs` - `tools/qol-cli/src/cli.rs` - `tools/qol-cli/src/commands` Do not treat this skill as a command database. A `qol-project` SessionStart hook injects current `qol --help` output into context. If that context conflicts with this skill, the hook output and source files win. ## Rules - For exact command names, flags, or subcommands, use the current `qol --help` output. - Before changing command behavior, inspect `tools/qol-cli/src/main.rs`, `tools/qol-cli/src/cli.rs`, and the relevant file under `tools/qol-cli/src/commands`. - After changing `tools/qol-cli`, run `qol setup` before trusting the installed `qol` binary. ## Ownership Model - `qol` is the terminal CLI and owns the command parser. - `qol dev` is a CLI workflow/dashboard that starts `qol-tray --write-mode=dev` as a child process. - `qol dev` dashboard rows are CLI-owned status/action panes, not tray launcher commands. - `qol-tray` exported launcher commands live separately in `apps/qol-tray/src/commands/mod.rs`. ## Dev console design rules These are the full rule set. They are load-bearing: each one exists because the opposite shape shipped once and drifted. ### One frame, breadcrumb sign `draw()` renders a single bordered frame (the `qol dev` panel) and hands its inner `Rect` to the view. The view paints its content s