[oblomov-dev]

From the @abap2ui5/node-runtime release after 1.147.0 on, the package transpiles a host's classes together with the framework and writes an entry point into the host's own output (abap2UI5/abap2UI5#2916). That is what the transpiler's maintainer asked for on abaplint/transpiler#1999 (closed), instead of an option that leaves a library out of the output. This PR builds the dev apps that way on such a release. Older releases build exactly as before.

What changes

• fullTranspileOf recognises a release that can do this: it records abap2ui5.expressIcfShim and carries setup/transpile.mjs and srv/framework.mjs.
• buildFull transpiles everything in one run:
  • inputs: the sandbox and the package's downport/;
  • libraries: open-abap-core and express-icf-shim, given by url (the url names each library's folder in the output). Both are fetched at the recorded commits by ensureGitLibrary, generalised from ensureOpenAbapCore;
  • output: a staging folder that becomes the new apps/, a complete runtime. Its init.mjs creates every table and its runner is left exactly as the transpiler wrote it.
• Entry point: the package's own writeEntry( ) writes host.mjs and claim.mjs into apps/. It runs as a child with the output as argv[1], so the module does not start its CLI. The build adds boot.mjs.
• Nothing is rewritten.
• npm-host: a full build is booted through apps/boot.mjs, and the exports come from apps/host.mjs. The package's own entry point is never imported; it would load a second runtime, which the package refuses.
• app_list: on a full build, apps/ also holds the framework, so dev and framework apps are told apart by the sandbox's names, as on a checkout.
• Additive result fields: the build result gains full and expressIcfShim, and the build record gains layout: "full". CHANGELOG and AGENTS.md describe it.

Tests

• Fixture: a new layout: 'full' release whose package entry point throws when it is imported.
  • npm-runtime.test.mjs checks:
    • apps/ is a complete runtime, and the transpiler's imports are left untouched;
    • boot.mjs and the build record are correct;
    • the runner runs from apps/;
    • an unchanged build is skipped.
  • npm-host.test.mjs checks that the full build is served through apps/host.mjs.
  • npm-backend.test.mjs covers the pure helpers.
• Real package: I ran the server against the release packed from abap2UI5#2916, with the real transpiler and real git fetches:
  • a changed build took 16 s including both fetches (8 s on the old path);
  • an unchanged build took 0 s;
  • the unit test passed;
  • z2ui5_cl_ui5_app_hi_world and the own app started, and the framework caught the app's own exception (500 naming ZCX_E2E_ERROR);
  • app_list labelled the apps correctly.
• Suites: npm run check gives 554 passed and 17 skipped. With A2UI5_MCP_NETWORK_TESTS=1, npm-integration.test.mjs against the published 1.147.0 (old path) passes.

Lands safely before the release: on 1.147.0 and earlier nothing changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GPMAtn6BycCF2mKRUHGpek

---

Generated by Claude Code