Optimistic drag inconsistency after returning placed card to hand creates local-only placements

[khushal-winner]

Describe the bug
when player already placed a card on the table and if he drag the card from the table back to hands it appear to be happening in the UI, but not happening actually, and after putting the main "your card" in the hands again, the player can move as many cards to the table other than "your card"
it only appears to be happening in the UI but not actually happening in the backend, only creates inconsistency. it only syncs when some other player puts card on the table.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://copi.owasp.org/games
2. create a new game make 3 players join
3. place any card on the table.
4. move back the card in the hand, and try putting cards on the table other than "your card"
5. see all the cards are appearing to be placed on the UI

Expected behavior
Once the player placed the card on the table , there should be 2 expected things should be happening :
1. normal behaviour
when placed the card on the table , the cursor should be blocked from both the table cards and hands cards.

2. better UI/UX behaviour
when placed the card on the table, the player can only move the hand cards and his table card only in the non intercepting constraint boundaries creates a better UI/UX, they can move the cards in certain boundaries and when released back to the original position

Video Demo

2026-03-03.15-01-00.mp4

Desktop (please complete the following information):

• OS: All
• Browser All
• Version All

Smartphone (please complete the following information):

• Device: All
• OS: All
• Browser All
• Version All

Additional context
the game is working perfectly fine , this update will make the UX more better

[khushal-winner]

2. better UI/UX behaviour
   when placed the card on the table, the player can only move the hand cards and his table card only in the non intercepting constraint boundaries creates a better UI/UX, they can move the cards in certain boundaries and when released back to the original position

this would be a better choice, In my opinion, @sydseter

[rewtd]

Once a card is played you should not be able to unplay it. Maying the UI do what the backend already enforces is the right choice here, I think.

[khushal-winner]

Got it @rewtd , aligning the UI to strictly match the backend rule ('once played, can't unplay') by disabling drag on table cards & hands too entirely makes the most sense and avoids any desync/confusion. Thanks for the clarity, can u assign this to me, happy to start working ASAP :)