Support hosted Honcho (honcho.dev) as a first-class option

[UnbrandedTech]

Summary

Honcho setup currently defaults to Cloud Honcho but the actual sync scripts hardcode http://localhost:18790. The cloud Honcho option (honcho.dev) needs proper support including API key auth and different base URL.

What needs to change

• shared.py — HONCHO_BASE_URL defaults to localhost. For cloud Honcho, this should be https://api.honcho.dev (or whatever the cloud URL is)
• scripts/setup_honcho.sh — currently auto-defaults to cloud with no configuration. Should prompt for Honcho API key and save it
• get_honcho() in shared.py — may need to pass an API key header for cloud auth (the local version has no auth)
• honcho_slack_sync.py, honcho_obsidian_sync.py, load_to_honcho.py, update_dossiers.py, honcho_write.py, generate_initial_dossiers.py, analyze_priorities.py — all use get_honcho() so the change is centralized, but need to verify cloud API compatibility
• Test the full pipeline against honcho.dev to ensure batch operations, peer.chat(), conclusions, and sessions work identically to local
• Document the tradeoffs: local (free, private, needs Postgres+Ollama) vs cloud (paid, managed, no infra)

Setup flow

"Honcho memory system:"
"  1. Honcho Cloud (honcho.dev) — managed, no infrastructure"
"  2. Self-hosted (PostgreSQL + Ollama) — free, private"
"Which? (1/2): "

If cloud: prompt for API key, save to ~/.openclaw/workspace/.honcho_env, update HONCHO_BASE_URL in config.