fix(attribution): CloudBase JS SDK API 返回结构不清晰，导致文章创建后无法正确获取文档 ID (issue_mnpr3lei_r3vw5t)

Author: CodeBuddy Attribution Bot

config/source/guideline/cloudbase/SKILL.md

@@ -221,7 +221,7 @@ Prefer long-term memory when available: write the scenarios and working rules th
 2. **Authentication**: Read the `auth-web` and `auth-tool` skills - Use Web SDK built-in authentication
 3. **Database**:
    - NoSQL: `no-sql-web-sdk` skill
-   - Web SDK create-result reminder: after `db.collection(...).add(...)`, the new document ID is `result.id`
+   - Web SDK create-result reminder: after `db.collection(...).add(...)`, the new document ID is `result._id`
    - MySQL: `relational-database-web` and `relational-database-tool` skills
 4. **UI Design** (Recommended): Read the `ui-design` skill for better UI/UX design guidelines
 5. **Quick SDK reference**:
@@ -264,7 +264,7 @@ Prefer long-term memory when available: write the scenarios and working rules th
 
 **Web Projects:**
 - NoSQL Database: Refer to the `no-sql-web-sdk` skill
-- For CloudBase Web SDK `db.collection(...).add(...)`, read the created document ID from `result.id`, not `result.data.id`, `_id`, or `insertedId`
+- For CloudBase Web SDK `db.collection(...).add(...)`, read the created document ID from `result._id`, not `result.id`, `result.data.id`, or `insertedId`
 - MySQL Relational Database: Refer to the `relational-database-web` skill (Web) and `relational-database-tool` skill (Management)
 
 **Mini Program Projects:**

config/source/skills/SKILL.md

@@ -61,6 +61,7 @@ alwaysApply: true
 
 3. Database and storage tasks:
    - Reuse the current shared `app`, `auth`, `db`, and storage helpers instead of creating parallel SDK wrappers.
+   - For CloudBase Web SDK `db.collection(...).add(...)`, persist the created document ID from `result._id`.
    - For writes, validate the actual SDK result instead of assuming success.
 
 4. Targeted repair tasks:

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

@@ -47,7 +47,7 @@ Keep local `references/...` paths for files that ship with the current skill dir
 - Using `wx.cloud.database()` or Node SDK patterns in browser code.
 - Initializing CloudBase lazily with dynamic imports instead of a shared synchronous app instance.
 - Treating security rules as result filters rather than request validators.
-- Misreading the return shape of `db.collection(...).add(...)`. In the CloudBase Web SDK, the created document ID is exposed at top-level `result.id`, not `result.data.id`, `result._id`, or `result.insertedId`.
+- Misreading the return shape of `db.collection(...).add(...)`. In the CloudBase Web SDK, the created document ID is exposed at top-level `result._id`, not `result.id`, `result.data.id`, or `result.insertedId`.
 - For CMS-style collections that need **app-level admin users** to edit/delete all records while editors can only edit/delete their own records, do not oversimplify the rule to `READONLY`. A validated pattern is a `CUSTOM` rule that reads role from `user_roles` by `auth.uid` and combines it with `doc.authorId == auth.uid`, while frontend writes can stay on `.doc(id).update()` / `.doc(id).remove()`.
 - Forgetting pagination or indexes for larger collections.
 
@@ -121,8 +121,8 @@ Important rules:
    - For writes, do not treat a resolved promise as success by default. Check write result fields such as `updated` / `deleted` or surfaced `code` / `message`.
 
 5. **Persist IDs from create operations correctly**
-   - For Web SDK `.add(...)`, the newly created document ID is `result.id`.
-   - Do not look for the ID under `result.data`, `_id`, or other driver-specific fields.
+   - For Web SDK `.add(...)`, the newly created document ID is `result._id`.
+   - Do not look for the ID under `result.id`, `result.data`, or other driver-specific fields.
 
 ## Quick examples
 
@@ -143,7 +143,7 @@ const result = await db.collection("posts").add({
   createdAt: new Date()
 });
 
-const articleId = result.id;
+const articleId = result._id;
 ```
 
 ### Ordered pagination

config/source/skills/no-sql-web-sdk/crud-operations.md

@@ -20,13 +20,13 @@ const result = await db.collection('todos').add({
     // _openid is automatically populated from authenticated user session
 });
 
-console.log('Added document with ID:', result.id);
+console.log('Added document with ID:', result._id);
 ```
 
 **Return Value:**
 ```javascript
 {
-    id: "generated-doc-id",  // Auto-generated document ID
+    _id: "generated-doc-id",  // Auto-generated document ID
     // ... other metadata
 }
 ```
@@ -493,7 +493,7 @@ class TodoManager {
             createdAt: new Date(),
             updatedAt: new Date()
         });
-        return result.id;
+        return result._id;
     }
 
     // Read (single)
@@ -579,7 +579,7 @@ async function safeCRUD() {
             title: 'New Todo'
         });
 
-        console.log('Created:', result.id);
+        console.log('Created:', result._id);
 
     } catch (error) {
         if (error.code === 'PERMISSION_DENIED') {