Move the build, release, and acceptance docs to the documentation site

The documentation site, docs.forgefirm.org, is the one home for the
developer documentation. BUILD.md, kas/README.md, and docs/ACCEPTANCE.md
are on the site under Developers, and they are deleted here. Every
reference points at the site: README.md, BRINGUP.md, UPDATE-SYSTEM.md,
the kas configuration comments, release.sh, the CI workflow comments, and
the releases, forgetest, and bench READMEs.

BRINGUP.md: "Next work" item 16, step timing under CPU contention, is
closed; the video work resolved it. The items after it are renumbered.
CAMPAIGN-LOG.md records the closure.

Documentation and comments only. No layer content changes, so the
manifest identity of the next image does not change. No catalog
consequence.

scripts/bench/README.md

@@ -4,7 +4,7 @@ Hardware-verification tools for the ForgeFIRM bench. All run ON the
 target board (dev image, python3 present) unless noted. The dev image
 installs them under `/usr/share/forgetest/bench/`, and the acceptance
 tool's **Bench diagnostics** tab (`http://<machine>:8090/#bench`,
-`docs/ACCEPTANCE.md`) runs them with their arguments and the output on
+the site, Developers, "Acceptance") runs them with their arguments and the output on
 the page - takeover and scope tools get forgectrl and the controller
 stopped and started around the run, live tools need the operator
 acknowledgment; the acceptance catalog itself is built from ports of

scripts/release.sh

@@ -24,7 +24,8 @@
 #   RELEASE_STAGING_DIR  where release assets are staged
 #                        (default: <repo>/release-staging)
 #   FORGEFIRM_ACCEPTANCE_SKIP  set to 1 to bypass the acceptance gate
-#                        deliberately (never the default; docs/ACCEPTANCE.md)
+#                        deliberately (never the default; see the site,
+#                        Developers, "Acceptance")
 #
 # Version contract: <version> == FORGEFIRM_RELEASE in forgefirm-image.bb
 # == /etc/forgefirm-version ("v<version>") in the built rootfs == .fw
@@ -142,7 +143,8 @@ STAMP=$(debugfs -R "cat /etc/forgefirm-version" "$EXT4" 2>/dev/null)
 # Acceptance gate: the committed acceptance artifact must authorize THIS
 # build. scripts/acceptance-gate.py recomputes every catalog test's domain
 # fingerprint from the manifest inside the release rootfs and requires the
-# recorded PASS to match (docs/ACCEPTANCE.md). A release is never signed
+# recorded PASS to match (https://docs.forgefirm.org/developers/acceptance/).
+# A release is never signed
 # without it; FORGEFIRM_ACCEPTANCE_SKIP=1 bypasses deliberately and loudly.
 ART="$REPO/releases/v$VERSION/acceptance.json"
 if [ -n "${FORGEFIRM_ACCEPTANCE_SKIP:-}" ]; then
@@ -202,7 +204,8 @@ fi
 
 echo "== stage assets =="
 cp -L "$DEPLOY/forgefirm-image-glowforge.rootfs.wic.gz" "$STAGE/forgefirm-image-glowforge.rootfs.wic.gz"
-# The acceptance artifact travels with the release (docs/ACCEPTANCE.md).
+# The acceptance artifact travels with the release (see the site,
+# Developers, "Acceptance").
 ASSETS="forgefirm.fw sha256sums.txt forgefirm-image-glowforge.rootfs.wic.gz"
 if [ -f "$ART" ]; then
   cp "$ART" "$STAGE/acceptance.json"
@@ -219,7 +222,7 @@ cat <<EOF
 
 == release v$VERSION staged ==
 
-Pre-publish checklist (kas/README.md "Push & release order" step 4):
+Pre-publish checklist (docs.forgefirm.org, Developers, "Release flow"):
   - meta-openglow pushed; kas config flipped to the pinned-remote block
   - kas lock refreshed
   - self-containment proven from a fresh clone