docs: Break lines at meaning boundaries

[krlmlr]

Superseded by #199, which is the same branch opened with its head in this repository so that it can join the pull request stack. Continue there.

Reformatting only, no wording changes. Prose in README.Rmd, both vignettes, and the roxygen and inline comments under R/ now breaks at sentence and clause boundaries rather than wrapping to a fixed width.

The payoff is sentence-level diffs. A reworded sentence touches one line instead of reflowing the paragraph around it, so review sees the change and not the rewrap.

-#' `here()` uses reasonable heuristics to find your project's files, based on
-#' the current working directory at the time when the package is loaded.
+#' `here()` uses reasonable heuristics to find your project's files,
+#' based on the current working directory at the time when the package is loaded.

man/ is left to CI

man/*.Rd is not committed here. roxygen2 passes source line breaks straight through to the .Rd, so reformatting the sources does move the generated files — but they are generated output, and the Commit and push the generated changes step after Roxygenize regenerates and commits them once this merges. man/ therefore ends this branch byte-identical to main, and the diff stays prose only.

The rendered help does not move either way: every topic was compared with tools::Rd2txt() before and after and is byte-identical. Same for the README — rendered twice, byte-identical both times, and the README.md/index.md diffs contain only line breaks.

What was left alone

• Blocks that already conform. A good deal of this package was already written this way; those are untouched, and the rest now matches them.
• R/aaa.R — its prose lives in string literals inside paste(..., sep = "\n") that build the \section{Project root} fragment. That is code, and re-breaking it would change generated output.
• Code inside chunks, @examples, and YAML front matter.
• Two vignette lines remain at 142 columns; both overrun only because of an embedded URL, which the convention exempts, and the only break points available would split inside a link.

The sentence gap

A line break which follows the end of a sentence currently renders as one space rather than two, so writing one sentence per line drops the sentence gap from the rendered help. Restoring it needs a patched roxygen2, which is a separate decision: it is #197, stacked on top of this chain, and can be taken or left on its own. Without it this change simply renders as the package renders today.

This is the first of a fleet-wide pass and the one I reviewed by hand before running the rest, so it is the right place to push back on the convention or the mechanics if either looks wrong.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WWhverMTZZKgEpUuTK117m

---

Generated by Claude Code