Social-action enrichment expects fields that differ from the pinned camel-oasis 0.2.5 trace contract. Muting records mutee_id, which the action exporter discarded; comment creation records comment_id but not post_id, so enrichment never found its parent discussion. Logged actions and graph-memory descriptions therefore lost the affected user or discussion.

Retain mute targets, including user 0, and resolve a created comment's parent post through its recorded comment ID. Existing explicit post IDs and follow-target enrichment remain supported.

Pinned contract source: OASIS v0.2.5 platform implementation, specifically mute and create_comment.

Validation:

• Real SQLite trace rows matching the pinned SDK flow through production extraction, action logger, monitor and memory text generation.
• Baseline: 3 failures and 2 passing controls (follow-to-user 0 and explicit comment post ID). Fixed full backend suite: 134 passed.
• Complete production runner module is imported with explicitly disclosed import-only Camel/OASIS name doubles. No simulation, model, or hosted graph call is executed.
• git diff --check passes.

AI assistance was used to investigate and prepare this locally verified patch.