---
title: "Reconcile a card moved by another collaborator"
description: "Verify that a board reflects a prepared remote card move and that opening the card shows the same persisted column as the board placement."
canonical_url: "https://vostride.com/agent-library/collaboration/board-card-concurrent-move.md"
md_url: "https://vostride.com/agent-library/collaboration/board-card-concurrent-move.md"
content_kind: "recipe"
topic: "collaboration"
---

# Reconcile a card moved by another collaborator

Verify that a board reflects a prepared remote card move and that opening the card shows the same persisted column as the board placement.

## Risk

Realtime boards can leave duplicate cards in old and new columns or update placement without updating the card detail. A prepared external actor creates a controlled remote change while the browser observes.

## Fixtures

- A test board has columns Planned, Active, and Done with one card QA remote move initially in Planned.
- The fixture manifest records the card key, and a separate actor can move it to Active through an approved test interface.
- No other board changes occur, and the product defines a bounded refresh or realtime-update behavior.

## Steps

1. Open the board and verify the fixture card appears once in Planned and nowhere else.
2. Trigger the prepared remote move to Active and confirm its committed state through the fixture actor.
3. Wait for the documented update behavior, using the product refresh action if that is the contract, and verify the card appears once in Active.
4. Verify Planned no longer contains the card and Done remains unchanged.
5. Open the card detail and verify its status is Active, then reload the board and verify the same single placement persists.

## Expected results

- The final board contains exactly one visual instance of the original card key.
- The card detail status and independent committed state both identify Active.
- The original column loses its reference, preventing a stale duplicate from surviving the remote move.

## False-pass traps

- A new card in Active alone does not prove the old Planned instance was removed.
- Silently dragging the card locally would replace the intended remote-update observation with a different test.

## Cleanup

- Restore the card to Planned or delete the test board and stop the remote actor.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Collaboration QA recipes](/agent-library/collaboration.md)
- [Software factory QA library](/agent-library.md)