Add XML 1.1 tags and EL functions to both taglibs #131

Reviewed 2026-09-25 (America/Los_Angeles) against main at bd249f5. Execution order and cross-issue ownership: #169. Batch 03.

This scope replaces the dated implementation prescriptions in the original report and earlier comments; linked historical evidence remains useful but must be rechecked before implementation.

Implementation and dependencies

PR #168 implements this issue at 7bfa00f3242c8918b7d201c8e55bbd7b1b31e00e. #167 has already supplied facade/descriptor/invocation/parity tests, so that work must not be recreated. This issue and #168 form one delivery unit, not duplicate requests.

• Review and land Add XML 1.1 tags and EL functions to both taglibs #168 through normal PR review: three matching tag classes in each adapter, all three tag/EL functions in advanced TLDs and forXml11 in basic TLDs.
• Keep the descriptor exclusion list exactly {forJava}; parameterized invocation cases must exercise new tags and preserve null, Unicode and buffer-boundary contracts.
• Preserve XML 1.1-only control/reference guidance, text-versus-attribute distinctions and JSP/Jakarta source parity. XML 1.1 output must not be advertised for XML 1.0/HTML.
• Keep README/release notes aligned with the new surface and the intentional forJava omission.
• Coordinate Constrain OSGi imports to actual adapter API requirements and freeze bundle identities #137's minimum-core/package wiring so adapters cannot resolve against a core lacking their APIs; Render every current JSP and Jakarta tag/EL binding through isolated JSP engines #120 adds actual JSP-engine rendering coverage after the final TLD surface is known.

Review observed all 20 GitHub checks successful for the reviewed head and local parity validation across 33 files. This issue remains open until the implementation merges; no merge is performed by triage.