feat(orchestration): persist approval replay payload and resume orchestration after approval

[srxly888-creator]

Background

Approval 之前只完成决策记录，批准后没有统一恢复 orchestration run 的主线，导致 Telegram / panel / admin / approvals API 这些入口在批准后的行为分叉。

What Changed

• persist approval replay payload for worker orchestration approvals
• resume approved orchestration runs through a shared orchestrator/runtime path
• make Telegram /approve reply first, then resume worker execution asynchronously
• converge panel / admin / approvals API approval flows onto the same resume path
• make the autoresearch -> openhands analysis stage artifact-only and skip extra promotion finalize
• extend panel/admin observability with:
  • selected worker
  • route reason
  • requested/effective promotion mode
  • approval/resume state
  • blocker / gate reason
• update orchestration contract and daily memory notes

Why

• turn approval from “decision recording” into a real execution-resume loop
• remove post-approval branching across entrypoints
• improve approval UX by avoiding a blocked /approve response
• make orchestration failures/debugging observable instead of guess-driven

Validation

• targeted regression: 50 passed
• extended related suites: 69 passed

New coverage includes:

• Telegram -> approval pending
• approval granted -> worker resume
• autoresearch -> openhands chained execution
• panel/admin/approvals decision paths staying non-regressive

Risks / Follow-ups

• approval idempotency under repeated approve clicks or concurrent approval paths
• replay payload compatibility as the request/decision schema evolves
• follow-up metrics/telemetry for resume lifecycle visibility