docs(loop): remove ledger row wedged into the status legend table#76
Merged
Conversation
A `reduce-motion` data row sat between the status legend's header and its first `proposed` entry, so the legend rendered as a broken 2-column table with a stray 10-column row in it. The Ledger table already carries a reduce-motion row, so the stray one was a duplicate -- but it held the implementation notes the reconciled row had dropped, so fold those into the surviving row rather than losing them with the deletion. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A
reduce-motiondata row sat between the status legend's header and its firstproposedentry, so the legend rendered as a broken 2-column table with a stray 10-column row inside it. Pre-existing onmain— surfaced while resolving the ledger conflicts across #49–#73.The Ledger table already carries a
reduce-motionrow, so the stray one was a duplicate. But the stray row held the implementation notes that the reconciled Ledger row had dropped, so those notes are folded into the surviving row rather than deleted along with it.Docs-only; no code touched. Both tables now have consistent column counts (legend 2, ledger 10).
Note (not changed here): that row still reads
pr-openthough #51 merged on 2026-07-06. Status reconciliation is the loop's job per the file's own "GitHub is the source of truth" note, so I left it alone.🤖 Generated with Claude Code