[oblomov-dev]

Why

Coverage read 100 % only because 48 demo kit samples were excluded by the rule "the control must exist since UI5 1.71". src/02 already holds 221 ports that need a newer runtime for a member, so excluding a newer control was inconsistent. The maintainer decision is to drop that exclusion.

Coverage is now 669 / 669 (12 hold-outs reserved). The only samples left unported are 20 on deprecated controls, 37 that are not app views (OPA5, routing, view templating) and 3 demo apps without a control.

Rule change

• generate-coverage.mjs: scopeOf no longer returns newer. A port of a post-1.71 control must carry a POST_171 deviation naming the control (the gate fails otherwise); that deviation files it under src/02.
• scaffold.mjs: writes that deviation and scaffolds straight into src/02. It also no longer clips GROUP-nested names to an identical sap.m... description.
• scope-of.mjs reports such a control IN_SCOPE. lib-packages.mjs reads the release level from POST_171 only, so the four newer entries of ui5/scope-exceptions.json are gone.
• AGENTS.md, README, TRAINING.md, the generation prompt, the skills and the golden fixtures are updated.

Ports: apps 624–671, all in src/02

Batch	Control	Apps
b52	sap.m.Avatar	624–628
b53	sap.m.IllustratedMessage	629–638
b54	sap.m.DynamicDateRange, sap.m.ExpandableText	639–643
b55	sap.m.p13n Container/Engine/Popup, sap.m.VariantManagement	644–651
b56	sap.m.plugins.UploadSetwithTable	652–661
b49	sap.f.AvatarGroup, SidePanel, ProductSwitch	662–666
b50	sap.f.HeroBanner	667–671

What could not be ported 1:1 is declared in the sidecars:

• Illustration sets: there is no way to call IllustrationPool.registerIllustrationSet, so 630 and 635–638 show no Custom/tnt illustration. This is a new ❌ row in CAPABILITIES.md.
• Function-typed properties: p13n.Popup.reset, FilterPanel.itemFactory, itemValidationHandler, customPageContentHandler and app-written DynamicDateOption subclasses have no equivalent.
• p13n Engine (645–649): the controller logic runs in ABAP. The Popup is a fragment that is built per press and destroyed on close.
• Uploads (652–661): emulated by vetoing beforeUploadStarts; the backend adds the row.

Live verification

Every new port now has an e2e interaction module, and all 25 LIVE_TESTs are closed. STATUS.md shows 0 open. The interactions found and fixed real defects:

• DynamicDateRange (639, 640, 642): toDates() returns UniversalDate objects, so every row was filtered away. The dates are now sent as .getJSDate().
• p13n (645, 648, 649): a never-opened p13n.Popup leaks its panels in UI5, and the second re-render died on a duplicate id.
• 650: JSON.stringify is not available in event-handler expressions, so no request was ever sent.
• 651: the bound VariantItem template broke the favourites list on UI5 1.152, and translate() failed on the transpiled runtime.
• 644: the new view's name now matches the original.
• 638: the countdown tick no longer flashes the busy indicator.

e2e harness

• e2e_smoke.theme (new sidecar opt-in): boots a port with the theme CSS. sap.f.AvatarGroup (662) loops when unthemed; with the theme it passes. The opt-in is re-verified each run and fails as stale if the port also passes unthemed (641 uses it too).
• App 600: its interaction now waits for in-flight POSTs instead of the busy indicator, which UI5 shows only after a delay. That wait was flaky under full-corpus load.
• Apps 351, 353 and demo_004: their modules compare origins instead of hard-coding port 3000.

Shared changes

• view-gates.mjs ADVISORY_BUDGET: follows what the originals carry (+14 missing-accessibility, +13 editable-control-without-binding, +1 event-on-disabled-control).
• 7bit_ascii: the excludes gain 649, 668 and 671 (Müller, €). The source rule set changes first in app-rules: exclude samples-controls apps 649/668/671 from 7bit_ascii abap2UI5#2928, and check-app-rules stays red until that PR is merged. Copies are in abaplint: exclude samples-controls apps 649/668/671 from 7bit_ascii samples#884 and conformance apps: exclude samples-controls apps 649/668/671 from 7bit_ascii protocol#10; samples-stack still needs the same line.
• Docs: the journal entry in docs/history.md, and the e2e-debugging guide records the lessons above.

Validation

• npm run gates: green.
• npm test: 64/64.
• view-gates --strict with render: 670 ports, 0 failing.
• abaplint, standard and cloud: 0 issues.
• CI abap-702: green.
• e2e:
  • all 48 new ports pass on a rebuilt backend;
  • the full-corpus run's remaining failures were the three port-hardcoded modules (now fixed) and a one-off framework flake on 545 that passes on re-run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PTMAfPJZ78qd9zmLoHGZwx

[oblomov-dev]

check-app-rules is red because this PR adds 649, 668 and 671 to the 7bit_ascii excludes. The check compares against abap2UI5 main, and the shared rule set there only changes with abap2UI5/abap2UI5#2928. Nothing in this PR can fix it: once #2928 is merged, a re-run turns it green.

The copies in the other consumers are in abap2UI5/samples#884 and abap2UI5/protocol#10. samples-stack still needs the same one-line copy. I could not reach that repository from this session.

e2e_pr went red on app 662 (sap.f.AvatarGroup): Rendering has been re-started too many times. The cause is the harness, not the port:

• The harness boots UI5 unthemed, and AvatarGroup measures its unstyled avatars and loops.
• With the theme CSS loaded it renders once.
• c37bd33 adds a sidecar e2e_smoke.theme opt-in that boots such a port with the theme CSS. The opt-in is re-verified each run and fails as stale if the port also passes unthemed.
• Locally, 662 now passes with the theme.

---

Generated by Claude Code