mirror of
https://github.com/morluto/rea.git
synced 2026-11-16 11:43:20 +00:00
refactor(cli)!: name a failure's per-call control flag at the CLI boundary (#11413)
* 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)
This commit is contained in:
1 parent
23eee86bd5
commit
49d4991a18
18 files changed
+321
-45
No files matched your search
@@ -294,9 +294,12 @@ to parse that sentence to identify an editable setting.
|
||||
|
||||
A deadline controlled by something other than a registered setting reports
|
||||
`details.limit` with `control_kind` instead of `setting`.
|
||||
`control_kind: "parameter"` names the per-call `parameter` and its `cli_flag`
|
||||
`control_kind: "parameter"` names the per-call contract field in `parameter`
|
||||
(`native_command_timeout_ms`, `native_ui_deadline_ms`,
|
||||
`pwntools_timeout_ms`) and applies on the next call.
|
||||
`pwntools_timeout_ms`) and applies on the next call. Services and their
|
||||
remediation text name only that field. A CLI command adds `cli_flag`, the
|
||||
option that sets the field on that command, from its own field-to-flag
|
||||
binding; MCP results do not carry it.
|
||||
`control_kind: "environment"` names the `environment` variable REA reads when
|
||||
it starts (`REA_SWIFTC_COMPILE_TIMEOUT_MS`): `applies_at` is `next_startup`,
|
||||
or `next_invocation` for a one-shot invocation. Both carry `effective_value`,
|
||||
|
||||
Reference in new issue
Block a user