Editor: composition wireframe — pull-out, stacking, and simplify

docs/ux-second-pass.md

@@ -24,6 +24,17 @@ record the resolution into the contract (`docs/architecture/09`+`10` and the rel
   `storageErrorNotification` and `entityStorageErrorNotification` in `services/storage-errors.ts`
   and the import-quota copy in `services/transfer.ts`.
 
+- **"Row" vs "column" naming differs between the wireframe's pull-out and pair drags** — the
+  frame-margin pull-out chip/announcement (`pullLabel`, `commitDrop`) name the new full-span band
+  by its _spatial_ shape (a `vconcat` slot is "a new row above"; an `hconcat` slot "a new column
+  left"), while the pair-into-split chip/announcement use the _container_ convention (`hconcat` =
+  "row", `vconcat` = "column"). Both describe the same axis — pulling a view above a row and
+  pairing two views vertically are both a `vconcat` — yet one calls it a row and the other a
+  column. Each reading is locally sensible (a pulled-out band reads as a row; a 2-cell vertical
+  split reads as a column) but the divergence can confuse. Decide: unify on one vocabulary, or keep
+  the gesture-specific framing. In `components/CompositionWireframe.tsx` (`pullLabel`, the
+  `'row'`/`'column'` ternaries in `resolveDrop`/`commitDrop`).
+
 ## Deferred (not design debts, revisit on demand)
 
 - **Drag-and-drop field assignment** — chips are click/keyboard-first by design; drag would