ROUND 355 — Astraloom mock completion and StuFlow local session boundary Captured: 2026-09-06T09:04:31.034173+00:00 ASSESSMENT Two additional Chinese-language coding/collaboration projects are source-level leads, not newly verified operating swarms. Neither inspected current tree supplied a retained real-model team conversation. Chinese prose and supported Chinese model providers do not establish a Chinese lab operator. ASTRALOOM Primary: https://github.com/huzjie/astraloom Pinned commit: 6d05a4febc61f2a11a0dc7b3b03820a32a620299 GitHub metadata: created 2026-08-29 07:01:01 UTC; pinned commit committer date 07:01:43 UTC. Complete recursive tree: 165 entries, not truncated. Publisher/GitHub dates are not independent archive authentication. README explicitly motivates the project by an August 29 report about OpenAI Astra. This is evidence of its stated inspiration, not verification of that news or evidence of a preexisting independent swarm. README advertises long-duration collaboration, persistent memory and checkpoint recovery, and explicitly states the default provider is offline mock. Inspected astraloom/orchestrator.py, providers/mock.py, collaboration/session.py and tests/test_orchestrator.py, without execution: - Default team names planner, executor, reviewer, researcher, critic. - run_goal iterates planned tasks sequentially. A topology name is recorded, but this path does not implement parallel dispatch simply by selecting that name. - _run_task catches a provider exception, sets task.status to failed, then unconditionally overwrites status to done and logs task_done. The error text remains in result. Consequently this task status cannot reliably establish success. - run_goal unconditionally marks the goal completed after its task/review sequence, unless an uncaught exception exits the path. - _review_goal sends reviewers the goal title, without passing task outputs in those calls. This does not substantiate the comment's claim of reviewing executor outputs. - CollaborationSession has post/broadcast/inbox methods, but the inspected orchestrator path only joins participants; it never calls post or broadcast. - resume returns saved checkpoint state; this method itself does not resume task execution. - Mock replies are canned Chinese judgments, including a nine-point quality rating, or a hash-derived summary. The end-to-end test explicitly selects mock and asserts completed status and a nonempty goal count. This test is not a real-model team transcript. We did not run it. These are scoped observations about the inspected paths, not a claim that every module is inert or that the project is fraudulent. Real-provider adapters are present in the tree. No captured multi-hour run was found in the inspected artifact inventory. STUFLOW Primary: https://github.com/znc15/StuFlow Pinned commit: 1f554b47da473f382f043ef017857ee3c5ebbe91 Metadata and complete tree retained privately in round 354; README and selected source in 355. Chinese README describes a local assistant prototype built around OMA. Architect/developer/reviewer are the advertised team; ordinary conversation can route to one assistant. Illustrative README output is not a run transcript. src/core/run-task.ts validates API-key configuration, routes chat separately, or calls orchestrator.runTeam. It appends user, agent-output, result and summary session events when context storage is enabled. src/context/session-store.ts implements local session persistence. These paths identify what an operator-exported artifact could look like; they do not supply such an export. README says sessions are local .stuflow data, and the inspected current tree does not contain public runtime captures. NEXT SEARCH DIRECTIONS Prefer operator bug reports with task IDs, captured inboxes and commit outputs over another framework's role count. The strongest recent comparison remains round 349's five DSH fixtures (5822 events, 172 tool calls), round 351's commit joins, and round 346's selected ccteam inbox. Those records still do not establish escaped Chinese-lab activity. New search lead: huashu-agent-swarm, surfaced through an English translation marketplace entry. Find original Chinese author/source and actual operator artifacts; a translated skill is not independent Chinese provenance. ACPs-community was already examined in round 265; do not count it as new. INFRASTRUCTURE Most useful feasible addition: an existing always-on mainland-broadband computer, dedicated browser profile, and SSH or remote desktop. Planning estimate: 2 CPU cores, 4 GB RAM, 40–70 GB free disk; no GPU required for page collection. This is an engineering estimate, not a vendor quote. A browser vantage could retry blocked Chinese forums and article hosts; success is not guaranteed. Hong Kong cloud hosting is not equivalent to mainland residential access. Public-page HTML/PDF exports with URL and UTC capture time are also useful. No infrastructure change was necessary for this round's GitHub reads; no purchase or new service was provisioned. METHOD AND RETENTION Read-only public HTTP; no target code, skill, test, model call or demo executed. No accounts joined and no messages posted. Private captures: investigation/china/355-private; raw files not published. Repository metadata/tree for StuFlow: 354-private. Public report is a sanitized analytical derivative. No change to zero confirmed escaped actors.