Component releases

releases/foundation.json is a draft component manifest, not a platform release.

Component	Kind	Manifest version
Agentweaver.Abstractions	Contract	0.0.0
Agentweaver.Providers	Library	0.0.0
Agentweaver.Persistence.Postgres	Library	0.0.0
Agentweaver.Secrets.AzureKeyVault	Library	0.0.0
Agentweaver.Identity	Library	0.0.0
Agentweaver.Telemetry	Library	0.0.0
Agentweaver.Telemetry.AzureMonitor	Library	0.0.0
Agentweaver.ObjectStore.AzureBlob	Library	0.0.0
Agentweaver.Identity.Broker	Service	0.2.0

The manifest pins exact project-reference compatibility. Its Broker entry does not pin an image digest; the existing f989 image remains separate from this package baseline. The eight NuGet packages use the 0.0.0 initial baseline. Their initial release notes come from the archived P0 changesets referenced by the prior release receipt.

Each product component change needs a fresh .changeset record. The record names the manifest component ID and semver intent. Documentation-only changes do not need a changeset.

Validate and prepare

Run the validator:

npm run release:validate
npm run release:validate -- --base <full-base-commit-sha>

The base-aware form checks changeset coverage for changed components. CI supplies the pull request base commit.

npm run release:plan writes a source-bound plan under ignored artifacts/release/. It does not change component versions.

npm run release:apply updates manifest versions, project version mirrors, changelog, archive records, and a receipt. It requires a clean tree and a valid source-bound plan.

npm run release:pack builds and packs the manifest components. It writes local package and image artifacts. It does not push them to a registry or package feed.

Publication boundary

The manual publication workflow requires an explicit publish choice and environment approval. It publishes the prepared artifacts only.

The source has no platform release composition or deployment gate. Release preparation does not prove Azure acceptance.