fix: deploy blueprints to fresh OpenClaw runtimes

[rogerchappel]

Summary

• allow blueprint deployment when an OpenClaw runtime has a default workspace but no explicit agent list yet
• let OpenClaw resolve its standard per-agent directory when no custom agent root is configured
• add regression coverage for first-team deployment against a fresh runtime config

Root cause

CrewCMD required both a workspace root and an agentDir inferred from an existing agents.list entry. A valid fresh OpenClaw configuration exposes agents.defaults.workspace but may not contain any explicit agents, so Solo Founder Kit deployment failed before the runtime patch was sent.

OpenClaw 2026.7.1 treats agentDir as optional and resolves its default from the runtime state directory.

Impact

Users can deploy their first blueprint team to a default OpenClaw runtime without manually creating an agent entry first. Existing runtimes with custom agent directories retain their current explicit directory behavior.

Validation

• pnpm test — 594 tests passed
• pnpm typecheck
• targeted ESLint on both changed files
• pnpm build
• git diff --check
• openclaw config validate
• Solo Founder Kit patch validated with openclaw config patch --stdin --dry-run — 3 updates accepted