## Description

Migration `1786279107` fails when the active bar uses a custom clock widget instead of `omarchy.clock`.

The bar configuration uses this custom clock ID:

```json
{
  "id": "fcabral.clock"
}
```

The migration runs:

```bash
omarchy bar put omarchy.keyboard-layout --after omarchy.clock
```

## Steps to reproduce

1. Configure a custom clock widget with an ID different from `omarchy.clock`.
2. Run `omarchy update`.
3. Let migration `1786279107` execute.

## Actual behavior

The update reports:

```text
Running migration (1786279107)
Add the keyboard layout widget to the bar
omarchy-bar: Not ready to accept queries yet.
```

After the shell is ready, the migration can be reproduced with:

```text
omarchy-bar: could not find target widget omarchy.clock
```

The update then reports that something went wrong. The migration remains pending.

## Expected behavior

The migration should detect the active/custom clock widget, use a valid fallback position, or otherwise complete without failing when `omarchy.clock` is not present.

The migration comments appear to describe fallback behavior, but the current implementation fails when the target widget is absent.

## Workaround

The migration succeeds after manually placing the widget relative to the custom clock:

```bash
omarchy bar put omarchy.keyboard-layout --after fcabral.clock
```

Then `omarchy update` can be run again.

## System information

Omarchy version:

```text
4.0.0.r1614.g4cc1493-1
```

Debug log: https://logs.omarchy.org/Bs6LDL