Kaoru0822andClaude Opus 5.5 a936303723 fix(json): name a leading byte-order mark in rejected JSON input (#1510) ...

Strict JSON file inputs reject a leading UTF-8 byte-order mark, but the
diagnostic was the parser's own message, which quotes the invisible U+FEFF
as the unexpected token: Unexpected token '', "{"invento"... is not
valid JSON. Editors such as Windows PowerShell 5.1 write that mark by
default, and nothing in the message showed it.

CLI JSON files (whole and streamed), Evidence and snapshot JSON files, and
process scenario files now report that the input begins with a UTF-8
byte-order mark and how to save it. Acceptance is unchanged.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-10 01:37:41 -07:00

..

acceptance

fix(javascript): retain returned-reference mutation uncertainty (#1471)

2026-10-10 15:46:24 +08:00

boundary

fix(json): name a leading byte-order mark in rejected JSON input (#1510)

2026-10-10 01:37:41 -07:00

composition

fix(artifacts): keep case-distinct archive names in inventory (#1480)

2026-10-10 15:21:16 +08:00

conformance

docs: align the Indonesian README with the other translations (#1512)

2026-10-10 16:26:52 +08:00

evaluation

test: exercise source test selection through Git and Vitest

2026-10-10 00:35:17 +08:00

fixtures

feat: add Hermes as a supported MCP client (#1403)

2026-10-10 16:03:25 +08:00

process-global

refactor: consolidate boundary semantics and prune redundant tests

2026-10-10 05:56:01 +08:00

support

fix(ci): scope verification and reuse native runners (#1344)

2026-10-09 18:22:03 +00:00

processOwnershipRunner.ts

test(process): retire native caches at worker teardown

2026-10-09 04:12:49 +08:00