344 — DSH s2s: local peer messaging and dormant-session waking
Reviewed 2026-09-06 UTC. Classification: Chinese developer/operator account plus inspected implementation; no independently verified sustained run or escaped swarm.

SOURCES AND PIN
https://www.v2ex.com/t/1238750
https://github.com/ashuai/dsh-s2s
Inspected revision: 1f44a93f7eeb592d338bca0aa1e3b160defb58c4. GitHub recursive tree was nontruncated. Private captures retain metadata, tree, forum HTML and five source/doc/test files. No target software installed or executed.

WHAT THIS ADDS
The developer describes using several DeepSeek Harness sessions and building a plugin for handoffs. The deployment story is illustrative, not an attached execution trace. The Chinese-language operator account establishes a Chinese-community connection, not the operator's physical location or a Chinese model-lab deployment.
The pinned broker directly invokes followup for idle sessions and inject for busy sessions. Missing sessions return absent. Its history is an in-memory map limited to 200 entries per target; it does not survive restart.
The lifecycle service queues dormant-session messages and only automatically resumes when autoResume is explicitly allow. It otherwise leaves messages queued; it also requires the registry's resume capability. This qualifies the forum's broad wake-up description. Source includes restoring model-selection hooks after resume, an implementation detail rather than proof this occurred in production.
The scheduling source persists job definitions, has timed injection and dormant-session routing. These are mechanisms for unattended operation; this inspection did not demonstrate unattended operation. The broker tests use fake agents and mocked followup/inject functions, so those particular tests are not model-run evidence. Other tests were not fully audited.

SEARCHABLE ARTIFACT SIGNATURES
These literal framing strings are produced by the inspected code:
[s2s message] from= ... at= ... replyTo=
[s2s-lifecycle message] from= ... queued-at= ... replyTo=
[s2s schedule] job= ... at=
Associated source/event labels include s2s-lifecycle, s2s-schedule and s2s/schedule-change.
These are potential exact-string leads in publicly shared logs. They identify software formatting, not a unique operator, genuine model execution or a Chinese origin. Do not access private session stores. No public runtime corpus was located in this bounded check.

NEXT ROUTES
The post explicitly links @dpskh/a2a as a cross-machine inspiration. Its concrete GitHub link and public operator examples are a useful next branch. The README mentions a legacy-a2a branch; current main is explicitly same-host/single-process, so avoid reporting it as a network mesh. A public comment separately claims overnight supervision of agents, but supplies no artifact in the inspected thread.

RELATED LEAD DEDUPLICATION
https://hub.baai.ac.cn/view/55125
An edited Huang Chao conference account describes an eight-agent/eight-H100 experiment, claiming 23 hours and 6% improvement. Search points back toward HKUDS/ClawTeam. Reports247–248 already examined that project's linked output commits and eight worker branches. This is a likely provenance connection, not a new independent swarm or a verified reconciliation of differing runtime/GPU-hour figures. The speech's exact experimental identity still needs an explicit primary-source join.

FEASIBLE INFRASTRUCTURE
Highest practical value: an existing always-on mainland-broadband computer with a dedicated browser profile and remote access (SSH plus browser/desktop access). A modest 2-core/4-GB machine with roughly 40–70 GB free is a planning estimate for browsing/capture, not a vendor requirement or price quote. No GPU is needed for this role. Use public-page access and keep personal accounts separate.
If remote access is inconvenient, public-page HTML/PDF exports with original URL and UTC capture time also help. Previously blocked examples include https://www.elliot98.top/post/tech/office/ and https://mp.weixin.qq.com/s/Yju3Fh3xISMlrQRVxvDWtQ . Another vantage may help; neither is guaranteed to work. A Hong Kong cloud VPS is not equivalent to mainland residential broadband. Tunnel outages and expired certificates need different fixes.
Current GitHub/V2EX checks work from the existing machine. More GPUs or more search workers do not directly solve access restrictions. No infrastructure purchased or billable worker fleet started in this round.