# Comment-artifact phrases — patterns indicating that a review-tool comment (BugHerd, Asana,
# Slack, Google Docs) was executed as live copy instead of being responded to.
#
# These are BLOCKER severity. If any of these appear in live HTML or in a "final" content brief,
# it almost always means someone copy-pasted a comment into the wrong place.
#
# A real launch shipped with "Is there a way to emphasize 100%" as live copy — that was a
# comment-artifact leak. The Production Artist read a BugHerd comment as if it were copy
# direction, embedded it in the page, and shipped it.

# Question-form review comments
Is there a way to
Can we
Could we
Should we
What if we
Why don't we
Why not
How about
What about
Is it possible to
Would it be possible to
Do we need

# Suggestion-form review comments
Maybe we
Maybe try
Perhaps
Consider
Let's try
We should

# Status-update review comments
Pending
In progress
Need to
Need a
Waiting on
Waiting for
Awaiting

# Direct annotation phrases
This needs
This should
This isn't
This doesn't
Note:
Note to
NOTE:
TODO:
FIXME:
XXX:

# Approval/feedback patterns
Approved
Approve
Rejected
Reject
Looks good
LGTM
Sign off
Needs sign off

# Question-mark patterns (already covered by triple-question-marks regex but listed for clarity)
???
?!
?!?
