Community Release Announcement

Problem Description

Nexus, a developer tools company, ships a new version of their CLI tool today. The product team has jotted down the release highlights in a rough internal notes file. These notes are accurate but written for internal use — they're dense, jargon-heavy, and use bullet fragments.

You need to turn these notes into a polished announcement that the community manager, Dani, can post directly into the #announcements channel of Nexus's public Discord server. The server has thousands of members, a mix of experienced developers, early adopters, and newcomers. Many members are not deeply technical.

Dani needs something she can copy-paste without editing. She's also mentioned that when there's a tricky tone decision to make, a short note explaining the choice would help her.

Output Specification

Save your output to a file called announcement.md.

Input Files

The following file is provided as input. Extract it before beginning.

=============== FILE: inputs/release-notes-internal.txt =============== Release: nexus-cli v2.4.0 Date: 2024-03-21

CHANGES (internal notes — do NOT publish as-is):

• Fixed: race condition in nexus sync when multiple workspaces open simultaneously → was causing silent data corruption on Windows, only in edge cases but bad when it hit
• New: --watch flag for nexus build — runs incremental builds on file save, uses inotify/FSEvents under the hood
• Improved: startup time down ~40% due to lazy-loading plugin registry (previously scanned all plugins at boot even when not used)
• BREAKING: removed deprecated --legacy-auth flag from nexus login (was deprecated in v2.1, gave 6 months notice)
• New: nexus doctor command — runs env checks, prints actionable fix suggestions for common setup issues
• Known issue: --watch mode has occasional false positives on symlinked directories; workaround: exclude symlinks via .nexusignore

Internal: do not hype the sync fix too much, don't want to alarm users who weren't affected. Focus on the positive.