Commit Graph
8291 Commits
Author SHA1 Message Date
Jason Chenandmorluto 55fd0ff590 fix(cli): preserve mcp doctor output choices on argument errors (#2693)
fix(cli): preserve doctor output choices on argument errors

Signed-off-by: Jason Chen <jasonhuang404505@gmail.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 10:56:53 -05:00
Arif Aliandmorluto bba3a3f0d9 fix(javascript): recover RPC link URLs declared with template literals (#2963)
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 10:56:30 -05:00
ShuaixinHuangandShuaixinHuang 644cb8243d fix(ci): expose failed test modules in portable diagnostics (#12069)
* fix(ci): expose failed test modules in portable diagnostics

* test(ci): verify failed paths render as literal text

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:54:41 -05:00
ShuaixinHuang 884fda99f0 fix(native): index only address-bearing Mach-O initializer symbols (#12070) 2026-11-18 10:53:42 -05:00
Paritosh LahreandClaude Opus 5.5 cb8096d522 fix(cutter): explain empty discovery when Cutter 2.5.0 rejects the plugin (#10310)
* fix(cutter): explain empty discovery when Cutter 2.5.0 rejects the plugin

Official Cutter 2.5.0 builds have been observed to reject Python plugins at
startup, including Cutter's own sample plugin and REA's bridge
(rizinorg/cutter#3659). No session is published, and list_cutter_sessions
returns no_live_bridge_found with nothing pointing at the Cutter release.

The list_cutter_sessions contract now says what no_live_bridge_found means
and names the observed 2.5.0 rejection. The Cutter bridge docs describe
installing the plugin, the startup log lines Cutter prints when it rejects
it, and that 2.4.1 loaded the bridge in the reported check. A minimal
independent plugin fails the same way, so the bridge itself is unchanged.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): report empty-discovery causes in the shared result

The guidance lived only in the MCP tool description, which
`rea list-cutter-sessions` never shows. The docs also assumed a known package
folder, which npx installations do not have.

The discovery result now carries limitations, owned by
cutterDiscoveryLimitations in the domain. For no_live_bridge_found they list
the causes discovery cannot tell apart, including the observed Cutter 2.5.0
Python-plugin rejection (rizinorg/cutter#3659). CLI and MCP project the same
text, and the tool description returns to its previous wording. The docs now
take the plugin from the published package of the matching version with
npm pack.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): name failed status probes among no-live causes

no_live_bridge_found also covers a published session whose status probe
fails: a stale descriptor after Cutter exited, an unresponsive bridge, or
an incompatible bridge version. The limitation named only process,
plugin-loading and directory causes. It now lists these too, and the
dead-status-endpoint test asserts that such a discovery carries it.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cutter): give the finalization discovery fixture its limitations

commandFinalizationCancellation builds a Cutter discovery through the
list_cutter_sessions output schema, which now requires limitations. CI
shard 4 failed all five final-close cases with a ZodError. The fixture
now takes the owner's empty limitations for sessions_found.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): count unanswered sessions beside found ones

When one session answered and another published session failed its status
probe, discovery returned sessions_found with no limitation. The partial
result looked complete. The client already throws for live ceiling
mismatches, so every other descriptor without a session is a failed probe.
It now passes that count to cutterDiscoveryLimitations, which reports the
unlisted sessions for sessions_found. The stale-descriptor case in
cutterBridgeRequestLimit asserts it.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): name unpublished bridge sessions among no-live causes

When Cutter loads the plugin but the bridge cannot write its session
descriptor, for example in an unwritable or full bridge directory,
_BridgeServer.run closes the socket without logging. Cutter's log then shows
the plugin as loaded, yet discovery finds nothing. The no-live limitation now
names that cause and says the bridge does not log it. The Cutter docs say to
check the bridge directory when the plugin is loaded but no session appears.

Refs #10299

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): count unreadable descriptors among unlisted sessions

The descriptor loader dropped filename-matching candidates it could not read
before listSessions counted unanswered sessions, so a found session beside a
malformed, oversized, non-private or misnamed descriptor reported no
limitation. The loader now returns its unreadable count, and the discovery
limitation owner reports it beside failed status probes for both
sessions_found and no_live_bridge_found. The no-live text keeps only the
causes that leave nothing published; published sessions are now counted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cutter): leave session existence unknown for unreadable descriptors

A filename-matching candidate the loader could not read does not establish
that any session exists: it may be malformed, misnamed or removed while
reading. The limitation now counts unreadable descriptor candidates and
says whether they describe Cutter sessions is unknown, instead of saying
their sessions are not listed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(mcp): record the list_cutter_sessions limitations in the advertised summary

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:49:22 -05:00
RRFZ afd277dabc refactor(zip): read EOCD and trailing archive fields via BinaryReader (#11918)
* refactor(zip): read EOCD and trailing archive fields via BinaryReader

* perf(domain): avoid subarray allocations in BinaryReader and prefilter EOCD scan

Check field bounds via a private helper and read 16-, 32-, and 64-bit
integers directly from BinaryReader.bytes by offset instead of slicing
via range(), and skip non-0x50 bytes before full signature comparison
in zipEndOfCentralDirectoryCandidates.

* perf(zip): scan EOCD signature candidates with Buffer.lastIndexOf

Jump directly between 4-byte EOCD signatures with Buffer.lastIndexOf
instead of probing every byte in JavaScript, preserving reverse
candidate order, earliest-offset bounds, and zero-copy Uint8Array views.

* perf(zip): bound EOCD lastIndexOf scan to the 65557-byte tail window

Slice a zero-copy tail view starting at earliest before calling
Buffer.lastIndexOf so exhausting zipEndOfCentralDirectoryCandidates on
large archives never scans bytes before the maximum comment window.
2026-11-18 10:49:14 -05:00
David Muñoz Rey 090c22720b fix(native): name the unsupported Thumb mode for an odd raw ARM entry (#10683)
A 32-bit ARM raw-binary entry such as 0x4001 was refused as not 4-byte
aligned, and the remediation only said to correct the load argument. An
odd ARM address is how a Thumb function pointer is spelled, so a caller
holding one could not tell that the real limit is the unsupported raw
Thumb mode rather than a typo.

For `arm` entries with bit 0 set, the refusal now adds that the address
can be a Thumb function pointer but raw-binary arm decodes ARM state
only, so a Thumb entry is unsupported and the entry was not adjusted. It
does not assume the caller's mode or change the entry. Even misaligned
ARM entries and all arm64 entries keep the existing text.

Validation: src/domain/rawBinary.test.ts fails on the base (the odd ARM
cases lack the note) and passes 32/32 after; check:fast passes.

Refs morluto/rea#8210
2026-11-18 10:49:04 -05:00
David Muñoz Rey 93bf4df3e4 test(inspector): spell Node discovery targets as Node reports them (#10663)
* test(inspector): spell Node discovery targets as Node reports them

The fake V8 Inspector gave Node-type targets a percent-encoded WHATWG file
URL, while Node's /json/list reports `file://` plus the raw pathname with
quotes and backslashes replaced by underscores. The product reads that
channel literally, so a TMPDIR containing a space or percent sign named a
pathname that did not exist and the target stayed unresolved: the
Inspector cancellation test and "includes targets outside the old caller
root filter" failed on unrelated assertions.

Add nodeDiscoveryTargetUrl to the fake and use it where a resolved Node
target location is asserted. The underscore case stays with
createNodeDiscoveryTempDirectory.

Validation: 69 inspector/browser/MCP/acceptance test files, 1168/1168
passing under TMPDIR spellings with an underscore, a space, a percent sign
and none; check:fast passes.

Refs morluto/rea#9996

* test(inspector): pin special-character Node discovery spellings

Review follow-up for Node discovery target URLs.

Neither caller gave nodeDiscoveryTargetUrl an explicit special-character
path, so spaces and percent signs were exercised only when TMPDIR
happened to contain them. A boundary case now lists two targets in one
discovery root. "with space %41.js" is reported literally and resolves
to its file. 'with "quote".js' is reported with underscores and stays
an unresolved, unverifiable file location.

Tests: tests/boundary/inspector/javascriptRuntimeObservation.test.ts
passes (31).

* test(inspector): spell the consolidated target listing as Node reports it

main folded the test this branch had respelled into "lists all
connectable targets on the selected endpoint across directories", which
still built its two discovery targets with pathToFileURL. Under a
temporary directory with a space or a percent sign those targets came
back unresolved and the file-location assertions failed.

Build them with nodeDiscoveryTargetUrl, as the rest of this branch does.
2026-11-18 10:48:59 -05:00
ShuaixinHuangandShuaixinHuang 932afbeec5 fix(pe): map import hints independently of names (#11817)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:47:30 -05:00
ShuaixinHuangandShuaixinHuang a7c4ee8394 fix(desktop): align exported task whitespace interpretation (#11947)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:47:22 -05:00
ShuaixinHuangandShuaixinHuang 7d357b8325 fix(desktop): preserve commas in apt source fields (#11926)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:47:14 -05:00
ShuaixinHuangandShuaixinHuang 1ab212164c fix(elf): preserve Unicode separators in kernel config strings (#11831)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:46:49 -05:00
f46b97d1ed fix(ghidra): avoid Java probes for missing installations (#11732)
* test(mcp): observe cleanup failures at their current delivery boundary

* fix(mcp): preserve workflow completion progress through delivery

* test(setup): keep the Windows Kimi profile fixture on a supported profile

The Windows-only case at `clientConfigurationEnvironment.test.ts:226` wrote
`rea_mcp_input_schema_profile: "full"`. That profile was retired: the reader
now refuses it ("REA_MCP_INPUT_SCHEMA_PROFILE accepts only \"compact\" …"),
so `configureClientConfiguration` returned `failed/readback` before writing
and the case failed on every Windows run, including main's own
`Windows capability and package lane`.

The case has no Windows dependency — it passes an explicit `configPath` and
the Kimi write dialect is the same everywhere — so it now runs on every
platform, which is what let the stale value rot unnoticed. The fixture keeps
the lowercase explicit key the case is about, with the supported value.

Verified on `main` `d6bcfc10`: the same fixture driven through
`configureClientConfiguration(..., "win32")` on this host reproduced
`{"status":"failed","reason":"readback"}` with the retired value and now
returns `{"status":"configured"}` with `compact`. The file's 75 cases pass
here (66 run, 9 platform-conditioned skips) and `check:fast` passes.

* test(ci): restore verifier and MCP contract regressions

* test(captures): assert adapter-owned input issue field names

* fix(ghidra): avoid Java probes for missing installations

---------

Co-authored-by: g0at <50488370+g1at@users.noreply.github.com>
Co-authored-by: IvenKooLab <276572622@qq.com>
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:46:44 -05:00
RRFZandmorluto 8a10fa9c00 fix(pcap): resolve tshark and capinfos on the Windows PATH (#11734)
* fix(pcap): resolve tshark and capinfos on the Windows PATH

On Windows, resolvePcapTools kept the bare names "tshark" and "capinfos"
for the launcher to search PATH/PATHEXT. The owned Windows launcher
starts only absolute paths, so it refused the bare name (Win32 87) and
every pcap operation reported "Selected tool tshark could not be
launched (ERR_REA_WINDOWS_NATIVE)", even with tshark on PATH.

Resolve a PATH selection on Windows through the shared PATH/PATHEXT
search, from absolute entries only as on POSIX, and report the same
<tool>_missing failure when no image is found.

* test(pcap): assert typed missing-tool failures

* test(pcap): clarify PATH fixture platform

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 10:38:15 -05:00
RRFZandmorluto 5aa1fc5737 fix(process): resolve Windows root-relative commands on the selected drive (#11763)
* fix(process): resolve Windows root-relative commands on the selected drive

* test(process): pin drive-less PATH entries and UNC root-relative commands

A Windows PATH entry rooted without a drive now counts as relative, so
programOnPath skips it. Pin that with a Windows case, test a
root-relative command under a UNC working directory, and say in the
relativeEntry and windowsPathCandidates docs that drive-less entries
count as relative.

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 10:23:14 -05:00
RRFZ 23adfc610f fix(process): require a drive or UNC root for selected Windows tools (#11786)
* fix(process): require a drive or UNC root for selected Windows tools

REA_ADB_PATH, REA_APKTOOL_COMMAND, REA_TSHARK_COMMAND and
REA_CAPINFOS_COMMAND must be absolute. On Windows the check used
win32.isAbsolute, which also accepts \tools\adb.exe: a path rooted on
the current drive. Such a setting names a different file depending on
REA's working drive, and the owned Windows launcher refuses it.

Add isQualifiedCallerPath to the caller-path owner, which on Windows
requires a drive root or a UNC or device root, and use it for all four
settings. POSIX keeps posix.isAbsolute.

* fix(filesystem): require a complete UNC root for a qualified Windows path

Two leading separators were treated as a UNC root, so ///tools/adb.exe,
\\\tools\adb.exe and a bare \\server passed, though win32 parses them
with a single-separator root on the current drive. Use win32's own root:
qualified only when the path is absolute and its root is longer than one
separator.

* test(process): use qualified paths for simulated Windows tools
2026-11-18 10:09:30 -05:00
David Muñoz ReyandLcokHcak fbd6fd1c4f fix(android): reject invoke coverage without site evidence (#10679)
The JADX bridge emits or removes direct_invokes and direct_invokes_exhaustive together. A protocol item carrying only the coverage flag reached trace_android_references as a reference that claimed true or false coverage over a null site list, while the coverage summary counted it as unknown. The protocol schema now rejects that combination.

Rebased onto current main from morluto/rea#2850. The companion change that removed the null default from the result schema already landed on main.

Co-authored-by: LcokHcak <268763621+LcokHcak@users.noreply.github.com>
2026-11-18 10:09:26 -05:00
RRFZ c1c9783a9e fix(contracts): omit widened regex disjunctions (#11781) 2026-11-18 10:09:21 -05:00
hhangandhhang 090d5668c8 fix(sqlite): page via declared rowid aliases (#11963)
Co-authored-by: hhang <169027046+xu91102@users.noreply.github.com>
2026-11-18 10:09:16 -05:00
ShuaixinHuangandShuaixinHuang 5fd543c59c fix(tests): reject truncated shared CLI frames at EOF (#12010)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:09:11 -05:00
ShuaixinHuangandShuaixinHuang 180e97f86f fix(audit): report GCC profile paths retained in Go build flags (#12029)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:09:07 -05:00
ShuaixinHuangandShuaixinHuang 754589d4bf fix(nuget): match the manifest relationship type exactly (#11934)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:09:02 -05:00
ShuaixinHuangandShuaixinHuang 224856bf62 fix(source-maps): reject empty comma-delimited mappings (#11970)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 23:07:25 +08:00
ShuaixinHuangandShuaixinHuang ac838a7f48 fix(artifacts): align Gradle version selectors with Java whitespace (#12019)
* fix(artifacts): classify Gradle version selectors by their grammar

* fix(artifacts): match Gradle ASCII range whitespace

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 23:07:18 +08:00
RRFZ 4c76284bf1 fix(build): apply the release patch from the dependency directory (#11768) 2026-11-18 23:06:18 +08:00
RRFZ 390969209d fix(process): classify a Windows launch of a non-image file as not executable (#11735)
A tool selection that points at a file Windows cannot start (a DLL, a
script, any non-PE file) was reported as "could not be launched
(ERR_REA_WINDOWS_NATIVE)" by the owned launcher, and as an unrecognised
EFTYPE failure by Node's spawn. POSIX reports the same mistake as
ENOEXEC: "exists but could not be executed".

Treat EFTYPE as not executable, and read the native launcher's
ERROR_BAD_EXE_FORMAT (Win32 193) as EFTYPE, the code Node's own spawn
reports for the same file. Other native codes stay unclassified.
2026-11-18 23:05:59 +08:00
ShuaixinHuang c2be327835 fix(tests): preserve child exit results after stdin EPIPE (#12045) 2026-11-18 23:05:54 +08:00
RRFZ 0adda3503c test: make registration-format and release-exposure suites pass on Windows (#10533)
The Windows-only Fx case still read mcp.rea, but a new Fx profile is written
under mcpServers. Two Fx cases assert POSIX modes or a private-directory
close that Windows never performs; they now run off Windows, beside the
existing Windows case. Two release-exposure assertions spelled paths with a
POSIX separator; one now accepts either separator and one uses the reader's
host-file/member spelling.
2026-11-18 10:05:23 -05:00
ShuaixinHuangandShuaixinHuang 2aaf76c5c1 fix(artifacts): read Maven and Gradle metadata with a UTF-8 BOM (#12009)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 10:04:54 -05:00
ShuaixinHuangandmorluto 2f6773cbc7 fix(ci): synchronize build-computer cancellation tests (#12042)
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 10:04:06 -05:00
morluto 25784cd4e7 fix(ci): refresh CLI decimal schema goldens 2026-11-18 10:02:07 -05:00
e2ccd682cb fix(native): report undecoded Objective-C category class properties (#11722)
* fix(native): report undecoded Objective-C category class properties

inspect_native_dispatch_metadata read a category's instance property
list and stopped. A category that also declares class properties kept
`decode.status: "decoded"` and `objc_properties_categories` stayed
complete, although its `_classProperties` list was never read.

When the image info declares the field and the list is present, the
category is now partial with `category_class_properties_not_decoded`
and coverage names the list field, as protocols already do for their
class property list.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* fix(native): keep a category whose class property field is unreadable

Reading the image info flags or the `_classProperties` pointer could
throw inside the category decode, which dropped the whole row and its
already decoded name, methods, protocols and properties.

Both reads now fail into a `category_class_properties_unreadable`
issue at the failing field, and the category stays as a partial row.
Same-named image infos are read together instead of taking the first.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* fix(native): report a truncated image info instead of reading it as absent

A present `__objc_imageinfo` section shorter than its 8 bytes was filtered
out, so a category in that image stayed decoded although whether its record
ends in `_classProperties` is unknown. The category now keeps its decoded
facts and is partial with `category_class_properties_unreadable`, located at
the image info.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* fix(native): resolve the category class property field and read image flags once

A bound `_classProperties` field read as zero and counted as a null list,
and so did a zero whose pointer fixups are unknown. The field is now resolved
through its fixup: a bind is a present list, and an unknown zero keeps the
category partial with `category_class_properties_unreadable`.

The image info declaration is read once per decode instead of once per
category; an image info that declares the field decides.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 09:44:09 -05:00
ShuaixinHuangandShuaixinHuang 34f7d2131c fix(javascript): preserve loader conditions across application evidence (#12023)
* fix(javascript): honor loader semantics for BOM hashbangs

* fix(javascript): retain conditional BOM hashbang imports

* fix(javascript): share conditional hashbang recovery

* fix(javascript): recover suffix-only source imports

* fix(javascript): retain conditional CommonJS hashbang imports

* fix(javascript): preserve conditional hashbang dependency evidence

* fix(javascript): preserve ambiguous dotfile and worker evidence

* fix(javascript): qualify semantic evidence with source loader conditions

* fix(javascript): qualify all source-backed application evidence

* test(javascript): identify imports by their projected kind

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 09:42:46 -05:00
ShuaixinHuangandShuaixinHuang 919531c7c1 fix(source-maps): retain all candidates at shared section boundaries (#12026)
* fix(source-maps): retain mappings at shared section boundaries

* docs(source-maps): align boundary and decoder guidance

* test(source-maps): type named browser source-map leaves

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 09:42:28 -05:00
ShuaixinHuangandShuaixinHuang 0ba3b6049d fix(audit): split ELF linker search lists at every colon (#12035)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 09:42:13 -05:00
ShuaixinHuang 32b2020571 fix(elf): recover pointers from Android APS2 relocation tables (#12047) 2026-11-18 09:42:00 -05:00
ShuaixinHuangandShuaixinHuang c47442a2eb fix(desktop): read BOM-marked UTF-16 in state and task views (#12052)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 09:41:35 -05:00
Lewis WangandClaude Fable 5.2 1868d04ef9 fix(native): list Swift types recorded in __swift5_types2 (#11721)
* fix(native): list Swift types recorded in __swift5_types2

inspect_native_dispatch_metadata read nominal type records only from
`__swift5_types`. Swift records noncopyable types in `__swift5_types2`
with the same record layout, so those types were missing from
`swift_decls` while `swift_declarations` coverage stayed complete.

Both sections are now read, and each declaration's evidence names the
section its record came from.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

* test(native): assert complete Swift declarations across both type sections

The regression fixture left each descriptor's parent unset, so both
declarations were partial and the test asserted only the examined
count. The descriptors now share a module context, and the test asserts
decoded rows, their module and qualified names, and complete coverage.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-18 22:33:36 +08:00
RRFZ 146b4f1202 fix(tests): preload budget workers through portable file URLs (#11764) 2026-11-18 22:33:31 +08:00
RRFZ 7b02fec30b fix(cli): reuse decoded inline JSON during admission (#11790) 2026-11-18 22:33:07 +08:00
morluto c928f8aed3 test(desktop): consolidate queued action and progress coverage (#12057)
* test(desktop): consolidate queued action and progress coverage

* test(desktop): release reset when its first barrier fails
2026-11-18 09:32:42 -05:00
Phonandmorluto 6c3e9e0847 fix(tests): treat zombies as stopped in process liveness checks (#11819) (#12034)
fix(tests): treat zombies as stopped in process liveness checks

Fixes #11819.

Killed descendants waiting to be reaped read as alive to
process.kill(pid, 0), so three boundary tests fail in containers
whose PID 1 does not reap orphans. The liveness checks now treat a
zombie as stopped, using the existing observePosixProcess helper
(ps -o stat=, comm-safe) with two small wrappers,
processHasStopped / processGroupHasStopped, swapped in at the three
call sites. Test-only change; production code untouched.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 22:25:45 +08:00
RRFZ bb6e307de5 fix(har): preserve failed Playwright requests with unavailable timings (#11758) 2026-11-18 22:23:53 +08:00
RRFZ ce9635bcb4 fix(windows): report bytes appended after a Shell Link TerminalBlock (#11745)
The ExtraData TerminalBlock ends a Shell Link, but bytes after it were
never examined or mentioned, and coverage stayed complete. Appending a
payload to a shortcut is a common way to hide one.

Record a malformed_structure issue at the first appended byte, with the
byte count, so coverage becomes partial. Shortcuts that end at the
TerminalBlock are unchanged.
2026-11-18 09:23:48 -05:00
RRFZ 9c1e98f1cd fix(nuget): read packaging parts and dependency groups as NuGet does (#11845)
Members under package/ are OPC packaging parts, like _rels/ and
[Content_Types].xml; nuget pack writes the core properties .psmdcp there.

Dependencies come from every <dependencies> element. When any <group>
exists, ungrouped <dependency> elements are omitted with a limitation that
counts them, because NuGet's restore-time NuspecReader ignores them.
2026-11-18 09:23:27 -05:00
2SinceJuly 002716a998 fix(desktop): point the packing blocker at the moved guide (#10255)
The desktop-build archive-packing recovery message still sends readers
to docs/installation.md#run-rea-from-a-checkout. The documentation move
put that section in docs/getting-started/installation.md, so the
repository pointer resolved to no file.

Point at the existing section instead; the public VitePress route is
unchanged.
2026-11-18 09:23:16 -05:00
morluto d96f0380aa test(cli): verify the advertised outline-depth range (#12061) 2026-11-18 09:15:24 -05:00
Nianze Wuandmorluto a42f96d0bd fix(cli): preserve JSON version reports with timing flags (#8871)
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 09:12:01 -05:00
morluto da7982e105 fix(cli): preserve ADB extra schema in the product catalog (#12060) 2026-11-18 09:11:32 -05:00
IvenKoo 80f533da8a fix(cli): bound advertised decimal-token schemas by the domain range (#9808)
`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
2026-11-18 09:11:20 -05:00