[ChrisRackauckas-Claude]

Ignore until reviewed. This PR was opened by an AI agent and must not be merged until a human has reviewed it.

Summary

LazyArrays 2.13 added materialize!(::MatLdivVec{<:UnitOrUpperTriangularLayout, <:PaddedColumns}) (LazyArrays/src/padded.jl:865), which overlaps this package's MatLdivVec{TriangularLayout{'U',_,AlmostBandedLayout}} methods on the B side. Aqua's ambiguity check on master fails with the pair for both 'U','N' and 'U','U', and a padded right-hand side throws MethodError: ambiguous at runtime.

Add the joint specializations. A padded RHS is zero past its data, so an upper-triangular solve only needs the leading square block of the factor (and the Zeros tail cannot be written into anyway). The prefix is obtained with public ArrayLayouts.colsupport + view, then back-substituted in place using strictly-upper almost-banded entries (banded superdiagonals plus fill rows, never j ≤ k) so storage is O(n) in the prefix length rather than a dense n×n copy. A zero pivot in the stored prefix throws SingularException(k) for non-unit UpperTriangular, matching the dense path; unit-upper solves still ignore the stored diagonal.

LazyArrays.PaddedColumns still appears in the method signatures because that is the layout name that has to match LazyArrays' methods to resolve the ambiguity; it is not public in LazyArrays yet. paddeddata is not used.

In-place ldiv! on Vcat(v, Zeros) uses these methods for all LazyArrays 2.x; out-of-place \ only keeps a padded RHS from LazyArrays 2.13 (older versions copy to a dense Vector first).

Also adds import LazyArrays so the module name is bound (the pre-existing LazyArrays.arguments calls in __arguments were already relying on it).

Test plan

• QA group reproduces CI failure unfixed: test/qa/qa.jl → 19/20, "Method ambiguity" (2 pairs)
• With fix: 20/20 pass on Julia 1.13
• In-place ldiv!(UpperTriangular(A), Vcat(p, Zeros)) matches the dense reference for UpperTriangular and UnitUpperTriangular on LazyArrays 2.0.0 and 2.14.2
• Out-of-place \ asserted on LazyArrays ≥ 2.13
• Negative upper bandwidths u=-1 and u=-2, both triangular variants, full-rank fill, vs dense reference
• Zero pivot in the stored prefix throws SingularException(2) like the dense control
• qa.jl keeps a qualified-access ignore only for PaddedColumns, with a comment that it is irreducible until LazyArrays declares the layout public

Risk assessment

• Risk: medium
• Blast radius: Adds two Base.materialize! methods for upper-triangular AlmostBanded solves with a LazyArrays.PaddedColumns right-hand side. The exported API is unchanged. The signatures must name non-public PaddedColumns to disambiguate; the solve itself uses public colsupport.
• Evidence: GROUP=Core (93 pass / 2 pre-existing broken) and GROUP=QA (11/11 alloc, 20/20 QA) on Julia 1.13.1 / LazyArrays 2.14.2.
• Independent review (round 1): Codex gpt-6-astra, CHANGES — non-public access, quadratic densify, inaccurate 2.13-inert claim.
• Independent review (round 2): Codex gpt-6-astra, CHANGES — negative-bandwidth back-substitution and missing SingularException on zero pivots. This update addresses those.
• Merge: ignore until reviewed — remaining PaddedColumns qualified access still needs a human.

Agent-Harness: Cursor Agent CLI
Agent-Model: auto
Agent-Session: ~/sandbox/goals/ci-green/work/cig-fabm91-r1/log.txt (local transcript, amdci2)