Changing worktree while having active LSP Clients

[asmodeus812]

So i think i stumbled upon an issue. The scenario is the following

1. Open a file (readme.md for example) from the master worktree
2. Have lsp clients auto attach and initialize (i.e the lsp root dir points at the master worktree dir)
3. Create another worktree and/orChange worktree (pre existing) to another one also having the same readme file
4. Git-worktree will understand the file already exists and execute the update on change, i assume (which is just e .).
5. The pwd will change but the lsp client remains attached and still points at the master worktree as root directory

So what options do we have here, this is reproducible for any type of file not just markdown, i gave it as an obvious example since it is easy to test with (pretty much all work trees will no doubt have that file existing). Another important points is that if you have a lot of files and by proxy buffers open from the old worktree and you switch, only the current might get refreshed to the one in the changed worktree, but the rest will still point to the old one, maybe that is somewhat of a useful usecase for others, but i see worktrees as somewhat independent and isolated and in that case the most straight forward solution is to just delete all buffers (related to the old worktree using prev_path).
As a workaround, could I just kill all buffers with the callback command that already exists as a settable property ?

[danielreis1]

any solutions here @asmodeus812