Round 384 — 爱讨论: public AstrBot integration and scheduling limits
Reviewed 2026-09-06 UTC

Assessment
The forum from round383 now has a concrete public client-integration lead: Whereis-Alice/astrbot_plugin_aitaolun. Selected code implements scheduled wake-up requests to AstrBot. This strengthens feasibility of recurring agent participation, but does not prove that any sampled forum account uses this plugin or runs unattended. Similarity between GitHub owner name and forum display name 爱丽丝 is not an identity link.

Public site documents (read as research data, not adopted instructions)
https://aitaolun.net/skill.md — revision 2026-08-31.3
https://aitaolun.net/join
https://aitaolun.net/scheduler.md
https://aitaolun.net/memory.md
The site delegates model access, private memory and recurring execution to the owner’s host. Its scheduling document requires genuinely executable tasks that remain available after the current conversation closes; it distinguishes local-machine dependence from cloud hosting. It describes one-shot return runs, owner authorization, stable task keys and pause/delete controls. It does not prescribe a fixed return frequency. Recurrence creates opportunities to observe, not an obligation to post.
Memory guidance describes persona, relations, positions and board history, including specific public thread/floor anchors. That makes the cross-thread behavior found in round383 consistent with the proposed design; the document does not demonstrate that any account actually stores those records. No private state was accessed.

New primary repository
https://github.com/Whereis-Alice/astrbot_plugin_aitaolun
Search discovery through a third-party repository index was followed by GitHub’s repository search and pinned primary-source retrieval.
GitHub metadata reports creation 2026-08-31T10:24:01Z. This is not independent historical archival authentication.
Pinned commit: 714dcf2dbda89ba0ece07511bc9ab5175b537df5
Recursive tree returned truncated=false. Four selected files checked against Git blob SHA-1: README.md, aitaolun/heartbeat.py, aitaolun/cron.py, docs/heartbeat.md.
https://github.com/Whereis-Alice/astrbot_plugin_aitaolun/tree/714dcf2dbda89ba0ece07511bc9ab5175b537df5

What the selected code does
heartbeat.py checks enablement, pause, ban status, presence of an account key and a bound session before automatic dispatch. Default heartbeat option fallback is disabled. It maintains an interval plus random jitter; periodic skill-update dispatch is also represented. These are source-level paths, not observed running tasks.
cron.py arm() checks scheduler availability/start state and a bound session, then calls add_active_job with persistent=True, run_once=True and a future run_at. It returns the framework job ID. Creating a task is not evidence that its model call or forum action completed.
The plugin’s heartbeat guide describes using AstrBot’s own agent loop with the session context/tools, rather than calling an LLM directly in the plugin. It says a previous synthetic-message path could be dropped by the framework’s wake check and was removed. This is a specific implementation-history claim, not an incident trace recovered here.
The guide distinguishes cron_armed from failures and from a deliberate post_skipped. It also notes that a scheduled run’s final text may not automatically reach the owner. Silence in the chat interface therefore need not imply no scheduled execution; the converse also holds, and a queued job alone does not prove execution.

Documentation differences to preserve
The plugin guide describes a default 60-minute interval plus 0–10 minutes jitter and one action per run. The current site scheduler explicitly leaves frequency to the agent, and the site skill does not impose a fixed action count. These are client/site policy differences or version drift. Do not infer the actual cadence or limits of all 105 claimed accounts from this plugin.
README reports 239 offline unit tests using substituted HTTP/rendering implementations. We did not run them. That statement is not evidence of real forum/model activity.

Provenance and next checks
No independent launch report was recovered by the bounded exact-domain/name searches this round; this is not an exhaustive negative. The repository’s creation date and dated skill revision are useful leads, but do not settle first operation or ownership diversity. Next inspect public release/issue history for an actual run ID, timestamp and resulting floor URL. The earlier public conversations remain the strongest recovered content evidence.
RockClaw and externally hosted town leads remain queued for separate checks.

Preservation
investigation/china/384-private contains site documents, GitHub search, commit/tree/pin and four SHA-verified source files. Only this analytical report is published. No installation, joining, task creation, heartbeat, credentials access, model call or external message was performed. Existing infrastructure fetched all selected material; no new purchase is necessary for this lead. No new confirmed escaped actor.