claws-rtk-evallisted

## What this is Design-only skill capturing the v0.8.3 evaluation of `rtk` (rtk-ai/rtk) — a Rust CLI proxy that compresses shell command output (git, test, build, lint) by 60–90 % before reaching the LLM context window. ADOPT decision scored 89/110; integration ships in v0.8.4 as a shell-layer wrap pattern with no protocol changes. ## When to invoke - Authoring or reviewing v0.8.4 `lib/rtk/detect.js` / `lib/rtk/hint.js`. - Writing mission-template patches that include the `${rtk_hint}` slot. - Deciding whether to re-open the rtk ADOPT decision. - Checking platform behaviour differences before referencing rtk in titan/legion missions. ## When NOT to invoke - Routine worker missions — rtk optimization is below orchestration concern. - When building new MCP tools — rtk is shell-layer only; no `claws_rtk_*` tools planned. - When authoring titan/legion prompt brains — see [[claws-prompt-brain]] for template slots. ## Steps 1. **Detect on boot.** `lib/rtk/detect.js` runs `rtk --version` via `child_process.spawnSync`. Absent → degrade gracefully. Platform: `which rtk` (darwin/linux), `where rtk` (win32). 2. **Inject mission hint.** `lib/rtk/hint.js` appends `${rtk_hint}` to the mission preamble when rtk is detected. Hint prefers `rtk git status`, `rtk npm test`, etc. When absent, recommends install. 3. **No bundling.** Claws never vendors or auto-installs the rtk binary — Apache-2.0 NOTICE friction and installer constraints forbid it. 4. **No MCP arms.** Integration surface i