chore(changeset): the turso ADR-0087 disposition reads registered against main (#14478)

Card 6/6's `already-registered` was honest at its own base, where card 5/6 had
already registered `turso-config-timeout-to-timeout-ms`. Measured against `main`,
this branch's combined diff is what ADDS that registration, so the honest
disposition at this level is `registered` — which is what
check-adr-0087-registration.mjs --base origin/main names.

The explanation moves to a second comment on its own line: every
whitespace-separated token after the id on the marker line itself is parsed as
another id.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G4138K1EG7kQ81FNba5Kp4

Author: claude

.changeset/driver-turso-config-timeout-ms.md

@@ -4,7 +4,10 @@
 
 feat(driver-turso)!: the published connection config names its timeout's unit (#15682, ruling B on #14478)
 
-<!-- adr-0087: not-required (already-registered turso-config-timeout-to-timeout-ms) that protocol-18 conversion rewrites `datasources[].config.timeout` to `timeoutMs` for turso datasources, which is the same authored key this package's schema mirrors — a second entry would restate the same rewrite without converting anything more -->
+<!-- adr-0087: registered turso-config-timeout-to-timeout-ms -->
+<!-- The protocol-18 conversion above is registered by card 5/6 of the #14478 stack; relative to
+     `main` this combined diff is what adds it, so `registered` is the honest disposition at this
+     level even though `already-registered` was honest per-card. -->
 
 **BREAKING** — `TursoConfigSchema`'s `timeout` is renamed to **`timeoutMs`**. The
 value is unchanged: the same milliseconds, the same `min(0)` bound, the same