Package canonical agent workflow sources for host adapters #81

VidXP currently packages its agent workflows as part of the Codex/OpenAI plugin tree. Define and validate the package-relative canonical workflow source that Codex, ChatGPT, Claude, and future supported host adapters consume without maintaining behaviorally divergent copies.

The shared ingest and evidence workflows should remain authoritative workflow guidance. Host bootstrap instructions, manifests, presentation metadata, and installation mechanics may differ by supported host.

Current implementation

• Keep one editable plugin tree at plugins/vidxp/.
• Include plugins/vidxp/ in source distributions.
• Copy the plugin tree into wheels at vidxp/bundled_plugins/vidxp/ during the build.
• Preserve a stable package-relative location used by the current Codex/Desktop integration.
• Assert the current Codex plugin manifest, three skill folders, and OpenAI metadata in wheel builds.
• Define which packaged files constitute the host-neutral canonical workflow snapshot.
• Keep host-specific bootstrap skills and metadata outside that shared-source contract.
• Provide a stable discovery interface for host-package assembly without requiring consumers to understand the Codex bundle layout.
• Assemble supported host packages from the canonical source without maintained workflow copies.
• Assert the canonical workflow snapshot in both wheel and sdist artifacts.
• Document how each host adapter consumes the packaged source and adds its own metadata.

Required properties

• The canonical workflow source is versioned with VidXP releases.
• Host packages preserve shared workflow behavior while allowing host-specific metadata and lifecycle operations.
• Build and validation checks detect missing files and behavioral drift.
• Packaging does not install skills into an agent host or modify user configuration.
• Installation remains explicit, conflict-safe, and owned by Package and install VidXP agent skills across supported hosts #49 and its host-specific follow-up work.

Non-goals

• Defining one manifest or filesystem layout that every host must support.
• Treating Codex-specific installation guidance as portable workflow content.
• Completing every host marketplace, review, or remote registration flow in this issue.

This issue provides the packaging foundation for the broader supported-host distribution work in #49.