#10 update_member cloud field updates silently no-op for non-cloud members

[Anonymous]

Originally created by: kumaakh
Originally owned by: joiskash

Problem

When update_member is called with cloud-specific fields (e.g., cloud_activity_command, cloud_idle_timeout) on a non-cloud member, the fields are silently ignored. The user gets a success response with no indication that their input had no effect.

Expected behavior

Either:

• Return a warning: "cloud fields ignored — member is not a cloud member"
• Or reject: "cannot set cloud fields on non-cloud member"

Priority: LOW

UX issue, not a bug. No data loss or incorrect behavior.

Source

Code review Round 3.
File: src/tools/update-member.ts

[Anonymous]

• assigned_to: joiskash

[Anonymous]

Originally posted by: kumaakh

Fixed: src/tools/update-member.ts:100-110 now explicitly warns when cloud-specific fields are passed for a non-cloud member instead of silently ignoring them.

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed