fix: daemon bloom-planner prompt gates capture on user request and names nonexistent skills

[tbrownio]

Follow-up from #74 (agent-invocable-capture).

daemon/src/sessions.ts:176-177 — the bloom-planner planning prompt says "when the user asks for a plan/spec, use this repo's existing skills (/create-feature, /create-epic, /create-issue)". Two defects:

1. It gates capture on the user asking, which contradicts the model-proactive capture policy shipped by feat: Make create-plan and create-epic agent-invocable #74 — the headless Linear-session path (the VM/tracker scenario that motivated feat: Make create-plan and create-epic agent-invocable #74) still will not proactively invoke capture.
2. It names /create-feature and /create-issue, which do not exist — the real skills are /create-plan and /create-epic. This naming bug predates feat: Make create-plan and create-epic agent-invocable #74.

Fix both together: reword the prompt so the agent starts capture itself when the discussion converges on capturable work with no existing item (publish still gated by the capture skill's explainer-alignment pause), naming the real skills; then run daemon pnpm typecheck && pnpm build && pnpm test.

The daemon is orchestra-only (excluded from both sync scripts), so this is deliberately a separate item from #74's synced-skill-system change.