pub struct EamModifyResult {
pub task: String,
pub changed: Vec<String>,
pub definition: Value,
pub put_outcome: Option<ModifyOutcome>,
pub readback: Value,
}Expand description
The ign eam task modify output model — all keys always.
Fields§
§task: StringThe post-write name (rename is NOT supported — always the name as found).
changed: Vec<String>The dotted key paths the change touched: "enabled",
"description", "config.profile.scheduleMode",
"config.settings".
definition: ValueThe verbatim PUT body (the single record — the client wraps it in the one-element array envelope): the agent’s read-back of exactly what was sent, signature + collection included.
put_outcome: Option<ModifyOutcome>The captured 200 outcome
(ModifyOutcome — changes[].newSignature is
authoritative for the NEXT mutation, §6a; its problem rides
verbatim on the refusal shapes). null when a 2xx carried no
body (the lenient client Option).
readback: ValueThe post-PUT find, serialized — the echo semantics make the
read-back meaningful (§6a: newSignature == read-back
signature, mutated keys landed, unknown round-trip keys
preserved). null when the read-back itself failed (the PUT
already succeeded — a read blip must not mask a landed write).