Safe placement → moved

This material is now part of the concepts deep-dive:

➡️ Stacked tables & Benchling reinitialise — see The danger zone & safe placement and The lane model and the row-overlap invariant.

Key rules (summary):

Always safe: above the title row; in columns outside the lane’s column band; under a cell’s own named range.
Content in a disjoint column band (a different lane) is always safe, even if it shares the same rows as the lane’s stack. Each lane’s row-shift is bounded to its own columns, so other lanes are never moved. ✓ Example: a Right table in cols E-G sitting at the same rows as a Left table in cols A-C — the gap at col D keeps them in separate lanes.
Do not place a table or loose content within another lane’s column span — especially under a wide table that bridges two column groups — because bridging joins both groups into one lane and a row overlap is rejected. ✗ Example: if a Wide table (cols A-G) straddles Left (A-C) and Right (E-G), Right becomes part of Left’s lane; any paste into Right raises SideBySideNotSupportedError. Move Right past the wide table’s right edge (cols I-K, say) to give it its own disjoint lane.
A floating shape (image or text box) anchored inside the lane band is flagged. The exception message names the shape and says how many rows down (or how many columns to the right, for a widen) to move it. After moving and re-running, the scan re-checks and proceeds.