[Yue-Zhengyuan]

Add OrthAdjoint for differentiating both left_orth(!) and right_orth(!). QRAdjoint is now its compatibility alias.

They will be useful in #422 (SI-CTMRG projector) and #441 (split-CTMRG).

[codecov]

Codecov Report

❌ Patch coverage is 95.34884% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/utility/orth.jl	95.23%	2 Missing ⚠️

Files with missing lines	Coverage Δ
src/Defaults.jl	85.71% <ø> (ø)
src/PEPSKit.jl	100.00% <ø> (ø)
src/algorithms/ctmrg/c4v.jl	89.88% <ø> (+89.88%)	⬆️
src/algorithms/ctmrg/ctmrg.jl	81.11% <ø> (+71.69%)	⬆️
src/algorithms/ctmrg/projectors/c4v_qr.jl	64.28% <ø> (+64.28%)	⬆️
src/algorithms/ctmrg/projectors/projectors.jl	87.50% <100.00%> (+50.00%)	⬆️
src/utility/orth.jl	95.23% <95.23%> (ø)

... and 93 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leburgel]

If this is possible, I would prefer to use one struct for both the QR and LQ pullback hooks. The QRAdjoint name predates the MatrixAlgebraKit update which now allows passing one algorithm (e.g. HouseHolder) to both left_orth and right_orth, but now it might be good to do something similar in spirit for the pullback hooks.

[pbrehmer]

I agree with Lander that it would be nicer to have a single OrthAdjoint struct (and at first glance this seems straightforward to add I think?) but other than that this looks good to me!

[pbrehmer]

I only have minor comments now, otherwise this is good to go for me.