chore: strip the comments this branch added

Removes every comment introduced on this branch: website/ in full, pages.yml
in full, and only the blocks added to ci.yml and release.yml — their
pre-existing comments are untouched.

Two directives survive because they are load-bearing rather than prose: the
triple-slash vite/client reference, and nothing else.

Two comments were carrying behaviour that the code did not state, so the
code now states it. useCopy's rejection handler clears the copied flag
instead of sitting empty, and writeTheme returns whether the write actually
landed instead of swallowing the failure in a bare catch. isExternal drops
its regex for two startsWith calls, which reads the same and no longer
hides a `//` inside a literal.

.github/workflows/ci.yml

@@ -2,12 +2,6 @@ name: CI
 
 # Branch pushes are covered by the pull_request trigger. Listening to both for
 # every branch ran the whole matrix twice per PR.
-#
-# website/ holds the GitHub Pages site and no Rust. Ignoring it here must stay
-# in lockstep with the same list in release.yml: the two skip together, so the
-# release ci-gate never waits for a CI run that was never queued. Deliberately
-# not applied to pull_request — CI is a required check there, and a skipped
-# required check leaves the PR permanently unmergeable.
 on:
   push:
     branches: [master]

.github/workflows/pages.yml

@@ -1,7 +1,5 @@
 name: Pages
 
-# Only the website. The Rust workflows ignore this same path, so a site-only
-# push runs this alone and a code-only push never rebuilds the site.
 on:
   push:
     branches: [master]
@@ -29,8 +27,6 @@ jobs:
         with:
           bun-version: latest
 
-      # --frozen-lockfile so a drifted bun.lock fails here rather than
-      # silently shipping different dependency versions than were tested.
       - name: Install
         run: bun install --frozen-lockfile
 
@@ -40,8 +36,6 @@ jobs:
       - name: Lint
         run: bun run lint
 
-      # Emits one static HTML file per route plus a 404, so direct links
-      # answer 200 with real markup instead of the SPA shell.
       - name: Build
         run: bun run build
 
@@ -51,14 +45,10 @@ jobs:
 
   deploy:
     name: Deploy
-    # Pull requests get the build as a check; only master publishes.
     if: github.ref == 'refs/heads/master' && github.event_name != 'pull_request'
     needs: build
     runs-on: ubuntu-latest
     timeout-minutes: 10
-    # Scoped to the deploy, not the workflow: a workflow-level group would
-    # queue PR builds behind an in-flight master deploy for no reason. Never
-    # cancel in flight — a half-uploaded artifact leaves the live site broken.
     concurrency:
       group: pages
       cancel-in-progress: false

.github/workflows/release.yml

@@ -2,8 +2,6 @@ name: Release
 
 on:
   push:
-    # Must match ci.yml's paths-ignore exactly. A website-only push skips both
-    # workflows, so ci-gate is never left polling for an absent CI run.
     branches: [master]
     paths-ignore: ['website/**']
   workflow_dispatch:
@@ -51,10 +49,6 @@ jobs:
               2>/dev/null || echo "unreachable")
             case "$verdict" in
               success)          echo "CI passed for $GITHUB_SHA"; exit 0 ;;
-              # `cancelled` is what CI's own cancel-in-progress does to the
-              # older SHA when two pushes land back to back. Treating it as a
-              # failure turned every rapid push into a red release; keep
-              # waiting instead, and let the newer SHA's run decide.
               absent|running|unreachable|cancelled) ;;
               *) echo "::error::CI concluded '$verdict' for $GITHUB_SHA - refusing to release"; exit 1 ;;
             esac