`rtk init --hook-only` does not work

Description

It is possible to have project level hooks configured in claude code. These are written to .claude/hooks and are referenced in .claude/settings.json. It is desirable to limit special tools to specific projects to evaluate them. When installing the rtk system for a project the only modification is the creation of a large CLAUDE.md file, instructing the agent in the use of rtk, and no hooks are configured. Given that the hooks do not require explicit instruction I was expecting them to be configured instead.

Steps to Reproduce

➜ rtk init --hook-only
[warn] Warning: --hook-only only makes sense with --global
    For local projects, use default mode or --claude-md

Expected Results

The .claude/settings.json file should be created or updated with the following content:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "$CLAUDE_PROJECT_DIR/rtk/hooks/claude/rtk-rewrite.sh"
          }
        ]
      }
    ]
  }
}

(I had to expand $CLAUDE_PROJECT_DIR to the absolute path)

The .claude/hooks folder should contain at least rtk-rewrite.sh

Start at the rtk init --hook-only CLI entry point and reproduce the warning shown in the issue. Compare the expected .claude/settings.json hooks configuration with the .claude/hooks/rtk-rewrite.sh files created by local initialization. Done means local hook-only initialization creates or updates both the settings entry and the hook script without requiring --global.