Allow an account to reconnect after a previous shutdown reports an error, while preserving error reporting.
Add regression tests for failed and pending shutdown tasks.
docs/onebot-actions.md is referenced twice but does not exist in the repository, so both "动作参考" links in the README resolve to 404s. The OneBot action reference is published on the docs site, kept in sync from collectActionDocs() via the sync-docs-catalog workflow, so link there instead. Also add a deploy row pointing at the Docker/Windows guide, which the README had no entry for.
Co-authored-by: zhngzhu <215231231+zhngzhu@users.noreply.github.com>
* feat(core): carry hook process status in notifications
`offline` alone cannot tell an external supervisor whether the QQ session dropped (log back in) or the process is gone (restart the client). Resolve the hook process behind a UIN at notify time and expose `status`, `pid` and `error` as template variables; a failing lookup degrades to empty values so delivery is never blocked.
The default webhook/email templates gain a process-status line; existing channels keep their stored template untouched.
* fix(core): preserve notification lifecycle ordering and simplify state
---------
Co-authored-by: zhngzhu <215231231+zhngzhu@users.noreply.github.com>
Co-authored-by: 手瓜一十雪 <nanaeonn@outlook.com>
晚晴