@pm keeps double-posting (e.g. homelab #187: self-posted report + framework transcript reply) — the prompt-level rule from #104 is ignored by the model. Enforce it in the harness instead:\n\n- fetch-thread.sh records the thread\u2019s newest comment id before the agent runs (/tmp/thread_max_cid).\n- publish.sh (pm/ops reply path): if any comment by the agent exists with a newer id, the self-post IS the reply \u2014 skip the duplicate framework comment. Ids are monotonic, no date parsing; comments fetched with the same pagination pattern as fetch-thread.\n\nMarker processing (CLOSE_ISSUE / DELEGATE / MERGE_PR / subtasks) is unaffected. Verified separately: the \ud83e\udd16 gate DID hold on #187 \u2014 no second run fired; this is purely the double-post.
@pm keeps double-posting (e.g. homelab #187: self-posted report + framework transcript reply) — the prompt-level rule from #104 is ignored by the model. Enforce it in the harness instead:\n\n- `fetch-thread.sh` records the thread\u2019s newest comment id before the agent runs (`/tmp/thread_max_cid`).\n- `publish.sh` (pm/ops reply path): if any comment by the agent exists with a newer id, the self-post IS the reply \u2014 skip the duplicate framework comment. Ids are monotonic, no date parsing; comments fetched with the same pagination pattern as fetch-thread.\n\nMarker processing (CLOSE_ISSUE / DELEGATE / MERGE_PR / subtasks) is unaffected. Verified separately: the \ud83e\udd16 gate DID hold on #187 \u2014 no second run fired; this is purely the double-post.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@pm keeps double-posting (e.g. homelab #187: self-posted report + framework transcript reply) — the prompt-level rule from #104 is ignored by the model. Enforce it in the harness instead:\n\n-
fetch-thread.shrecords the thread\u2019s newest comment id before the agent runs (/tmp/thread_max_cid).\n-publish.sh(pm/ops reply path): if any comment by the agent exists with a newer id, the self-post IS the reply \u2014 skip the duplicate framework comment. Ids are monotonic, no date parsing; comments fetched with the same pagination pattern as fetch-thread.\n\nMarker processing (CLOSE_ISSUE / DELEGATE / MERGE_PR / subtasks) is unaffected. Verified separately: the \ud83e\udd16 gate DID hold on #187 \u2014 no second run fired; this is purely the double-post.