llm: Add test constants placement rule to testing skill

[SaintPatrck]

🎟️ Tracking

LLM tooling improvement — no Jira ticket.

📔 Objective

Add a "Test Constants Placement" section to the testing-android-code skill documenting the convention: declare test constants as top-level private const val at the bottom of the file, not inside companion object.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.16%. Comparing base (94e550d) to head (5558e8b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6726   +/-   ##
=======================================
  Coverage   86.16%   86.16%           
=======================================
  Files         840      840           
  Lines       59258    59258           
  Branches     8516     8516           
=======================================
  Hits        51060    51060           
  Misses       5244     5244           
  Partials     2954     2954           

Flag	Coverage Δ
app-data	17.26% <ø> (ø)
app-ui-auth-tools	20.33% <ø> (ø)
app-ui-platform	15.72% <ø> (ø)
app-ui-vault	26.67% <ø> (ø)
authenticator	6.51% <ø> (ø)
lib-core-network-bridge	4.23% <ø> (ø)
lib-data-ui	0.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Documentation-only change adding a "Test Constants Placement" section to the testing-android-code skill. The new guidance documents the existing codebase convention: declare test constants as top-level private const val at the bottom of the file, not inside companion object. The section is well-placed between "Test File Organization" and "Test Naming" and is clear and actionable.

Code Review Details

No findings. Clean documentation addition with no code, security, or architectural concerns.