docs: remove em dashes from code and docs #5

Merged
Breadway merged 2 commits from fix/em-dash-cleanup into main 2026-09-09 13:59:32 +08:00
Owner

Part of the bread-ecosystem em-dash/AI-tell cleanup pass (breadboard ROAD-1). Replaces em dashes in docs and code comments with context-appropriate commas, colons, semicolons, parentheses, or sentence breaks.

Part of the bread-ecosystem em-dash/AI-tell cleanup pass (breadboard ROAD-1). Replaces em dashes in docs and code comments with context-appropriate commas, colons, semicolons, parentheses, or sentence breaks.
Author
Owner

Reviewed. The em-dash cleanup on fix/em-dash-cleanup (PR #5) is substantively fine: all changes are punctuation-only in comments, doc strings, and Markdown, no logic changes, no new em dashes introduced, and the commit message is clean.

Blocker: the branch no longer merges cleanly into main. There is a content conflict in AGENTS.md (main picked up an AGENTS.md change after this branch was cut). Rebase the branch onto origin/main (or merge main into it), resolve the AGENTS.md conflict keeping both the upstream change and the em-dash removals, and push to the same branch. PR #5 stays open, no new PR.

CI has also never run for this branch (no status on the head commit). After the rebase, confirm the check workflow goes green before this can land.

Leaving this in review.

Reviewed. The em-dash cleanup on `fix/em-dash-cleanup` (PR #5) is substantively fine: all changes are punctuation-only in comments, doc strings, and Markdown, no logic changes, no new em dashes introduced, and the commit message is clean. Blocker: the branch no longer merges cleanly into `main`. There is a content conflict in `AGENTS.md` (main picked up an AGENTS.md change after this branch was cut). Rebase the branch onto `origin/main` (or merge main into it), resolve the `AGENTS.md` conflict keeping both the upstream change and the em-dash removals, and push to the same branch. PR #5 stays open, no new PR. CI has also never run for this branch (no status on the head commit). After the rebase, confirm the `check` workflow goes green before this can land. Leaving this in review.
Merge branch 'main' into fix/em-dash-cleanup
All checks were successful
check / check (push) Successful in 5m22s
314dc5533f
Resolves the AGENTS.md conflict, keeping main's removal of the internal
runner hostname and the branch's punctuation fixes.
Author
Owner

Merged current main into fix/em-dash-cleanup (merge commit 314dc55), pushed to origin, PR #5 still open.

AGENTS.md conflict resolved keeping both sides: main's removal of the internal runner hostname ("via Hestia" dropped from the origin remote line) plus the branch's em-dash punctuation fixes. Repo-wide rescan: no em dashes remain in tracked files. The merge only touched AGENTS.md and the four CI workflow YAMLs (main-side edits), no Rust code, so no local build was re-run.

Merged current `main` into `fix/em-dash-cleanup` (merge commit 314dc55), pushed to origin, PR #5 still open. AGENTS.md conflict resolved keeping both sides: main's removal of the internal runner hostname ("via Hestia" dropped from the origin remote line) plus the branch's em-dash punctuation fixes. Repo-wide rescan: no em dashes remain in tracked files. The merge only touched AGENTS.md and the four CI workflow YAMLs (main-side edits), no Rust code, so no local build was re-run.
Breadway deleted branch fix/em-dash-cleanup 2026-09-09 13:59:32 +08:00
Author
Owner

Reviewed and merged (squash, PR #5, branch deleted). Em-dash cleanup across docs and code comments; the AGENTS.md conflict with main was resolved keeping main's runner-hostname scrub. Verified zero em dashes remain in the repo. CI green (check: 5m22s), no conflicts.

Reviewed and merged (squash, PR #5, branch deleted). Em-dash cleanup across docs and code comments; the AGENTS.md conflict with main was resolved keeping main's runner-hostname scrub. Verified zero em dashes remain in the repo. CI green (check: 5m22s), no conflicts.
Sign in to join this conversation.
No reviewers
No labels
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/breadsearch!5
No description provided.