HSLG Media

Tools Packaging

Tools Packaging module

Packages independent WordPress presenter and API plugins.

Independent release artifacts

These scripts package the browser presenter and WordPress components from reviewed source and approved assets. They must keep independent plugin identities and exclude build caches, signing material, development-only guides and fake native app components. Their output should be an installable ZIP, not the entire source tree accidentally placed inside WordPress.

Version and regression evidence

Package versions, expected WordPress paths, required entry files and output checksums should be visible in the release report. A successful ZIP integrity test proves archive structure only; staging activation, browser navigation and data migration tests remain distinct. Do not let the presenter ZIP become the source of the real mobile customer UI.

Failure response

If package contents include a private signing key, unexpected node_modules folder or demo fixture in a native export, discard that artifact rather than shipping with a warning. If the WordPress ZIP lacks its plugin bootstrap or expected bundled assets, packaging should fail before installation. Preserve the last verified version for rollback.

Source files in this module

Maintenance and evidence

Check all affected file references and the matching human-readable user/architecture page when source changes. Run the module’s contract or governance checks; staging, payment and native hardware tests remain independent of source inventory coverage.