Summary

Renamed the field name in result JSON from "action" to "result" for better semantic clarity.

Why?

The field name "action" in the result JSON was confusing because:

• An action is something you plan to do (future/present)
• A result is the outcome of what was done (past)

This change makes the distinction clearer:

• Plan JSON: Uses "action" field → what will be done ("create", "update", "delete", "skip")
• Result JSON: Uses "result" field → what was done ("created", "updated", "deleted", "skipped")

Changes

Before

{
  "files": [
    {
      "action": "created",
      "source": "/path/to/file.txt",
      "target": "s3://bucket/file.txt"
    }
  ]
}

After

{
  "files": [
    {
      "result": "created",
      "source": "/path/to/file.txt",
      "target": "s3://bucket/file.txt"
    }
  ]
}

Impact

• Breaking Change: Yes, this changes the JSON output structure
• Migration: Users parsing result JSON will need to update from action to result field

Testing

• Build successful
• All tests pass
• Manual testing with real S3 bucket confirmed correct JSON output

🤖 Generated with Claude Code