docs: keep chat output plain text to avoid reverse-video

Craig's terminal renders Markdown bold and inline-code spans as reverse video, which is hard to read. I added a rule to interaction.md: in conversational output, write command names, paths, and key chords as plain text, and lean on headers, dashes, parentheses, and quotes for structure. It governs chat output only, not the Markdown source of the rule and spec files he reads in an editor.

I also made the keybinding-display example plain text so the convention shows the format the way it should appear in chat, with a pointer to the new rule.

0 files changed, 0 insertions, 0 deletions