State the second pinned layout, its word table and how admission reads
the payload length for each layout. Record that the six-word roles come
from the V8 sources and that runtime compatibility with a V8 8.8 through
11.7 producer remains unverified.
No V8 8.8 through 11.7 producer runs in the test environment, so the
fixture is synthetic, as it already is for the narrow header: a real
cache without its build-constant word and its alignment word, which is
the container those releases define.
Cover the admitted layout through the parser and the public CLI, the
bit 31 module flag, a truncated six-word container, a container that
fits both layouts, and the word-table rule for a 24-byte header. The
short-header case now also covers the new 24-byte minimum.
The CLI case is the recorded lifecycle coverage of the provider, so its
new title is updated there as well.
The reader pinned the seven-word header that V8 11.8 and later write and
took the payload length from the word at 0x14. V8 8.8 through 11.7,
which Node 16 through 20 embed, define six words: there is no read-only
snapshot checksum word, the payload length is the word at 0x10 and the
header is 24 bytes on both pointer widths. For such a container the word
at 0x14 is the payload checksum, so a complete cache was refused as
truncated or corrupt.
Admit the six-word layout when the word at 0x10 reaches the end of the
file from a 24-byte header, and report its six words. A container that
fits both layouts is refused as ambiguous. The six-word roles come from
the V8 sources of those releases, so only the magic and the
payload-length relation are reported as confirmed, and the result states
that the layout was not measured against one of their producers.
A container that fits neither layout is no longer described as certainly
truncated or corrupt, since an unadmitted header has the same effect.
`file -b` reports `data` for an XML plist containing a control character
or NUL byte, which CoreFoundation still reads. plistSourceFormat only
probed the source for markup when `file` reported text, so these sources
were labelled `unknown` and skipped REA's XML reader. When that reader
would have refused them, the result also lacked the limitation that says
the value came from plutil's conversion. Two plists shipped with macOS
27.2.1 are affected.
Probe the source prefix for any description that does not name binary,
XML or JSON. Such XML now takes the same route as XML that `file`
recognizes: REA's reader decodes it directly, or #12251's plutil fallback
records REA's refusal reason. OpenStep and other non-markup sources stay
`unknown`.
dyld treats an image as restricted only when a __RESTRICT segment holds a
section named __restrict. inspect_binary_hardening reported restrict_segment
enabled for any segment named __RESTRICT, so a binary linked with
`-sectcreate __RESTRICT __other` was reported restricted although dyld still
honours DYLD_* variables for it.
The segment reader that already walks every section header now also returns
the first __restrict section. The row is enabled only for that section and
points at its name; a __RESTRICT segment without it is disabled with a basis
that names the missing section and points at the segment name.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
OpenPGP packet headers read their one-, two- and four-byte lengths with
raw Buffer reads after the header-width checks. Read them through an
openpgp BinaryReader. This was the last counted raw numeric read, so the
raw-buffer-read baseline is removed and the guard now refuses any new
copy outright. The CI change-scope test names another baseline file as
its static-only path.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
BMPString and UniversalString decoding read code units with raw Buffer
reads after their length-multiple checks. Read them through the
pe-certificate-table BinaryReader instead.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The fixed-string custom-attribute prolog and the embedded resource length
were raw Buffer reads after their length and directory checks. Read them
with the managed BinaryReader formats the other metadata readers use.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The Objective-C method and Swift relative-pointer decoders read 32-bit
displacements straight from the image bytes, beside the checked u32 and
pointer readers. The shared dispatch readers now provide i32 through the
image BinaryReader and both facets use it, so they no longer take the raw
image bytes.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The build-version platform and tool count were read through a local
DataView after the command-size check. Read them with machoWordReader,
as the other load-command decoders do, and drop the now-unused viewOf.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
readGnuPropertyWords decoded property type, size and feature words with
endian-selected raw Buffer reads. Every read already sits behind the
record length checks, so the shared reader returns the same values.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
A binary plist UID projects as `{ UID: n }` and the XML convention as
`{ CF$UID: n }`, so the structural check accepted a UID-valued $top as the
roots dictionary. A plist naming another archiver with such a $top was then
decoded with an invented root named after the UID key. The kind test now
also requires that $top is not a UID. NSKeyedArchiver archives keep their
existing $top handling.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keyed archives may now name another archiver, so the name is source
metadata a caller needs: a SceneKit scene says SCNKeyedArchiver. The
keyed-archive result gains `archiver`, the declared `$archiver` string, and
the inspect_keyed_archive contract describes archives written by
NSKeyedArchiver or a subclass archiver such as SCNKeyedArchiver instead of
NSKeyedArchiver plists only.
The reviewed golden graph adds `"archiver": "NSKeyedArchiver"` for its
capture; only its provenance digest changes, and the captured XML does not.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Foundation's NSKeyedUnarchiver decodes a keyed archive whatever its
$archiver names. SceneKit writes .scn scenes with SCNKeyedArchiver, so
inspect_keyed_archive refused system and third-party scenes such as Audio
MIDI Setup's SpeakerRoom.scn as "not an NSKeyedArchiver archive" and pointed
the caller at inspect_plist.
An archive named NSKeyedArchiver keeps its current handling, including
format failures for a damaged table. Another string archiver name is a keyed
archive when the plist also has an $objects table and $top roots; without
them it stays an ordinary property list with the inspect_plist workflow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(artifacts): keep a ZIP inventory when one member uses an unsupported compression method
zip.js refuses a member whose compression method it has no codec for, such
as bzip2 (12) or LZMA (14), before reading its data. typedZipFailure turned
that refusal into an archive-level unavailable failure, so inventory_artifact,
inspect_artifact and compare_artifacts rejected the whole archive and never
listed or hashed its readable members. unzip and bsdtar list them all.
A refusal raised while reading one member is now ArtifactEntryContentUnavailable,
the per-member failure the inventory scan already records, as UnityFS members
with unsupported compression do. The member keeps its occurrence with an
unavailable hash and a limitation naming the method, siblings are hashed, and
coverage is unknown. Extraction of that member is still refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(artifacts): keep ZIP entry coverage complete for an unreadable member codec
The central directory still lists every entry when one member's compression
method is unsupported; only that member's content is unreadable. Recording an
unknown traversal made inventory coverage, whose scope is container entries,
claim that entries might be missing. Drop the traversal override, as the
encrypted-member path already does, and let the occurrence limitation carry
the content gap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Chromium DevTools writes serverIPAddress from NetworkRequest.remoteAddress(),
which starts as "" and stays empty when a request has no remote endpoint,
such as a refused connection, an aborted request or an internal redirect.
har-schema requires an IPv4 or IPv6 value, so inspect_web_network_capture
refused the whole export at the first such entry.
For the declared WebInspector 537.36 profile, an empty serverIPAddress is
omitted from the validation copy only, as bracketed IPv6 already is. Reported
Evidence keeps the empty value, and the record gains a limitation that the
server address is unknown. Other producers' empty addresses still fail
validation.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The key reader stripped each line with JavaScript's trimStart(), which also
removes Unicode spaces such as U+00A0 and U+3000. GLib skips only
g_ascii_isspace, so it keeps those bytes inside the key and the record never
matches Name= or Hidden=.
The drift had a safety direction: a line indented with U+00A0 and reading
Hidden=true was accepted as a hidden override by REA but never by the desktop
environment, so findHiddenDesktopEntry() claimed a deletion that GLib would not
honour. #12708 closed this for group headers by validating the captured padding
against GLib's ASCII set; the blank-line, comment and key checks still used the
Unicode-aware trim.
I now strip only [ \t\f\r] before deciding whether a line is blank, a comment
or a key, and hand that same string to the record matcher. ASCII indentation
still parses as before. The inventory test covers the refusal when a hidden
override carries the padding, and the domain tests cover the three Unicode
spaces for keys, blank lines and comments.
The image and publisher cleanup retry built its composite and bound the
parts by hand; providerCleanupErrorFromFailures builds the same composite.
It names close_binary, the ProviderCleanupError default that the parts
and the previous composite used.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
ArtifactAnalysisResources built its multi-failure cleanup composite and
bound the parts by hand; providerCleanupErrorFromFailures builds the same
composite with the existing per-part diagnostics.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The resolver retry built a multi-marker ProviderCleanupError and bound
the markers by hand; providerCleanupErrorFromFailures builds the same
composite, including the distinct resource list.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
V8InspectorProvider built its multi-failure cleanup composite by hand and
bound the parts with bindCleanupDependencies. providerCleanupErrorFromFailures
builds the same composite: resources, reason, operation, aggregate cause
and release tracking.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
Parts of one cleanup composite can share a resource, such as a common
runtime root. Callers deduplicated the list by hand before composing;
normalize it once in the owner so they can use it directly.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The desktop state-reader close collects up to three failures (artifact
scope, SQLite service, and the export worker retry), but composed only
the first two with analysisErrorWithCleanupFailure and bound the rest by
hand. The third failure's reason never reached the caller. Fold the
failures through analysisErrorWithCleanupDependencies so each keeps its
reason and owner; two failures produce the same composite as before.
Refs #11859
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The completed-abort-reclassification pattern matched any `.ok && …aborted`,
including `!outcome.ok && signal?.aborted`, which attaches a secondary
cancellation to an already failed primary and reclassifies nothing. Move
the pattern to completed-abort-guard.mjs, where the receiver chain
(member, optional, private, element and call segments) must start the
check, and cover positive and negated forms in tests.
DesktopApplicationState and FridaInstrumentationService leave the
baseline.
Fixes#11920
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
A fresh CLI Ghidra session discards an annotation edit when the command
exits, which the help did not say. The returned Evidence and the MCP
contract already describe the lifetime; the help now names the
checkpoint setting and the MCP alternative.
Fixes#8242
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The compare_wasm_interfaces guidance sat at the end of the PE/ELF export
section, where an agent comparing native exports would read an
inapplicable follow-up. Regenerate the Cursor plugin copy.
Fixes#8334
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
npm ci and npm run build:cached leave the Windows addon and manifest
unbuilt; point checkout readers at the contributor guide's extra step.
Fixes#10317
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
DOCTOR_PROVIDER_IDS accepts desktop_build alongside the five engines,
but the CLI guide implied that only engines are accepted.
Fixes#10251
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
The setup summary still said setup pins package-runner registrations to
the installed version. Setup records the absolute runtime and entry
script instead, as the guide's MCP Registry section already explains.
Fixes#10252
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>