0.1.5

Clears the remaining review warnings. No behaviour change.

What changed

The warning list was mostly one omission repeated: unwrap() returned any, so
every field read off a pairing response, a summary or a note reached TypeScript
untyped, and each access was reported separately.

• ApiResult<T>, PairingStart, PairingToken and WhoAmI are declared, and the
  pairing calls and planPull() now say what they return.
• unwrap() returns unknown rather than any, so a caller has to state the
  shape it expects — that is what stops it spreading again.
• PairModal declares its fields instead of using constructor parameter
  properties, which no-unused-vars read as three dead parameters.
• Notice and modal copy no longer place the product name mid-sentence.

33 findings → 7, and zero errors throughout.

Still open, deliberately. The remaining seven are one cause: this plugin
declares minAppVersion 1.13.0, and on 1.13 the classic display() settings tab
is deprecated in favour of getSettingDefinitions(). Adopting it means rewriting
the settings tab — the only path a user has to connect the plugin — for warnings
that do not block installation. 1.13.0 itself is the honest floor: tested down the
range, 1.11.0 still reports an unsupported API.

Verified: 0 lint errors, 28/28 tests, clean tsc, and main.js reproduces
byte-for-byte from source with a GitHub artifact attestation.