domains / families / software-engineering / assemble-ppmplugin

assemble-ppmplugin

separate

Assemble the final `.ppmplugin` binary bundle for a PAM native extension and verify its contents. First **reconciles** the manifest's declared `entrypoints` against the binaries actually staged — if the manifest declares a platform with no built binary it gates (build it / ship without it / stop) rather than shipping a broken bundle. Then re-runs the plugin's upload-compatibility checks on the reconciled manifest, zips the manifest plus whichever of `android/<PascalName>Plugin.dex` and `ios/<PascalName>Plugin.framework/` are present into `ppmplugin/<name>.ppmplugin`, and verifies the archive layout with `jar tf` (exactly the manifest + the shipped binaries — nothing missing, nothing extra). Output: a statically verified `.ppmplugin` file on disk. Prereqs: `jar` (JDK). Run after /generate-ppmplugin-manifest and the build skill(s).

When to use

• Reconcile manifest entrypoints against staged binaries
• Zip manifest and binaries into .ppmplugin
• Verify archive layout with jar tf
• Run upload-compatibility checks on reconciled manifest

When not to use

• Author the manifest
• Build any binary
• Upload to Dataverse
• Wire into a canvas app

Skill page

Source