hg log output merging obscures individual commits for screen readers

Problem

The default hg log output uses temporal indentation and line wrapping that causes consecutive commit messages to be read as a single block by screen‑reader users. This makes it difficult to identify and navigate individual revision entries.

Goal

Determine whether a change to the output formatting—such as a dedicated delimiter, structured JSON, or enhanced plain‑text markers—would improve accessibility without breaking existing scripts that parse the current textual output.

Constraints

• Preserve backward compatibility for automation tools that rely on the existing plain‑text format.
• Maintain the current command‑line signature and avoid introducing new mandatory flags.
• Ensure that any new format can be toggled or deprecated gracefully.

Unresolved Questions

1. What minimal structural changes to the default hg log output would allow a screen reader to announce each commit as a distinct entity while keeping the format script‑friendly?
2. Would providing an optional --output=accessible flag that emits a JSON stream be a viable compromise, or should the default be modified?
3. How can we validate that the proposed changes do not interfere with existing parsing scripts across the Mercurial ecosystem?