Commit Graph
8396 Commits
Author SHA1 Message Date
morluto 2b7d54257f fix(unityfs): share bounded header probing with desktop inspection (#12169) 2026-11-19 03:34:19 +00:00
morlutoandwunianze666-netizen 3d313b56bc fix(zip): share desktop and APK framing and preserve bounded ZIP64 views (#12157)
* fix(desktop): reject split ZIP volume metadata

Refs #12137

* refactor(zip): read Zip64 disk fields through BinaryReader

* fix(desktop): validate ZIP extra fields before selection

Refs #12146

* fix(desktop): keep bounded ZIP pairing compatible with Python 3.9

* fix(desktop): retain exact counts in bounded Zip64 views

* fix(desktop): follow the declared Zip64 directory frame

* fix(desktop): recognize empty ZIP state views (#12163)

* fix(desktop): recognize empty ZIP state views

(cherry picked from commit 263b25bd34)

* fix(desktop): reuse empty ZIP admission for wrapped documents

* refactor(zip): share the local-header signature with desktop state

---------

Co-authored-by: wunianze666-netizen <wunianze666@gmail.com>

* test(zip): inherit the portable ZIP count deadline

---------

Co-authored-by: wunianze666-netizen <wunianze666@gmail.com>
2026-11-19 03:33:31 +00:00
morluto 27e04ea2ec fix(javascript): share source-map admission and path resolution (#12161)
* fix(source-map): share bounded structural inspection with local analysis

Refs #12135

* fix(javascript): retain relative URL traversal and decline unusable map paths

* fix(javascript): retain source content beyond coordinate admission
2026-11-19 03:32:08 +00:00
morluto 261c6d06d1 fix(browser): derive body media types from observed headers (#12159)
* fix(browser): derive scenario media types from observed headers

Issue #12124

* fix(browser): retain body redaction mode through privacy replay
2026-11-19 03:31:13 +00:00
morluto 5dc54183f2 fix(evidence): identify snapshots across portable file readers (#12172) 2026-11-19 03:30:41 +00:00
morluto e1cb620ecc perf(javascript): reuse member syntax across ambient alias queries (#12174) 2026-11-19 03:29:59 +00:00
ShuaixinHuangandShuaixinHuang 342471f28d ci(windows): reuse built runtime for package verifiers (#12178)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 22:29:21 -05:00
morluto f4f8181553 fix(mcp): share registration environment admission (#12150)
* fix(mcp): share registration environment admission

Refs #12123

* docs(registration): explain the resulting behavior
2026-11-19 11:18:43 +08:00
morlutoandhongthana ca3f35dcbb fix(zip): publish EOF after extraction finalization (#12164)
* fix(zip): publish EOF after extraction finalization

Adapt the ZIP extraction changes from #8431 to current main.

* test(zip): bound producer-settlement acknowledgements

---------

Co-authored-by: hongthana <thanawat.rn@gmail.com>
2026-11-19 11:14:25 +08:00
ShuaixinHuangandShuaixinHuang b95a757c33 ci(windows): report package verification phase timings (#12167)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 22:07:57 -05:00
morluto 61af8abeb6 fix(android): share decoded Android XML admission (#12158)
* fix(android): share decoded manifest root and package admission

Refs #12139

* fix(apktool): keep foreign XML out of decoded string entries

Refs #12139
2026-11-19 11:07:25 +08:00
ShuaixinHuangandShuaixinHuang 3b8151125c fix(ci): keep dispatcher fixture exports aligned with runtime (#12131)
* fix(ci): keep real dispatcher cancellation classification in tests

* test(cli): require complete output fixture exports

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-19 11:06:46 +08:00
morluto 0f6bc14e32 refactor(providers): declare architecture admission exhaustively (#12166) 2026-11-18 22:02:37 -05:00
morluto 0aee26def4 fix(desktop): share state and window admission with exported verifiers (#12154)
* fix(desktop): share state view admission with the exported verifier

Refs #12133

* fix(desktop): share keyfile syntax with exported state readers

Refs #12141

* fix(desktop): share X11 window property interpretation

Refs #12140
2026-11-18 22:01:30 -05:00
morluto 461cedd73c fix(evidence): recognize misplaced snapshots across bundle readers (#12151)
* fix(evidence): recognize misplaced snapshots across bundle readers

Refs #12126

* docs(evidence): explain recovery for misplaced snapshots
2026-11-18 22:01:18 -05:00
morluto 72be66d050 docs(dev): clarify parser ownership and boundary verification 2026-11-18 21:36:51 -05:00
ShuaixinHuangandmorluto b1a390fcee fix(desktop): honor clean env launch prefixes (#12117)
* fix(desktop): honor clean env launch prefixes

* fix(desktop): retain process ownership across env prefixes

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 02:10:50 +00:00
morluto c5e44c8857 docs(dev): clarify parser ownership across runtimes
Refs #12120
2026-11-18 21:10:00 -05:00
ShuaixinHuangandShuaixinHuang b7059f8866 fix(ci): scope the short SAZ redaction assertion to source data (#12115)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 21:09:23 -05:00
ShuaixinHuangandmorluto 8062a14a3a fix(desktop): discover application state under its launch home (#12114)
* fix(desktop): discover application state under its launch home

* fix(desktop): preserve filesystem traversal in state roots

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 21:08:25 -05:00
Akshad Jogiandmorluto ae25050dff feat(native): surface inferred prototype instruction conflicts (#8161)
* feat(native): surface inferred prototype instruction conflicts

- Add evidence-backed x86-32 stack-read and stdcall cleanup diagnostics in ReaGhidraBridge.java without rewriting signatures or function bodies.

- Carry prototype conflicts through native API schemas, analysis summaries and retained dossier views so CLI and MCP share the observations.

- Update Ghidra analysis profile digests, documentation and MCP boundary tests for the new diagnostic contract.

* fix(native): follow framed paths and retain zero cleanup conflicts

- Traverse decoded entry-frame paths in ReaGhidraBridge.java instead of stopping at an address-ordered early return, so later reachable reads remain visible.

- Detect explicit, implicit and partial EBP writes and use decoded operands with p-code loads, preventing stale-frame warnings and recognizing real Ghidra stack reads.

- Compare immediate return cleanup with inferred stdcall stack bytes even when either side is zero, and allow zero in the native API contract.

- Add real Ghidra instruction probes and MCP/CI regressions for the reported cases and document the bounded checks.

* fix(native): attribute frame reads before register writes

- Check a decoded stack read before invalidating EBP in ReaGhidraBridge.java so instructions that read and replace the frame still report the conflict.

- Match each candidate operand's address p-code to its LOAD pointer so a POP from ESP into an EBP destination cannot masquerade as an argument read.

- Cover both decoded instruction cases in ReaPrototypeConflictProbe.java and await verifier-owned scratch cleanup on success and failure.

* fix(ghidra): recompute raw profile digests after rebase

- Recompute the 6502 and disabled-analyzer raw-binary profile digests in GhidraRawProfileDigest.test.ts so the pinned values commit to the merged shared policy on current main.

* fix(native): locate the entry frame by address and own verifier cleanup

- Find PUSH EBP; MOV EBP, ESP from the function entry address in ReaGhidraBridge.java so an owned block below the entry cannot hide a reachable argument read.

- Run analyzeHeadless in its own process group and stop that group before removing scratch in verify-ghidra-prototype-conflicts.mjs, so the JVM and decompiler children are addressed as one owned family.

- Cover the lower-owned-block case in ReaPrototypeConflictProbe.java with an entry frame preceded by a decoded lower block.

* fix(native): size prototype fixture and own Ghidra cleanup

- Allocate the instruction fixture through the lower-block offset in verify-ghidra-prototype-conflicts.mjs so the entry frame and decoded block exist for the probe.

- Check the detached process group instead of the leader exit code before cleaning up, so lingering decompiler children receive SIGTERM and SIGKILL before scratch removal.

* fix(native): own Ghidra probe cleanup with shared process owner

- Use REA's ProviderProcessSupervisor and token-verified cleanup in verify-ghidra-prototype-conflicts.mjs so the JVM and descendants are stopped before scratch removal, including failed launches.

- Preserve the source-owned x86 fixture with an entry frame and lower block while asserting verified cleanup.

- Build the pinned verifier dependency graph in the Ghidra bridge CI job and extend its timeout before running the real probe.

* fix(native): end verifier waits on interrupt before cleanup

- Install SIGINT and SIGTERM handlers before spawning Ghidra and abort the wait, so Ctrl-C no longer leaves the detached process group running.

- Keep cleanup handlers installed until the shared process owner reports verified cleanup, then remove scratch only after the process family is stopped.

* fix(native): preserve verifier cleanup interruption errors

- Keep interrupt handlers installed through process cleanup and workspace deletion, then check cancellation before reporting success.

- Preserve and report the failing cleanup step instead of replacing it with an interruption or deleting a tree that may still be unsafe.

* fix(native): retain probe failures across verifier cleanup

- Record the probe error before cleanup so a late SIGINT or SIGTERM cannot replace its stack and captured Ghidra diagnostics.

- Prefer the earlier probe failure when cleanup also fails, while preserving cleanup diagnostics and temporary state for diagnosis.

* test(kuna): raise caller matrix verifier budget for parallel CI

- The multi-target verifier spawn used a 10s timeout while sibling verifier cases use 25s.

- Under 8-way sharded CI load this intermittently exceeded 10s and produced ETIMEDOUT, failing shard 1/8 and portable tests.

- Raise to 30s to match the existing verifier budget and avoid load flakes.

* ci: retrigger checks after transient Ghidra SDK download 403

- The ghidra_bridge lane failed in upstream's untouched SDK acquisition step: curl returned 403 with 0 bytes downloaded in 0.046s from the GitHub release CDN.

- Push an empty commit to start a fresh run because rerunning on the upstream repository requires admin rights.

* fix(native): keep the cleanup lease on combined verifier failures

- Run the prototype-conflict probe through withVerifierFixture so a probe failure and a failed release surface as one AggregateError that keeps the probe error as its cause and attaches the retained fixture as cleanupLeases, instead of throwing the probe error alone and dropping the cleanup owner.

- Report the failed cleanup step and retained project only when the fixture was not released, and keep interrupt handlers installed until release finishes.

* test(native): use shared MCP prototype test deadlines

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 01:55:13 +00:00
170429eb7d feat(ghidra): admit plain MIPS32 PIC shared images (#2362)
* feat(ghidra): admit plain MIPS32 PIC shared images

Add an elf32-dyn-o32-arch32r2-standard-v1 lane for ET_DYN images without
an ASE flag (shared libraries and ET_DYN executables), beside the MIPS16
lane. It reuses the complete dynamic-relocation inspection and admits
R_MIPS_NONE, symbol-bearing R_MIPS_REL32 and the TLS loader slots
DTPMOD32/DTPREL32/TPREL32, which stay unapplied with a limitation.

Ghidra's default moves an image linked at 0 to 0x10000 and then shifts
only nonzero local GOT entries, so page-zero GOT entries (how GNU-ld
libraries call static functions) keep unshifted values and calls through
them decompile to wrong addresses. The lane imports at the image's own
ELF image base instead (lowest PT_LOAD in the first 20 headers, as Ghidra
computes it), commits it in the analysis profile and requires the bridge
handshake to report it. Images with a prelink trailer are refused.

verify:ghidra:mips32-shared checks LE, BE and soft-float LLD fixtures laid
out like GNU ld output against an independent readelf oracle: every
REL32, local GOT entry (including a zero page entry), global GOT entry
(EXTERNAL or lazy-binding stub) and unapplied TLS slot, plus named calls
in the decompilation, snapshot round trip and CLI evidence.

Refs #2338

* style(ghidra): format link-base regression scenarios

* test(ghidra): require zero-valued local GOT coverage

* test(ghidra): cover TPREL32 in the shared lane and drop duplicated session suites

Add an initial-exec TLS variable so the MIPS32 shared fixture declares
R_MIPS_TLS_TPREL32 beside DTPMOD32/DTPREL32, and require all three slots
to stay UNSUPPORTED with unchanged bytes. Remove the soft-float and
mutation handshake suites that the main reconciliation duplicated in
GhidraSessionValues.test.ts.

* test(ghidra): read the section table in the MIPS32 shared-library oracle

parseMipsReadelf now confirms the fixture's section types from readelf -S
(main added -S to the executable, relocatable and PSP oracles). Request it in
the shared-library oracle too.

* test(ghidra): follow main's verifier contracts in the MIPS32 shared lane

Main made the Ghidra installation probe asynchronous behind the shared
inspectVerifierGhidraInstallation helper, and analyze_function now returns a
summary unless detail "complete" is requested. Use both, as the other MIPS
lanes do.

* refactor(ghidra): keep Ghidra's image-base rule out of shared ELF parsing

The shared MIPS ELF reader computed Ghidra's ElfHeader.getImageBase rule
(lowest PT_LOAD address among the first 20 program headers) and the domain
type described it as Ghidra's base. Record source facts instead: every
PT_LOAD virtual address with its program-header index, plus the Android
prelink trailer. ghidraMipsElfImageBase in GhidraMipsProfile now applies
Ghidra's rule to those facts. The committed elf_image_base is unchanged.

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
2026-11-19 01:51:37 +00:00
f10d557f06 fix(cli): deliver complete TOON beyond the string limit (#12074)
* fix(cli): deliver complete TOON beyond the string limit

* fix(cli): own cancellation through TOON delivery

* test(cli): await TOON stage acknowledgements

* fix(cli): build TOON cancellations through domain factory

---------

Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 20:40:21 -05:00
ShuaixinHuangandmorluto bd5c985b3f fix(desktop): honor env working directories in launch commands (#12111)
* fix(desktop): honor env working directories in launch commands

* fix(desktop): create the replay working directory before launch

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 01:31:34 +00:00
Aurelio Bernalandmorluto 9b1ffa1f7d fix(ghidra): protect only unapplied relocation destinations, not their whole block (#11996)
Since #10483, an unapplied loader relocation in a non-writable block made
that whole block volatile. TLS slots are such relocations and sit in .got
beside the entries Ghidra did apply, so in any shared object or PIE with
initial-exec or dynamic TLS every GOT-indirect call decompiled as pointer
arithmetic instead of a named call.

Mark each unapplied destination volatile through its data item's Mutability
setting, creating an undefined item of the relocation's length where nothing
is defined. Fall back to the whole block only when an instruction or a data
item starting before the destination occupies it. Eligibility, limitations,
the read-only path, permissions and source FileBytes are unchanged.

The loader-relocation fixture now reads an initial-exec TLS variable whose
R_X86_64_TPOFF64 slot shares .got with the applied entries. The probe
requires that block and its applied entries to stay non-volatile and both
unapplied destinations to have volatile data items; on the previous bridge
it fails at applied_got_relocations_not_volatile.

Rename loader_relocation_semantics to
volatile-unapplied-relocation-destinations to state the new behavior.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 20:30:01 -05:00
458f583e14 fix(desktop): check retained reader JSON numbers (#11833)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 09:17:12 +08:00
26bec6f653 fix(artifacts): name no slice in trace-dylib-resolution Evidence (#11838)
trace_dylib_resolution Evidence named the slice the session happened to
open, not what was traced. On Apple silicon, `rea trace-dylib-resolution
/bin/ls --architecture x86_64` returned a subject selecting the arm64e
slice (offset 65536, architecture "arm64") while its parameters and
roots said x86_64. Whole-file traces of universal images and app bundle
traces also carried that host slice.

Root cause: the artifact provider built the execution without a
subject, and bindExecutionTarget binds such an execution, like any
subject that names the target's own bytes without a selection, to the
open target's selection. A provider had no way to state that an
observation covers the whole file.

EvidenceSubjectTarget.selection now accepts null, meaning the
observation selects nothing even though a session opened one slice.
bindExecutionTarget already inherited a selection only when none was
stated; its comment now says so. The trace states selection: null. This
matches inspect-binary-hardening and the other whole-file inspectors,
which already record no selection for a universal image.

Validation (macOS arm64, Node 24.22.1):
- New CLI boundary regression: a universal arm64 + x86_64 tool, traced
  whole and with --architecture x86_64, has a subject with no
  architecture or selection and the expected roots. Before this change
  the subject carried the opened slice.
- dylibResolutionCli and dylibResolutionMcp: 44 passed, 2 skipped.
- Suites that exercise subject binding (binarySession,
  analysisEvidenceAdapterParity, artifactMcp, bundleResourceRootCliMcp,
  appleBundleTraversalCoverage, AppBundleResourceRoot,
  ArtifactComparisonEvidence): 144 passed, 1 skipped.
- evidence, BinarySession and ArtifactProvider unit tests: 186 passed.
- Real /bin/ls trace with --architecture x86_64: subject selection and
  architecture null, roots [x86_64]. Format, typecheck, lint and
  architecture guards pass.

Not changed: inspect-macho, inspect-signature and
inspect-native-dispatch-metadata also record the opened slice for a
universal image; whether each examines only that slice was not checked.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 09:07:16 +08:00
morluto 55a50f53f9 fix(elf): reject undersized interpreter ranges before provider admission (#12113)
fix(ghidra): reject empty RISC-V PIE interpreter ranges
2026-11-18 20:04:59 -05:00
2SinceJulyandmorluto 206a2e067f fix(environment): refuse incomplete browser probes of body-taking tools (#11115)
A browser probe was only checked for POST, PUT and PATCH when deciding
whether capture.network.request_body had to be selected. A state-backed
bulk DELETE names its entities in a request body despite its method, so
an incomplete probe was admitted and replayed without the call
arguments the served tool needs, contaminating the comparison.

Derive the requirement from the parsed probe requests and the served
catalog's body-argument facts, matching each request to its tool the
same way comparison does. Keep bodyless item DELETEs accepted, and
remove the superseded method-only parser.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-19 09:03:30 +08:00
David Muñoz Rey 80af53bbe5 perf(javascript): queue binding initializers once per ambient alias query (#10681)
Ambient-write indexing resolves every escaped call argument and method
receiver through the ambient path resolver. Within one query, each
identifier read it reached requeued every selected initializer of its
binding, although an initializer already expanded with the same
projection only revisits its expanded root. Where locals copy each other
inside loops, as in wasm2js output, one query reaches hundreds of reads of
bindings with hundreds of initializers, so the work per query grew
quadratically. On pdf.js's openjpeg_nowasm_fallback.js, ambient indexing
alone took 137 s in-process.

Reads that select the same initializers for the same projection now share
one queue entry, whose remaining items are taken in the original
last-in-first-out order. Items already taken are not requeued. Every
expansion that is not a revisit happens in the same order as before, so
resolutions are unchanged.

Validation:
- New work-count regression: during the single escape query of a looping
  a=b/b=a cycle, reads of the copied values are 1087 and 2175 for 32 and
  64 copies (base: 5551 and 20319). The test fails on the base revision.
- npm run test:local over src/domain/javascript (187 files, 5817 tests)
  and src/application/javascript (31 files, 695 tests): pass.
- Ambient write and escape effects, retained global call receivers and
  escaping reference stores are byte-identical before and after on
  openjpeg_nowasm_fallback.js. Static facts and member-mutation state are
  byte-identical on 12 other bundles.
- openjpeg_nowasm_fallback.js, ambient indexing in-process from the built
  dist, one cold run each on a 4 vCPU host: 137.4 s -> 26.4 s; process
  CPU 154.0 s -> 31.0 s; peak RSS 863 MB -> 388 MB.
- npm run check:fast: pass.

The CLI still does not complete that file: its worker now exhausts the
1024 MiB heap in member-mutation traversal after 246 s, rather than
reaching the 300 s per-source deadline.

Refs morluto/rea#2498
2026-11-19 08:54:04 +08:00
ShuaixinHuang af20de3509 feat(native): resolve RISC-V ELF initializer pointers (#12109) 2026-11-18 19:45:05 -05:00
Abhay Tiwari 8d226251a7 feat(ghidra): admit RISC-V position-independent executables (#4487) (#4811)
* feat(ghidra): admit RISC-V position-independent executables (#4487)

Admit little-endian RISC-V ELF32 and ELF64 position-independent executables
(ET_DYN with PT_INTERP) into the pinned generic Ghidra lane.

- Collect `PT_INTERP` during the existing validated ELF table walk in
  `validateElfDeclaredRanges` and record `hasInterpreter` in target metadata,
  supporting arbitrary table offsets and extended program counts without duplicate scanning.
- Admit ET_DYN images when `hasInterpreter` is present under lane identities
  `elf32-pie-le-double-float-generic-v1` and `elf64-pie-le-double-float-generic-v1`.
- Preserve refusal for non-PIE ET_DYN targets (shared libraries without PT_INTERP)
  explaining that shared libraries require separate load verification.
- Record load model facts (`load_model: "pie"`, `expected_default_image_base: "0x10000"`
  or `"0x100000"`, `has_interpreter: true`) in `riscv_elf` analysis profile parameters.
- Record default image base analysis coordinates limitation for PIE targets.
- Update `docs/ghidra-riscv.md` with PIE admission boundary and evidence semantics.
- Add unit tests for PT_INTERP collection, high-offset program headers, and PIE profile resolution.
- Add PIE fixture generation capability to `tests/conformance/ghidra/riscv-fixture.mjs` and
  pass `-Wl,-pie` to ensure bare-metal drivers generate ET_DYN.
- Extend `scripts/verify-real-ghidra-riscv.mjs` to test both ET_EXEC and ET_DYN.

Fixes #4487

* fix(ghidra): check structured facts and rethrow typed errors in PIE tests

* style: format GhidraRiscvProfile.test.ts

* fix(ghidra): restrict PIE admission to verified double-float RISC-V lanes
2026-11-18 19:44:40 -05:00
ShuaixinHuang 3e69b37327 fix(ci): remove an unused Ghidra COM export
(cherry picked from commit c145ebc8a9)
2026-11-18 19:32:29 -05:00
RRFZandmorluto f192180fb5 refactor(desktop): pass export task reader runner through a port (#11858)
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 19:31:12 -05:00
ShuaixinHuang 0c83de1642 fix(desktop): preserve ELF filesystem lookup bytes (#12108) 2026-11-18 19:24:16 -05:00
ShuaixinHuangandShuaixinHuang 229fc6aae8 fix(ci): synchronize CDP handshake and attach deadlines (#12110)
Co-authored-by: ShuaixinHuang <197200901+ShuaixinHuang@users.noreply.github.com>
2026-11-18 19:23:46 -05:00
RRFZ 2076b7bf88 refactor(desktop): inject HostFileReader port into build solve and witness (#11880)
refactor(desktop): inject HostFileReader port into build solve and witness workflows
2026-11-18 19:22:40 -05:00
morluto 21829964ef fix(kuna): recover explicit direct-call destinations (#12106)
* fix(kuna): recover explicit direct-call destinations

* fix(kuna): preserve call evidence on decompile failure
2026-11-18 19:07:02 -05:00
morluto b44d949bfe feat(kuna): verify release 1.1000 (#12107) 2026-11-18 18:52:55 -05:00
David Muñoz Rey 15090cf848 docs(i18n): fix two Spanish strings flagged in review of #12103 (#12104)
The FAQ sentence put an imperative before a link whose text is also an
imperative ("Consulta Usa la CLI"); the link now reads "cómo usar la CLI".
The TH04 figure label coordinated two singular adjectives after a plural
noun; it now names each ring.
2026-11-18 18:42:15 -05:00
Nianze Wu c6033aaaca fix(desktop): bound exported XML selector traversal (#12105) 2026-11-18 18:41:18 -05:00
e3713bea60 feat(rust): read cargo-auditable dependencies from WebAssembly modules (#5069)
* feat(rust): read cargo-auditable dependencies from WebAssembly modules

cargo-auditable embeds the same zlib-compressed `.dep-v0` JSON in a
WebAssembly custom section for wasm32 targets, but inspect_rust_binary
rejected every module as an unsupported target because only ELF, PE and
thin Mach-O containers were recognized.

Walk the section framing of version 1 core modules to locate the
`.dep-v0` custom-section payload and the data section, where rustc keeps
its constant /rustc/<hash>/ paths. Rust lookups now read one
format-neutral layout, so native and WebAssembly images share a single
dependency-section owner. WebAssembly declares no container word size, so
`bits` is null for that format only; the Evidence subject format is
`file`, as for inspect_wasm_artifact.

Truncated sections, invalid LEB128 sizes, custom-section names that run
past their section or are not UTF-8, duplicate `.dep-v0` sections and a
second data section are malformed. Components, such as wasm32-wasip2
output, embed core modules and are refused as unsupported, like universal
Mach-O containers, rather than inspected through one selected module.

* fix(rust): bound the WebAssembly section walk

The WebAssembly reader visited every section synchronously, and the format
sets no section count. A 256 MiB input of three-byte custom sections with
empty names walked about 89 million sections and held the event loop for
about 7.4 seconds, delaying cancellation and other MCP requests; empty type
sections took about 1.9 seconds.

Refuse a module with more than 65,536 sections with a typed cpu resource
constraint that reports maximum_wasm_sections, as the Go header search
reports its work budget. Producer output holds a few dozen sections, and the
same inputs are now refused within tens of milliseconds.

* fix(rust): accept WebAssembly Evidence in retained dependency views

Retained Rust views compared the parent subject with a Mach-O-only format
mapping, so WebAssembly Evidence, whose subject format is file, was refused
as a different artifact. The report domain now owns the subject format next
to the architecture mapping, and the service and the view both use it. The
real CLI/MCP view workflow now also covers a WebAssembly module.

* fix(rust): name the WebAssembly section-walk allowance in recovery

Fixed-allowance recovery mapped every Rust resource other than capacity and
transport to the parser allowance, so the section-walk refusal said host
memory does not raise it. Each Rust resource now maps to its own allowance,
and the cpu bound is a fixed work allowance. The MCP error contract test
checks that the refusal is not retryable and names that allowance.

* fix(rust): require WebAssembly container facts in reports

The report schema tied a null word size to WebAssembly, but it accepted a
wasm report that named a native architecture or big-endian byte order, and
a native report that named the wasm architecture. Retained views parse
imported Evidence with this schema, so such a contradictory report was
accepted. The architecture is now wasm exactly when the container is
WebAssembly, and a WebAssembly report must be little-endian.

* docs(rust): record the WebAssembly dependency-metadata feature

Feature work now carries a spec, plan and task list under docs/specs.
This adds that record for reading cargo-auditable metadata from
WebAssembly core modules and indexes it. The record states that it was
written during review and lists the verification that remains open.

* fix(rust): bind section names to containers and share the LEB128 reader

The report schema accepted a dependency section name that does not belong
to the report's container, such as a WebAssembly report naming the Mach-O
section. rustDependencySectionName now owns that name for the reader and
the schema, which refuses a mismatch for every container.

The WebAssembly reader decoded section sizes with its own loop. It now
uses the shared readLeb128, and an integer cut off by the end of the file
is truncated rather than malformed.

* fix(rust): classify a cut-off WebAssembly integer by its boundary

The reader called an unfinished LEB128 integer truncated whenever its
limit equalled the file length. A name length cut off inside the final
section was therefore truncated, and the same bytes followed by another
section were malformed. Each caller now states whether the file or the
enclosing section bounds the integer.

* fix(rust): report a duplicate WebAssembly dependency section first

The section walk kept two .dep-v0 matches but walked on, so a module with
two dependency sections and more than 65,536 sections after them was
refused for the section bound instead of the duplicate it had already
established. The walk now ends at the second match.

* test(rust): assert WebAssembly container facts instead of limitation prose

The CLI acceptance test matched an English limitation sentence. It now
checks format, architecture, bits and byte order on the parsed report.

* fix(rust): state container word size as 32 | 64 | null

Output contract: inspect_rust_binary bits, including the summary view, is
32 | 64 | null. Null is valid only for WebAssembly and is not a number.
ELF, PE and Mach-O reports stay 32 or 64. The schema description, guide,
feature record and skill state that, and CLI renderers keep null instead
of substituting a word size.

---------

Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
2026-11-18 18:29:31 -05:00
morluto e09d6273a1 fix(native): preserve caller-selected paths in binary sessions (#12102)
* fix(mcp): preserve caller-selected binary session paths

* test(mcp): verify caller paths across snapshot replay

* test(mcp): separate session alias and snapshot replay coverage

* fix(evidence): preserve selected paths across binary workflows

* fix(evidence): retain authentication admission for caller aliases
2026-11-18 18:27:29 -05:00
David Muñoz Rey c3531b9f1c docs(i18n): review the Spanish guides, case studies and blog (#12103)
* docs(i18n): complete the Spanish website translations

The Spanish catalog had 63 of 1,808 messages without a translation, so the RL environments guide and a few setup sentences fell back to English in the Spanish edition.

They are translated now, with the wording the catalog already uses for the same terms and the formal address most of its pages use.

* docs(i18n): fix spacing and separators in the Spanish website catalog

About 210 Spanish messages carried marks of an automated pass: a space before punctuation or inside parentheses ("REA .", "( Windows )"), a space between a name and the tag that closes it, doubled spaces, and an asterisk where the source has a middle dot ("01 * Tú").

The spacing next to each placeholder now follows the source message, the stray spaces are gone, and the middle dot is restored. No wording changes.

* docs(i18n): review the Spanish onboarding pages

Read the home page, Get started, Your first investigation and the dinosaur
speed lab in full, with the shared navigation and interface messages. These
pages mixed the informal address of the edited strings with the formal
address of the initial draft; they now use the informal one throughout.

Fixes wrong-sense words (sucursal for a code branch, cheque for a check,
punto final for an endpoint), broken placeholder order, copy-button labels
and the stale translation of the RL environments task line.

* docs(i18n): fix wrong-sense words in the Spanish website catalog

Outside the onboarding pages, replace words found by search that carry the
wrong sense: cheque for a check, punto final for an endpoint, camino for a
path, puerto for a software port, and codificación in coding agent. Rewrite
the sentences around them where articles, placeholder order or other words
were broken, and use the navigation's Casos prácticos in the breadcrumbs.

* docs(i18n): keep the ownership sense of owned protocol stdin in Spanish

The Aegis setup sentence rendered "owned protocol stdin support" as support
for the protocol's own stdin, which drops who owns the process. Say that the
package must accept protocol stdin for the processes REA starts and controls.

* docs(i18n): review the Spanish guides and FAQ

Read the guides index, the native, browser, JavaScript and RL environments
guides and the FAQ in full against their source. They now use the informal
address and the terms of the edited strings (prompt, skill, la CLI, agente de
programación), and the Notes button keeps its on-screen label.

Fixes wrong-sense renderings such as "la persona que llama" for a caller,
"guión" for a script, "grabadora CSV" for the CSV writer and the
translated field name in summary.ipc, and broken placeholder order.

* docs(i18n): call the browser capture block a command in its copy label

The block copies a terminal command, not a prompt.

* docs(i18n): review the Spanish case studies

Read the case-study index and the Aegis, CTF, DX-Ball, Notion and TH04 case
studies in full against their source, with their three figures. They now use
the informal address and the terms of the edited strings.

Fixes wrong-sense renderings such as "viñetas" for bullets, "rebajas" for
Markdown, "bandeja de sonido" for sound pan, "tienda" for a store
instruction, "asamblea" for assembly and "PRINCIPAL.EXE" for MAIN.EXE,
keeps path and field names as written, and repairs placeholder order.

* docs(i18n): keep the DX-Ball figure labels inside their boxes

Three Spanish labels were wider than the boxes drawn for them. Shorten the
title, the caller label and the matching-bytes label.

* docs(i18n): review the Spanish blog essays

Read the blog index and the two essays in full against their source. The
Touhou reconstruction essay is retranslated: it rendered RE as augmented
reality, a ledger as an accounting book, game titles as literal phrases and
compounding as getting worse. The models essay, already edited, gets term
fixes: control-flow graph, compiler feedback, training, floating point.

Imperatives addressed to the reader use the informal address, and the
author's first-person voice is kept.

* docs(i18n): keep the setup question in the informal voice

"¿Ya está conectado?" read as formal address next to informal imperatives.
Ask it of the reader in the informal form.
2026-11-18 18:15:09 -05:00
IvenKooandmorluto 27db243533 fix(static): keep quoted sample text out of the tech-debt marker scan (#11712)
fix(static): read comments instead of quoted text in the tech-debt scan

`npm run scan:todos` matched raw text, so a marker quoted inside a sample
string counted as debt: on `main` at a10037ef1 the only finding is the
JavaScript sample in
`tests/boundary/filesystem/mcpClientValidationGuard.test.ts`, and the
`Deep static checks` lane is red for every PR that runs it.

Decide what a comment is before counting a marker. JavaScript and TypeScript
are parsed with `@babel/parser`, whose comment ranges also survive a quote
inside a regex literal; `bridge/**/*.py` and `bridge/**/*.java` use a small
scanner that skips quoted and triple-quoted strings. Markers are matched per
occurrence, so a quoted marker earlier on the line no longer consumes a real
one, and an unparsable file stays conservative: every marker counts.

Fixes #11717.

Verified: `npm run scan:todos` exits 0 on this tree; the extended
`tests/boundary/process/scanTodos.test.ts` (3 tests) covers a clean tree, a
quoted sample with a real marker on the same line, and comments in
TypeScript, Python and Java. `check:fast` passes.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 17:54:40 -05:00
00a3f4d2b9 fix(process): preserve Darwin snapshot and cleanup failures (#12100)
* fix(process): preserve Darwin opening snapshot failures

* fix(process): retain the exact Darwin helper cleanup owner

Transfer the failed helper-root capability across repeated prepare failures. Reuse that same owner for retirement and reader close so stale cleanup cannot remove a replacement helper.

Co-authored-by: Anandumv <anandumv@gmail.com>
Co-authored-by: nextjohnp7 <nextjohnp7@gmail.com>

* test(process): isolate retained cleanup and compiler acknowledgements

---------

Co-authored-by: Anandumv <anandumv@gmail.com>
Co-authored-by: nextjohnp7 <nextjohnp7@gmail.com>
2026-11-18 17:34:25 -05:00
morluto 230f86240f docs(browser): describe exact role locator names (#12099)
* docs(browser): describe exact role locator names

* style(browser): format role locator schema metadata
2026-11-18 17:20:26 -05:00
RRFZandmorluto caab34d0de fix(javascript): qualify releases after resource method mutation (#10166)
* fix(javascript): qualify releases after resource method mutation

* fix(javascript): qualify releases after opaque receiver mutation

* fix(javascript): preserve release ordering and mutation facts

* fix(javascript): order mutations of fresh resource receivers

* fix(javascript): match release mutations to captured receivers

* fix(javascript): check delegated release method identity

* fix(javascript): track paths back to native resource prototypes

* fix(javascript): respect native release member ownership

* fix(javascript): retain shared prototype effects across calls

* fix(javascript): order release effects after definite acquisition

* fix(javascript): preserve prototype effects across receiver replacement

* fix(javascript): preserve native release identity across proven effects

* fix(javascript): preserve shared prototype uncertainty after opaque calls

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
2026-11-18 17:02:04 -05:00
ClarkandClark 2191896f3b docs(i18n): complete zh-CN translations including rl-environments (#12079)
Co-authored-by: Clark <301422770+clark970417-eng@users.noreply.github.com>
2026-11-18 16:54:04 -05:00
David Muñoz Rey 1bd45f073c docs(i18n): complete the Spanish website translations (#12092)
* docs(i18n): complete the Spanish website translations

The Spanish catalog had 63 of 1,808 messages without a translation, so the RL environments guide and a few setup sentences fell back to English in the Spanish edition.

They are translated now, with the wording the catalog already uses for the same terms and the formal address most of its pages use.

* docs(i18n): keep the ownership sense of owned protocol stdin in Spanish

The Aegis setup sentence rendered "owned protocol stdin support" as support
for the protocol's own stdin, which drops who owns the process. Say that the
package must accept protocol stdin for the processes REA starts and controls.
2026-11-18 16:53:49 -05:00