ADR-0006 · Proposals show as tracked changes inside the page

Status: Accepted, 2026-10-10.

Context

Open merge requests were listed beside the document as operations, which asks the reader to map a list back onto the text.

Decision

GitRedline draws one merge request into the rendered page: replaced blocks get word-level <del> and <ins> from diffWords, deleted blocks are struck through, inserted blocks appear in place. One proposal at a time; pressing it again restores the page exactly.

Why

Reviewing in short bites on the rendered page is the thesis; tracked changes in place are what readers already know from word processors.

Consequences

The side list (GitTrackChanges) remains for an overview of all proposals. A whitespace-only run between two changes joins them, so a phrase replacement reads as one change.

Evidence

c067010, acf44f5; test/e2e/redline.spec.js.

Revisit when

Several proposals need to be compared inline at once, or block-level diffs prove too coarse.