fix: JSON field naming using snake_case instead of camelCase in 3 files

[gandalf-at-lerian]

Problem

Three Ring files have code examples using snake_case for JSON struct tags, contradicting the mandatory camelCase convention defined in dev-team/docs/standards/golang/api-patterns.md.

Agents using these files as reference will generate code with the wrong naming convention.

Files to Fix

File	Issue
platforms/opencode/standards/golang.md	QueueMessage fields: organization_id → organizationId, etc.
dev-team/docs/standards/golang/messaging.md	Same QueueMessage copy
default/skills/production-readiness-audit/SKILL.md	GOOD/BAD reference examples are inverted — marks snake_case JSON as correct

Convention (per api-patterns.md)

Context	Convention	Example
JSON body fields	camelCase	organizationId, createdAt
Query parameters	snake_case	sort_order, start_date
Database columns	snake_case	organization_id, created_at

Reference

Branch fix/json-snake-case-to-camelcase has the fix ready if useful.

Reported by @alexgarzao