chore(release): cut 0.4.31 — sync to chat@4.31.0

[patrick-chinchill]

Cuts 0.4.31, synced to upstream vercel/chat@4.31.0.

Version anchors

• pyproject.toml version 0.4.30 → 0.4.31
• UPSTREAM_PARITY 4.30.0 → 4.31.0
• Fidelity check + CI clone re-pinned chat@4.30.0 → chat@4.31.0 (verify_test_fidelity.py, lint.yml)
• CLAUDE.md / README.md / CHANGELOG.md updated

Why the re-pin is string-only

The 13 mapped-core test files (packages/chat/src/*.test.ts) are byte-identical between the chat@4.30.0 and chat@4.31.0 tags, so no new core test ports are required — verify_test_fidelity --strict against chat@4.31.0 reports 732/732 (0 missing). The core source delta is the LinkButton stable-id field (already on main).

Wave content (already merged on main)

• Linear agent-sessions L1–L5 (Port Linear agent sessions (adapter-linear) — deferred from 0.4.30 #151 — feat(linear): agent-session types + kind discriminator (chat@4.31/#151 — L1/5) #168/feat(linear): agent-session thread-id encode/decode (chat@4.31/#151 — L2/5) #170/feat(linear): agent-session webhook parse + routing (chat@4.31/#151 — L3/5) #171/feat(linear): agent-activity emit — post/typing/stream raw GraphQL (chat@4.31/#151 — L4/5) #172/feat(linear): agent-session fetch + append-only guards raw GraphQL (chat@4.31/#151 — L5/5) #173): raw-GraphQL, schema-hardened
• Teams SDK-free primitive subpaths (teams/api, graph, format, webhook, cards+cards_input, modals)
• Slack 4.31 (feat(slack): webClientOptions + @mention-in-URL fix + stable link-button action_id (chat@4.31) #155): @mention-in-URL fix, web_client_options, stable link-button action_id
• Telegram rich messages (rich.py) + slash-command router
• LinkButton(id=…) stable id + opt-in ThinkingChunk stream type (feat(core): optional ThinkingChunk StreamChunk variant (default-off, upstream-compatible; supersedes #39) #169)

Not ported (documented)

• The new chat/adapters static catalog — npm-addressed + ~13 vendor adapters this SDK doesn't ship; documented as an intentional non-port in docs/UPSTREAM_SYNC.md, deferred demand-driven.

Validation (local, against chat@4.31.0)

ruff check ✓ · ruff format --check (283 files) ✓ · audit_test_quality.py 0 hard failures · verify_test_fidelity --strict 732/732 · pytest 5246 passed / 4 skipped.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added Linear agent-sessions mode with GraphQL support
  • New Teams primitive subpaths with security enhancements
  • Telegram rich messages support
  • Enhanced LinkButton functionality
  • ThinkingChunk stream type option
  • Slack improvements including URL mention handling and stable link button IDs

• Chores

  • Version bumped to 0.4.31, synced with upstream

[coderabbitai]

Warning

Review limit reached

@patrick-chinchill, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 636e3915-41bf-405d-8103-e348077abaf1

📥 Commits

Reviewing files that changed from the base of the PR and between 5b3520a and 230fc37.

📒 Files selected for processing (1)

• docs/UPSTREAM_SYNC.md

📝 Walkthrough

Walkthrough

The PR bumps the Python SDK and upstream parity version from 0.4.30/chat@4.30.0 to 0.4.31/chat@4.31.0. The UPSTREAM_PARITY constant, pyproject.toml version, CI workflow clone tag, fidelity script string literals, and all documentation references (README, CLAUDE.md, CHANGELOG, UPSTREAM_SYNC.md) are updated to the new version.

Changes

Version Bump to 0.4.31 / chat@4.31.0

Layer / File(s)	Summary
SDK version constant and package metadata src/chat_sdk/__init__.py, pyproject.toml	UPSTREAM_PARITY constant updated to "4.31.0" and package version bumped to 0.4.31.
CI workflow pin and fidelity script literals .github/workflows/lint.yml, scripts/verify_test_fidelity.py	git clone tag in the lint workflow and three string literals in the fidelity script (docstring, ts_parity fallback, error message) updated from chat@4.30.0 to chat@4.31.0.
Docs, changelog, and README README.md, CLAUDE.md, CHANGELOG.md, docs/UPSTREAM_SYNC.md	README status line, CLAUDE.md version mapping and fidelity instructions, full 0.4.31 changelog section (Linear agent-sessions, Teams primitives, Slack/Telegram/LinkButton/ThinkingChunk, non-ported chat/adapters catalog), and UPSTREAM_SYNC non-parity table row updated to 4.31.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Sync upstream 4.31 (next wave after 0.4.30) #152: This PR is the implementation that directly satisfies the upstream sync request described in that issue, updating the SDK from 0.4.30 to 0.4.31.
• Sync upstream 4.30 (next wave after the 4.29 cut) #135: This PR follows the same version-tracking pattern as issue #135 (which tracked the 4.30.0 sync), updating the same constants and files for the next upstream wave.

Possibly related PRs

• Chinchill-AI/chat-sdk-python#72: Introduced the fidelity baseline and CI wiring that scripts/verify_test_fidelity.py and lint.yml now pin to chat@4.31.0.
• Chinchill-AI/chat-sdk-python#134: Same pattern of updating the pinned git clone --branch chat@... tag in lint.yml and the ts_parity literal in verify_test_fidelity.py.
• Chinchill-AI/chat-sdk-python#146: Previous version sync bump touching the same UPSTREAM_PARITY, fidelity script, and workflow files, moving from 4.29.0/4.30.0 → 4.30.0.

Poem

🐇 Hop, hop, the version leaps ahead,
From four-thirty to thirty-one instead!
The constants aligned, the docs all agree,
Linear sessions and Slack fixes, yay for me!
A tiny bump, but perfectly done—
chat@4.31.0, here we come! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: cutting version 0.4.31 and syncing to upstream chat@4.31.0, which aligns directly with the changeset's primary objective.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request bumps the package version to 0.4.31 and updates the parity sync to upstream vercel/chat@4.31.0. It updates documentation, changelogs, and helper scripts to reflect this new version. There are no review comments, so I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b3520a49b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate the fidelity baseline after the parity bump

With this bump, the default fidelity workflow is now unusable: load_baseline() compares scripts/fidelity_baseline.json's ts_parity (still chat@4.30.0) to this UPSTREAM_PARITY and exits before checking tests. I verified python scripts/verify_test_fidelity.py exits with the baseline parity mismatch, so this release should also update/regenerate the baseline to chat@4.31.0 rather than leaving local baseline mode broken.

Useful? React with 👍 / 👎.