The quick start shows `Running` after `ax apply`, but new tasks start `Suspended`

[eren23]

What happens: In the README quick start, ax get tasks shows PHASE Running right after ax apply. CreateTask (internal/server/server.go:141) always stores a new task with phase Suspended. The task does not start until ax resume task <name>. demo.sh does this and says so, but the README does not.

Suggested fix: Add ax resume task task123 to the quick start after ax apply, or document that new tasks start suspended.

Environment: google/ax d0bc38b and Agent Substrate 1d7ca8c, on a local kind cluster (Docker Desktop on Apple Silicon).

[cloudonly]

Fix ready on my fork: docs/quick-start-workerpool-and-examples (diff vs upstream) — PR creation is currently rejected by the repo's collaborators_only policy (as tracked in #358), so I'm leaving the branch here and will open the PR as soon as that allows.

For this issue, the quick start now runs ax resume task task123 right after ax apply (matching CreateTask storing new tasks as Suspended), keeps the sample ax get tasks output as post-resume Running, and notes that a slow first resume usually means workspace initialization rather than failure — the CLI's 15s timeout can fire before the workspace finishes cloning while the task keeps coming up in the background (ax get tasks shows where it is). Also synced the demo.sh header outline with the resume step the script already performs.