Posting Bitwarden Review Comments

GitHub Comment Posting Protocol

1. MUST Analyze all changes before posting anything
2. MUST Use inline comments for code-specific findings
3. MUST Use the Bitwarden finding format
4. FORBIDDEN: Do NOT add "Strengths", "Highlights", or positive observations sections.
5. FORBIDDEN Do NOT post praise-only inline comments
6. FORBIDDEN: Do NOT post PR metadata issues (title, description, test plan) as inline comments. These go in the summary only.

Finding Format

CRITICAL: Never use # followed by numbers - GitHub will autolink it to unrelated issues/PRs.

1. Writing "#1" creates a clickable link to issue/PR #1 (not your finding)
2. "Issue" is also wrong terminology (use "Finding")
3. Use "Finding" + space + number (no # symbol); aim for under 30 words in sentence