Compare two branches

I must compare branch feature/session-cache against main to prepare the merge. Show the file diffs between feature/session-cache and main, list the files added, modified, or deleted, and identify any conflicts that will occur on merge. Also produce a short summary of functional changes to session handling.

Before I open the PR to merge feature/session-cache into main, make the comparison easy to approve: surface the diffs that affect public session APIs up front, summarize behavioral changes and performance impacts, flag any changes that touch auth or persistence layers, and list potential merge conflicts with recent main commits.

CI went green for feature/session-cache compared to main, but the security reviewer suspects a session regression in edge cases. I don’t know which tests would catch it. Which targeted tests or manual checks should I run against the diff to reassure reviewers, and who on the team should sign off last before I merge?

Our team regularly merges feature branches that pass CI but cause user-facing regressions. Where are we failing — test coverage, review depth, or merge timing — and what repeated habit change will reduce regressions the most? Recommend a single gating rule we can adopt this month and how to enforce it without blocking small fixes.