[lmjabreu]

Context

• users.update({ name }) sent name, but comms-backend's UserUpdateBody reads full_name and ignores fields it does not know. The call returned 200 and changed nothing, so a rename from comms-mcp's update-user-info looked like it worked.

What was changed

• update() sends name as full_name. The public name argument is unchanged, so callers need no change.
• New test in users-client.test.ts fails without the fix (name sent where full_name is expected) and passes with it. npm run verify passes.
• Live against Comms with the same name, so nothing changed: {"name": ...} returns 200 and writes nothing; {"full_name": ...} now reaches Todoist.
• Not fixed here: with an OAuth token, that Todoist hop returns 401 "Invalid token" for name, timezone and language alike, because comms-backend forwards the caller's token to Todoist's /user/update (Doist/comms-backend#518). That needs a backend change.

Refs

• Doist/comms-mcp#72, where the live test found it.

🤖 Generated with Claude Code

[doistbot]

This PR fixes users.update to send the rename as full_name, the field comms-backend actually reads, while keeping the public name argument unchanged — so a previously silent no-op now reaches Todoist, and new MSW tests pin the exact wire format including the no-name case. No inline issues were flagged; the mapping through the existing snakeCaseKeys serialization and the test coverage match the repo's established patterns.

I also included a few optional follow-up notes in the details below.

Optional follow-up notes (2)

• src/clients/users-client.test.ts:246: These new tests instantiate UsersClient directly, but the repository's write-tests convention and AGENTS.md's definition of done exercise clients through the public interface: new CommsApi(TEST_API_TOKEN) then api.users.update(...). Routing through CommsApi keeps the tests on the public API and matches most other client test files.
• src/clients/users-client.test.ts:267: This test would still pass with the change undone (update({ timezone }) already sent exactly { timezone }), so it adds no proof for this fix. It also cannot guard the name === undefined branch it seems to target: even { ...rest, fullName: name } with name undefined serializes to {"timezone":"Europe/London"} because JSON.stringify(snakeCaseKeys(...)) drops full_name: undefined before MSW parses the body. Drop it, or fold the timezone passthrough check into the first test.

_{Share Feedback • Review Logs}

[lmjabreu]

These new tests instantiate UsersClient directly, but the repository's write-tests convention and AGENTS.md's definition of done exercise clients through the public interface

Done in 83093c0. The test now calls api.users.update(...) on a new CommsApi(TEST_API_TOKEN).

This test would still pass with the change undone (update({ timezone }) already sent exactly { timezone }), so it adds no proof for this fix.

Done in 83093c0. Dropped it, since the first test already checks timezone and lang pass through next to full_name.

[lmjabreu]

@engfragui the release after this merged got stuck halfway: GitHub returned a 500 while semantic-release was pushing its notes, so the v5.0.2 tag and release commit are on main but nothing reached npm (still 5.0.1). Re-running the job doesn't help, it skips because main has moved past that commit (run).

Would you be able to publish 5.0.2, or know who can? No rush if another release is due soon, #147 would carry it too.

[doist-release-bot]

🎉 This PR is included in version 5.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[scottlovegrove]

@lmjabreu All done.