[area:live-data] Sorting a range that includes a live block: the next refresh puts the live columns back, and the columns typed beside them end up on the wrong rows #235

Found by the PO while reviewing #234 (#232), on a production build of 7fa77b2. Not touched by #234: sortSelection has no live-data guard on main either.

Repro (1280, Thai)

1. Live data → "ลองต่อ: ยอดขายสด" → Test → Save and add → Insert. The block lands at A1:G6 (sku, name, category, price, qty, total, updated_at), refreshing every 5 s.
2. In H2:H6, beside the block, type a note per row: n-CF-01, n-CF-02, n-BK-01, n-BK-02, n-TE-01.
3. Select D2 (price) and press "เรียงจากมากไปน้อย". The sort range grows over A1:H6.
4. Wait for the next refresh.

The sort moved the whole rows, the refresh rewrote A:G in the source's order, and H stayed sorted. Two notes now sit on the wrong product, with no message. The sort itself was announced as done.

Done when

• A sort whose range includes live-data cells (or a template's locked structure, check what it does today) is refused whole, with the note Say why a live-data or template cell refused an edit (#207) #231/Refuse a paste, fill, cut or delete that reaches live data, and say so (#232) #234 use under the cursor cell, naming the cells and the way out ("เอาออก" / "Remove").
• Sorting a range entirely outside a live block works as before, including a block to its left or right that the detected range does not reach.
• A unit test on the store and an e2e flow that sorts next to a live block, both red on main.

Part of the hold set (silent wrong values). Queue: after #51, before #219.