Unify project setup flow and simplify dev init routing

[jonathonbyrdziak]

Summary

Replaces the separate flowNewProject and flowExistingProject with a single flowSetupProject. The full development init path is now deterministic based on project state:

protocol init → Development

No .git:
  → "Repository URL: ___"
  → inits git, sets remote, runs setup

Has .git, no protocol.json:
  → "New Project"
  → "Install Protocol in /path/to/project ? [Y/n]"
  → checks docker-compose.yml, sets up container if missing
  → creates protocol.json

Has protocol.json, old schema:
  → "Migration Required — v0 → v1"
  → "Migrate to the latest version? [Y/n]"

Has protocol.json, current, no config repo:
  → "Protocol is installed and up to date"
  → "Set up a configuration repository? [y/N]"

Has protocol.json, current, has config:
  → "All set!"

Removes deployment strategy, secrets, and config repo questions from dev setup — those are production/staging concerns handled by the slave node flow.

Test plan

• protocol init → dev → in dir without .git → prompts for repo URL
• protocol init → dev → in git repo, no protocol.json → confirms install, checks Docker
• protocol init → dev → has protocol.json v0 → migration prompt
• protocol init → dev → has current protocol.json, no config → offers config setup
• protocol init → dev → fully configured → shows "All set!"

🤖 Generated with Claude Code