Address CodeRabbit Review

Read comments: Use gh api repos/carrot-foundation/methodology-rules/pulls/<PR_NUMBER>/comments to fetch all review comments. Identify which ones are from CodeRabbit.

Triage each comment into one of three categories:

• Valid issue: A real bug, missing validation, incorrect logic, or meaningful improvement
• False positive: The tool misunderstood the code or the suggestion does not apply
• Style preference: A subjective suggestion that does not affect correctness

Fix valid issues:

• Implement the fix following project conventions
• If the suggestion is directionally correct but the specific fix is wrong, implement the right fix instead
• Group related fixes into a single commit

Dismiss false positives: Leave a brief, respectful reply explaining why the suggestion does not apply. Be specific — reference the actual behavior or constraint that makes the suggestion unnecessary.

Handle style preferences: Apply if they align with project conventions. Skip if they contradict existing patterns or add no value.

Run quality checks after all fixes:

pnpm lint:affected
pnpm ts:affected
pnpm test:affected

Push fixes: Commit with a message like fix(shared): address CR feedback on schema validation and push to the PR branch.