Summary
When a caller sends fields that imply an update target, such as entity_id, but the storage layer creates a new entity instead, the response does not explicitly warn that update semantics were ignored.
Impact
Agents may miss that they have created duplicates until they manually inspect the returned entity IDs and resolver path.
Expected
Return a prominent warning such as ignored_fields: [entity_id] or operation_mismatch: requested_update_but_created_new_entity.
Actual
The response indicated action: created and resolver details, but did not explicitly flag that the provided update target was ignored.
Privacy
Redacted. No personal data, account names, sensitive preferences, or original task details included.
Summary
When a caller sends fields that imply an update target, such as
entity_id, but the storage layer creates a new entity instead, the response does not explicitly warn that update semantics were ignored.Impact
Agents may miss that they have created duplicates until they manually inspect the returned entity IDs and resolver path.
Expected
Return a prominent warning such as
ignored_fields: [entity_id]oroperation_mismatch: requested_update_but_created_new_entity.Actual
The response indicated
action: createdand resolver details, but did not explicitly flag that the provided update target was ignored.Privacy
Redacted. No personal data, account names, sensitive preferences, or original task details included.