docs: code style parity between README and website examples #140

Problem

Website MDX guides use double-quoted strings and trailing semicolons. README Quick Start examples use single quotes and often omit semicolons. This creates minor cognitive friction when switching between npm README and website documentation.

Proposed Changes

• Pick one code-style profile for all first-party documentation (recommend: double quotes + semicolons, matching the website)
• Consider running Prettier with a shared config across doc code blocks in all three repos (ergo, ergo-router, centralping.github.io)
• Also normalize numeric separator usage: prefer 60_000 over 60000 (already dominant on website; some older examples still use bare numbers)

Source

External adoption evaluation, Phase 1.5 findings S05, C01, C05.