`limactl start` ignores edit flags for existing instances

[AkihiroSuda]

limactl start ignores edit flags such as --video and --cpus for starting an existing instance.
The flags are still applied for fresh instances.

[ginglis13]

@AkihiroSuda is the expected behavior that limactl start changes the actual configuration for that instance, or only that running occurrence of the instance?

i.e. is this expected:

$ cat ~/.lima/default/lima.yaml | grep cpus
cpus: 4
$ limactl start default --cpus 6 
...
$ limactl list
NAME       STATUS     SSH                VMTYPE    ARCH       CPUS    MEMORY    DISK      DIR
default    Running    127.0.0.1:60022    qemu      aarch64    6       4GiB      100GiB    ~/.lima/default
$ limactl stop default
$ limactl start default
...
$ limactl list # edited configuration, 6 CPUs
NAME       STATUS     SSH                VMTYPE    ARCH       CPUS    MEMORY    DISK      DIR
default    Running    127.0.0.1:60022    qemu      aarch64    6       4GiB      100GiB    ~/.lima/default

or this:

$ cat ~/.lima/default/lima.yaml | grep cpus
cpus: 4
$ limactl start default --cpus 6 
...
$ limactl list
NAME       STATUS     SSH                VMTYPE    ARCH       CPUS    MEMORY    DISK      DIR
default    Running    127.0.0.1:60022    qemu      aarch64    6       4GiB      100GiB    ~/.lima/default
$ limactl stop default
$ limactl start default
...
$ limactl list  # original configuration, 4 CPUs
NAME       STATUS     SSH                VMTYPE    ARCH       CPUS    MEMORY    DISK      DIR
default    Running    127.0.0.1:60022    qemu      aarch64    4       4GiB      100GiB    ~/.lima/default

[AkihiroSuda]

i.e. is this expected:

...
or this:

The former one