Support title/tag metadata updates in note PATCH APIs

[Copilot]

The client’s note update methods were still typed for an older metadata shape and did not allow updating title or tags, even though the latest API supports both fields. This aligns the user-note and team-note PATCH payloads with the current metadata update contract.

• API surface

  • Added a shared UpdateNoteOptions type for note PATCH payloads
  • Expanded supported update fields to include:
    • title
    • tags
    • existing content/permission/permalink fields

• Client methods

  • Updated updateNote() to accept the latest metadata fields
  • Updated updateTeamNote() to accept the same payload shape for parity

• Coverage

  • Added focused tests asserting that note and team-note PATCH requests pass title and tags through unchanged

await client.updateNote('note-id', {
  title: 'Updated title',
  tags: ['api', 'metadata']
})

await client.updateTeamNote('team-path', 'note-id', {
  title: 'Updated team note',
  tags: ['team', 'shared']
})

---

Note

Low Risk
Low risk: this is a TypeScript type-surface expansion for existing PATCH endpoints plus tests, with no behavioral changes to request/response handling beyond allowing additional fields through.

Overview
Updates the Node.js client’s updateNote and updateTeamNote method signatures to accept a new shared UpdateNoteOptions payload type, enabling PATCH updates of note metadata (title, tags) alongside existing content/permission/permalink fields.

Adds tests ensuring both user-note and team-note PATCH calls pass title/tags through unchanged (and for user notes, still return etag when unwrapping data).

^{Written by Cursor Bugbot for commit 6b63270. This will update automatically on new commits. Configure here.}