A single, scannable list of the real inconsistencies and bugs found while researching this library -- the kind of thing you want to remember exists rather than rediscover by debugging. Each one is confirmed against the actual source, not inferred.
Almost everything in this library takes a single options object ({ postId, content }, not positional args). A handful of methods don't:
FilesClient.getMeta(fileId) and FilesClient.delete(fileId)NotificationsClient.markRead(id), markUnread(id), dismiss(id) All four take a bare string. Everything else on those same sub-clients (FilesClient.list(), NotificationsClient.list()/unreadCount()/markAllRead()) takes an options object as usual. Check the exact signature before assuming uniformity.
FilesClient.upload(), AdminClient.restoreFromFile(), and AdminClient.backupDownloadUrl() skip HttpClient and either build a raw fetch() multipart request or just build a URL directly -- HttpClient always JSON-stringifies its request body, which doesn't work for FormData. A practical consequence: errors from an upload or restore call are not guaranteed to arrive as a KowloonError subclass the way errors from every other method are. If you're writing generic error-handling that pattern-matches on the KowloonError hierarchy, add a plain-Error fallback specifically around these calls.
updatePost's content field is remapped, not passed through
client.activities.updatePost({ postId, updates: { content } }) does not send content at object.content. It's remapped to object.source = { content }, matching where the server's Update handler for Posts actually expects content patches. Similarly, to/canReply/canReact patch values are nested inside object, not sent at the activity's top level. Get this wrong and the update silently no-ops on the field you meant to change rather than erroring.
createInvite has an exact field-name requirement
client.admin.createInvite({ email, maxRedemptions, ... }) -- a code comment in the client itself warns that an earlier version used recipient/amount instead, which the server silently dropped (unrecognized fields, no error), shipping invites with no recipient email and no redemption cap. Use email/maxRedemptions exactly.