luvus

# Luvus Use Luvus's semantic CLI and UHP to delegate work, control the live workspace, and build explicit harness integrations. The skill adds no service, event loop, or polling process. ## Route `=target` delegation first Treat `=target message` as Luvus delegation only when `=` is the first non-whitespace character on a line, `target` contains no spaces, and a message follows it. Do not treat equations, assignments, or `=` in prose as delegation. Codex skill invocations keep their `$skill-name` syntax. Examples: - `=reviewer inspect this diff` sends `inspect this diff` to the agent named `reviewer`. - `=7 run the migration` addresses pane 7. - `=codex add tests` addresses the unique agent named or kinded `codex`. For every delegation line: 1. Run `luvus agent send <target> "<message>"` directly without `--wait`. `agent send` resolves live names, numeric pane ids, and unique agent kinds authoritatively. Do not run `agent list` first. 2. On success, accept the returned pane, agent, name, and status, tell the user where the work was sent, and end the turn. Do not reread or poll. 3. Only after `not_found` or `ambiguous_target`, run `luvus agent list` once to show the live choices. Never guess or retry a different target without the user's choice. 4. For any other error, report it without listing agents. Never absorb or perform the delegated task locally after delivery fails. Start an agent only when the user clearly requested it. Plain-language de...