DeryFerd 499ac18011 fix(web): reject NUL bytes in web tool local path inputs ...

Four web tools accepted caller-selected local paths as plain strings, so
a NUL byte passed contract validation and reached filesystem calls. The
services only checked isAbsolute, and isAbsolute admits a NUL, so the
failure surfaced later as a raw ERR_INVALID_ARG_VALUE instead of a named
input constraint. Every other local-input tool already refuses NUL through
the shared local-path schema, and the existing OS-invalid-local-input
harness covers those but not these web tools.

inspect_web_network_capture.capture_path, export_web_scripts.capture_path
and output_directory, trace_web_source_location.manifest_path and
source_map.path, and trace_web_module_imports.manifest_path and
import_map.path now use localPathStringSchema. Each field already required
a nonempty string, so the advertised pattern and minLength stay the same
and only the NUL refusal is added.

Validation: a new schema test rejects NUL in all seven fields while
accepting ordinary absolute paths; the four tools are added to the
OS-invalid-local-input harness and reject NUL through the real advertised
MCP contracts; typecheck, oxlint, oxfmt, and toolSchemaValidity with a
regenerated catalog. Two webScriptExport boundary cases fail identically
with and without this change on this Windows host (symlink EPERM and
private-runtime-root authority), so they are environmental.

2026-10-11 23:32:52 +07:00

..

historicalCaptureResources.test.ts

fix(bun): report the real runtime and enforce worker memory budgets on Windows (#1730)

2026-10-11 19:20:00 +08:00

inspectorLifecycle.test.ts

fix(mcp): deliver typed errors without invalid structured output (#1277)

2026-10-09 13:54:32 +00:00

localToolContracts.test.ts

fix(web): reject NUL bytes in web tool local path inputs

2026-10-11 23:32:52 +07:00