Fleet CLI polish: help text, E2E tests, daemon health visibility

[Shooksie]

Context

Agent 365 (GitHub/Microsoft) GA is ~28 days away (May 2026). ao-fleet has 14K LoC across 7 crates with 49 CLI commands, but the CLI UX is rough:

• Command help text is terse (no descriptions beyond subcommand names)
• No E2E or integration tests (only 56 unit tests)
• No daemon health rollup (% projects healthy, reasons, stale warnings)
• No project sync verification (last sync time, sync errors)

Scope (Phase 1 — CLI Polish)

1. Help text: Add meaningful about descriptions to all clap subcommands and key flags
2. E2E tests: Add at least 3 end-to-end CLI tests covering the founder bootstrap flow (create team → register project → assign host → daemon status)
3. Daemon health rollup: ao-fleet daemon health showing per-project health status, last sync time, error count
4. Project sync status: ao-fleet project status <id> showing sync state, last activity, pending tasks

Success Criteria

• ao-fleet --help shows clear, useful descriptions for all 6 domains
• E2E tests pass in CI
• A founder can demo the full fleet workflow in under 5 minutes

Priority

P1 — Ship before Agent 365 GA (May 2026)