Remove em dashes from code and docs #6

Merged
Breadway merged 1 commit from fix/em-dash-cleanup into main 2026-09-09 13:59:24 +08:00
Owner

Replaces every em dash across Rust source, doc comments, Markdown docs, the vendored openscreen PATCHES.md notes, and CI workflow YAML with colons, semicolons, commas, or parentheses, chosen per-instance for what reads most naturally. No intentional em-dash placeholder glyphs exist in this repo, so this is a full, exception-free cleanup. Also carries along a small pending AGENTS.md "Persistent memory" note that was already staged on main before this branch was cut.

Replaces every em dash across Rust source, doc comments, Markdown docs, the vendored openscreen PATCHES.md notes, and CI workflow YAML with colons, semicolons, commas, or parentheses, chosen per-instance for what reads most naturally. No intentional em-dash placeholder glyphs exist in this repo, so this is a full, exception-free cleanup. Also carries along a small pending AGENTS.md "Persistent memory" note that was already staged on `main` before this branch was cut.
docs: remove em dashes from code and docs
All checks were successful
check / check (push) Successful in 4m42s
55f98d95c7
Author
Owner

Reviewed and approved for merge. breadcast is not on the release train, CI (check / check (push)) is green on the head commit, and the branch merges cleanly.

Acceptance criteria (my read): remove every em dash across Rust source, doc comments, Markdown, the vendored openscreen PATCHES.md notes, and CI YAML, replacing each with natural punctuation; no functional changes.

Assessment: all edits are punctuation-only in comments and string literals (log lines, error context, the bakery description). No logic changes, diff is line-for-line balanced. No em dashes remain in the tracked tree. No new em dashes on added lines. Commit message is clean. The only extra is a 3-line "Persistent memory" note appended to AGENTS.md, consistent with the same note across sibling repos in this pass, harmless.

I was not able to execute the merge myself: the merge action was blocked by a permission guard in this session. Everything checks out, so this just needs a manual squash-merge of PR #6 (delete the branch) and then this issue can move to done.

Leaving in review pending that manual merge.

Reviewed and approved for merge. `breadcast` is not on the release train, CI (`check / check (push)`) is green on the head commit, and the branch merges cleanly. Acceptance criteria (my read): remove every em dash across Rust source, doc comments, Markdown, the vendored openscreen PATCHES.md notes, and CI YAML, replacing each with natural punctuation; no functional changes. Assessment: all edits are punctuation-only in comments and string literals (log lines, error context, the bakery description). No logic changes, diff is line-for-line balanced. No em dashes remain in the tracked tree. No new em dashes on added lines. Commit message is clean. The only extra is a 3-line "Persistent memory" note appended to `AGENTS.md`, consistent with the same note across sibling repos in this pass, harmless. I was not able to execute the merge myself: the merge action was blocked by a permission guard in this session. Everything checks out, so this just needs a manual squash-merge of PR #6 (delete the branch) and then this issue can move to done. Leaving in review pending that manual merge.
Breadway deleted branch fix/em-dash-cleanup 2026-09-09 13:59:24 +08:00
Author
Owner

Reviewed and merged (squash, PR #6, branch deleted). Pure em-dash cleanup: every U+2014 across Rust source, doc comments, Markdown, the vendored openscreen PATCHES.md, and CI YAML replaced with plain punctuation, no functional changes. Verified zero em dashes remain in the repo. CI green (check: 4m42s), no conflicts.

Reviewed and merged (squash, PR #6, branch deleted). Pure em-dash cleanup: every U+2014 across Rust source, doc comments, Markdown, the vendored openscreen PATCHES.md, and CI YAML replaced with plain punctuation, no functional changes. Verified zero em dashes remain in the repo. CI green (check: 4m42s), no conflicts.
Sign in to join this conversation.
No reviewers
No labels
bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadcast!6
No description provided.