The distributable is the terminal artifact, and a library-form application stages its runtime files (#622)

[Sunrisepeak]

Two defects the plugin half of #622 surfaced while packaging an Android application against the merged engine (#623), fixed before the 2026.9.12.3 tag.

• mcpp pack --format <name> and mcpp run --format <name> report the request's terminal artifact: the output of an introduced artifact action that no other introduced action consumes. A provider that is a chain (dist-apk: link, add libraries, align, sign) had its first output, the unsigned base.apk, handed to adb-run, and adb install refused it. Intermediate outputs are still verified to exist; mcpp run refuses a format that ends in more than one file, naming them. tests/e2e/656 now uses a two-step provider.
• On a row where an application's form is a shared library (kind = "app" on *-linux-android), mcpp pack staged only lib/<name>.so; the files deploy placed under bin/<to>/ never reached the staged tree, so dist-apk's assets/ was empty. They are staged at the same relative path under bin/ as on every other row. tests/e2e/652b deploys a file and asserts it.

docs/10 and its zh mirror state the terminal-artifact rule; CHANGELOG [Unreleased] carries both. Verified locally with the bootstrap 2026.9.12.2: e2e 656, 652b, 638, 651, 649 pass; mcpp test pack 8 passed.