fix(channels): verify real WeChat task endpoint

[acedatacloud-dev]

Root causes

• get_task_status called /api/messages/tasks/{id}, but Wisdom exposes /api/tasks/{id}. The missing route returned 404 before auth, so doctor falsely accepted wrong tokens.
• Local Windows install was a stale editable 0.1.0 pointing at a deleted worktree; pip said satisfied while the module was absent.
• Module version was hard-coded 0.1.0 even in CalVer wheels.

Fix

• Use /api/tasks/{id} throughout client/docs/tests.
• Runtime version comes from wheel metadata.
• Add Windows stale-editable recovery + PowerShell/CMD token syntax.

Validation

• ruff clean; 29 focused tests pass; wheel builds.
• Real gateway: correct token doctor exit0; wrong token 401/exit1.
• Real channels start: WebSocket connected; token redacted.

Adversarial review

VERDICT CLEAN. Endpoint/auth/version/install/secret handling reviewed.