Commit Graph
5333 Commits
Author SHA1 Message Date
ShuaixinHuangandShuaixinHuang f4efc293dd fix(ci): retry GitHub file reads after gateway timeouts (#11987)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 14:58:02 -05:00
ShuaixinHuangandShuaixinHuang e39a53d5cd fix(windows): preserve opaque ANSI shortcut path identity (#11923)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 14:56:47 -05:00
ShuaixinHuangandShuaixinHuang c4f9ead498 fix(verify): honor an explicit conformance source root (#11943)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 14:56:35 -05:00
David Muñoz ReyandDayan Kijege 53977802b3 test(process): count zombie descendants as stopped in cleanup checks (#12091)
Where PID 1 does not reap orphans promptly, a killed descendant stays a zombie for a while. Signal 0 still reaches a zombie, and a raw process table still lists it, so four boundary tests decided a stopped process was alive although cleanup had worked.

The stop assertions in artifactVerifierCleanupOwner and desktopBuildOwnedCommand now use processHasStopped. The run-token sweep in ownedCommand reads the product's liveProcesses view, which drops zombie rows. The testing guide says to assert a stop this way and not with signal 0.

Ported onto current main from morluto/rea#11837. The helper and the first eight cases landed in morluto/rea#12034, so this keeps the four that remained.

Co-authored-by: Dayan Kijege <dayanusa7@gmail.com>
2026-11-18 14:48:37 -05:00
ShuaixinHuang 75482a9ef9 fix(ota): merge partition info without discarding integrity claims (#11836) 2026-11-18 14:47:46 -05:00
ShuaixinHuang 004c43e32a fix(maven): preserve qualified property keys in metadata (#11860)
fix(maven): preserve qualified property keys
2026-11-18 14:47:42 -05:00
mengzhe ganandmorluto 82e16b4dda fix(setup): write the recommended tool call timeout into dsh registrations (#4043)
* fix(setup): write the recommended tool call timeout into dsh registrations

rea setup --client dsh wrote registrations without toolCallTimeoutMs, so
DeepSeek Harness applied its 60-second default while a native provider
startup alone can exceed it. Setup now derives the deadline from the same
provider allowance plus operation headroom used for Kimi and Codex,
preserves a positive caller-selected value, and doctor reports a
registration without a usable timeout as stale.

ProviderRequestBudgetResolver declares an optional budgetSettings read
set, so the fail-closed budget gate rejects unresolved Cordis expressions
only for settings the derivation may read plus the timeout inputs; an
unrelated expression such as GHIDRA_INSTALL_DIR still refreshes, and an
expression in REA_IDA_MCP_CONFIG fails closed.

* test(setup): record the dsh tool call deadline in the NUL repair fixture

The NUL refusal scenario rewrites a valid dsh registration and expects
doctor to report it healthy. That fixture omitted toolCallTimeoutMs,
which doctor now reports stale, so the repaired registration records the
deadline a current dsh registration carries.

* test(setup): separate dsh timeout repair coverage

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 14:31:34 -05:00
morluto 30006cfd24 test: align Cutter and loader fixtures with current contracts (#12088)
* test(cutter): preserve discovery limitations in authority fixture

* test(javascript): distinguish wrapper collisions from syntax recovery
2026-11-18 13:23:24 -05:00
Ali RazaandClaude Opus 5.5 f64433c93e fix(sqlite): refuse one-byte files instead of reporting an empty schema (#8727)
* fix(sqlite): refuse one-byte files instead of reporting an empty schema

* test(sqlite): assert refusal facts instead of the full error sentence

The one-byte and corrupt-input acceptance tests froze the sentence that
SqliteDatabaseWorkerExecution builds from fixed wording, SQLite's
diagnostic and the selected path. Share one helper that keeps the code,
issue path, reason and single-issue shape exact, and checks the
diagnostic and selected path separately, so rewording the sentence no
longer breaks either regression.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 13:11:23 -05:00
ShuaixinHuang 5fd6c0db71 fix(desktop): preserve env option boundaries in launch commands (#12033) 2026-11-18 13:07:56 -05:00
2SinceJuly b99e7737de fix(evidence): derive default authority from subject binding (#10321)
* fix(evidence): derive default authority from subject binding

evidenceEnvelopeForAdmission defaulted a missing authority to shipped-artifact
for every observation, including ones with no artifact subject and ones
produced by a live debugger session. An unbound record therefore claimed
authority over an artifact it cannot name, and live GDB, Rizin and Cutter
observations could never qualify a live-observation contract because that
contract accepts only controlled-replay or external-service Evidence.

Default to analyst-inference when no subject is bound and keep
shipped-artifact when one is, so the default matches what the record can
actually support. Declare controlled-replay at the eight live debugger
observation sites (GDB 6, Rizin 1, Cutter 1) so those records describe the
controlled replay they performed and satisfy the documented contract.

* fix(gdb): label retained process-exit observations as controlled replay

The GDB command process-exit branch was the only unbound retention path that
named no authority, so this branch's new default derived it as
analyst-inference. That label cannot support the live-observation contract,
and every sibling path (timeout, cancellation, protocol failure, startup)
already states controlled-replay.

The authority and the unavailable-subject reason now live beside the
provider identity so the retention paths read them from one place instead
of repeating the literals and drifting apart.

* style(evidence): apply repository formatting

* fix(cutter): classify command observations as external-service

The bridge drives the documented already-running Cutter GUI, whose
document state REA neither owns nor resets, so its command
observations claim no controlled replay. Label them external-service
like the comparable IDA and Frida bridge evidence: live-observation
obligations still accept it, while controlled-replay-only verifier
contracts and bundle replay scenarios no longer include these
observations.

* fix(adb): keep device observations at external-service authority

The admission default now derives authority from the subject, so a subjectless ADB observation fell to analyst-inference. A device is a service REA attaches to rather than drives, so the observation supports external-service and must stay eligible for live-observation contracts.

Carry an explicit authority through AnalysisObservation so a producer that knows its own authority can name it, and set it for every ADB operation.

* fix(adb): keep retained observations at external-service authority

The admission default derives authority from the subject, and a subjectless
observation falls to analyst-inference. createAnalysisExecution never carried
an authority field, so every observation the ADB adapter built through it was
committed at the subject-derived default instead of the service's.

Name the authority once in the domain model, stamp it on every successful
execution at the adapter boundary, and route the cleanup-failure and
cancellation-retention sites through one helper. Open the execution options
field so other providers can name their own authority.

Verified: a push whose device digest does not match now retains its receipt at
external-service; removing the stamp fails that assertion. check:fast passes.

* fix(adb): keep the retained verification receipt at device authority

The verificationFailed branch built its retained receipt with createEvidence
directly, so the admission default derived the authority from a subjectless
target and labelled an observed push as analyst-inference. Pass the device
authority through the same way the neighbouring digest-mismatch partial does,
so the receipt can still support live-observation verification.

* style(adb): apply oxfmt formatting to the authority fix

The previous commit wrapped two expressions that oxfmt keeps on one line, so
npm run format:check failed on Static checks.
2026-11-18 13:06:25 -05:00
morluto 31aaec6b4f fix: restore PE release scanning and CommonJS test coverage (#12083)
* fix(artifacts): preserve unresolved PE debug coverage

* test(javascript): use valid CommonJS loader shadowing
2026-11-18 12:54:53 -05:00
JoshandJosh ad82b61641 fix(inventory): validate PE headers before classification (#11691)
* fix(inventory): validate PE headers before classification

* fix(inventory): retain declared PE record windows

---------

Co-authored-by: Josh <joshuakrishna21@gmail.com>
2026-11-18 12:35:59 -05:00
ShuaixinHuangandmorluto f7849cad3f fix(elf): require sizes for declared Android RELR tables (#12067)
* fix(elf): require sizes for declared Android RELR tables

* test(android): allow JNI relocation cases without RELR aliases

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 11:35:39 -05:00
Oke Iyanuoluwa Enochandmorluto a43a1b6453 fix(setup): name an unresolved client location in the picker (#11699)
* fix(setup): name an unresolved client location in the picker

When a client's configuration location cannot be resolved, such as
Claude Desktop with migrated Claude-Data storage, setup refuses to write
it and the user has to register REA by hand. The client picker still
said "Existing configuration needs repair before setup" (6.9.0, where
the state is invalid) or "Detected · choose to configure" (main, where
#10698 records it as unknown), and neither is true.

Show "Configuration location unresolved · register REA manually" for
any client with a location error, and keep the repair hint for
configurations that are actually malformed.

Fixes #11697

* test(setup): type picker fixtures as SetupClientState

The journey fixtures used array paths and a marker field that setup
never sends, and omitted registrationProfile. They now satisfy the
production contract so the type checker rejects drift.

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 11:21:49 -05:00
IvenKooandmorluto ec17f39e82 fix(process): keep the Darwin helper exit cleanup from crashing the host (#11714)
fix(process): keep the Darwin helper's exit cleanup from crashing the host

When the macOS ownership helper root cannot be removed while the process
exits — descriptor exhaustion is the recorded case — `cleanupAtExit` let
`rmSync` throw from a `process.once("exit")` listener. Node reports that as
an uncaught error, so a successful command exits 1 and prints a stack for a
directory nobody can retry.

Remove the root best-effort at exit and name the retained root once through a
guarded synchronous write: Node cannot drain a queued stderr chunk from an
exit listener, so the warning uses `writeSync(2, ...)` and swallows a failed
report. The root's normal cleanup path, its retained-cleanup error and every
caller's classification are unchanged; only the exit-time failure stops
changing the exit status.

Verified: `src/process/DarwinHelperExitCleanup.test.ts` asserts the root is
gone after a successful removal with no report, and that a root the process
cannot remove is retained, named once, and does not throw (2 tests). The
permission case is skipped for root and Windows, where permissions do not
prevent removal. `check:fast` passes.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 11:18:57 -05:00
ShuaixinHuangandmorluto 475250ac52 fix(javascript): apply observed loader grammar before analysis (#12066)
* fix(javascript): apply observed loader grammar before analysis

* fix(javascript): retain grammar errors in mixed loader syntax

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 11:15:03 -05:00
ShuaixinHuang c0ad2c1a22 fix(desktop): preserve distinct JSON record selector identities (#12072) 2026-11-18 11:03:20 -05:00
sunfleeting f93a8db72d fix(cli): use canonical option flags in llms manifests (#11928)
The --llms-full manifest and discovery table rendered raw object keys
(--blockSize), which disagreed with command help (--block-size). Reuse
optionFlagName so manifests emit the same canonical flags as help, and
update the two CLI parity goldens. Adds a boundary test asserting both
surfaces agree on canonical flag names.
2026-11-18 10:57:01 -05:00
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
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 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
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
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
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 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
ShuaixinHuang c2be327835 fix(tests): preserve child exit results after stdin EPIPE (#12045) 2026-11-18 23:05:54 +08: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
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
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
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
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
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
RRFZ 41cf9654da fix(setup): honor retained Kilo activation during uninstall (#11795) 2026-11-18 09:11:08 -05:00
fceb4693fc fix(cli): admit activity extras with the runtime contract (#10289)
Discovery accepted any nonempty --extra string, so start-adb-activity advertised inputs the activity contract rejects.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 09:05:26 -05:00