* refactor(native): bind producer_limits and max_input_bytes as the per-call controls of pwntools and Apple dispatch refusals
producerLimitControl in src/domain/producerResourceLimits.ts names one producer budget as producer_limits.<field>; the shared provider outcome classifier now carries a resource signal's limit. Pwntools file-size, CPU and output refusals and the Apple dispatch input refusal bind their control, and their remediation no longer names CLI flags.
* fix(native): report the selected output allowance as the omitted file_bytes default
* fix(native): bind producer_limits.diagnostic_bytes as the pwntools command output-limit control
* refactor(rust): bind producer_limits as the per-call control of Rust input and report refusals (#11458)
* refactor(rust): bind producer_limits as the per-call control of Rust input and report refusals
* test(rust): cover the complete-report refusal's producer_limits control
* refactor(browser): bind caller-selectable browser deadlines as per-call controls instead of naming CLI flags (#11466)
* refactor(rust): bind producer_limits as the per-call control of Rust input and report refusals
* test(rust): cover the complete-report refusal's producer_limits control
* refactor(browser): bind caller-selectable browser deadlines as per-call controls instead of naming CLI flags
deadlineParameterLimit in src/domain/analysisResourceLimits.ts owns the millisecond deadline control that nativeDeadlineRecovery and the browser recoveries share. CDP command and discovery, web bundle per-script and total, network capture and source-map decode deadlines now carry it; browserDeadlineIncrease no longer takes CLI flag text.
* fix(browser): record a per-script deadline's parameter control in partial web bundle results
* refactor(providers): bind Wabt, SQLite, EVMole, Apktool and Go controls instead of naming CLI commands (#11472)
* refactor(providers): bind Wabt, SQLite, EVMole and Apktool deadline and byte controls instead of naming CLI commands
These remediation strings named rea commands and flags through template text the cli-option guard did not count. Wabt byte refusals and output limits bind max_input_bytes, max_tool_bytes or max_output_bytes while a larger value is selectable; SQLite worker_timeout_ms, EVMole timeout_ms and Apktool decode_timeout_ms bind through deadlineParameterLimit; the shared provider outcome classifier now carries an output limit's control.
* refactor(go): bind Go analysis budgets as per-call controls instead of naming CLI flags
* fix(providers): keep the typed primary when Wabt, EVMole or pwntools command cleanup fails
* ci(guards): count template-built CLI option and command text outside the CLI layer (#11478)
* refactor(providers): bind Wabt, SQLite, EVMole and Apktool deadline and byte controls instead of naming CLI commands
These remediation strings named rea commands and flags through template text the cli-option guard did not count. Wabt byte refusals and output limits bind max_input_bytes, max_tool_bytes or max_output_bytes while a larger value is selectable; SQLite worker_timeout_ms, EVMole timeout_ms and Apktool decode_timeout_ms bind through deadlineParameterLimit; the shared provider outcome classifier now carries an output limit's control.
* refactor(go): bind Go analysis budgets as per-call controls instead of naming CLI flags
* fix(providers): keep the typed primary when Wabt, EVMole or pwntools command cleanup fails
* ci(guards): count template-built CLI option and command text outside the CLI layer
The cli-option-text-outside-cli pattern now also matches "(CLI ...", "on the CLI", "or use rea ..." and backticked `rea <command>` references, so remediation built from a template such as --${name} or rea inspect-... <path> is counted. Doctor.ts is exempt: setup and doctor run only through the CLI. The baseline records the newly counted pre-existing sites (22 -> 45 across 21 files).
* ci(guards): extract the CLI text matcher, exempt host-only commands with written reasons, and test each spelling
* ci(guards): exempt a host-only command and its own arguments in any matched CLI phrase
* fix(native): bind producer_limits.output_bytes for oversized pwndbg debugger replies through one owner
* fix(cli): name an Evidence target source failure's control by the source option that sets it
* feat(cli): render the flags of result-recorded controls in the full-output envelope (#11507)
* feat(cli): render the flags of result-recorded controls in the full-output envelope
* fix(cli): collect result controls only for a full-output envelope, in its requested format, past undefined values
* ci(guards): end a host-only command's arguments before the next CLI command
* refactor(reverse): record the output budget that stopped a one-shot command as a parameter control (#11528)
* fix(cli): read result controls only at positions the output schema declares as recorded controls
* refactor(providers): record the controls that bounded Rust compiler paths and kernel module text instead of naming CLI options (#11532)
* refactor(rust): record the control that bounded compiler-path coverage instead of naming CLI options
* refactor(native): record the controls that omitted kernel module .modinfo text instead of naming CLI options (#11534)
* fix(rust): describe compiler coverage from the retained result after report trimming
* refactor(providers): record managed representation and JavaScript semantic ceiling controls instead of naming CLI options (#11537)
* refactor(managed): record the representation budget on a resource-limit issue instead of naming its CLI option
* refactor(javascript): record the semantic retention ceilings that stopped a graph instead of naming CLI options (#11540)
* fix(cli): name a composed command's source options for the controls its result records
* fix(cli): read result controls from the delivered Evidence when a summary wraps it
* fix(rust): keep the report-byte control recorded when trimming omits every compiler path
When the complete-report allowance left room for no compiler path, rustc_commit became null and its coverage.limit was lost, so --full-output could not name the option that raises the allowance. The report now records rustc_commit_omission { reason, limit } outside the dropped record, and the summary view carries it.
* refactor(flutter): record the string-pool budgets that left a projection partial instead of naming the CLI option (#11541)
* refactor(flutter): record the string-pool budgets that left a projection partial instead of naming the CLI option
* test(flutter): assert the complete set of recorded string-pool budgets
* feat(cli): name the options of controls a failure's partial Evidence records (#11557)
meta.cli_controls was collected only from a successful result. A failure whose partial observation is Evidence of the command's own operation is now read the same way, at the positions the output schema declares as recorded controls; Evidence of another operation or a retained reference is not read. When --evidence_output publishes the partial, the delivery records it before replacing it.
* refactor(javascript): record the evaluator budgets that limited sources instead of naming the CLI option (#11564)
Per-value unknown reasons and the Electron wrapper limitation named --semantic-precision. The static examination now records the semantic_precision controls that limited a source (examination.controls), and analyze_javascript_application's semantic_graph.coverage.controls records every evaluator budget that limited any source (examination and semantic IR coverage), beside the retention ceilings. The CLI renders --semantic-precision from those records in meta.cli_controls; the reason texts name only the contract field.
* refactor(rust): report cargo-auditable section failures through ParseFailure
RustAuditableFormatFailure restated the malformed/unsupported algebra and
the provider translated it by hand; container BinaryFormatFailures were
re-wrapped and lost their kind. The reader now throws ParseFailureError
(format rust-auditable), container failures propagate unchanged, and the
provider maps both through parseFailureAnalysisError. A counted guard
keeps new per-format failure classes from returning.
* test(rust): pin the container's truncated failure facts through the Rust reader
Classify lipo parse failures once for native and artifact consumers, retain valid read-only ELF ranges independently of optional section names, and map IL2CPP reader architecture through the existing CPU identity owner before Mach-O parsing.
Regression-first checks reproduced malformed lipo output, lost unnamed-section compiler paths, and the amd64/x86_64 adapter mismatch. Focused parser, artifact, Rust CLI/MCP, Go, and IL2CPP controls passed; authored fixtures do not establish real-provider behavior.
Fixes#5982Fixes#3397
Keep validated PE padding in the selected Evidence range while consumed zlib bytes own compressed and inflate-ratio limits. Preserve typed resource failures and bounded allocation. Validated accepted padding, over-ratio and compressed-size controls through source, real CLI and stdio MCP workflows.
Reject duplicate decoded JSON names before object conversion. Use one checksummed zlib stream parse and retained PE FileAlignment to distinguish exact zero padding from trailing payload bytes. Exercise public CLI and stdio MCP.
Fixes#6814Fixes#6793
Move ELF, PE and Mach-O container parsing into a shared native owner. Go alone selects and validates Go build-info sections, so unrelated malformed Go metadata no longer blocks Rust dependency or IL2CPP inspection. Remove the superseded Go-specific container representation and migrate all consumers. Adapted from draft PR #5510 without asserting human PR readiness.
Validation: 51 compiled CLI/MCP acceptance tests across Rust, Go and IL2CPP; 186 shared-reader tests; full check:ci passed. Three public synthetic-file probes reproduce the baseline Rust refusal and validate the fixed SDK-advertised MCP output, artifact digests and unchanged bytes. The exact zero-address nonallocated ELF case now succeeds for Rust while Go still reports invalid_format. No target execution or real compiler-artifact qualification was performed; no performance improvement is claimed.
Closes#3398
* feat(native): read embedded cargo-auditable Rust dependency lists
* fix(native): trim PE section padding and compute dependency cycles iteratively
* fix(native): ignore SHT_NOBITS sections and validate dependency edges linearly
* fix(native): bound compiler path scanning and retained hashes
* fix(rust): pass package arrays as named parameterized test cases
* fix(rust): admit graph expansion and preserve resource units
* fix(rust): reject malformed packages, false cycles, and hidden compiler paths
Fail the first malformed cargo-auditable package before Zod collects an
issue per field. Require cyclic dependency indices to match the cycles in
package dependencies. Keep read-only ELF ranges when a section name does
not fit the bounded name window, so a rustc path in that range is still
reported.
* fix(ci): repair integrated checks and Hopper test baseline
* fix(go): verify Mach-O sections against segments
---------
Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>