Accurate, scoped documentation

Documentation and code examples must be technically accurate, idiomatic, and appropriately scoped. Before writing or approving docs:

• Verify claims against actual implementation rather than assumption. For example, describe sqlite3.Row as acting like a namedtuple (supports both positional and key access) rather than vaguely “like a tuple”, and confirm template-loading precedence by reading the loader source instead of guessing.
• Use correct, idiomatic, up-to-date syntax in examples (e.g. print('...') instead of Python 2 print statements, asyncio.create_task instead of deprecated ensure_future, lowercase true/false/none as the Jinja default rather than the Python-cased aliases).
• Never show or imply insecure/unsafe defaults in examples, such as binding the dev server to --host 0.0.0.0; keep examples demonstrative without encouraging misuse.
• Keep each document scoped to its purpose: quickstart/tutorial pages should stay concise and link to full API references rather than duplicating exhaustive tables or details (e.g. move full converter lists to API docs, keep quickstart to a short example and a link).
• Keep the changelog limited to user-facing, installable-library changes; doc-only fixes, typo corrections, or internal tooling updates don’t need an entry.
• When recommending third-party tools or servers in guides, favor neutral, cross-platform examples and explicitly note that alternatives exist, avoiding the appearance of endorsement.

Applying these checks during review prevents misleading guidance, broken or outdated examples, and documentation bloat that duplicates or contradicts other docs.</description> </invoke>