Preserve bot telemetry and improve activity logging

[adrunkhuman]

Preserve playerbot decision evidence and make current activity easier to follow without dumping Compose lifecycle chatter into routine test output.

• Remove JSONL repeat suppression and the hunt-candidate telemetry cap. Add server-run/controller correlation, event sequencing, startup-failure reasons, and operational summaries with resources and recovery context. Existing schema-1 event names remain compatible.
• Send concise orange console messages to every online player as [Bot One][8] Message. Any character can DM a managed bot logs off or logs on; the per-bot setting survives relogs, resets on server restart, and never affects JSONL.
• Quiet successful Compose commands unless -Verbose is enabled. Preserve command output, streamed generations, final diagnostic events, and restart/exit/OOM evidence in failure artifacts.
• Make hunt assertions distinguish scored candidates from actual route validations, so complete candidate output does not invalidate search-budget checks.

Full candidate output materially increases log volume. Increase Docker retention from three to ten 10 MiB files (about 100 MiB total); longer investigations must still capture the stream separately. Applying the logging limit requires recreating the server container. Announcement controls are intentionally unrestricted development functionality.

The live surround/blocked-route failure tracked in #28 is not fixed here; navigation changes will follow separately.