fix: clarify cron delivery error status

[ctrlBizz]

Summary

• clarify cron list wording so delivery failures are not mistaken for execution failures
• add CLI regression coverage for a successful run with a delivery error

Verification

• ./venv/bin/python3 -m pytest tests/hermes_cli/test_cron.py tests/cron/test_jobs.py::TestMarkJobRun::test_delivery_error_cleared_on_success -q -o 'addopts='
• hermes cron list --all | grep -A12 'ad510105c212'
• hermes cron status

[mxnstrexgl]

🤖 Automated PR Review

Security Scan

• ✓ No hardcoded secrets, injection sinks, unsafe deserialization, or dependency red flags found by this automated scan.

Code Quality

• ✓ No blocking code-quality issues found by this automated scan.

Summary

Status: APPROVE — security findings: 0, quality suggestions: 0.

Automated review; raw diff content intentionally omitted.

[teknium1]

Thanks for the focused CLI regression coverage. The premise remains valid on current main: hermes_cli/cron.py:167-179 renders an ok execution status separately from last_delivery_error, so the old Delivery failed: wording can be read as an execution failure.

Problems

• website/docs/guides/cron-troubleshooting.md:75 says a delivery failure appears in last_error, but cron/jobs.py:1476-1488 records it in last_delivery_error independently of execution status. Please update that troubleshooting guidance alongside the CLI wording.

Suggested changes

• Document that hermes cron list can show a successful last run plus a separate last-delivery failure.

Automated hermes-sweeper review.