`/status` full re-authentication UX: document or offer lighter-weight status

[rosspeili]

Problem

docs/BOOT_AND_SECURITY.md: /status calls boot_up_sequence() again, including full re-authentication and camera. Surprising on laptops or remote sessions.

Goal

Either: (A) document prominently in /help and README that /status is a hard reboot path, and/or (B) add a “soft” status (env, Ollama, DB ping) without camera loop—product decision in issue discussion.

Acceptance criteria

• User-facing help text matches behavior.
• If “soft status” is added, old behavior remains available (e.g. /status full).