fix(lint): unbreak main — node:assert/strict → node:assert in bytes-scan-crash test

[kriszyp]

Summary

integrationTests/resources/bytes-scan-crash.test.ts:26 imports { ok } from 'node:assert/strict', which the no-restricted-imports eslint rule forbids. That left lint:required (runLinter) red on main — 1 problem (1 error) — which surfaces on every downstream PR's CI.

The import was added in 7945918 (fix(table): reject bare-array roots…). ok is identical when imported from node:assert, which is the form all sibling integration tests already use.

-import { ok } from 'node:assert/strict';
+import { ok } from 'node:assert';

Test plan

• npm run lint:required passes locally (was exit 1, now exit 0)

🤖 Generated with Claude Code

[claude]

Reviewed; no blockers found.

[gemini-code-assist]

Code Review

This pull request updates the import in integrationTests/resources/bytes-scan-crash.test.ts from node:assert/strict to node:assert. There are no review comments, and I have no feedback to provide.

[Ethan-Arrowood]

Fine with this to unblock main, but I'm generally not okay with the switch from node:assert/strict to node:assert. But that is a separate conversation.

_{sent with Claude Fable 5}