Added value: +{
+  "description": "nextCursor from a previous call, passed with the same itemId, to continue the traversal at the next unseen comment without repeating or skipping any. Omit to start from the top.",
+  "type": "string"
+}

Previous value: -"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Popular stories often have more top-level comments than maxComments — to see nesting, raise maxComments together with depth, or call again with a specific comment's itemId to drill into a subtree."New value: +"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Replies below this depth are never fetched — to read them, raise depth or call again with a specific comment's itemId to drill into its subtree. Ignored when cursor is set: the depth the cursor was issued with applies."

Previous value: -"ID of the story, comment, or poll to fetch the thread for."New value: +"ID of the story, comment, job, poll, or poll option to fetch the thread for."

Previous value: -"Maximum total comments to include across all depth levels. Highest-ranked top-level comments resolve first; replies fill in only after the level above is exhausted."New value: +"Maximum comments in one response, across all depth levels. Highest-ranked top-level comments resolve first; replies fill in only after the level above is exhausted. A response also stops at a fixed 64,000-byte text budget. When either limit stops the traversal, nextCursor continues it."

Previous value: -"Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting."New value: +"Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting. With cursor, the page continues the same order."

Previous value: -"Machine-readable failure mode. Declared by this tool: `item_not_found`: HN reports no item exists for the given itemId. `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `item_not_found`: HN reports no item exists for the given itemId. `invalid_cursor`: The cursor was issued for a different itemId than the one passed with it. `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler."

Previous value: -[
-  "item_not_found",
-  "upstream_rejected",
-  "upstream_rate_limited",
-  "upstream_unavailable",
-  "upstream_html",
-  "upstream_malformed"
-]New value: +[
+  "item_not_found",
+  "invalid_cursor",
+  "upstream_rejected",
+  "upstream_rate_limited",
+  "upstream_unavailable",
+  "upstream_html",
+  "upstream_malformed"
+]

Added value: +{
+  "description": "Comment and poll-option IDs whose fetch failed after retries, so neither they nor their replies are in this response. They are not deleted or missing and may load on a later call. Failed comments ride in nextCursor and are retried when you continue; without one, call again, or pass an ID as itemId to fetch that comment and its replies. Absent when everything the traversal reached loaded.",
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}

Previous value: -"The root item (story, comment, or poll)."New value: +"The root item: a story, comment, job, poll, or poll option."

Added value: +{
+  "const": true,
+  "description": "Present and `true` when the root is dead (flagged or killed); its replies are still walked. Omitted otherwise.",
+  "type": "boolean"
+}

Added value: +{
+  "const": true,
+  "description": "Present and `true` when HN reports the root deleted; its author and text are gone, but its replies are still walked. Omitted otherwise.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "For a poll root, its options with text and votes in parts order, resolved at every depth including 0. Deleted and dead options are kept and marked; an option whose fetch failed is listed in failedIds instead. Options do not count toward maxComments or totalLoaded.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One poll option.",
+    "properties": {
+      "dead": {
+        "const": true,
+        "description": "Present and `true` when the option is dead (flagged or killed). Omitted otherwise.",
+        "type": "boolean"
+      },
+      "deleted": {
+        "const": true,
+        "description": "Present and `true` when the option was deleted. Omitted otherwise.",
+        "type": "boolean"
+      },
+      "id": {
+        "description": "Poll option ID.",
+        "type": "number"
+      },
+      "score": {
+        "description": "Votes for this option.",
+        "type": "number"
+      },
+      "text": {
+        "description": "Option text (HTML stripped). Absent once deleted.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Added value: +{
+  "description": "For a comment root, the ID of the story or comment it replies to — pass it as itemId for the context above.",
+  "type": "number"
+}

Added value: +{
+  "description": "For a poll root, its option IDs in HN order.",
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}

Added value: +{
+  "description": "For a poll-option root, the ID of its poll.",
+  "type": "number"
+}

Previous value: -"Story/job title."New value: +"Story/job/poll title."

Added value: +{
+  "description": "Pass as cursor, with the same itemId, to continue from the next unseen comment. Present when truncationReason is count, size, or rate_limited; absent on the last page.",
+  "type": "string"
+}

Previous value: -"Truncation context: counts of deleted/dead comments dropped during traversal, then either how to get past the maxComments cap when it stopped the traversal, or a raise-maxComments-or-depth hint when totalLoaded < totalAvailable. Absent when no comments were dropped and all available comments were loaded."New value: +"Traversal context: counts of deleted/dead comments dropped, the IDs that failed to load and how to retry them, then what stopped the traversal and how to continue — nextCursor for a count, size, or rate-limit stop, or a larger depth or a comment id as itemId for a depth cut. Absent when nothing was dropped, failed, or left unread."

Previous value: -"Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again."New value: +"HN's total comment count for the root (descendants), which also counts dead and deleted comments. Absent for comment and job roots."

Previous value: -"Number of comments actually fetched and included."New value: +"Number of comments in this response (this page, when paging with cursor)."

Previous value: -"True when maxComments stopped the traversal while comments remained. Absent when every available comment was loaded, even at exactly maxComments."New value: +"True when comments remain unread: reachable through nextCursor (truncationReason count, size, or rate_limited), or below the depth limit (depth). Absent on a terminal page — including a thread that loads in full at exactly maxComments."

Added value: +{
+  "description": "Why the traversal stopped short: count = maxComments (or the 1,000-item ceiling per call) was reached; size = the 64,000-byte response budget was reached; rate_limited = the HN API throttled the fetches; depth = replies lie below the depth limit, which nextCursor does not reach — raise depth or pass a comment id as itemId. When a cursor reason and a depth cut both apply, the cursor reason is reported.",
+  "enum": [
+    "count",
+    "size",
+    "depth",
+    "rate_limited"
+  ],
+  "type": "string"
+}

Previous value: -"Truncation context: counts of deleted/dead comments dropped during traversal, or pagination hint when totalLoaded < totalAvailable. Absent when no comments were dropped and all available comments were loaded."New value: +"Truncation context: counts of deleted/dead comments dropped during traversal, then either how to get past the maxComments cap when it stopped the traversal, or a raise-maxComments-or-depth hint when totalLoaded < totalAvailable. Absent when no comments were dropped and all available comments were loaded."

Previous value: -"True when the comment list was capped by maxComments."New value: +"True when maxComments stopped the traversal while comments remained. Absent when every available comment was loaded, even at exactly maxComments."

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Added value: +false

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "item",
+      "comments",
+      "totalLoaded"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `item_not_found`: HN reports no item exists for the given itemId. `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "item_not_found",
+            "upstream_rejected",
+            "upstream_rate_limited",
+            "upstream_unavailable",
+            "upstream_html",
+            "upstream_malformed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

Removed value: -[
-  "item",
-  "comments",
-  "totalLoaded"
-]

Previous value: -"number"New value: +"integer"

Added value: +9007199254740991

Added value: +-9007199254740991

Previous value: -"number"New value: +"integer"

Previous value: -"number"New value: +"integer"

Added value: +{
+  "description": "The maxComments cap that was applied.",
+  "type": "number"
+}

Added value: +{
+  "description": "Number of comments returned.",
+  "type": "number"
+}

Added value: +{
+  "description": "True when the comment list was capped by maxComments.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "Truncation context: counts of deleted/dead comments dropped during traversal, or pagination hint when totalLoaded < totalAvailable. Absent when no comments were dropped and all available comments were loaded.",
+  "type": "string"
+}

Removed value: -{
-  "additionalProperties": false,
-  "description": "Counts of comments dropped during BFS traversal. Present only when at least one comment was dropped, so the caller can tell when a thread view is partial due to moderation rather than depth/maxComments limits. Absence means no moderation truncation.",
-  "properties": {
-    "dead": {
-      "description": "Count of comments dropped because HN flagged them dead (autoflagged).",
-      "type": "number"
-    },
-    "deleted": {
-      "description": "Count of comments dropped because HN flagged them deleted (author/mod removal).",
-      "type": "number"
-    }
-  },
-  "required": [
-    "deleted",
-    "dead"
-  ],
-  "type": "object"
-}

Added value: +{
+  "const": true,
+  "description": "Present and `true` when the comment author matches the root item author (OP replying within their own thread). Omitted otherwise — including when either author is missing. Most threads carry no OP replies, so absence is the common case; treat missing as \"not OP\" rather than unknown.",
+  "type": "boolean"
+}

Added value: +{
+  "additionalProperties": false,
+  "description": "Counts of comments dropped during BFS traversal. Present only when at least one comment was dropped, so the caller can tell when a thread view is partial due to moderation rather than depth/maxComments limits. Absence means no moderation truncation.",
+  "properties": {
+    "dead": {
+      "description": "Count of comments dropped because HN flagged them dead (autoflagged).",
+      "type": "number"
+    },
+    "deleted": {
+      "description": "Count of comments dropped because HN flagged them deleted (author/mod removal).",
+      "type": "number"
+    }
+  },
+  "required": [
+    "deleted",
+    "dead"
+  ],
+  "type": "object"
+}

Previous value: -"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Popular stories often have more top-level comments than maxComments — to see nesting, raise maxComments together with depth, or call again on a specific commentId to drill into a subtree."New value: +"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Popular stories often have more top-level comments than maxComments — to see nesting, raise maxComments together with depth, or call again with a specific comment's itemId to drill into a subtree."

Previous value: -"Flat comment list ordered by ranked BFS traversal. Use depth/parentId to reconstruct nesting."New value: +"Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting."

Previous value: -"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Deeper threads on popular stories can be very large — start with 2-3 and go deeper if needed."New value: +"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Popular stories often have more top-level comments than maxComments — to see nesting, raise maxComments together with depth, or call again on a specific commentId to drill into a subtree."

Previous value: -"Maximum total comments to include across all depth levels. Traversal stops when this limit is reached. Comments are resolved breadth-first by HN ranking."New value: +"Maximum total comments to include across all depth levels. Highest-ranked top-level comments resolve first; replies fill in only after the level above is exhausted."

Previous value: -"Item type."New value: +"Item type: story | comment | job | poll | pollopt."

Previous value: -"Total comment count from the root item (descendants field). If totalLoaded < totalAvailable, increase maxComments or depth to see more."New value: +"Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again."

Added value: +"A single comment in the thread with its tree position."