Core and desktop comments describe the code to a stranger (#6224)

Milestone 546 "Bring the repo to the comment standard (rule 32) and
compose defaults (rule 198)", step #6224 "Comment standard sweep: Rust
core and desktop client".

Doc comments and comments across inkwell-core, the Tauri app and
desktop/packaging now say what the code does and the non-obvious why in
the present tense. Gone: milestone tags (M10.x, M11.3, M13, M304, M315,
M314, milestone 325), issue and Scribe-note numbers, family-idea and
family-rule citations, the run numbers and commit hashes behind past
bugs, and the narration of what used to be (the stable channel before it
held its own bundles, CARGO_PKG_VERSION as the shown version, the
MANIFEST_TAG split, the store's missing tests, the old PKGBUILD). The
schema's migration notes keep what each step does and why, without
"until now". The forge is called the forge rather than Forgejo.

Hazards stay as facts: the dev-rolling tag that must not shadow the
branch, the manifest matched on this build's version, the APK's fixed
name surviving the prune, the LIKE guard in v9, -wal/-shm moving with
the renamed store, panic = abort ending the app.

34 files, comments only: a comment-stripping diff of every changed file
against HEAD is identical.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

desktop/packaging/arch/package-prebuilt.sh

@@ -3,8 +3,8 @@
 # Build a PREBUILT Arch package (.pkg.tar.zst) from the binary the desktop CI job
 # already compiled — no makepkg, no Arch container, no second Rust build.
 #
-# WHY prebuilt: the source PKGBUILD this replaces required every user to install
-# rust + nodejs + npm and compile for minutes before they could open the app.
+# WHY prebuilt: a source PKGBUILD would make every user install rust + nodejs +
+# npm and compile for minutes before they could open the app.
 # Distribution means shipping a package people can just install, so the one-command
 # installer (install.sh) can `pacman -U` a real native package on Arch/CachyOS
 # instead of falling back to the AppImage.
@@ -14,8 +14,8 @@
 # SONAME at runtime, and those sonames are identical on both distros; SQLite is
 # compiled in (rusqlite "bundled"). glibc symbol versioning is forward-compatible,
 # and we build on Debian's older glibc and run on Arch's newer one — the safe
-# direction. Using the host's graphics stack is also exactly what keeps issue 2021
-# (bundled-lib EGL_BAD_PARAMETER black window) fixed.
+# direction. Using the host's graphics stack is also what avoids the bundled-lib
+# EGL_BAD_PARAMETER black window.
 #
 # A .pkg.tar.* is just a tar whose FIRST entry is .PKGINFO, so we assemble it
 # directly rather than nesting an Arch container over the docker socket.
@@ -33,10 +33,9 @@ BINARY="$REPO_ROOT/target/release/inkwell"
 OUT_DIR="${1:-$REPO_ROOT/target/release/bundle/arch}"
 
 PKGNAME="inkwell"
-# The names this package used to ship under: `thoughtsync` until the app became
-# Inkwell (Scribe note 5071), `thoughtsync-desktop` before that. pacman needs both
-# conflict and replace to retire them: without them a `pacman -U` of the renamed
-# package installs ALONGSIDE the old one (issue 2075).
+# Earlier names of this package: `thoughtsync` and `thoughtsync-desktop`. pacman
+# needs both conflict and replace to retire them: without them a `pacman -U`
+# installs ALONGSIDE the old one.
 REPLACES=(thoughtsync thoughtsync-desktop)
 PKGREL=1
 PKGDESC="Inkwell desktop — local-first Keep-style thought capture"
@@ -58,11 +57,9 @@ DEPENDS=(webkit2gtk-4.1 gtk3)
 
 # Single source of truth for the version: the SAME helper the bundle build uses.
 #
-# It used to read tauri.conf.json directly, which was right until dev builds began
-# overriding the version on the command line (M10.9) — the file still says 0.1.0, so
-# the pacman package came out stamped 0.1.0 around a binary reporting 0.1.132. A
-# package that lies about its version is exactly what makes a later "which build is
-# this?" question unanswerable.
+# Not tauri.conf.json: dev builds override the version on the command line and the
+# file says 0.1.0, so reading it would stamp the package with a version its binary
+# doesn't report.
 # `|| true` so a miss falls through to the explicit error below rather than
 # aborting on pipefail with no explanation.
 # The ORDERING KEY: pacman compares this, and it must match the filename the
@@ -127,7 +124,7 @@ INSTALLED_SIZE="$(du -sb "$STAGE" | cut -f1)"
 # pacman uses .MTREE for `pacman -Qkk` file verification; it is NOT required to
 # install, and generating it needs bsdtar (libarchive-tools), which the Debian CI
 # image may not carry. Emit it when we can, skip loudly when we can't, rather
-# than adding an apt install to the job (rule 5: the image is the toolchain).
+# than adding an apt install to the job (the image is the toolchain).
 MTREE_ENTRY=()
 if command -v bsdtar >/dev/null 2>&1; then
   ( cd "$STAGE" && LANG=C bsdtar -czf .MTREE --format=mtree \