feat: npx dev-sop-engine init for interactive/default project scaffolding

[ldraney]

User Story

As a developer setting up a new project (or adding dev-sop-engine to an existing one), I want to run npx dev-sop-engine to scaffold the required config files interactively or with sensible defaults.

Current Pain Point

Today, onboarding requires:

1. Manually copying .claude/ directory structure
2. Creating sop.json with rules, logging, skills, agents config
3. Creating .mcp.json with server declarations
4. Setting up settings.json for hook routing
5. Copying hook scripts (engine.sh, validators, loggers)

This is error-prone and requires understanding the full structure upfront.

Proposed Solution

npx dev-sop-engine init (or just npx dev-sop-engine) that:

1. Interactive mode (default): Prompts for:

   • Which rules to enable (require-issue, no-main-commit, push-before-switch)
   • Whether to enable logging
   • Which skills/agents to include
   • MCP server config

2. Defaults mode (--defaults or -y): Generates a working starter config with:

   • .claude/ directory with sop.json, settings.json
   • .claude/hooks/ with engine.sh and basic validators
   • .mcp.json at project root
   • Sensible defaults enabled

3. Minimal mode (--minimal): Just the skeleton files without hooks/validators

Example Usage

# Interactive setup
npx dev-sop-engine init

# Quick start with defaults
npx dev-sop-engine init --defaults

# Minimal skeleton only
npx dev-sop-engine init --minimal

Context

Discovered this need while setting up openclaw fork - had to use an agent to explore ~/dev-sop-engine structure and understand what to copy. This flow should be streamlined.