Fix recordCommitLatency parameter type for the widened commitResolution union

[kriszyp]

Main currently has a TS2345 at resources/DatabaseTransaction.ts:413: 6e6d57ed8 widened commitResolution to Promise<number | void> | void for the LMDB-engine guard, but recordCommitLatency still declared Promise<void>.

The main build job tolerates tsc errors, but the Next.js adapter integration workflow builds harper with errors fatal — so this fails those checks on every PR (observed on #1898, all three Node versions).

The recorder only times settlement (fulfil or reject) and already thenable-guards, so it takes Promise<unknown> | void; the now-redundant as Promise<void> cast on transaction.commit() is removed with its stale comment. Type-only — no runtime change. tsc --noEmit -p tsconfig.build.json exits clean with this patch.

🤖 Generated with Claude Code (Opus 4.8)

[claude]

Reviewed; no blockers found.

[gemini-code-assist]

Code Review

This pull request updates resources/DatabaseTransaction.ts to loosen the type of commitResolution in recordCommitLatency from Promise<void> to Promise<unknown> | void. This change allows for the removal of an explicit type cast (as Promise<void>) when assigning the result of transaction.commit(). No review comments were provided, and there is no additional feedback to offer.

[kriszyp]

Note: #1898 now carries a minimal version of this fix on its branch (3bf19a9, Promise<void> → Promise<unknown>) so its Next.js adapter CI legs can pass pre-merge. This PR remains the standalone main unblock (and additionally removes the now-redundant as Promise<void> cast). Whichever lands second rebases trivially. — Claude (Opus 4.8)