Add parent's operations manual (repo + baked at /usr/share/doc) and

document the Gitea OTA update path (bootc switch + publish routine)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

BUILD-CONSOLE.md

@@ -99,6 +99,35 @@ docker run --rm localhost/bc250-console-gnome:latest rpm -q kernel
 
 First successful build shipped `kernel-7.0.9-ogc3.2.fc44` — fine.
 
+## Publish an update (OTA to the installed console)
+
+The installed console follows `git.lazypugs.com/ckoch/bc250-console-gnome:latest`
+(one-time `bootc switch` after install — see below). To ship an update:
+
+```bash
+# rebuild the image (steps 1–2 above), then:
+docker login git.lazypugs.com          # Gitea token with package write scope
+docker tag localhost/bc250-console-gnome:latest \
+  git.lazypugs.com/ckoch/bc250-console-gnome:latest
+docker push git.lazypugs.com/ckoch/bc250-console-gnome:latest
+```
+
+The console's `uupd` timer picks it up automatically; to force it,
+SSH in and run `sudo bootc upgrade && sudo systemctl reboot`.
+
+**One-time, on the console after first install** (points the OS at the
+registry instead of the offline install source):
+
+```bash
+sudo bootc switch git.lazypugs.com/ckoch/bc250-console-gnome:latest
+```
+
+If the Gitea package is private, the console needs pull credentials first:
+put a read-scope token in `/etc/ostree/auth.json`:
+`{"auths":{"git.lazypugs.com":{"auth":"<base64 of user:token>"}}}` —
+or make the package public in Gitea (Packages → bc250-console-gnome →
+Settings) and skip that.
+
 ## Smoke test + install
 
 1. **VM test**: boot the ISO in a VM (KVM works headless: