growthub-cms-sdk-v1

To parse NDJSON execution event streams, you read the per-node execution events sequentially to extract individual node outcomes and generate execution summaries for hosted workflows. This allows structured interpretation of continuous execution streams.

A capability manifest defines the available operations for hosted execution. You need to validate node schemas when structuring workflow payloads to ensure type-safe interaction with the CMS API contract before executing workflows.

You enforce type-safe payloads for a CMS API contract by validating node input schemas against the capability manifest. This ensures workflow payloads conform to the expected structures, preventing runtime type errors during hosted execution.

No, this SDK requires the @growthub/api-contract package to function. It enforces API_CONTRACT_VERSION 1 and exposes subpaths for capabilities, execution, manifests, and schemas, making the package dependency mandatory.

The best way to structure workflow payloads for hosted execution is by reading capability manifests and validating NodeInputSchema definitions. This approach ensures type-safe payloads that predictably match the CMS v1 contract specifications.

The limitation of parsing NDJSON streams with a fixed API contract version is that the SDK strictly enforces API_CONTRACT_VERSION 1. You cannot process execution events or validate schemas from other contract versions without encountering compatibility errors.