feat(cli): record 写入 --typecast/--order/--field-key-type + 附件字段 URL 导入 skill 文档 (0.2.0)

skills/inkreach-teable/api-reference/field-types.md

@@ -21,8 +21,7 @@ Complete reference of all Teable field types, aliases, option shapes, and smart
 | `date` | Date | Date or datetime | No |
 | `checkbox` | Checkbox | Yes/no toggle | No |
 | `rating` | Rating | Star/numeric rating 1..10 | No (defaults: max=5, star, yellow) |
-| `attachment` | Attachment | Files, images, documents | No |
-| `user` | User | Person/collaborator reference | No |
+| `attachment` | Attachment | Files, images, documents; cell values also accept `{"url":"https://…"}` items (server downloads the file) | No || `user` | User | Person/collaborator reference | No |
 | `link` | Link | Reference records in another table | Yes (`foreignTableId`/`foreignTableName`) |
 | `lookup` | Lookup | Mirror a field from linked record | Yes (`lookupOptions`) |
 | `rollup` | Rollup | Aggregate linked records (SUM, COUNT, etc.) | Yes (expression + `lookupOptions`) |
@@ -410,6 +409,7 @@ When `--type` is omitted, the CLI infers the type from the field name:
 | `user` | `{"id":"usrXXX","title":"Alice"}` | `"Alice"` or `"alice@example.com"` |
 | `link` (single) | `{"id":"recXXX"}` or `[{"id":"recXXX"}]` | `"Record Display Name"` |
 | `link` (multi) | `[{"id":"recA"},{"id":"recB"}]` | `["Record A","Record B"]` |
+| `attachment` | `[{"url":"https://…/f.png","name":"f.png"}]` (V1 legacy bases: token items only) | `"https://…/f.png"` or `"https://…/a.png,actXXX"` (comma-separated urls/ids) |
 
 **When to use**: always use `--typecast` when creating/updating records with user or link fields — it eliminates manual ID lookups.
 

skills/inkreach-teable/api-reference/rest-api.md

@@ -152,6 +152,16 @@ const res = await fetch(triggerInput._apiBaseUrl + "/api/table/tblB/record", {
    `401` = bad/expired token, `403` = scope or base-role too low.
 6. To see the exact request the CLI sends for any operation, run it with
    `--debug` (prints method/url/body) — the fastest way to learn a route.
+7. **Attachment fields accept URLs** (2026-10): pass `{"url":"https://…","name":"…"}` items
+   (or a URL string with `typecast:true` — note `typecast` is a BODY key) in
+   record create/update `fields`, and the backend downloads the file
+   (SSRF-guarded, size-capped) into attachment storage — response items come
+   back with real `token`/`presignedUrl`. A failed download rejects the whole
+   request (400); nothing is silently dropped. V1 (legacy) bases need
+   `typecast:true` for the string form, V2 bases accept both. The dedicated
+   `POST /api/table/{tid}/record/{rid}/{fid}/uploadAttachment` (multipart,
+   `file` or `fileUrl`) is the older single-record path — the plain record
+   routes now cover URL imports.
 
 ## 5. Full Route Inventory (this guide ≠ the whole API)