feat: add bootcamp init to scaffold a config file

[Arthur742Ramos]

Summary

Adds a bootcamp init command that scaffolds a .bootcamprc.json configuration file in the current directory, so users can customize style, defaults, prompts, and excluded docs without hand-writing config from scratch.

Usage

bootcamp init                          # write .bootcamprc.json
bootcamp init --print                  # preview on stdout, write nothing
bootcamp init --force                  # overwrite an existing config
bootcamp init --style corporate --path bootcamp.config.json

Behavior

• Writes .bootcamprc.json (or --path) using the existing generateExampleConfig() template
• Refuses to overwrite an existing file unless --force
• --print writes to stdout instead of disk (handy for piping/inspection)
• --style presets a built-in pack and is validated against the known packs

Implementation note

The root command already defines -s, --style, so Commander routes a bare --style to the root rather than the subcommand. This is the same collision the diff command handles for --output, so init reuses the existing getCliFlagValue helper to read --style reliably.

Changes

• src/commands/init-command.ts — runInitCommand() + buildInitConfig()
• src/cli.ts — registers the init subcommand
• Docs: README (config section + commands table) + CHANGELOG

Testing

• test/init-command.test.ts — 9 unit tests (default write, overwrite guard, --force, --print, invalid style, style embedding, custom path, buildInitConfig) with mocked fs/promises
• test/e2e/init-command.e2e.test.ts — 4 real-CLI e2e tests in an isolated temp cwd (scaffold + overwrite guard + --force, --print, --style/--path, invalid style)
• Added an init subcommand assertion to the CLI wiring test
• Local validation: lint ✓, typecheck ✓, build ✓, full unit suite 1049 passing, coverage above thresholds (init-command.ts ~91%), all e2e ✓