treefmt: apply prettier

Pure `nix fmt` output from the commit before this one — no hand edits.
203 files: 52 md, 42 tsx, 32 js, 32 css, 21 ts, 13 html, 8 json, 3 mjs.

Reproduce with `nix develop -c nix fmt` on the parent commit; the result
should be byte-identical to this tree.

None of the 13 `.prettierignore` entries appears here — verified by
intersecting the changed-file list against the ignore file, with a
control proving the intersection finds a match when one exists.

docs/integrations/github.md

@@ -109,7 +109,7 @@ Forgejo's notifications API is modelled on GitHub's, so one tolerant
 parse serves both: `id`, `repository.full_name`,
 `subject {title,url,latest_comment_url}` and `updated_at` line up field
 for field. The two real differences are absorbed by lenient
-deserializers — GitHub sends the thread id as a *string* where Forgejo
+deserializers — GitHub sends the thread id as a _string_ where Forgejo
 sends a number, and says `PullRequest` where Forgejo says `Pull`. Todo
 keys are prefixed `gh:<id>` so a github thread id cannot collide with a
 forge one.
@@ -118,16 +118,16 @@ Two host differences worth knowing before touching this code:
 
 - **Auth scheme, not just value.** Forgejo takes
   `Authorization: token <t>`; GitHub wants `Bearer <t>` plus `Accept:
-  application/vnd.github+json`, `X-GitHub-Api-Version` and a
+application/vnd.github+json`, `X-GitHub-Api-Version` and a
   `User-Agent`. Sending Forgejo's form to GitHub does not error — it
-  authenticates as *nobody* and silently drops to the unauthenticated
+  authenticates as _nobody_ and silently drops to the unauthenticated
   rate limit. The cheap way to tell the two apart is the rate-limit
   header: `x-ratelimit-remaining` near 5000 is an authenticated user,
   near 60 is anonymous.
 - **GitHub sets the cadence.** It returns `X-Poll-Interval` (60s in
   practice, slower than our own tick) and rate-limits callers who ignore
   it, so the loop re-arms to the server's interval whenever that is
-  *slower* than ours. A hint faster than our own tick is not a reason to
+  _slower_ than ours. A hint faster than our own tick is not a reason to
   poll harder.
 
 ⚠️ **This needs the `notifications` scope on the PAT.** A token minted