/assemble-ppmplugin

The final step: take the label (manifest.json from /generate-ppmplugin-manifest) and the binaries the build skills produced, zip them into the single <name>.ppmplugin file, and verify the box contains exactly the right items. The output is the deliverable — the file you can hand off / upload. Before zipping, it reconciles the manifest's declared platforms against the binaries that actually built, so the shipped bundle never claims a platform it doesn't contain.

Read shared/ppmplugin-format.md §1 — the bundle layout this skill produces and verifies.

What this skill does NOT do

Does not author the manifest or build any binary — it consumes the staged outputs of the prior third-party-control skills (manifest + the build skill(s)).
Does not upload to Dataverse / wire into a canvas app (Stage 3 — deferred).
Does not build any binary — it consumes whatever the build skills staged (android/<Pascal>Plugin.dex from /build-android-binary and/or ios/<Pascal>Plugin.framework/ from /build-ios-binary) and bundles those present.

Step 1 — Read shared docs + prereq block

Read shared/shared-instructions.md and shared/ppmplugin-format.md.
Prereq: jar (ships with the JDK). Print the visible block (shared-instructions §9.2):