[allisonmahmood]

What changed

This PR adds release 18's What's new entry, written from b23e6ad. It covers everything merged since release 17's through (5dd94f3), and it sets the patchy release to 0.18.0 in packages/patchy/package.json and CURRENT_RELEASE. With this release, onboarding ends in a Final step on Home that follows the person's agent through setup and lets them confirm it right there (#906).

Change	PRs
New: A Final step to connect your AI agent	#916, #917
New: Confirm your computer without leaving Home	#918
Improved: Setting up ends with your first page	#914
Improved: The logo takes you Home	#913
Behind the scenes: the first time someone opens a colleague's tool is counted, for activation	#915

One merged PR gets no line: #905 is release 17's own entry.

Look at

• The entry, at the top of releases in packages/core/src/whatsNew.ts. Its labels are the pages' own: Final step, Later, Not me, Home, Patches.
• Rollback safety, from the live commit a049a3c to b23e6ad.
  • No PR in the range is labelled one-way, and every PR answers both Release impact questions with "Yes".
  • Migrations 0026 and 0027 are additive: the setup_prompt_sign_ins and setup_links tables, and a nullable device_logins.setup_link_id with ON DELETE SET NULL. Release 17 never reads them.
  • rollback-rehearsal exercised both migrations on the landed heads:
    • feat(ui): Final step, a panel over Home until your agent is connected #916: Exercised rollback paths passed: a049a3c → 6037d86 → a049a3c → 6037d86, in 234s.
    • feat(auth): setup links tie the agent's fetch, login and key to the person's Final step panel #917: Exercised rollback paths passed: a049a3c → d03a5bf → a049a3c → d03a5bf, in 217s.
    • feat(ui): confirm your computer inside the Final step panel #918 and feat(analytics): a colleague's first open of a patch is a business event #915 change no migration or handler descriptor, so they had nothing to rehearse.
  • A rollback takes the Final step panel and setup links away. Home goes back to the old guide, and a CLI at 0.18.0 stays usable against release 17: --setup is only sent when /llms.txt prints it, and release 17's /llms.txt doesn't.

How it was verified

• pnpm typecheck and pnpm lint pass, and so do packages/core, packages/api, packages/portal and the skill lock test (245 tests), including whatsNew.test.ts, schemas.test.ts and WhatsNewPages.test.ts.
• The live commit was pinned from /healthz/deep: a049a3c, release 17. The Deploy run updated last succeeded, and none is unfinished.
• Each PR in the range was read, including its Release impact answers. All six landed with the reviewed trees: each squash left main's tree identical to its PR's reviewed head.

Release impact

• Breaking — requires action from anyone already running this
• Not breaking — no action required

This PR changes only the changelog text and the patchy version. As with every release, a CLI installed before this deploy is told to upgrade.

• What does a revert leave behind? Nothing. People whose seen marker reached 18 would just see no new release.
• Does the release before it still work with that? Yes.

If this release misbehaves, roll back to a049a3cf544ae89691eec547dea46773febfdf05 (release 17).

Made by Claude Opus 5.5 in Claude Code, running in T3 Code.