Track workflow renames

[josephjclark]

Difficult branch to resolve issue #1594 and replace PR #1587

The basic problem we have is this:

Locally, the CLI uses an id, derived on checkout from a workflow's name, to identify workglows. This id is used as a key in various bits of tracking.

When a workflow name changes in the app, or if a user renames a workflow on the file system, the id changes and a lot of the tracking against that workflow breaks.

Now this can be resolved simply with a fresh checkout, which is what #1587 does. But a deploy shouldn't do a full checkout, and it encourages workflow folders to be deleted, rather than renamed.

What I want is better tracking of workflow identity so that a rename isn't totally distructive.

Here's how we're achieving that.

What this PR basically does is track the UUIDs of each workflow in the checkout.yaml file, and uses UUIDs to match local to remote workflows. When a workflow name changes locally, the id and local paths arent updated - they basically are used as aliases. Users can fix the local paths if they want, or maybe we'll add CLI utils for this. But for now, paths stay the same.

Here's a bit more detail on the changes:

• Track each workflow's UUID in checkout.yaml
• Add a util to track workflows where the id may have cahnged
• When merging, use UUID as the primary identiifer to track a workflow
• Better tracking for workflows on deploy

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

• I have used Claude Code
• I have used another model
• I have not used AI

You can read more details in our
Responsible AI Policy