chore: bump the pinned abap2UI5 framework commit

A2UI5_PIN

@@ -1 +1 @@
-e4d89a69c7fe7f6c2652ef7852a1eb012e98714d
+d4b17595d3a858e558e94a96e655f73645f9becd

AGENTS.md

@@ -736,7 +736,7 @@ comes to say a port is blocked when it is not (and the reverse):
 
 | Pin | Where | Answers |
 |---|---|---|
-| `A2UI5_PIN` is a **commit** on main and reads `e4d89a69` | root file; `node-setup`, the web/Pages build and `bump-a2ui5.yaml` read it | **What a port DOES.** The transpiled backend, the e2e smoke and every reproducible build run this framework, so it decides whether a frontend action, an event-arg projection or a `control_by_id` method exists at all. A sidecar sentence about a wire working or not working is a statement about THIS pin, and `check_pins` policy 6 holds those sentences to it. The weekly bump moves this cell with the pin (`node scripts/check-pins.mjs --fix`, called from `bump-a2ui5.yaml`) - it rewrites only present-tense claims in the top-level prose, never a sidecar and never a sentence in the past tense. |
+| `A2UI5_PIN` is a **commit** on main and reads `d4b17595` | root file; `node-setup`, the web/Pages build and `bump-a2ui5.yaml` read it | **What a port DOES.** The transpiled backend, the e2e smoke and every reproducible build run this framework, so it decides whether a frontend action, an event-arg projection or a `control_by_id` method exists at all. A sidecar sentence about a wire working or not working is a statement about THIS pin, and `check_pins` policy 6 holds those sentences to it. The weekly bump moves this cell with the pin (`node scripts/check-pins.mjs --fix`, called from `bump-a2ui5.yaml`) - it rewrites only present-tense claims in the top-level prose, never a sidecar and never a sentence in the past tense. |
 | the **`main` branch** | `"branch"` on the abap2UI5 dependency in `abaplint.jsonc` and `abap_cloud.jsonc` | **Whether the corpus COMPILES against the current framework.** Until 2026-08-31 this was a release tag ("does it compile for a reader") — but that coupled every merge using new framework API to a framework RELEASE, and releases are monthly snapshots that never gate a merge (maintainer decision, the hash_* wave). What a port needs beyond the latest release stays in its sidecar prose ("needs abap2UI5 newer than x.y.z"); `check-pins.mjs` policy 2 enforces the explicit `"branch": "main"`. |
 | the **`702` branch** | `"branch"` on the abap2UI5 dependency in `.github/abaplint/abap_702.jsonc` | **Whether the corpus DOWNPORTS.** The framework's own `auto_downport` rebuilds that branch from main, so it is the one moving target in the build set — an allowlisted, reasoned exception in `check-pins.mjs` (policy 2) because `"branch"` feeds `git clone --branch`, which takes a branch or a tag and never a commit. The 702 build is therefore not byte-reproducible, and a 702-only failure that nothing here changed is the first thing to suspect on a branch-head move. |