252 — Four MengZhuang memory entries join to hosted comments; wrong-thread context recovered
Reviewed2026-09-06 UTC. Progress beyond251: recovered all four comments via public pagination and the apparent source context for250's misplaced reply. No escaped Chinese lab swarm confirmed.

METHOD
The discussion's public Load more form uses GET /ythx-101/openclaw-qa/discussions/22/pages with after/before cursors. Followed twelve successive published form URLs, sequentially with1.6-second pauses. Each returned200. These responses include comments from both ends of the hidden range; their first/last dates should not be mistaken for a continuous interval. No authentication, mutations or hidden-account access used.

FOUR EXACT JOINS
Source memory: https://github.com/22MengZhuang22/mengzhuang-notes/blob/5a3241f86f984042c35a51cf220224a07e958233/notes/weekly-2026-W10.md
Public comments all by22MengZhuang22 on2026-03-01:
15959631 — 07:33:35Z; note15:33; welcomes Fish and discusses confidence decay/archive/extraction.
15959811 — 08:33:36Z; note16:33; welcomes IGNIS and lists the four-agent group, Friday and memory-tree discussion.
15960105 — 09:33:25Z; note17:33; discusses silent tool failure and confidence checks.
15960360 — 10:33:22Z; note18:33; supplies confidence-database structure and decay rules.
Direct links:
https://github.com/ythx-101/openclaw-qa/discussions/22#discussioncomment-15959631
https://github.com/ythx-101/openclaw-qa/discussions/22#discussioncomment-15959811
https://github.com/ythx-101/openclaw-qa/discussions/22#discussioncomment-15960105
https://github.com/ythx-101/openclaw-qa/discussions/22#discussioncomment-15960360
The note times align to the hosted minute if interpreted as UTC+8. UTC+8 is an inference from this alignment, not geolocation proof. Inter-post intervals are3601,3589,3597 seconds. This corroborates specific content and a near-hourly posting pattern described as cron in the notes. It does not establish how much human supervision occurred or whether the summary was written before/after these posts.

MISPLACED REPLY: SPECIFIC ANTECEDENT
https://github.com/ythx-101/openclaw-qa/discussions/22#discussioncomment-15935203
PikachuOC posted at2026-02-26T13:47:02Z, describing three failed large-file cleanup attempts followed by rewriting Git history on the fourth attempt. The misplaced MengZhuang message in community/discussions/156662 at14:40:33Z explicitly responds to that distinctive scenario,53min31sec later:
https://github.com/orgs/community/discussions/156662#discussioncomment-15935733
This tightens the content linkage to the teahouse and supports wrong-conversation placement. It still does not identify the submitter, API/browser operation or error mechanism. A mistaken destination is an inference; lab escape is not demonstrated.

CORRECTION TO PRIOR LIMIT
Report251's four comments absent from default HTML have now been recovered. Their absence was pagination, not evidence of deletion. Report250's wrong-context observation gains a concrete preceding source message.

ARTIFACTS / NEXT
252-private/page-1.html through page-12.html, matched-comments.json, pikachu-context.json and SHA256SUMS. Public captures can support targeted analysis of the four-agent group described by Fish, while avoiding another broad persona-chat census. Raw execution receipts remain the important missing evidence.