Phase 6: Release rehearsal and integration

[up2dul]

Objective

Prove the complete prerelease and consumption workflow before committing to 1.0.0.

Implementation checklist

• Consume the package from a registry artifact in a real project.
• Rehearse a Changesets prerelease through the next channel.
• Verify npm Trusted Publishing, provenance, tarball contents, changelog, and installation instructions.
• Collect integration feedback before 1.0.0.

Gate

A real application consumes the registry artifact, and every release check is repeatable.

Qalbwise consumes the exact registry release profanity-kit@0.1.0-next.2. The integration replaces its local English and Indonesian forbidden-word implementation with the package's public core, languages/en, and languages/id entry points. Local application validation completed successfully with no integration issue reported.

Dependencies

Begins after package, corpus, performance, and documentation gates pass.

Evidence

• Dependency installation: qalbwise/app@3a5fd5a
• Application integration: qalbwise/app@5997b6a
• Published prerelease: https://www.npmjs.com/package/profanity-kit/v/0.1.0-next.2
• GitHub prerelease: https://github.com/up2dul/profanity-kit/releases/tag/profanity-kit%400.1.0-next.2
• Successful publish workflow: https://github.com/up2dul/profanity-kit/actions/runs/34031089796

References

• docs/adr/008-release-engineering.md

[up2dul]

Stable release completed successfully.

• npm: profanity-kit@0.1.0
• npm dist-tags: latest = 0.1.0, next = 0.1.0-next.2
• GitHub release: profanity-kit@0.1.0
• Version PR: chore(release): version packages #33
• Successful Trusted Publishing and registry-verification run: https://github.com/up2dul/profanity-kit/actions/runs/34084474386
• SLSA provenance v1 attestation is present in the npm registry.

This completes the Phase 6 gate and the MVP release rehearsal.