* feat(errors): name the fields a failure's recovery selects so the CLI renders their flags
AnalysisError gains related { parameters, operations } (contract fields and operation names), projected as details.related_parameters / related_operations and kept through the domain re-attribution helpers. The CLI projection adds details.related_cli_flags for its own command's fields. inspect_plist's missing-default failure and inspect_sqlite_database's column-evaluation failure name fields only in their text.
* test(sqlite): check MCP omits CLI flags on the failure that names related fields
* 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(javascript): bind max_heap_mb and analysis_timeout_ms flags from the limit, not remediation text
The CLI projection now also names the flag of a registered setting limit that carries a request parameter (javascript.max_heap_mb, javascript.analysis_timeout_ms). The JavaScript worker heap and timeout remediation and the web bundle heap remediation no longer name CLI flags; a web bundle heap exhaustion that a larger max_heap_mb raises now binds max_heap_mb as its per-call control.
* test(javascript): assert the adapter-neutral heap remediation in the worker order audit
* refactor(managed): bind max_snapshot_bytes as the per-call control of a managed snapshot refusal (#11453)
* refactor(cli)!: name a failure's per-call control flag at the CLI boundary
Services name the contract field a deadline failure reports in
details.limit.parameter; a contract command's output projection adds
details.limit.cli_flag from the command's own field-to-flag binding.
BREAKING CHANGE: MCP failures no longer carry details.limit.cli_flag, and
native deadline remediation text no longer names the CLI flag. CLI output
still reports cli_flag for the command that ran.
* fix(cli): key nested flattened members by their dotted path; restore the test's exit status
* refactor(reverse): bind command_timeout_ms as the per-call control of an objdump or Rizin deadline (#11442)
* refactor(reverse): bind command_timeout_ms as the per-call control of an objdump or Rizin deadline
The deadline failure now comes from nativeDeadlineRecovery: it names command_timeout_ms and carries limit {control_kind: "parameter"}, so the CLI projection adds --command-timeout-ms and MCP output names the field only. The service no longer writes CLI flag text.
* refactor(wasm): bind max_artifact_paths as the per-call control of an auxiliary path admission refusal (#11444)
inspect_analysis_view and inspect_il2cpp_metadata wrote "--evidence-bundle"
and "--ghidra-seeds needs --binary" into their own input issues, copying
the CLI's option spelling into the service. They now name the field
(binary_path) or the input ("An Evidence bundle"), and the CLI's field
binding keeps owning option spellings.
A counted architecture guard records the 41 remaining REA CLI option
spellings outside src/cli (mostly "(CLI: --flag)" remediation hints) so
the list can only shrink.