Add Projects launch to April 24 changelog

[eclairen]

Summary

Adds a bullet to the April 24 changelog entry announcing the Projects launch, with a link to the Projects doc.

Test plan

• Preview renders on Mintlify

---

Note

Low Risk
Low risk documentation-only change that adds a single changelog bullet; no code or behavior changes.

Overview
Adds a new April 24 changelog bullet announcing the launch of Projects, linking to /info/projects and describing environment separation, per-project API key scoping, and concurrency caps (with existing resources moved into a Default project).

^{Reviewed by Cursor Bugbot for commit fefe57a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Apr 24, 2026, 5:20 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: This PR only modifies changelog documentation and does not change any API endpoints or Temporal workflows.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Risk assessment: Very Low.

I verified the diff directly: this PR adds a single changelog bullet in changelog.mdx and does not modify application code, infrastructure, permissions, auth, or runtime behavior. Blast radius is limited to documentation content on one page.

Given the narrow docs-only change and no existing approval from this automation, approving.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low.

I verified the diff directly: it only adds one bullet under April 24 in changelog.mdx and does not modify application logic, APIs, infrastructure, auth, permissions, or other shared runtime code paths.

Blast radius is limited to documentation/changelog content, so operational and security risk are minimal.

Per policy, I am not re-approving because this PR already has an approval and there are no new higher-risk changes to trigger approval removal.

  

_{Sent by Cursor Automation: Assign PR reviewers}