AgentTeams follow-up: recovery gap, sync diagnosis and patch status
Reviewed September 6, 2026 UTC. Public read-only issue/PR evidence.

SUBMISSION WITHOUT NOTIFICATION
https://github.com/agentscope-ai/AgentTeams/issues/1177
An August13 proposal reports a reproduction pinned to aa650ccacc2ba6171d1b0b5efd2a49b1472abe5d: submit_task persists a submitted result and returns notificationNeeded, but a separate message must wake the leader. The author says the reproduction ran three times through the real MCP entry point while replacing the external mc process with a successful test double. It explicitly was not a full Kubernetes/Matrix deployment test. Preserve this distinction: project-1/example.test and the printed JSON are controlled reproduction evidence, not identifiers from a recovered live swarm.
Five comments were retrieved. Discussion agrees on the persistence/notification gap; the author and reviewer explicitly say draft PR1183 implements state-contract groundwork, not the scanner, leader wakeup or retryable delivery needed to close the problem. The final evaluation identifies itself as automated. No full recovery fix or independently repeated reproduction is claimed here.

UNRESPONSIVE WORKER REPORT
https://github.com/agentscope-ai/AgentTeams/issues/949
June20 report describes long quiet intervals, repeated HEARTBEAT.md synchronization, and a972-second later run. It links a work.log attachment, which was not downloaded in this pass. The issue body discusses credential-file synchronization; no credential content was requested or inspected.
Its causal claim that the sync loop shares the agent event-loop process is challenged by an explicitly bot-authored response: the shell sync loop runs separately. The original numerical claim is also inconsistent:24,000/54,630 is about43.9%, not88%. Accordingly neither the alleged root cause nor its percentage is accepted as established. These are debugging leads, not proof that file synchronization caused all observed inactivity.

LINKED PATCH CHECK
https://github.com/agentscope-ai/AgentTeams/pull/971
Direct GitHub metadata: state closed, merged_at null, merge_commit_sha null. Therefore this PR is NOT a verified merged fix.
Its inspected diff changes worker-entrypoint.sh to exclude runtime files from change detection and stop pushing HEARTBEAT.md from workers. The added test uses shell syntax and source-string checks; it does not demonstrate a live synchronization loop is cured. The diff also contains an integration-test edit outside that focused change. No tests or target code executed. Similar code may have landed elsewhere, but that was not checked.

RUNTIME VERSION / MENTION LOOP REPORT
https://github.com/agentscope-ai/AgentTeams/issues/803
May12 user report describes thinking text and automatic mentions causing worker reply loops. A reviewer corrects the claim that all linked upstream fixes were already merged/closed. The user later reports partial improvement while leader output/thread handling remains problematic. A later comment identifies PR1077 and fb3a40be1f005bd584f45544fc73bd4601d5c52a as an upgrade and asks for retesting. That comment is a lead; PR1077 itself and the screenshots were not inspected here, so no blanket fix claim is made.

ASSESSMENT
Public failure reports continue to provide stronger operator-specific leads than diagrams, but reported deployments, controlled reproductions, automated triage and merged fixes must remain distinct. Nothing here establishes an escaped Chinese swarm or links these users to XZ. The next useful artifact is a redacted task/message trace with a source revision and demonstrable result, rather than another proposed recovery design.

PRESERVATION
319-private: issue1177/949/803 JSON, their comments, PR971 metadata and files, SHA256SUMS, publication-check.json. Raw captures private. No log attachment, credentials, installation, model call, target execution, room access or operator contact.