when you run for example chainloop att init --workflow my-wf --contract my-contract ... what happens is

1 - a new workflow called my-wf is created (if it doesn't exist) associated with the contract my-contract
2 - a new run is performed

This means that if you after the first run, you provide another contract name chainloop att init --workflow my-wf --contract contract-2, the first contract (my-contract will be used, in other words, the provided contract-2 will be ignored, which was reported as unexpected behavior