[prx-my]

Closes #1283.

What changed

• Replaced all 54 em dashes across 17 files under src/ (43 in emitted strings, 11 in comments/JSDoc):
  • Emitted clauses use : where a clause follows (e.g. 1 packument fetch failed: remediation guidance may be incomplete.), ;/period where a colon read poorly
  • HTML <title> separators use - (CVE Lite - <project>)
  • Comments and JSDoc use a plain -
• Updated the 8 tests that assert these strings exactly (multi-folder-scan, scanner-cache, html-reporter) after reading each assertion
• Also cleaned repo docs: README.md (10), docs/output-before-after.md (8), scripts/clean-dist.mjs (1). The docs/ sample output now matches current source (printers.ts colon, formatters.ts hyphens)
• Verified src/skills/content.ts output by eye (shipped AI-assistant docs, least coverage)

Verification

• grep -rn "—" src --include="*.ts" returns nothing
• npm test passes (163 suites, 2249 tests)
• npm run build is clean

Notes

• tests/output.test.ts:2944 intentionally keeps not.toContain("—") as the convention guard.
• Out of scope for this PR: website/docs/ (859) and examples/ (68) still contain em dashes; can be a follow-up docs PR.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[prx-my]

Update: this branch has been refreshed with the latest main. It is no longer behind and now only awaits the required review/status checks before it can merge.

[sonukapoor]

Exactly the scope of #1283 and nothing beyond it: 54 removed across the 17 files it counted, and src/docs/CONTRIBUTING.md correctly left alone since the issue's count excludes it. 2319 tests, build clean.

I went looking for the one way a mechanical replacement like this bites, a dash sitting somewhere parsed rather than printed, and there is nothing: every changed occurrence is inside a string literal, a template literal or a comment. Three lines tripped my own crude filter and all three are false positives, a trailing comment on a line containing === and the two HTML <title> lines.

Approved. The dozen left in CONTRIBUTING.md are our own writing and our own follow-up, not yours.

[sonukapoor]

Same situation as #1269, where I have put the detail. self-scan is red here because the branch predates #1307's handlebars bump on main, not because of anything in the change. A rebase onto current main should take it green.

The sweep itself is complete: src comes back clean of em dashes on your branch and still clean after merging into current main, with the suite and the build green on that merge result.

[sonukapoor]

Merged, thank you @prx-my.

Worth saying what made this one easy to take: you updated every assertion in lockstep with the string it covers, so the suite stayed at full green the whole way rather than needing anything reconciled at the end. On a change touching thirty-six files that is the difference between a review and an archaeology session.