[Brian Krabach (bkrabach)]

The independently buildable workspace metadata package has no standalone publication path. Add it to the existing finite component publisher while preserving its amplifier-workspace-metadata distribution and amplifier_workspace_metadata import.

The dedicated workflow builds one wheel/source archive from an exact selected revision, verifies their source-bound bytes, and tests that same installed wheel outside the checkout. Explicit publication from main uses the existing immutable tag/assets and draft-recovery rules under workspace-metadata-vX.Y.Z; it never replaces the app latest release. Existing components retain their names and selection behavior.

Validation on exact 38b986c13489fcb26a2420b7bd89efd794b03578:

• 64 maintained publisher controls passed, including workspace identity, first/partial/completed publication and changed-asset refusal using a fake GitHub API.
• All six existing workspace metadata tests passed against the actual installed wheel in an owned Linux ARM64/Python 3.13 environment. The import came from that environment; Unified, Core and Foundation were absent. Runtime dependencies remain empty.
• Ordinary isolated wheel/sdist build plus exact Git/source/asset checks passed on first execution. Qualification SHA256: 54cf9110479315a43eec955e3b1b68e30f90ca542fb3d1131549e010b086361d.

No version change, tag, publication, app adoption, runtime/workspace behavior, identity migration or new publisher framework. Linux qualification does not establish Windows/macOS acceptance. Standalone installation remains separate from Unified; do not coinstall their overlapping package ownership.