Release manifest and generated package policy#

release/pulse-release-manifest.json is the canonical owner of the synchronized release version, documentation origin and exact segment, repository metadata, support tiers, package roles, direct-install guidance, supported entry points, and stability promises.

Beta candidate#

Candidate: Pulse 1.0.0-beta.1 — Beta
Version: 1.0.0-beta.1
Activation stage: documentation-release
License: Apache-2.0
Supported Node: ^22.14.0 || ^24.0.0
Minimum Node: 22.14.0
Release seal Node: ^24.0.0; the exact patch used is recorded in seal evidence
Reproducible publication toolchain: Node 24.18.0 with npm 11.15.0
Readiness register: release/release-preflight.json
Documentation inventory: release/documentation-inventory.json
Exact documentation: https://pulsecompute.io/v1.0.0-beta.1/
Runtime targets: 3
Packages: 18

The installed CLI ships the same machine-readable data as release-manifest.json. The atomic snapshot transaction aligns the Beta label, beta channel, release date, package metadata, and exact-version documentation inputs. Tooling can read the hosted JSON copy without scraping package READMEs.

Generated consumers#

The manifest drives:

all package README status blocks;
the package support table and tier pages;
package repository, homepage, and bug metadata;
supported-entry-point release checks;
release prerequisites and documentation classification;
exact-version documentation URLs;
the homepage target pipeline and release badge;
the hosted version banner and release search index.

Runtime targets#

ID	Label	Mode	Contract
`node`	Node	`execute`	Explicit Native and generally available JavaScript execution over one canonical application contract.
`fastly`	Fastly Compute	`execute-and-build`	Explicit Native direct-host-ABI Wasm and generally available JavaScript source/deployment candidates.
`none`	Compile only	`compile`	Compilation and inspection without a runnable provider target.

The target list is consumed by the public homepage and must stay aligned with the built-in provider support catalog and project configuration schema. Project-owned provider packages do not become official release targets merely because a project selects them through the namespace convention or an exact scoped package name.

Support tiers#

ID	Label	Promise
`canonical-application`	Canonical application surface	Fully documented and supported as the Pulse application authoring or workflow contract.
`supported-extension`	Supported provider/extension surface	Documented entry points are supported; implementation and toolchain subpaths are explicitly excluded.
`implementation`	Implementation/transitive surface	Installable as part of the synchronized release set, without an application-author compatibility guarantee.

Synchronized packages#

Package	Support tier	Canonical guide	Direct installation
`@pulse-compute/runtime`	Canonical application surface	Guide	Yes. Install it in every Pulse application.
`@pulse-compute/pulse`	Canonical application surface	Guide	Yes. Install it in every conventional Pulse project.
`@pulse-compute/cli`	Canonical application surface	Guide	Yes. Install the package globally or as a project development dependency.
`@pulse-compute/provider-fastly`	Supported provider/extension surface	Guide	Yes, for Fastly projects. Node-only projects do not need to import it directly.
`@pulse-compute/grip`	Supported provider/extension surface	Guide	Yes, only when the application uses GRIP/Fanout behavior.
`@pulse-compute/assets`	Supported provider/extension surface	Guide	Yes, only when the application uses the assets capability.
`@pulse-compute/crypto`	Supported provider/extension surface	Guide	Yes, when an application uses the crypto verification surface directly; JWT applications receive it transitively.
`@pulse-compute/jwt`	Supported provider/extension surface	Guide	Yes, when an application verifies JWTs.
`@pulse-compute/entities`	Supported provider/extension surface	Guide	Yes, when an application declares entity operations.
`@pulse-compute/wasm-build-support`	Implementation/transitive surface	Guide	No for application projects; it is installed transitively where required.
`@pulse-compute/wasm-compiler`	Implementation/transitive surface	Guide	No for application projects; use the pulse CLI.
`@pulse-compute/wasm-guest-link`	Implementation/transitive surface	Guide	No for application projects; it is an internal synchronized compiler dependency.
`@pulse-compute/wasm-contracts`	Implementation/transitive surface	Guide	Provider toolchain authors may install it for the versioned bootstrap contract; application projects receive it transitively.
`@pulse-compute/wasm-host-runtime`	Implementation/transitive surface	Guide	No for application projects; it is installed transitively.
`@pulse-compute/wasm-library-kit`	Implementation/transitive surface	Guide	No for application projects; it is installed transitively.
`@pulse-compute/provider-node`	Implementation/transitive surface	Guide	No for application projects; select provider: node through the CLI.
`@pulse-compute/wasm-runtime-core-as`	Implementation/transitive surface	Guide	No for application projects; it is installed transitively.
`@pulse-compute/wasm-schema-json`	Implementation/transitive surface	Guide	No for application projects; declare schemas in the selected .pulse/config.ts profile.

A package export that is absent from its manifest entry is not promoted to a supported application-author API merely because Node or npm can resolve it.