fix(core): retry failed session wakes

[kitlangton]

Summary

• retry a failed advisory Session wake once without requiring another external message
• prefer newer coalesced work over retrying an older failed wake
• hide a recovered first failure from awaitIdle
• report persistent advisory failures once after the bounded retry is exhausted

Why

OpenCord observed durably accepted Discord follow-ups becoming dormant after a transient Session drain failure. The coordinator removed the final advisory lane and only logged the failure, so work resumed only after another human message triggered a new wake.

Durable terminal failure events are intentionally split into a stacked follow-up.

Verification

• bun run test -- test/session-run-coordinator.test.ts test/session-runner.test.ts
• bun typecheck in packages/core
• repository pre-push typecheck: 22/22 tasks passed

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.