no_agent cron 投递在 Telegram 上仍包含 "Cronjob Response" 封装层

[jf112411]

版本

Hermes Agent v0.18.0

平台

Telegram

预期行为

根据 references/cron-raw-delivery.md，当 no_agent=true 时，
脚本的标准输出应原样投递 — 无 "Cronjob Response:" 标题或 "要停止或管理此任务..." 尾注。

实际行为

Telegram 投递仍包含完整的封装层：

Cronjob Response: 新币扫描
(job_id: 1de6b7774651)

[原始脚本输出]
要停止或管理此任务，请给我发送新消息...

Cron 配置

no_agent: true
脚本: cron_new.py
投递方式: origin

影响

Alpha 信号机器人 — 每次推送都会被系统噪音污染，用户本不应看到这些信息。

[GottZ]

This was generated by AI during triage.

Summary

Two PRs address #57647 by bypassing the generic cron response wrapper for no-agent jobs so their stdout is delivered verbatim. #57688 implements the behavior through a focused helper with delivery tests and documentation, while #57773 applies the same core condition inline without corresponding tests or docs.

Related pull requests

• fix(cron): deliver no_agent job output verbatim without the response wrapper #57688 best fix — (+80/-4) — fixes: Adds _should_wrap_cron_response() so no_agent output is always unwrapped while agent-driven jobs retain the global cron.wrap_response behavior; it also tests the actual Telegram-style delivery boundary and documents the exception. The contributor keep_open review identified an unreachable per-job override and missing docs, and the current diff explicitly addresses both by removing that branch and updating the relevant documentation.
• fix(cron): skip delivery wrapping for no_agent jobs (#57647) #57773 [closed] fixes — (+5/-3) — fixes, but closed as duplicate of fix(cron): deliver no_agent job output verbatim without the response wrapper #57688: Implements the same no-agent bypass inline in _deliver_result(), directly correcting the reported wrapper pollution. It remains relevant as corroborating implementation evidence, but contributor discussion closed it in favor of the earlier and more complete fix(cron): deliver no_agent job output verbatim without the response wrapper #57688.

Duplicates

#57688 and #57773 implement essentially the same no_agent wrapping bypass in cron/scheduler.py; #57773 is the narrower duplicate of #57688.

Suggested consolidation

Merge #57688 — it is the verified best fix, covers the reported delivery behavior with a focused helper, exercises the real delivery path, documents the contract, and has incorporated the keep_open review's requested scope and documentation changes. Keep #57773 closed as a duplicate of #57688.

Complex graph

flowchart LR
    classDef open fill:#dbeafe,stroke:#1d4ed8,color:#1e3a8a
    classDef merged fill:#dcfce7,stroke:#15803d,color:#14532d
    classDef closed fill:#e5e7eb,stroke:#6b7280,color:#1f2937
    classDef unverified fill:#f3f4f6,stroke:#9ca3af,color:#374151
    classDef best stroke-width:3px,stroke:#b45309
    classDef target stroke-width:3px,stroke:#4338ca
    I57647(["issue #57647 (open)"])
    subgraph Dup57688 ["PRs duplicating each other"]
        P57688["PR #57688 (open)"]
        P57773["PR #57773 (closed)"]
    end
    P57688 -->|best fix| I57647
    P57773 -->|fixes| I57647
    class I57647 open
    class I57647 target
    class P57688 open
    class P57773 closed
    class P57688 best
    click I57647 "https://github.com/NousResearch/hermes-agent/issues/57647"
    click P57688 "https://github.com/NousResearch/hermes-agent/pull/57688"
    click P57773 "https://github.com/NousResearch/hermes-agent/pull/57773"

Loading

Graph: solid arrow = fixes / best fix, dashed arrow = partial or unverified (see edge label); boxed group = PRs duplicating each other; amber border = best fix; indigo border = target; gray node = closed or no verify verdict yet (state tag in the node label).

Cross-PR triage: Reviewed 2 pull requests and 1 issue in this complex. Each diff was read against this issue; Assessment working set: 8 kB of PR diffs, 5 kB of issue/PR text, 4 kB of discussion (6 comments), 4 verify verdicts. verdicts reflect diff content, not PR titles. Part of an automated triage batch.