fix: CloudBase JS SDK Skill 文档缺乏认证状态同步与存储 API 使用说明

[binggg]

Attribution issue

• issueId: issue_mnrz9iv5_2a0jmm
• category: skill
• canonicalTitle: CloudBase JS SDK Skill 文档缺乏认证状态同步与存储 API 使用说明
• representativeRun: application-js-react-cloudbase-cms-scaffold/2026-04-09T21-10-58-aaa0a8

Automation summary

• root_cause: This is a real product-facing documentation defect in the CloudBase JS SDK skill set. The Web document-database skill covered CRUD and permissions, but it did not explicitly tell agents to wait for browser auth/session restoration before the first protected query, and it did not explain that file-bearing fields such as coverImage must be handled through Cloud Storage APIs first and only then persisted as database references. In CMS-style Web tasks, that gap can lead to anonymous-looking first reads after refresh and incorrect storage/database usage.
• changes: Updated config/source/skills/no-sql-web-sdk/SKILL.md with the minimal product-facing fix: added a sibling reference to the Cloud Storage Web skill, expanded common gotchas/checklist items, documented an auth-state synchronization pattern using auth.onAuthStateChange(...) before protected CRUD, and added a storage-boundary section showing app.uploadFile(), app.getTempFileURL(), and app.deleteFile() as the correct path for document fields backed by uploaded files.
• validation: Read the available internal evaluation evidence and the related skill docs, reviewed the resulting diff, and ran a small conte

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-19T17:43:11.816Z

Cases

• [FAILED] — primary — evaluation failed