v1.0.61-beta.2

Added

• Chat emotion favorite local image (#85955640) — dws chat emotion favorite now accepts --file-path for a local image (jpg/jpeg/png/gif/webp/bmp, up to 10MB) as an alternative to --media-id; the CLI validates the file locally, uploads it through dingtalk-file/upload_media (bizType=chat_emoticon), and reuses the existing favorite flow with the returned mediaId (mediaIdV1 preferred, falling back to mediaIdV2). --media-id behavior is unchanged.

• Contact label management — adds dws contact label update, dws contact label delete, dws contact label add-members, dws contact label remove-members, and dws contact label update-member-scope to modify, delete, add/remove members, and adjust member scope for contact labels (roles). Also updates dws contact label create to require an explicit --type role|group: --type role requires --parent-id with a real label group ID; --type group creates a root-level label group and must omit --parent-id (the CLI passes parentId=-1).

• Contact custom field management — adds dws contact ext-field create, dws contact ext-field update, and dws contact ext-field delete to manage organization custom employee fields (add_org_ext_attrs, update_org_ext_attrs, remove_org_ext_attrs).

Changed

• DingTalk task workflows — adds strict write receipts and read-back verification,
  executable parameter constraints, local dry-run plans for write shortcuts, bounded
  list scripts, and per-item verification ledgers for batch creation.

Fixed

• Beta shortcut response contracts (#1167) — fixes HRbrain talent-pool business-page parsing and Mail template draft-mode input, while keeping OA form listing and other incompletely proven operations fail-closed.

• Doc output compatibility — preserves the empty pagination failure ledger and lets completed import recovery report an unverified result when the original target is unavailable.

• Markdown routing and diff guidance — makes markdown create --folder
  detect the Drive or Doc destination before upload, clarifies markdown diff
  parameter validation, and improves mono/multi Agent routing.

• Chat message list result fields — keeps result.messages[] aligned with the top-level messages[], including the stable messageId used by edit and recall, while preserving legacy message fields.