feat(new-pane): reduce master-stack transition churn #126

Merged

barrettruth merged 1 commit from feat/master-stack-transition-churn into main

2026-04-28 05:20:11 +00:00

barrettruth commented

2026-04-28 05:18:55 +00:00

Problem

master-stack still fell back to generic append when n = m > 1, so the first stack pane was born by splitting a master instead of appearing in the future stack branch.

Solution

Add an all-masters master-stack new-pane path for n = m > 1: split the tail directly for left and top, split the first master then bubble to the tail for mirrored right and bottom, and add fast-path plus acceptance coverage for the remaining topology change. This keeps the mirrored 1 -> 2 policy tradeoff out of scope for #114. Closes #112.

## Problem `master-stack` still fell back to generic append when `n = m > 1`, so the first stack pane was born by splitting a master instead of appearing in the future stack branch. ## Solution Add an all-masters `master-stack` `new-pane` path for `n = m > 1`: split the tail directly for `left` and `top`, split the first master then bubble to the tail for mirrored `right` and `bottom`, and add fast-path plus acceptance coverage for the remaining topology change. This keeps the mirrored `1 -> 2` policy tradeoff out of scope for `#114`. Closes #112.