Add guideline discouraging embedded newlines in puts

[andyw8]

Note: PR co-authored with Claude Code

Summary

This PR adds a guideline discouraging the use of embedded newline characters (\n) in puts calls, in favor of using separate puts calls.

Motivation

I've noticed that AI models frequently generate Ruby code using the pattern puts "\nmessage" when adding blank lines to output. I suspect this is due to training bias from Python codebases, where print("\nmessage") is an accepted and common style.

However, in Ruby, the idiomatic approach is to use separate puts calls:

puts
puts 'message'

This is more readable and aligns better with Ruby conventions.

Next Steps

I was intending to add a new RuboCop cop to enforce this guideline, but I wanted to open this PR here first for discussion. If the community agrees this is a worthwhile guideline, I'll proceed with implementing the corresponding cop in RuboCop.

Changes

• Added a new section "Separate puts for Newlines" in the Misc section
• Provided clear examples of the discouraged and preferred patterns

[koic]

This is more readable and aligns better with Ruby conventions.

I'm not sure how common this convention actually is. I've seen "\nmessage" used intentionally to reduce I/O overhead. It might be worth considering whether this should be enforced as a universal style rule.