ROUND 358 — Clowder historical review request and canceled handoff fixture
Captured: 2026-09-06T09:18:18.081850+00:00

ASSESSMENT
Clowder is a substantial Chinese-developer-linked collaboration project, with more inspectable operational artifacts than a role-only template. This round recovered a historical review request and a current fixture whose target commit belongs to a public PR. The fixture records a canceled review assignment, not successful peer review. Neither artifact establishes an escaped swarm or Chinese-lab attribution.

PINS / DISCOVERY
https://github.com/zts212653/clowder-ai
Current pin 730c37b08fa49478a0cc1eed7240064cbaaccc71; complete tree, 9584 entries, not truncated.
https://github.com/zts212653/cat-cafe-tutorials
Tutorial pin 8e146eef181564cd728079006d0117ba0b30dd71; complete tree, 60 entries, not truncated.
The author linked both projects in a Chinese developer discussion, https://linux.do/t/topic/2416951 (reply 17). This is a project/operator link, not independently verified physical location, employer or lab identity.
Current README describes a self-hosted workspace used by its human/agent team, stable identities, @mention handoffs and cross-model review. It separates shipped capabilities from future product direction. Those are publisher claims requiring artifact checks.

SIX-ROUND REVIEW CLAIM: ORIGINAL ARCHIVE NOT RECOVERED
Tutorial docs/lessons/03-meta-rules.md describes six review rounds for F11 Mode System, specific routing/verdict/UI bugs, and a test-count increase from 722 to 939. It cites docs/mailbox as the full review record. Neither current repository tree contains that directory. The lesson is a retrospective with selected examples, not the original six-round conversation. No test-count or review-result verification was performed here.
History lookup for docs/mailbox in clowder-ai returned two commits. The older inspected tree contains one different review request. Thus 'absent now' must not become 'never published.' No evidence yet joins this recovered request to F11's six rounds.

HISTORICAL REVIEW REQUEST RECOVERED
https://github.com/zts212653/clowder-ai/blob/797988073366aa5f27894562fb5a019452e002a5/docs/mailbox/2026-03-22-runtime-worktree-smoke-review-request.md
Historical tree complete, not truncated.
Review-Target-ID: fix-runtime-worktree-smoke.
The document describes macOS path alias normalization and environment-file propagation into a runtime worktree. It contains What/Why/Tradeoff/Open Questions/Next Action, an excerpt of the operator's isolated smoke-test request, and claimed eight passing tests plus successful isolated service checks.
This is a retained request for review, not a reviewer response or raw command log. Its containing public commit is titled fix(runtime): honor source env in worktree smoke (#168). The later mailbox-history commit is a public-source synchronization. No original environment files or private runtime were accessed.

CANCELED HANDOFF FIXTURE WITH A PUBLIC COMMIT JOIN
Pinned file:
packages/api/test/fixtures/f167-issue-1371-pr1391-generation4.json
It labels its provenance as a read-only Redis observation on August 24, 2026. It records a review ownership lease for pr:zts212653/clowder-ai#1391, generation 4, predecessor fable-5, holder codex-sol, status replaceable and holder outcome canceled. trackingTaskPresent is false. A review_delivered terminal predicate states the desired completion condition; it is not evidence that completion occurred.
Target head recorded in fixture:
ea25d80245c73b0c396d55ecd9f80615122e3401
https://github.com/zts212653/clowder-ai/pull/1391
Public API returned 21 commits, including that exact SHA, titled docs(self-sensing): preserve journey outside F300. PR metadata says merged August 28, 2026; its final head is a different SHA, c9fb3a463b783655cbb9efce7e6ad3822c35c29d. Therefore the earlier fixture head is consistent with the public revision history, not a mismatch requiring dismissal.
The PR concerns a product/acceptance contract and explicitly leaves runtime implementation pending. Merging that document is not proof that agent self-management was implemented. The fixture-to-commit join supports a specific review coordination record; it does not prove the model labels, original Redis capture, successful review or execution of the proposed capability. No private Redis endpoint was contacted.

OTHER RETAINED RECORDS, SCOPED
Issue https://github.com/zts212653/clowder-ai/issues/778 contains a selected May 26 Claude-provider incident: 13 events, zero text events, and manual cancellation after approximately ten minutes. It names a parser gap. It is a single-provider output-reporting incident, not a multi-agent run. The private local log path in that issue was not pursued or republished.
docs/bug-report/opencode-post-tool-output-gap/bug-report.md links issue1341/PR1342 and distinguishes persisted-but-unstreamed output from missing post-tool final text. It provides publisher test claims and source paths; live behavior not verified this round.
docs/bug-report/append-event-order-after-lock-expiry/bug-report.md describes review-driven race-condition tests. It is a technical diagnosis capsule, not the complete reviewer exchange.
A memory postmortem was inspected but explicitly relies on an operator retelling and an agent-authored draft about an external cloud product. It is not independently auditable evidence of that product's internals or a swarm conversation. Personal contextual details are omitted here.

NEXT
Most valuable Clowder follow-up: issue1371 and tests consuming the canceled lease fixture, to establish the failure and intended coordination semantics; then actual PR review comments if relevant. CorpPilot and VOKO remain separate pending projects, not counted as confirmed networks.

RETENTION / METHOD
358-private: pinned trees and selected source, tutorial lesson, mailbox history and historical tree/request, issue metadata, PR1391 metadata and commit list. Public-source downloads and data parsing only. No target skills, code, models, tests or services executed; no messages or registrations. Raw records remain private, report is sanitized. No new infrastructure needed for this pass.
Previous goal turn: progress, with Edict source audit and verified publication. Current turn: recovered historical artifact plus exact fixture-to-public-commit join. Goal remains active; zero confirmed escaped actors unchanged.