Reformat wherefore records for readability (no meaning change)#3
Merged
Conversation
Readability-only migration of the wherefore/ log to the verdict-led, scannable style. No decision, rationale, date, tag, supersession link, or question ID changed in meaning; this is a prose reformat and dash purge. - Purge em dashes and ` -- ` punctuation from log entries and topics.md (replaced with periods, commas, colons, or semicolons). CLI flags such as `npm pack --dry-run` and the `-> see <slug>` supersede banners are left intact. - Make Decisions bullets verdict-led and split compound bullets that fused multiple rulings (adr-positioning, dashboard-schema-and-ui, npm-asset-scope). - Remove inline bold used to fake structure in the rename-to-wherefore alternatives list. - Frontmatter safety: double-quote previously unquoted free-text scalars (8 entry titles, all 7 question texts, one resolution) and escape the embedded quotes in Q-005 so the dashboard viewer cannot misparse them. Frontmatter values are unchanged; no file renamed. The dashboard builds against this directory with no YAML parse error. Body prose in three entries still references the old hyphenated `superseded-by`/`superseded-date` keys as historical fact (the underscore-migration record and the schema entries); those are intentional and were not rewritten. No frontmatter key was hyphenated, so no key rename was needed. 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.
Readability-only migration of the wherefore/ log to the verdict-led, scannable style. No decision, rationale, date, tag, supersession link, or question ID changed in meaning; this is a prose reformat and dash purge.
--punctuation from log entries and topics.md (replaced with periods, commas, colons, or semicolons). CLI flags such asnpm pack --dry-runand the-> see <slug>supersede banners are left intact.Frontmatter values are unchanged; no file renamed. The dashboard builds against this directory with no YAML parse error. Body prose in three entries still references the old hyphenated
superseded-by/superseded-datekeys as historical fact (the underscore-migration record and the schema entries); those are intentional and were not rewritten. No frontmatter key was hyphenated, so no key rename was needed.