CM-1002: Add automated Linc release pipeline

[dantedanelian]

Summary

Add an automated GitHub Actions release pipeline for Linc so releases are prepared from CI after merges to main, instead of from a local laptop.

Resolves: https://linear.app/casemarkai/issue/CM-1002/add-automated-npm-release-pipeline-for-linc

Changes

• Add .github/workflows/release.yml with automatic push handling for main; non-release pushes prepare a patch release automatically.
• Keep manual dispatch in the Release workflow for explicit versions or minor/major bumps.
• Add a loop guard so the release commits produced by scripts/release.mjs do not trigger another release.
• Add .github/workflows/npm-publish.yml for npm Trusted Publishing; this matches the npm package trusted publisher configuration for casemark/linc and npm-publish.yml.
• Keep binary building and GitHub Release asset upload in .github/workflows/build-binaries.yml.
• Harden scripts/release.mjs to require main for local releases, run build/check/test before tagging, and push the prepared release commit explicitly to main.
• Document automatic release, manual release, npm Trusted Publishing setup, and recovery flow in docs/release.md; link it from the README.

Validation

• node --check scripts/release.mjs
• YAML parse for .github/workflows/build-binaries.yml, .github/workflows/npm-publish.yml, and .github/workflows/release.yml
• npm run check
• Previous local npm test mostly passed, with one test/footer-data-provider.test.ts watcher timing failure in the full run; focused rerun passed with npx vitest --run test/footer-data-provider.test.ts.

Checklist

• Tested locally
• Commits include ticket ID (e.g., CD-123: Fix thing)
• Linear ticket updated to "In Review"

---

Reviewer Reminder: You are responsible for the quality of this merge. The agent cannot merge on their own.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
linc-docs	Ready	Preview, Comment	Jun 15, 2026 9:29pm

[maxsonderby]