Rename runBleThroughputTest to runThroughputTest, and prepare the v0.4.0 release

[marknolan]

Two commits: the rename this PR was opened for, and the release prep that has to
land with it (the changelog roll conflicts with anything else that edits
[Unreleased], so it cannot sensibly be a second PR).

1. runBleThroughputTest() → runThroughputTest()

Nothing about this measurement is BLE-specific. It asks the device to blast a
dummy buffer (debug command 0x0B) and counts what arrives on the attached
transport, so it measures a Web Serial link exactly as it measures a Web
Bluetooth one — verisense-device-console has been running it over USB serial
all along, under a button labelled "BLE Throughput Test". The name was the only
thing claiming otherwise, and a caller who believed it would skip the test on a
serial connection for no reason.

• BleThroughputTestOptions / BleThroughputTestResult → ThroughputTestOptions / ThroughputTestResult
• The old names stay as a forwarding method and two type aliases, all
  @deprecated, so both consoles keep working on the builds they have vendored.
• The doc comment now separates what genuinely is link-specific: PHY, connection
  interval, MTU and packets per connection interval over BLE; that link's own
  ceiling over serial. packetsReceived is documented as chunks — BLE
  notifications, or serial reads — rather than notifications alone.

No behaviour change: the deprecated method forwards unchanged, and the renamed
types are the same shapes.

2. Release prep: the changelog, and what a release is

CHANGELOG.md held all 103 entries in one [Unreleased] section, back to
0.1.0, so it could not answer "what changed in the version we are running" —
the one question a consumer's sdk-source.json stamp makes you ask.

The entries are unchanged and none moved between Added / Changed / Fixed.
What moved is the version heading each sits under, derived from git rather than
judgement: the first package.json bump at or after the commit that introduced
it, dated by that bump. Merge ordering sent the version backwards more than once
(0.1.23 → 0.1.21 → 0.1.22 → 0.1.23 across two days), so a bump only counts
when it exceeds every version before it — without that rule the ExG codec landed
under 0.1.23 when its own release commit says 0.1.24.

Seven of the thirteen sections are confirmed by their release commit's subject
line: 0.1.22, 0.1.23, 0.1.24, 0.1.25, 0.1.26, 0.2.1 and 0.3.0
each name the work this places under them. The 0.1.8-dock.N prereleases fold
into 0.1.8, the release that carried that work. The ten entries written since
the 0.3.0 bump (DEV-1021, DEV-1023 and this branch's rename) become 0.4.0.

The reconstruction exposed a gap worth stating, so the preamble states it:
v0.1.1–v0.1.7 are the only tags and GitHub releases, while hand bumps for
vendoring carried package.json to 0.3.0. Cut Release is the only thing that
publishes and it tags every time, so that dozen of versions was never published
— they reached the consoles as vendored dist/ builds, which is how the
consoles consume this SDK anyway.

AGENTS.md now draws that distinction right where the vendoring instruction
sits, since following that instruction is what produced the drift.

## [0.4.0] - 2026-09-17 is dated for the release intended immediately after
this merges (Cut Release → minor).

Verification

npm run typecheck, npm run lint, npm run build and npm test (1889 tests,
96 files) pass locally, and CI is green. The changelog restructure was checked
mechanically: all 103 entry blocks appear verbatim in the rewritten file, and
the file is prettier-clean.

Companion PRs

• ShimmerResearch/verisense-device-console#48 — renames the console's UI, which is where the wrong name was visible
• Name ShimmerCapture's link test a throughput test webBLEDemos#87 — same vocabulary for ShimmerCapture's own throughput test

🤖 Generated with Claude Code

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}