* 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.