[marklearst]

Summary

• recover the package-family prerelease as 1.0.0-next.1
• accept npm's required bootstrap latest only while a package has no stable history
• extend bounded registry propagation checks and remove prerelease dist-tag mutation
• record the partial next.0 attempt accurately and make @next explicit in prerelease examples

Root cause

The first next.0 publish created @primitree/core, but npm's root metadata and provenance propagated after the original polling window. npm also assigned the new package a required bootstrap latest tag. The retry then failed because the release controller tried to delete that tag.

This change keeps next authoritative, validates complete version history before accepting a prerelease latest, and still rejects prerelease latest after any stable version exists.

Release impact

All six public packages are aligned at 1.0.0-next.1. The previous immutable tag and published core next.0 remain as a truthful partial release record.

Validation

• full formatting, lint, typecheck, unit, and coverage gates
• release contract and controller tests: 141 passed
• release metadata and six-package artifact verification at 1.0.0-next.1
• packed tarball consumer
• Playwright: 49 passed
• public prose, brand, links, API generation, and production docs build
• independent publisher and runbook audits

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
primitree	Ready	Preview	Aug 17, 2026 3:13pm