v0.1.2 — richer work item reads, safer writes, clearer errors

Ten fixes and additions since v0.1.1, focused on work item reads/writes and truncation/error reporting.

Changed

• Breaking: update_work_item, create_work_item, link_work_item, and add_work_item_attachment now return a minimal WorkItemWriteResult (id, rev, changed fields, success) instead of the full WorkItem.

Added

• includeRelations on get_work_item and get_work_items fetches relations without requiring a full fields expansion.
• expectedRevision on update_work_item lets a caller require a specific revision before writing; a mismatch is reported with the current revision instead of silently overwriting a concurrent change.
• descriptionFormat on get_work_item, get_work_items, and get_work_item_revisions (html default, text) strips markup and decodes entities from rich-text fields.

Fixed

• Eight list tools reported no truncation when a result exactly filled its cap. list_branches, list_commits, list_pull_requests, list_my_pull_requests, list_releases, list_release_approvals, list_builds, and get_work_item_revisions now request one extra item and report truncation the same way list_repository_items and list_work_item_comments already did.
• get_work_items failed with an opaque server error on an oversized id batch, and project pagination had no upper bound and could loop forever on a malformed continuation token. Both are now bounded client-side with a clear error.
• Authentication failures collapsed every 401/203 response into one generic message. It now reports the actual request URI, HTTP status, and the server's offered WWW-Authenticate schemes, without ever including the Authorization header or the PAT.

Known issues

• The write-path changes above (expectedRevision, the minimal write result shape) are verified only against stub Azure DevOps handlers in this release, not yet against a real Azure DevOps Server.

62 tools, 391 tests.

Full changelog: v0.1.1...v0.1.2