Automations : enabled local + config v3 + badge source

[64ix]

Parent

#130

What to build

How synced Automations behave on the second machine. An imported Automation arrives disabled (its enabled state is machine-local, defaulting off on import) with an "imported, disabled" badge and a source marker. A repository-instance automation target is stored without a machine-local workspace id (schema v3) and resolved at run time against the mounted project's own repository workspace, failing before creating a task if the Project is Unattached.

Acceptance criteria

• An Automation imported from the other machine is disabled by default and shows an "imported, disabled" badge; a source field distinguishes it.
• A repository-instance target is stored without a machine-local workspace id and resolves at run time to the local project's repository workspace.
• Running an automation for an Unattached Project fails cleanly before creating a task (no zombie task).
• Config edits on one machine sync to the other (whole-row LWW) while enabled stays local.

Blocked by

• 3 (engine), 6 (Unattached Project state — the run-time failure path targets it)