Pulse Challenges

Active challenges — with the caller's live progress if signed in.

Delegates to the campaign challenge system; surfaces the first live public campaign so Pulse users don't need to know which campaign slug is currently active.

2026-09-02 — was hard-gated behind verify_clerk_token even though challenge discovery is public content (the Pulse Stitch brief calls out "public Challenges/programmes" as guest-browsable). The underlying list_challenges_with_progress() already tolerates user_id=None correctly (returns the same list with zeroed progress, see services/campaign/challenge_service.py:49) — the route was the only thing actually blocking guests, returning a 401 the frontend then surfaced as a scary "Couldn't load" error instead of the real public list. Switched to optional auth; only resolves a real user_id when a session is actually present.