fix: 实时监听 API 缺乏初始数据就绪通知机制

[binggg]

Attribution issue

• issueId: issue_mnrzm5ru_70sm9m
• category: tool
• canonicalTitle: 实时监听 API 缺乏初始数据就绪通知机制
• representativeRun: application-js-react-cloudbase-realtime-battle-scaffold/2026-04-09T21-21-47-2xl1on

Automation summary

• root_cause: The realtime API already provides an initial readiness signal via the first onChange snapshot with dataType: 'init', so this was not a missing API capability. The real defect in this repository was a product-facing skill guidance gap: the main no-sql-web-sdk skill did not surface that readiness contract prominently enough, which made it easy for agents to wire watch() incorrectly and treat subscription setup as immediately ready.
• changes: Updated config/source/skills/no-sql-web-sdk/SKILL.md to make realtime initialization explicit in the main skill entry. Added a gotcha stating that callers must wait for the first onChange snapshot containing dataType: 'init' before treating data as ready, and added a working rule that .watch() should keep loading state explicit until that initial snapshot arrives.
• validation: Reviewed the repository evidence and confirmed the lower-level realtime reference already documents init snapshots, so no API shim was added. Verified the new main-skill text is present via diff/grep. No automated tests were run because this fix is limited to skill guidance text and there was no targeted test covering this wording.
• follow

Changed files

• config/source/skills/no-sql-web-sdk/SKILL.md

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: FAILED
• summary: at least one planned evaluation case failed
• updated_at: 2026-04-19T18:14:44.738Z

Cases

• [FAILED] — primary — evaluation failed