`projects update` response returns pre-write description (stale field)

[dyve]

Bug

basecamp projects update <id> --description '...' --json succeeds (the description is written to Basecamp and updated_at advances in the response), but the description field in the command's own JSON response remains "" — the pre-write state.

Steps to reproduce

# Update a project description
basecamp projects update 47201525 --description "New description" --json

# Response contains description: "" even though the write succeeded
# A subsequent show confirms the write worked:
basecamp projects show 47201525 --json | jq .description
# → "New description"

Expected behavior

The response from projects update should include the newly written description (and any other mutated fields) rather than the pre-write values.

Observed behavior

• updated_at in the response is correctly set to the current timestamp
• description in the response is "" (the pre-write value)
• The actual Basecamp record is updated correctly (verified via projects show)

Workaround

In basecamp-cli-mcp we now do a refetch after write (projects show <id>) to return accurate state to the calling agent.

Related

This appears to be in the same class as #412 (todos update --due not reflected in response), suggesting the issue may affect multiple update subcommands.

Version

basecamp-cli 0.7.2