docs: add release documentation and LICENSE [4/4]

[wyattjoh]

Summary

#43, #47, and #45 add a non-trivial release pipeline with three channels, multiple CI workflows, and safeguards that aren't obvious from reading the code alone. Without documentation, contributors won't know how to cut a release, what the channel model is, or what guardrails exist.

This PR adds:

• docs/releasing.md -- documents the full release flow end-to-end: the architecture (wrapper + platform packages), all three channels (stable, canary, snapshot) with their triggers and version formats, the versioning workflow via Changesets, and the safeguards built into each step (smoke tests, isPublished checks, org membership gating for snapshots).
• README.md -- updated with current CLI help output reflecting the monorepo commands.
• LICENSE -- MIT license.

Merge instructions

This is the last PR in a 4-PR stack (#43, #47, #45, #46). Squash-merge normally, no rebase needed after.

Test plan

• CI passes: format:check, lint, build, test
• Review docs/releasing.md for accuracy against the workflows added in feat: add release infrastructure with changesets [3/4] #45
• Verify README help output matches bun run dev -- --help

Summary by CodeRabbit

• Documentation

  • Added comprehensive contribution guidelines covering development setup, pre-release installation, and PR workflow.
  • Enhanced README with Installation and Usage sections for the CLI.
  • Added release process documentation.
  • Updated project guidance to reference contribution instructions.

• Chores

  • Added MIT License file.
  • Packaging now embeds the LICENSE into generated platform packages.

[wyattjoh]

PR Stack — Supersedes #31

	PR	Description
1	#43	Monorepo restructure
2	#44	Cross-compile build + smoke tests
3	#45	Release infrastructure (changesets)
4	#46	Release documentation + LICENSE — ← this PR

Review in parallel, merge sequentially 1→2→3→4.
Squash-merge each PR, then rebase the next branch onto the updated base before merging it.

[wyattjoh]

PR Stack -- Supersedes #31

	PR	Description
1	#43	Monorepo restructure (merged)
2	#47	Cross-compile build + smoke tests
3	#45	Release infrastructure (changesets)
4	#46	Release documentation + LICENSE -- ← this PR

Review in parallel, merge sequentially. Squash-merge each PR, retarget the next PR to main before deleting the branch, then rebase.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 631b482b-b8b0-4eb1-a387-f75b21600ce4

📥 Commits

Reviewing files that changed from the base of the PR and between 7110069 and ff18bb3.

📒 Files selected for processing (6)

• CLAUDE.md
• CONTRIBUTING.md
• LICENSE
• README.md
• docs/releasing.md
• scripts/releaser/index.ts

---

📝 Walkthrough

Walkthrough

Added CONTRIBUTING.md with local development, testing, PR, and pre-release installation guidance. Added a top-level LICENSE file containing the MIT license (2026 copyright). Added docs/releasing.md describing stable, canary, and snapshot release flows and tooling. Updated README with Installation and Usage sections (including npm install -g clerk). Updated scripts/releaser to copy the repository LICENSE into each generated platform package. Added a cross-reference to CONTRIBUTING.md in CLAUDE.md.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the pull request as adding release documentation and a LICENSE file, and the [4/4] notation clearly contextualizes it as the final part of a multi-PR stack.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@scripts/releaser/index.ts`:
- Around line 69-71: The packaging change now copies LICENSE (licensePath /
copyFile) into each platform package but there is no test; add a
unit/integration test that invokes the packaging step (call
generatePlatformPackage or the equivalent function used by the releaser) against
a temporary output location, then assert that each produced package output
(directory or archive for each platform) contains a top-level LICENSE file;
ensure the test creates its own temp workspace, runs the packaging function,
inspects each generated package (extract archive if needed) to check for a file
named "LICENSE", and cleans up after itself.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1bee525e-0583-43ad-8091-31330d8ac5db

📥 Commits

Reviewing files that changed from the base of the PR and between a2c0cc5 and 7110069.

📒 Files selected for processing (6)

• CLAUDE.md
• CONTRIBUTING.md
• LICENSE
• README.md
• docs/releasing.md
• scripts/releaser/index.ts