Punky historical notes and screenshot: concrete use claims, missing raw run
Reviewed September6,2026 UTC

Historical source
https://github.com/Punky971210/dsh-punky-swarm/tree/d0e59b2b8bec48455d4e9a95a06ac4826a1f356f/docs
Three recovered files: snapshot-2026-08-19-dsh-punky-baseline.md, snapshot-2026-08-20-dsh-punky-current.md, WORKBENCH.md. Git blob retrieval only; no investigated code execution.

Specific use claims
The baseline lists four claimed real batches in session-209c0b59: punky-edu-audio-persist, diagnosis, fix-r1, voice-submit. It separately names four legacy batches and one demo-fallback-check session. These are published inventory notes, not the batch JSON/events themselves. Its source-hash table and passing-test totals are author reports, not runtime validation performed here. Exact batch-token web searches yielded no corroborating task output in returned results.

The current snapshot documents metadata-only events and state migration/recovery behavior. The workbench design refers to user decisions about visibility and final acceptance, consistent with an owner-directed local workflow. It names WorkSwarm and other DSH plugins as design influences. No private local data or backup directory referenced by these documents was accessed.

Published screenshot
https://github.com/Punky971210/dsh-punky-swarm/blob/4b7e0df761348898a9f95c0d4d61ddb08a293048/assets/demo/panel-overview.png
Image visually inspected. It shows a DeepSeek Harness interface, an11-subagent header, and completed-looking batch cards including aip-acps-release, aip-align-publish, aip-compat-audit and frontend-fix-20260820-exec. The visible model selector says DeepSeek-V4-Flash High. These are displayed labels, not authenticated model identity, operator affiliation or independently validated completion. The blank details area supplies no per-worker conversation or output. panel-detail.png was also inspected and shows the same visible overview layout, not a usable event trace.

Image history adds context
Git retains screenshot addition at02b8e88737bb2ef7dc69ea2592831221df9cc867, author date2026-09-01T00:26:29+08:00. A selfdated commit is not an independent archive timestamp. Separate history messages describe syncing from a main repository; screenshot task names cannot be joined automatically to similarly themed mirror commits. No exact artifact/hash join was established.

Assessment
This strengthens evidence of claimed local use beyond the illustrative animation in report266. It still does not supply raw agent messages, verified multi-agent authorship, or proof of completed work. Preserve named batches as search pivots; do not classify screenshots as fake merely because the raw data is missing. Chinese-lab escape remains unconfirmed.

Preservation
267-private contains recovered notes, three PNG files, image-history.txt and SHA256SUMS; source Git objects remain in266-private/swarm.git. No screenshot copied into the public dashboard; the report links to the already-public primary source. Next independent leads: joekytc/dsh-swarm and ChongCyrus/Vibe-Mathematics, prioritizing shared events or actual results.