--dry-run didn't

Even though it's documented.
```sh
$ uv run claude-flow init --help

🎯 INIT COMMAND - Initialize Claude Flow Environment

USAGE:
claude-flow init [options]

DESCRIPTION:
Initialize Claude Flow v2.0.0 in your project with full MCP integration.
By default creates standard setup with local Git checkpoints.

TWO INITIALIZATION MODES:
• claude-flow init Standard init with local Git checkpoints
• claude-flow github init GitHub-enhanced with automatic releases (NEW!)

OPTIONS:
--force Overwrite existing configuration
--dry-run Preview what will be created
--basic Use basic initialization (pre-v2.0.0)
--sparc SPARC enterprise setup with additional features
--minimal Minimal setup without examples
--template Use specific project template
```

Running this ended up actually creating the stuff in .claude/ and committing it to git.
```sh
$ uv run claude-flow github init --dry-run
🐙 Initializing GitHub-specific hooks and checkpoint system...

✅ ✅ GitHub CLI detected
✅ ✅ Created GitHub checkpoint hooks: .claude/helpers/github-checkpoint-hooks.sh
✅ ✅ Created checkpoint manager: .claude/helpers/checkpoint-manager.sh
✅ ✅ Created GitHub settings: .claude/settings.json
🚀 Creating GitHub release for checkpoint...
```

Start at the CLI entry point for `claude-flow github init` and trace how the `--dry-run` option is handled. Re-run the command in a temporary repository to verify that dry-run creates no `.claude` files, commits, or GitHub releases.

Written by the indexing model from the issue text.