Docs
Release candidate notes
The public summary of the mmflow npm SDK release-candidate scope. The full repo manifest lives in docs/release-candidate.md.
Planned RC version
0.1.1
Phase 18 prepared this value for review across the five npm SDK packages. Phase 21 enables a guarded maintainer-triggered npm workflow without publishing from PR verification.
What this does not do
No registry publishing, git tags, GitHub releases, production deploys, billing/auth changes, trading execution, new market-data APIs, or archive schema changes happen during PR verification. Actual npm publish requires publish=true, version 0.1.1, and confirm publish-0.1.1 after merge.
Included packages
@mmflow/charts@mmflow/react@mmflow/vue@mmflow/indicators@mmflow/sdkRC verification
Package metadata and versions remain at planned RC version 0.1.1.
npm package dry-run, smoke imports, examples, and export audits are part of release:rc:check.
release:publish:plan, release:publish:dry-run, release:publish:guard, release:publish:npm, and release:postpublish:verify cover guarded release operations.
Docs and examples describe local workspace/pre-registry status honestly.
No packages are published, no git tag is created, and no GitHub Release is created during PR verification.
Launch-readiness docs
The canonical repo documents are docs/release-candidate.md, docs/launch-checklist.md, docs/release-operations.md, and docs/npm-release-notes-0.1.1.md. App pages link here so public navigation does not point at markdown files that may not be served as routes.