* test: own temporary directories through createTestTempDirectory in remaining tests/
Give per-test directories in the remaining tests/ suites to
createTestTempDirectory so onTestFinished removes them through
removeTestWorkspace. Keep suite-scoped roots and child-process directories
whose removal is the assertion.
* test: drop empty cleanup callbacks and keep the capture skip reason visible
Remove the no-op withVerifierCleanup steps left after directory removal
moved to createTestTempDirectory. Put the native capture skip explanation
in the Linux sample test name, because it.skipIf only tests truthiness.
Co-authored-by: morluto <morluto@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: morluto <morluto@users.noreply.github.com>
* fix(native): record inspected plist bytes and refuse files outside the bundle
An open app session keeps the executable as the Evidence subject for
inspect_plist, same as the other bundle-resource tools, but the result had
no digest of the plist bytes and any absolute path was sealed under that
subject. Record source_sha256 for the bytes read, and refuse a selection
that resolves outside the opened bundle.
Fixes#9479
* fix(native)!: scope plist selection to the opened bundle
BREAKING CHANGE: To inspect a plist outside an opened app bundle or resource root, open the plist as a separate target.
* fix(native): report plist snapshot filesystem effects
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
* test(apktool): give Windows a drive-rooted authored launcher
The apktool unit and CLI boundary tests configure REA_APKTOOL_COMMAND
as /authored/apktool, /opt/apktool/apktool or /nonexistent/apktool.
On win32 hosts REA admits a configured launcher only when it is drive-
or UNC-rooted, so 17 cases there failed with the absolute-path refusal
before reaching the behavior they test. On Windows they now use the
same paths under C:\; other hosts keep the original strings.
* test(adb): give Windows a drive-rooted missing adb in the CLI refusals
The two "/nonexistent/adb names the host requirement" cases hit the
same win32 absolute-path refusal as the apktool launcher cases before
reaching the not-found check. On Windows they now use C:\nonexistent\adb.
* fix(javascript): retain array-pattern iterator close effects
* fix(javascript): bound array-pattern close exposure
* fix(javascript): follow stored array elements at iterator close
* fix(javascript): retain iterator closes before array rest
* fix(javascript): retain proven property presence at reads
The read-time IR and projection boundary builds on the destructuring work in #7716. This change adds an indexed own-slot proof and uses it for ordinary member reads as well.
Co-authored-by: SII-YDD <38822679+SII-YDD@users.noreply.github.com>
* fix(javascript): retain destructuring proof in read order
---------
Co-authored-by: SII-YDD <38822679+SII-YDD@users.noreply.github.com>
* fix(node-sea): bound duplicate blob verification work
* 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
* test(ghidra): drop duplicate absent-installation coverage
Merging main reapplied the #11732 case beside the copy already on main.
Co-authored-by: morluto <morluto@users.noreply.github.com>
* test(node-sea): assert duplicate-blob refusal without stdout prose
The CLI coverage already checks the truncated code and limit details.
Co-authored-by: morluto <morluto@users.noreply.github.com>
---------
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
Co-authored-by: g0at <50488370+g1at@users.noreply.github.com>
Co-authored-by: IvenKooLab <276572622@qq.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: morluto <morluto@users.noreply.github.com>
The XML plist reader replaced every literal CR and CRLF with LF before
parsing. CoreFoundation keeps them, so REA reported a different string than
plutil for the same file, and two keys that differ only in their line ending
collapsed into one repeated key.
The document is now parsed as written. Source spans for integer, real, date
and data literals already count CR, CRLF and LF as one line break each.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>