fix(types): widen TransformResult response parameter

`$.ajax` resolves with a payload whose shape is defined by the consumer's
service, but `TransformResult` typed it `string | AutocompleteResponse`.
That rejected the README's own non-standard-response example (TS2339) and
also rejected a consumer-annotated `(response: MyResponse) => ...` callback
(TS2322, parameter contravariance). `unknown` fixes neither, so the
parameter is now `any` — the same type jQuery gives it.

Fixes #891

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X29RAqzWDUD7UptThtJZGv

Author: tkirda-bison

CLAUDE.md

@@ -72,7 +72,7 @@ The minified UMD is ~13 KB; the unminified is ~26 KB.
 
 ## Conventions
 
-- TypeScript strict mode is on. Don't introduce `any` in public types. Internal `as unknown as X` casts are OK at jQuery boundaries where typings are imprecise.
+- TypeScript strict mode is on. Don't introduce `any` in public types. Internal `as unknown as X` casts are OK at jQuery boundaries where typings are imprecise. The one deliberate exception is `TransformResult`'s `response: any` (#891) — it's the raw server payload, jQuery types it `any`, and `unknown` breaks both the README example and consumer-annotated callbacks. Don't "tighten" it back.
 - The `Autocomplete` class explicitly marks every member `private` unless it's part of the documented public API in `readme.md` (`setOptions`, `clear`, `clearCache`, `disable`, `enable`, `hide`, `select`, `dispose`, plus the `options` field and the static `defaults`/`utils`). When adding a new member, default to `private`; only drop the keyword when you also add a row to the README's instance-method table. JS callers can still reach private members at runtime — they're a TypeScript-surface contract, not a runtime fence — but the contract is what consumers will rely on.
 - Methods use `this` directly. The one exception is `initialize()`, which aliases `const self = this` for the jQuery delegation handlers (`function (this: HTMLElement)`) that need both `$(this)` for the matched element AND access to the Autocomplete instance. Don't add new `that = this` aliases elsewhere — use arrow functions for callbacks instead.
 - Prefer native array methods (`.map`, `.filter`, `.find`, `.some`, `.indexOf`) over jQuery's `$.each` / `$.grep` / `$.map` / `$.inArray` in new code; the JS-source equivalents have already been swapped where semantics match.

readme.md

@@ -256,6 +256,25 @@ $('#autocomplete').autocomplete({
 });
 ```
 
+`transformResult` receives the raw payload `$.ajax` resolved with, so its
+type is up to your service. In TypeScript you can annotate the parameter
+with your own response shape:
+
+```ts
+interface MyResponse {
+    myData: { valueField: string; dataField: number }[];
+}
+
+$('#autocomplete').autocomplete({
+    transformResult: (response: MyResponse) => ({
+        suggestions: response.myData.map((item) => ({
+            value: item.valueField,
+            data: item.dataField,
+        })),
+    }),
+});
+```
+
 ## Grouping results
 
 Set `groupBy` to a property name on `suggestion.data` to render group

src/types.ts

@@ -21,10 +21,11 @@ export type LookupFilter = (
     queryLowerCase: string
 ) => boolean;
 
-export type TransformResult = (
-    response: string | AutocompleteResponse,
-    originalQuery: string
-) => AutocompleteResponse;
+// `response` is whatever `$.ajax` resolved with — its shape is defined by the
+// consumer's server, not by us, and jQuery itself types it as `any`. `unknown`
+// won't do: it rejects both `response.myData` on an unannotated parameter and a
+// consumer-annotated `(response: MyResponse) => ...` (parameter contravariance).
+export type TransformResult = (response: any, originalQuery: string) => AutocompleteResponse;
 
 export type FormatResult = (suggestion: Suggestion, currentValue: string, index?: number) => string;