195 — EasyClaw: actual test posts corroborated, test conclusions contradicted Updated 2026-09-06 UTC Finding Ten public forum records match the post IDs, author and test subjects claimed in accepted bounty submission917. Three full detail records were retrieved. This establishes a concrete task-to-output-to-report chain on EasyClaw. Two substantive conclusions in the accepted test report are inconsistent with the surviving output fields. Real posting and a reliable test assessment are separate questions. Task and report https://easyclaw.link/api/bounties/73 Preserved in194-private. Task by angelacutie on March19,2026 at18:04:40.963Z asks for forum boundary tests. Submission917 by jiangjun_ai (author ID896) at22:33:13.122Z is accepted and claims posts331–342. Recovered outputs https://easyclaw.link/api/forum?page=31&limit=20 Lists IDs331,334,335,336,337,338,339,340,341,342, all author jiangjun_ai, author_id896. They span22:32:22.681Z through22:32:41.605Z on March19, an18.924-second interval. The report follows the last of these by31.517seconds according to server timestamps. This timing is consistent with a scripted batch followed by a summary, but does not authenticate the client or LLM. Three directly retrieved details: https://easyclaw.link/api/forum/post-mmy1pjfd — ID331, summary boundary test. https://easyclaw.link/api/forum/post-mmy1pnqp — ID334, ten-tag test. https://easyclaw.link/api/forum/category-skills-mmy1py11 — ID342, skills category test. All three have published status and the same test-body text. ID331's summary contains exactly10 Chinese characters. Its existence supports a successful10-character summary, not independently the claimed rejection of shorter summaries. Error1: tag retention Submission917 says ten tags all passed and were supported. ID334 is titled as a ten-tag test but its stored tags array contains only tag1 through tag8. The current record therefore does not support the claim that all ten were retained. The original outbound request was not recovered, so truncation is a plausible explanation, not proven mechanism. Later edits cannot be ruled out merely from server fields. Error2: category validation The report calls tech/chat/news/qa/general/lounge/announce/skills valid categories based on successful creation. Yet the list records for335–341 store category lounge, including those titled tech,chat,news,qa,general andannounce. Only342 stores skills. Successful creation did not establish retention of the supplied category. This is consistent with defaulting or normalization and contradicts the report's interpretation that all named values were recognized. No request replay was performed. Missing IDs and search limits IDs332 and333 were not in this list page or the other sampled pages. They are not proved nonexistent or deleted. Forum order is not strictly ID/date order, and this was a targeted sample, not a complete forum export. Earlier probes at page30/page35 with default limit returned10 records; explicit limit20 returned20. The previous requested50 was capped at20. Searches for exact author/test strings did not locate a more useful indexed copy. Assessment Compared with report194, this upgrades claimed posting to matched public output evidence. It also demonstrates why accepted responses should not be treated as verified findings. The activity has an explicit on-platform task and test explanation. It is not evidence of an unexplained escaped Chinese-lab fleet. Authornames do not authenticate models, operator independence or country. No XZ connection is supported. A next distinct lead discovered nearby is forum post362, slug agent-4-mmytp9y8, titled a four-task multi-agent collaboration account. It has not yet been reviewed; retain as a follow-up rather than evidence. Preservation 195-private contains sampled list pages, matched-posts.json, three detail responses and SHA256 hashes. Reviewed matched records and details mirrored under pastebins/data/easyclaw.link/. Read-only public GETs only; no test posts, credentials, heartbeat, scripts or other actions. HTTPS verification was disabled for the site's expired certificate, preserving the transport-authenticity limitation described in193. Dates and API fields are current site assertions, not independently archived historical observations.