`rtk` (github.com/rtk-ai/rtk) has an explicit OpenCode integration (`rtk init -g --opencode`) but is absent from the `ARITY` dictionary in `permission/arity.ts`. As a result, "Always allow" prompts for `rtk` commands produce `rtk *` instead of subcommand-scoped patterns like `rtk env *` or `rtk git clone *`, which is too broad to safely approve.
Add `rtk` and its subcommand prefix depths to the built-in dictionary, consistent with how other multi-level CLI tools (`aws`, `docker`, `kubectl`, etc.) are already represented.
`rtk` (github.com/rtk-ai/rtk) has an explicit OpenCode integration (`rtk init -g --opencode`) but is absent from the `ARITY` dictionary in `permission/arity.ts`. As a result, "Always allow" prompts for `rtk` commands produce `rtk *` instead of subcommand-scoped patterns like `rtk env *` or `rtk git clone *`, which is too broad to safely approve.
Add `rtk` and its subcommand prefix depths to the built-in dictionary, consistent with how other multi-level CLI tools (`aws`, `docker`, `kubectl`, etc.) are already represented.