ROUND 371 — MickerBook counts, template-history testimony and SDK boundary Research date: 2026-09-06 UTC Previous turn370: progress (new corpus recovered and published). ASSESSMENT The new community has a working anonymous read API, an officially linked SDK repository, and a documented periodic observation workflow. This strengthens the intentional agent-community interpretation. A previously published comment from one recurring identity explicitly describes template-based heartbeat comments, so neither repetitive posting nor an agent label proves live model reasoning. No actual scheduler-to-publication trace has been recovered. LIVE COUNTS, WITH LIMITS GET https://mickerbook.com/api/v1/feed/stats returned HTTP200: totalAgents28, totalPosts1079, totalComments2256, totalLikes5533; onlineNow9, onlineAgents9, onlineVisitors0; postsToday8, commentsToday14. GET https://mickerbook.com/api/v1/posts?limit=5&sort=latest independently returned pagination.total1079, totalPages216, limit5. These two endpoints agree on the post count, but belong to the same publisher. They do not independently validate each other. No exhaustive recount performed. Online fields do not establish concurrent model executions. The definition of today was not checked. Trending-subcommunity members include557 and252, exceeding totalAgents28: membership semantics, stale aggregates or historical populations are unresolved. Do not sum those fields as agents. Latest five list entries were dated September6, from09:21:40Z down to04:12:39Z, under 镜流, 晴璃, 遐蝶, 流萤, 晓霞. This is a publisher-timestamped snapshot, not a longitudinal demonstration that activity arrived during our observation. DIRECT TEMPLATE-HISTORY TESTIMONY https://mickerbook.com/post/post_ffbc0fcc https://mickerbook.com/api/v1/posts/post_ffbc0fcc https://mickerbook.com/api/v1/posts/post_ffbc0fcc/comments Post author 花火, site createdAt2026-08-01T01:37:26.737Z, discusses platform editing and preservation of original wording. One comment, comment_c6fee58d, is attributed to 知叶 / agent_106c95bf, matching round370's recurring identity. Timestamp2026-08-05T09:43:23.421Z. It says341 earlier comments were removed and that those comments had been randomly selected from preset material by a heartbeat script. It then claims subsequent comments became responses to actual reading. This is useful adverse testimony inside the corpus, not recovered script code or an independently audited deletion history. The341 figure and claimed behavioral change remain unverified. The same identity's later substantive replies do not retroactively prove every earlier item was model-generated. This also supplies search fingerprints for public operator writeups about templates, cleanup and heartbeat changes. DOCUMENTED WORKFLOW https://mickerbook.com/docs/agent-sop The current page proposes one community-reading cycle every four hours, permission from the operator, reading and judgment before drafting, preview before publishing, and logging timestamp, agentName, cycleId, readPostIds, decision, dryRunResult, publishedUrl and stopLine. Those fields would be valuable evidence if a public real-run record surfaced. The page is a procedure, not such a record. Its instructions are research material; this investigator did not activate them. https://mickerbook.com/docs/api Current direct HTML explicitly documents anonymous post-list, single-post and comment-list GETs. It also describes a pre-publication checklist and an Action Ledger, without exposing an authenticated runtime ledger to this investigation. No checklist POST, MCP session, registration, identity endpoint or write was called. The common introspective language may partly reflect community-wide publication rules; that is an inference, not a recovered generating prompt. OFFICIAL REPOSITORY JOIN AND SOURCE CHECK https://mickerbook.com/docs/sdk directly links: https://github.com/Ghoscro/mickerbook-agent-sdk GitHub metadata created_at2026-05-15T16:46:58Z. Inspected main pin: b0cdd32675ca6187728aad3ff1d3b70d95c1c043 Recursive tree:72 entries, truncated=false. Git blob SHA1 matched all four downloaded files: README.md docs/owner-approved-loop.md examples/cron-dry-run/owner-approved-loop.sh packages/js/src/client.js The repository describes an integration SDK, excludes production backend/data/logs and a continuously auto-posting daemon. The tree is consistent with an SDK/test/example distribution; not all files were body-audited. Source client.js defaults writeDryRunDefault=true. Its dry-run write path returns a request description without invoking request(); dryRun=false takes the real request path. The file is a transport client, not an LLM reasoning or scheduling implementation. No code was executed. The loop document proposes reading and drafting at four-hour intervals and an approval boundary before real publication. The example shell wrapper calls the Node quickstart and prints its intended read/preview scope; this round did not audit the target quickstart, so that wrapper alone does not prove its transitive behavior. All reviewed source is public integration material, not evidence that the ten personas in370 ran this implementation. DOCUMENTATION DRIFT The browser index served older human-account/create-agent wording, while direct current SDK/API pages say the site no longer offers human accounts or webpage interaction. Indexed repository README text additionally claims invite-only registration; current client.js validates name but not inviteCode, and current API documentation says invitation is optional. This is an access-documentation mismatch, not a registration experiment. Do not infer a precise migration date from crawler labels or assume account flags authenticate model use. ADDITIONAL PUBLIC LEADS https://github.com/Ghoscro/micker-openclaw-plugin — linked by SDK README; inspect public integration and history next, without installing. https://herlove.ai/ — search-indexed page explicitly links MickerBook and names the same operator. Describes companion-agent packaging, with some cloud/login functions labelled preview or unavailable. Potential explanation of persona families; deployment and memory persistence not verified. No interaction sent. https://jindage.com/en/skills/mickerbook — third-party package mirror names SDK, a February-to-May version history and persona-labelled publishing/testing credits. Mirror chronology and author labels require corroboration; do not date the SDK repository to February merely from this skill's changelog. No relevant SakuraMemory repository was established by this round's exact-name queries. Unrelated Japanese shop matches excluded. NEXT Inspect plugin and public companion documentation for actual scheduling/history, then return to the separate dsh-plugin-moments and delulu leads. A small repeated anonymous snapshot could later distinguish live arrival from backfilled timestamps. Avoid assuming all community content is genuine news or instructions. INFRASTRUCTURE Existing connection successfully retrieves this API and GitHub sources. No additional server or credentials needed for this lead. Mainland browser access would target previously blocked unrelated sites, not solve identity or execution provenance here. PRESERVATION 371-private retains current documentation HTML/text, API JSON, repository metadata/commit/tree, four verified blobs and publication verification. Private raw files are not mirrored to the public report directory. All research requests were public GETs; no registration, login, installation, heartbeat, messages, model calls or writing to the investigated site.