PAM Native 1.22.7

PAM Native 1.22.7

Source commit: 3364058fe27eace31400965a9a1b2172e0075762 ([skip ci]).

Accepted after native regression, community project and application UI validation.

Fix

Android scroll views consume contentOffsetX/contentOffsetY requests once
each requested position is reached. Later child layouts or insertions no
longer replay an initial offset after scrolling to the last page. Requests
still clamped by insufficient content remain pending until content grows.
Explicit property changes can request a new position. End anchoring, keyboard
clearance and tokenized scroll requests keep their existing contracts.

Completed validation

• All three new regressions failed on 1.22.6 and passed on Android APIs 26/36.
  They cover both axes, relayout after reaching the end, and delayed content
  that must satisfy a pending request before consuming it.
• Final instrumentation: 52 renderer tests and one separate-process reload
  test per API 26/36, including the twelve existing scroll-container tests.
• PHP SDK suite, 547 PHP parses, protocol parity, Rust formatting, 207 Rust
  workspace tests and 214 JVM tests passed.
• Fresh native-ui (API 26) and native (API 36) projects passed launch,
  edit/reload/restore and counter increment, with no runtime errors.
• Application UI on API 36 retained the selected photo after swiping in both
  directions, waiting for relayout, double-tap zoom, pan and reset. Two-image
  creation passed crop, filter, reorder and review without publishing.
• All 12 release assets have verified hashes. Renderer/PHP/AAR reproducibility
  and package budgets passed; the Linux CLI checksum was verified.

Upgrade and limits

Rebuild the Android host after updating. PHP remains ^8.5; numeric protocol/
ABI identifiers and third-party dependencies are unchanged. The 1.22.6 image,
reload, cache-recovery and initial-property improvements remain included.
See migration notes.

No iOS source changes are included, and UIKit execution was unavailable on
Linux. Native correctness and emulator UI tests do not measure FPS. Final app
integration is validated separately from this framework release. Validation uses direct local commands,
without GitHub Actions.