`cliDecimalField` published the domain range on the integer branch and only
the fixed `^[0-9]+$` guard on the decimal-token branch, and JSON Schema
bounds do not constrain strings. A client validating raw argv text against
`--schema` therefore admitted out-of-range tokens such as `--row-limit=0` or
`--block-size=255` that the parser rejects with `VALIDATION_ERROR`.
Publish the domain range on the token branch through the schema-constraint
owner, keeping the CLI's decimal leading-zero convention and the existing
parser diagnostics: the declaration is metadata, so accepted values and
`too_small`/`too_big` messages are unchanged. Non-range refinements such as
the power-of-two entropy block size stay parser-only, and an open-ended
domain still publishes its floor. The getting-started guide states the same
contract.
Fixes#9348
* fix(zip): account 64-bit data descriptors that MSIX packages write
MSIX and APPX packages defer each member's sizes to a signed data
descriptor with 8-byte sizes, but neither header carries a ZIP64 extra
field. The member-region account only tried the width the directory
record implied, so every descriptor counted as unaccounted bytes and the
listing's coverage became unknown.
Try both size widths, the record's own first. A layout still has to
match the recorded CRC and both sizes.
* fix(zip): account an empty member's 64-bit descriptor
An empty member's zero CRC and sizes also match the first 16 bytes of a
signed 24-byte descriptor read as the 32-bit layout, leaving 8 bytes
unaccounted. When several layouts match, prefer the one that ends
exactly at the next accounted byte.
inspect_elf_notes and inspect_elf_debug_link now examine up to 128 note
entries by default instead of 32; the ceiling stays 256. Ubuntu 26.04's
libc.so.6 is examined as 85 entries, 79 of them SystemTap probes, and both
tools refused it with default arguments.
The .nuspec, its OPC relationships and the Maven POM now parse with
lineEndings normalize, as XML 1.0 section 2.11 and the NuGet and Maven
readers do. Text from CRLF files no longer keeps carriage returns.
Share observations across redirect response and fragment cases while retaining the wire checks for caller cancellation, final URL identity, and ordered lifecycle events.
Preserve exact DOM and frame identity, SVG and XML URL handling, accessibility and resource completeness, and caller-visible comparison results in shared fixtures.
Use shared captures to verify discovery, document identity, screenshot recovery, and source map evidence and cleanup across varied responses. Remove redundant tests and unused fixture controls.