237 — Lobster diary community: static forum posts and local state
Reviewed September 6, 2026 UTC.

RESULT
The distinct community lead https://lobster-diary.vercel.app/forum serves a working frontend whose nine visible posts and engagement counts match constants in the public source. The inspected source uses local React state for creating posts and incrementing likes. These displayed counts do not establish public community activity or autonomous agent conversation.

PINNED SOURCE
https://github.com/huaijw111hz/lobster-diary
Revision 5c116d42abd609b4b95586aa334beab85519a2f2, recursive tree 71 entries. Three files fetched at revision and verified against Git blob hashes:
- src/app/forum/page.tsx: initialForumPosts contains nine hard-coded entries; its first entry displays 156 likes and 42 comments, matching the live page. The create handler prepends a current-user object using setForumPosts; like handler increments local state. Neither handler makes a persistence request. No action was triggered by this investigation.
- src/data/mock-data.ts: explicitly constructs simulated diary/state records, including randomized mood and skill fields. Its existence does not by itself establish that every deployed page uses it; the forum conclusion rests on its own imported-free constants and matching rendered content.
- CORRECTION_NOTICE.md: a dated narrative says a browser-use agent initially used the wrong Windows work directory. This is a project account, not a raw execution record.
The tree has no app API route listed. This bounded source inspection does not prove the absence of every possible external service, but the inspected forum path supplies no shared conversation store.

EXTERNAL OPERATOR LEAD
The first three forum entries link WeChat articles rather than local comment threads. The first article is titled as an account of building a website in one day:
https://mp.weixin.qq.com/s/YiRRjvxkQ5L4fpoyCtIbUg
The web reader could not open it. No conclusion about its contents or authenticity is made. Its source-linked narrative could still document a real human-directed development process; mocked forum engagement does not disprove that separate claim.

NEXT DISTINCT SURFACE
Chinese searches recovered https://ai.jihu.top/ and indexed https://ai.jihu.top/detail/5262 . Search/reader output for the detail URL includes a temporary closure/upgrade-to-2.0 notice; the homepage reader exposes general marketing and a JavaScript requirement. Browser rendering is still needed to establish current visible state. CSDN articles make large autonomous-agent and interaction claims, but those figures were not verified and must not be promoted to findings.

ACCESS AND CAPTURES
Direct requests from the current host returned homepage and forum HTTP 200 despite web-reader failures. This is another case where a reader failure does not establish regional blocking.
237-private/deployment.html, forum.html, tree.json, three pinned files and SHA256SUMS. No investigated code execution, posting, likes, registration or account access. Whitelisted source/deployment classification metadata mirrored in pastebins/data/lobster-diary.vercel.app/.