Turn a team Slack brainstorm into a structured content brief

You're the content lead at a WordPress plugin company. There's a 40-message Slack
thread where the team brainstormed ideas after a plugin update caused site crashes
for some customers, and support wants a public post explaining what happened. The
thread is messy: reactions, half-finished thoughts, and two people proposing
different angles.

SLACK THREAD (condensed): [
"Dana: we should just explain what broke and how we fixed it
Marcus: agreed, but also we should be upfront that we rushed the release, builds
trust
Priya: disagree, don't want to admit we rushed anything, could look bad legally
Dana: what about the actual technical cause? someone should ask the dev team
Marcus: it was a conflict with a caching plugin, I think? not 100% sure
Priya: if we're doing this can we also plug the new rollback feature
Dana: yes but that's a small mention, not the main point"]
GOAL: [a public post, transparent but not legally risky, explaining the incident]

Work through this before drafting the brief:
1. Separate genuine content ideas from banter and reactions, the emoji and one-word
   agreements aren't decisions, they're just reactions to someone else's idea.
2. Edge case: Marcus and Priya disagree on whether to admit the release was rushed.
   Don't silently pick a side when turning this into a brief, flag it as an open
   decision the writer or a manager needs to make before drafting, with both
   positions stated plainly.
3. Note where the thread contains uncertain technical detail ("I think it was a
   caching plugin conflict, not 100% sure") and convert that into an explicit
   research task ("confirm root cause with dev team") rather than letting an
   unverified guess get written into the brief as settled fact.
4. Keep the rollback feature mention sized the way the thread agreed it should be, a
   secondary mention, not the headline, even though it's tempting to lead with a
   feature plug.
5. Structure the output as an actual brief: goal, audience, tone, key points to
   cover, open decisions needing sign-off, research tasks, and things explicitly
   agreed to exclude or downplay.

Produce the content brief in that structure, ready to hand to a writer.

Replace the bracketed Slack thread and goal above with your own.