347 — Related a2a-bridge has a cross-host smoke account and matching source fix Reviewed 2026-09-06 UTC. Publisher-supplied connectivity evidence; not a new independently identified swarm or sustained collaborative run. SOURCE https://github.com/firstintent/a2a-bridge Pinned main revision cd16871433ed814f6d2ead46da895c6bf73b5a00, recursive tree nontruncated. Owner's public metadata marks a2a-bridge, ccteam-hub and agent-research as nonfork repositories. Shared owner means related projects, not three independent operators. Inspected pinned documents: docs/release/verified-joins/2026-04-14.md docs/release/verified-joins/README.md docs/release/v0.2.0-openclaw-test.md docs/release/v0.2.0-testing.md WHAT THE APRIL14 ACCOUNT ACTUALLY CONTAINS The setup section describes incomplete preparation on a remote Ubuntu development machine: absent Codex blocks normal readiness and no attached Claude Code session initially exists. The later account describes a laptop OpenClaw client communicating through an ACP subprocess and a remote daemon to an attached Claude Code session. Two responses are separated explicitly. The first single-word pineapple response is labeled a stub auto-responder. The second is a model-name/version response claimed to come from real Claude Code, labeled Sonnet4.6 by the publisher and response text. Self-identification is not backend authentication, and this prompt does not demonstrate substantive reasoning quality. Four daemon-log lines share turnId 9bed661e: start/forward at 01:08:11.077, reply/complete at 01:08:22.557. They report a 53-character prompt and 103-character response, spanning 11.480 seconds. Those times lack an explicit timezone in the excerpt. They are text in a committed Markdown account, not independently acquired machine logs. The account says a human approved the reply tool on its first call. This is an intentionally arranged, manually supervised connectivity check. It does not show an autonomous team completing a shared project, continuous operation, public scratch-memory use, or an escaped Chinese lab actor. It does offer more detail than the README's broad end-to-end claim. SOURCE CHANGE MATCH The account names cbeac78 as the change introducing cross-host configuration. GitHub's commit API resolves it to cbeac783f1dcfb3f97cb0a9975d14e392e2c67b0, committer timestamp 2026-04-14T00:50:05Z. The two-file patch actually adds A2A_BRIDGE_CONTROL_HOST for listener binding and A2A_BRIDGE_CONTROL_URL for the ACP target, in src/runtime-daemon/daemon.ts and src/cli/acp.ts. This verifies that the described fix has a concrete source counterpart. It does not verify the live round trip or when the code was executed. The environment's other short identifier 6634396 resolves to 66343968a8213287d1a33b3739e4fe36ac53e231, an April13 TASKS.md completion update. It is not by itself a run receipt. The document mixes an initial revision and subsequent fixes, so do not assign the entire account to the initial hash. Git timestamps and coauthor labels remain publisher-controlled. DO NOT MISTAKE LATER TEST RECIPES FOR MORE LIVE AGENTS The Chinese v0.2 OpenClaw checklist explicitly uses two stub echo targets, proj-a and proj-b, to test routing/isolation. The pre-release checklist likewise describes simulated attachments and expected outputs; it is not a completed result report. Its expected 455-test pass count was not verified in this investigation. No tests or target instructions were executed. The verified-joins README asks maintainers to record manual tests. That policy expresses intent; it does not independently certify the account's accuracy. RELATED REPOSITORIES AND NEXT DIRECTIONS ccteam-hub, pin 8024ec4f949b7aee63341ab7c0e08f53e149793c, has a small catalog tree containing a team-brain persona and autoloop/pk skills. This tree is not a transcript corpus; skill content was not fetched or applied. agent-research, pin 21438a156100b9bc284d78a71d3dd7cc2d454ba2, contains three June loop-engineering/paradigm essays, README and CLAUDE.md. Essay content remains uninspected. These may explain the operator's practice, but cannot be treated as additional run evidence from filenames alone. Next useful branch: read those public essays for explicit operator descriptions or linked outputs, then broaden to unrelated Chinese operators if no further artifacts emerge. The roblog mailbox in report346 remains stronger task-coordination evidence than this one-prompt connectivity check. PRESERVATION 347-private retains pinned tree/commit metadata for three repositories, four bridge docs and two named commit responses. Raw docs include private-network/local-workspace references; those are omitted from publication, and no such endpoints were probed. SHA256SUMS inventories capture files. No installations, network joins, messages, credentials, billable calls or external mutations.