When main is taking new commits but there is no conflicts it should not push lowest feature branch to rebase over and over

[DanialRazaviAtPropertyMe]

When main is taking new commits but there are no conflicts, it should not push the lowest feature branch to rebase over and over.

Current Problem:

Wasted CI/CD Credits: Re-running full test suites on unchanged layers drains resources.
Reviewer Fatigue: Constantly triggering notification spam for trivial branch updates.
Merge Queue Friction: Creating artificial bottlenecks at the bottom of the stack.

Proposed Optimizations:

Lazy Rebasing: Defer rebasing lower layers until a conflict actually occurs.
Virtual Merges: Let the UI simulate the merge against main without updating the branch.
Trimming Behavior: Only trigger cascading updates if a layer’s direct parent changes.

Expected Behavior:

Static Stacks: Lower branches remain untouched if their specific files are clean.
Smart Cascades: The stack only updates when an explicit conflict breaks the chain.