The hardest part of adopting a reusable capability is often the application integration around it. Playstack now publishes a versioned integration manifest and integrity-checked templates beside integration-facing packages.
Complete dry-run plans
playstack add <capability> --dry-run --json reports the selected package closure, surfaces, adapters, persistence ownership, package-manager commands, database compatibility, and normalized integration requirements.
Those requirements can include module imports, provider tokens, routes, environment variables, database artifacts, raw-body and framework configuration, health checks, required tests, and unresolved application decisions. Adapter conditions ensure a Redis, BullMQ, Stripe, or other provider requirement appears only when selected.
Playstack authors; Megamono places
Playstack remains authoritative for capability correctness and template integrity. Megamono combines that contract with its Nx-aware repository inventory, plans destinations, reports conflicts, and materializes reviewed templates as ejectable application-owned code.
The CLI does not apply its JSON report or generate migrations. It validates package and peer ranges, exposes exact retry commands after a partial installation failure, and preserves the boundary between package-owned contracts and repository-owned composition.
Version JSON now includes the source revision, dirty state, and a content-derived build ID so locally republished prerelease builds can be identified independently of their package version.
