Release notes

Slack alerts for Ask Layr milestones0.44.0

The team now hears in Slack when a customer reaches an Ask Layr milestone. Front-end documents added to an existing project land in Other docs again.

2026-11-02Minor2 pull requests1 migration

What’s new

Front-end documents you add to a project now land in Other docs, not Specifications.

Highlights

Ask Layr milestones post to #layr-notifications

When a customer asks their 1st, 5th, 25th or 100th Ask Layr question, a message posts to #layr-notifications. It shows who asked, which project, and the question (first 140 characters), with a link to the project. Layr counts questions across all of a person’s projects, deleted chats included. Layr staff (layrbuild.com, jakib.ai) never post. The panel’s automatic follow-up after a view tool does not count as a new question. Neither does a regenerated answer. (#922)

Fixes worth naming

Front-end documents added to an existing project with Add documents now land in Other docs. They had landed under Specifications, as seen on NEORSD. A new project already filed them right. (#921, Justin)

Upgrade notes

Migration 129_ask_conversations_user_index.sql adds an index on ask_conversations(user_id). Dev already has it. Prod applies it through deploy.yml on merge.
The PostHog destination “Ask Layr milestones → #layr-notifications” (event ask_milestone, source layr-server) is already set up in PostHog Layr Main. Nothing to configure.
No flag changes. No new dependencies.
package.json’s version is 0.44.0.

Known limits

Two questions that finish at the same moment can both post the same milestone.
Editing an earlier question deletes the messages after it. The count drops, so a milestone can post again.
Front-end documents already added under Specifications do not move on their own. Move them with the outline’s move menu.