mirror of
https://github.com/morluto/rea.git
synced 2026-11-19 21:23:45 +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
@@ -123,7 +123,6 @@ describe("translateNativeCommandFailure", () => {
|
||||
expect(projectAnalysisError(error).details?.limit).toEqual({
|
||||
control_kind: "parameter",
|
||||
parameter: "native_command_timeout_ms",
|
||||
cli_flag: "--native-command-timeout-ms",
|
||||
effective_value: 60_000,
|
||||
unit: "ms",
|
||||
minimum: 1,
|
||||
|
||||
Reference in new issue
Block a user