Package Lifecycle API
The /lifecycle entry point provides one implementation for local builds, CI checks, and explicit publication. Every operation compiles the same authoring definition and applies the same verification contract.
Configure a Command Builder
commandTargetBuilder adapts a project-owned build command to the SDK TargetBuilder contract. The command receives the selected target, immutable release, staged descriptor, staging root, target output root, and resolved target definition through environment variables.
The adapter captures bounded command output. A nonzero exit, signal, or process error rejects the active lifecycle before package assembly.
Build and Check
buildTapMiniapp compiles authoring, validates the staged descriptor, runs each target builder, assembles and verifies a portable package, invokes project verification hooks, and atomically replaces output. checkTapMiniapp runs the same path in temporary output and then removes it.
Neither operation invokes a publisher. A failed build preserves the previous complete output and removes its temporary staging transaction.
Publish Explicitly
publishTapMiniapp requires one publisher adapter in the authoring config. Without from, it performs the complete build path and publishes the verified staged package. With from, it revalidates an existing assembled package before invoking the adapter.
Publication receives exactly one verified package. Missing adapters, tampered artifacts, invalid locks, project hook failures, or publisher failures reject without mutating the assembled package.