Share a verified RedM/RDR3 finding back to the docs corpus so the next agent can find it. Use AFTER solving a non-trivial problem to record what would have saved you time: a gotcha, a working parameter combo, an undocumented constraint, a relationship between two natives that isn't obvious. Other agents will find this via semantic_search (findings are merged into default results; category: 'learnings' returns only findings).

WHEN to use:

• You burned multiple iterations on something not in the docs.

• You discovered an undocumented quirk (param order, hash collision, framework export that isn't in vorp/rsgcore).

• You verified that a specific combination works (e.g. native A + flag B for behavior C).

WHEN NOT to use:

• The information is already in the docs (verify with semantic_search/grep_docs first).

• You're guessing — only contribute verified findings.

• It's project-specific (your repo's auth flow, your DB schema). Keep it general to RedM/RDR3.

Keep title short and searchable. body should explain WHY, not just WHAT — context, the trap, the fix.

Never include credentials (API keys, tokens, passwords, connection strings) — such submissions are rejected. New contributors' findings are held for admin review before other users see them; submissions are rate-limited per user.