Add qq-ai-bot as a Harbor satellite service

[happysnaker]

Summary

• add qq-ai-bot as a Harbor satellite service
• expose the admin/status HTTP port and the OneBot reverse WebSocket port
• document the intended Harbor deployment shape for a QQ ↔ AI bridge

Why

qq-ai-bot is a self-hosted QQ ↔ AI bridge for OneBot 11 adapters such as NapCat and LLOneBot.

It fits Harbor's satellite/tooling layer well because it is not just a toy message forwarder:

• persistent session management
• ACP-compatible agent bridge
• progress streaming back to QQ
• command handling and group policies
• /healthz, /readyz, and Prometheus-style /metrics
• a simple Docker deployment path via ghcr.io/happysnaker/qq-ai-bot

This also adds a QQ-facing integration option alongside adjacent Harbor services like AstrBot, OpenClaw, Hermes, and nanobot.

What is included

• services/compose.qq-ai-bot.yml
• services/qq-ai-bot/override.env
• services/qq-ai-bot/group-rules.json
• profile keys in profiles/default.env
• service metadata entry
• wiki doc: 2.3.93-Satellite-qq-ai-bot

Notes

• this intentionally does not bundle NapCat / LLOneBot inside Harbor; the service stays focused on the AI bridge layer and exposes the reverse WebSocket endpoint for an external QQ adapter to connect
• the default override env keeps the upstream mock ACP agent so the service can boot cleanly before a user swaps in their real ACP runtime
• harbor open qq-ai-bot is pointed at /readyz, since this project's strongest built-in surface is its operational status endpoint rather than a dedicated web UI

If you'd prefer, I can follow up with a cross-service example doc showing a concrete NapCat wiring recipe from outside Harbor.