MigrateFields matched fields by key and type only. On every migrate door
(single move, bulk move, cross-workspace copy and its preflight):
- a value was carried into a destination field marked `computed`. It is
now dropped, with preflight reason `target_computed`.
- a value colliding on a destination `unique_scope` field answered 500
on single move (invocation_slug, which has an index), leaked the SQL
error through bulk move, and stored a duplicate on an unindexed unique
field. Provenance decides now, as TASK-2878 did for relation referents:
a CARRIED collision is dropped and reported as `not_unique`, and an
override or schema default that collides is refused with 409 conflict.
A required field emptied by the drop is refused as required.
One store check (UniqueFieldConflictsQ / DropCarriedUniqueCollisionsQ)
serves all four doors, including the tx-bound copy. The report names the
value, and names the item holding it only when the caller may see that
item. The activity row always uses the holder-free sentence.
Reporting, all additive and omitempty: warnings.not_unique on the move
response, the copy response and bulk updated[] rows; `detail` on the
preflight's dropped row; CLI copy dry run and result, plus ` dropped:`
lines on `item move` stdout; web copy dialog, move and copy toasts, and
the timeline move card. ToolSurfaceVersion 0.51 (behaviour bump).
The relation leg of the original report was already closed by TASK-2878.
Item 4 (terminal/abandoned state change) is PR 2. Out of scope and filed
separately: BUG-3200 (missing needs_value routes) and BUG-3202 (float64
precision; the migrateCopyFields comment now points there).
Claude-Session: https://claude.ai/code/session_01RYiqbqXmxQMoKHsGm8B77N
xarmian
fd95b79694