Several workflow files carry — where an em dash was meant. That is the UTF-8 encoding of — (bytes E2 80 94) read back as Latin-1 and re-saved, so the corruption is now on disk rather than a display artefact.
Files:
FerrFlow/.github/workflows/publish.yml
FerrGames-Cloud/.github/workflows/ci.yml
FerrGames-Cloud/.github/workflows/scorecard.yml
Kit/.github/workflows/release.yml
UI/.github/workflows/publish.yml
FerrVault/.github/workflows/e2e.yml (the operator repo, checked out locally as ferrflow-operator/)
Most sit in comments, but not all. FerrGames-Cloud/.github/workflows/ci.yml has it inside strings that get echoed:
run: echo "No api/** changes in this PR — skipping Rust checks."
so it reaches the Actions log, where anyone reading a skipped job sees the mojibake.
The fix is not to restore the em dash. The writing rule forbids it in prose, so these sentences want rewriting: a comma, a colon, or two sentences. — we hit GitHub 504s, — skipping, — they only bump Chart. all read better split anyway.
Worth doing in the same pass as #316, which is already touching workflow comments across the org, though the echoed strings in FerrGames-Cloud are a separate change since they are not comments.
How this surfaced: writing a French-comment detector for #316. Scoring on accented characters flagged an entirely English comment block in UI/.github/workflows/publish.yml, because the mojibake bytes decode as accented Latin-1 characters. Any tooling that judges these files by character class will trip on the same thing.
Several workflow files carry
—where an em dash was meant. That is the UTF-8 encoding of—(bytesE2 80 94) read back as Latin-1 and re-saved, so the corruption is now on disk rather than a display artefact.Files:
FerrFlow/.github/workflows/publish.ymlFerrGames-Cloud/.github/workflows/ci.ymlFerrGames-Cloud/.github/workflows/scorecard.ymlKit/.github/workflows/release.ymlUI/.github/workflows/publish.ymlFerrVault/.github/workflows/e2e.yml(the operator repo, checked out locally asferrflow-operator/)Most sit in comments, but not all.
FerrGames-Cloud/.github/workflows/ci.ymlhas it inside strings that get echoed:so it reaches the Actions log, where anyone reading a skipped job sees the mojibake.
The fix is not to restore the em dash. The writing rule forbids it in prose, so these sentences want rewriting: a comma, a colon, or two sentences.
— we hit GitHub 504s,— skipping,— they only bump Chart.all read better split anyway.Worth doing in the same pass as #316, which is already touching workflow comments across the org, though the echoed strings in FerrGames-Cloud are a separate change since they are not comments.
How this surfaced: writing a French-comment detector for #316. Scoring on accented characters flagged an entirely English comment block in
UI/.github/workflows/publish.yml, because the mojibake bytes decode as accented Latin-1 characters. Any tooling that judges these files by character class will trip on the same thing.