Owner: Elena Voss. Audience: admins, then the blog.
Shift swaps ship in this release. Managers approve or decline a swap in the mobile app. CSV import still loads, warns, and will fail closed next release. Read this before you upgrade a location.
Shipped
A manager can approve a swap from the phone, without the desktop site.
The employee sees the decision on the same swap, with the manager's name. The name is the manager who tapped approve, so the employee can see who decided.
CSV import warns on every upload and names the release that removes it. Use that warning on the upload screen, and do not soften it in the blog post.
Not in 4.12
Payroll sync is unchanged. Approved swaps still export on the old schedule. The blog post should not promise a faster sync, or any sync this release lacks.
Bulk approval is not in this release. One swap at a time, from the manager's phone.
After the upgrade
No admin action after the upgrade.Admins turn on shift-swap approvals under Settings, then re-save each location.
Re-save each location or the toggle stays off for that site. Saving once does not cover the next.
Tell managers the phrase in the app is approve a swap, not shift swaps. Keep the internal name in this note, and use the plainer phrase where managers read.
Shift swaps ship
Clara Beaumont
The headline says shift swaps. Customers do not use that phrase.
Ines Duarte
Say managers can approve a swap in the app.
No admin action
Obi Nwosu
@agent say what admins need to do after upgrading.
agent
Added the Settings steps admins take after upgrading.
resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: Loomwright 4.12 release notes in Gander, with a marketing thread and a scripted agent connect reply.
How release notes get reviewed today
Pasting notes into chat works when one person proofreads them. It splits when support, product, and marketing each need a different sentence and the agent is still editing the source file.
A shared doc collects comments and then someone retypes them into the file that will actually ship. A PR reviews the changelog next to code, which is good for engineers and easy to miss if you are not in the repo.
One draft of Loomwright 4.12
Elena Voss lets a Grok Build job drop Loomwright's 4.12 notes into a folder she watches with gander watch. The new file gets a link. She sends it to Ines Duarte, Obi Nwosu, and Clara Beaumont.
Clara highlights the headline and says 'shift swaps' is internal jargon for the blog. Ines replies with a plainer phrase. The agent is not on that thread.
Obi starts a new comment: "@agent say what admins need to do after upgrading." Elena's agent adds the Settings steps, replies, and resolves the thread. The same link updates for Ines and Clara. The notes then go out through the release process Loomwright already has.
Who's in the doc
WriterProductSupportMarketingThe author's agent
Writer Release manager or the engineer shipping the build. Sends one link.
Product Checks that the note matches what was promised.
Support Checks the steps admins and agents will be asked for.
Marketing Checks the words customers will read.
The author's agent Can add the missing admin steps when support uses agent connect.
Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.
Agents that fit release notes
Grok BuildA headless run can write notes into a folder you watch with gander watch.
CursorWhen the changelog lives in the repo, MCP returns agent connect to that session.
Claude CodeSame repo path. The skill can watch the release file after the session writes it.
CodexCodex can draft the notes from the diff. Agent connect comes back through MCP.