fix: squads init fails for new users in clean environment

[kokevidaurre]

Problem

squads init fails when run by a new user in a clean environment (no .agents, no config, no prior usage). This is the #1 friction point — every new user hits this on their first interaction.

Reproduction

docker build -f test/docker/Dockerfile.fresh-user -t squads-fresh-user .
docker run --rm squads-fresh-user bash -c "squads init"

Or run the automated test suite:

./test/docker/test-fresh-user.sh --auto

Fresh-user test results (2026-03-24)

Step	Result
squads --version	PASS
squads --help	PASS
squads init	FAIL
.agents dir created	FAIL
squads status	FAIL (depends on init)
squads list	FAIL (depends on init)
squads catalog list	FAIL (depends on init)
squads doctor	PASS
unknown command	PASS

Expected

squads init in a git repo should:

1. Create .agents/squads/ with a default squad
2. Create .agents/SYSTEM.md from built-in template
3. Create .agents/company.md with prompts
4. Create .agents/idp/catalog/ with a starter entry
5. Exit 0 with a success message

Acceptance Criteria

• squads init exits 0 in a clean Docker container
• .agents/ directory created with proper structure
• squads status works after init
• squads list shows the default squad
• All 9 steps in test/docker/test-fresh-user.sh --auto pass