Correct release note about room view.

AGENTS.md

@@ -80,6 +80,10 @@
   `state/stage-frame/`. Its persistent build/cache are
   `state/build-baiji/` and `state/ccache-cross-sdk/`. It configures
   `ENABLE_TESTS=OFF`; this is not a test build.
+- Snapshot release tarballs should use a fresh `STAGE_DIR` with the same Frame cross-SDK
+  build, then archive its `home/steamos/baiji` tree so the tarball root is `baiji/`. The
+  recipe and upgrade verification are in `docs/build-runbook.md`; do not upload or publish
+  without an explicit request.
 - `scripts/compile.sh [native|aarch64] [target...]` is the general container build
   helper; it defaults to `native` and `dolphin-emu`. It uses cached local Podman
   images `baijisteamvr-build:amd64` and `baijisteamvr-build:arm64` and does not rebuild

Readme.md

@@ -60,24 +60,31 @@ in the executable. If you have changed it, you may need to do some
 symlinking or hardlinking to have this end up unpacked into
 `/home/steamos/baiji`.)
 
+0. If you have installed a previous version of Baiji, make sure it's
+   not running.
 1. Start the Desktop environment in your Steam Frame.
 2. Navigate to this URL in a browser.
 3. Start `Konsole`, or the terminal of your choice.
 4. Copy this by clicking on the little double-square next to these
    commands:
 
-   ```bash
-   cd
-   wget https://github.com/thejerf/baijiSteamVR/releases/download/baiji-v0.1-alpha/baiji-v0.1-alpha.tar.bz2
-   tar xjf baiji-v0.1-alpha.tar.bz2
-   ssh frame "steamos-add-to-steam ./baiji/bin/baiji-vr"
-   ```
+    ```bash
+    cd
+    wget https://github.com/thejerf/baijiSteamVR/releases/download/baiji-v0.2-alpha/baiji-v0.2-alpha.tar.bz2
+    tar xjf baiji-v0.2-alpha.tar.bz2
+    ```
 5. Paste that into your Konsole session and hit "enter" on the
    keyboard.
+6. On first install only, add the launcher to Steam:
+
+   ```bash
+   ssh frame "steamos-add-to-steam ./baiji/bin/baiji-vr"
+   ```
    
 `baiji-vr` will appear as an option in your Non-Steam Games library.
 
-From there you'll need to load it up with your legally-acquired ROMs.
+Once installed, use the configuration menu to set your path to your
+ROM directory, or use File -> Open to play a ROM.
 
 ## Build and Install From an x86_64 Linux Machine
 
@@ -402,21 +409,7 @@ as I know these are currently not reasonable fixable:
     against a natively-compiled Dolphin.
   * Added + and - to mapping on left & right bumper for Wii +
     Nunchuck.
-  * Turning on Room View with the Steam UI stops rendering in Stereo
-    and VR mode and pauses the emulation, rather than continuing to
-    render and emulate and making it look like it was ignoring
-    controls.
-    
-    Ideally, we'd leave the game UI up if you bring up the Steam UI,
-    and only stop displaying the game if you go to full room view
-    mode, but once focus is removed from the game, baiji can't tell
-    what you're doing. Since we can't be smart about this, we have to
-    not display the game even if you only are looking at the Steam UI.
-    
-    This may be a bug in the UI's Room View support; it shouldn't let
-    us draw on it. If it correctly ignored our draw requests we could
-    get it to work like most other games, which still render in the
-    background.
+  * Room View support improved, but probably still needs work.
   * Improved the way a surface is requested for flat 2D mode. I'm
     honestly uncertain if v0.1-alpha was broken, but if it was this
     should fix it, if it wasn't, this should make future builds less

docs/build-runbook.md

@@ -44,6 +44,42 @@ The Frame's glibc is 2.39, so the dependency collector leaves glibc, `libmvec`,
 `libgpg-error` to the Frame's compatible system copies instead of bundling newer SDK
 builds.
 
+## Build a snapshot release tarball
+
+Build the normal Frame targets into a fresh staging directory, then archive the installed
+`baiji/` directory. A separate stage prevents files left by an older staged install from
+leaking into the release, while the normal CMake build and ccache remain incremental:
+
+```bash
+VERSION=v0.2-alpha
+STAGE_DIR="$(mktemp -d "$PWD/state/stage-release-$VERSION.XXXXXX")"
+INSTALL_PREFIX=/home/steamos/baiji STAGE_DIR="$STAGE_DIR" \
+  ./scripts/compile-cross-sdk.sh
+ARCHIVE="dist/baiji-$VERSION.tar.bz2"
+tar --sort=name -cjf "$ARCHIVE" -C "$STAGE_DIR/home/steamos" baiji
+```
+
+The archive's root entry is `baiji/`, matching the snapshot installation and upgrade
+commands in `Readme.md`. Check the archive contents and checksum before attaching it to a
+GitHub release; release upload/publication is a separate explicit step.
+
+To test an upgrade without touching a Frame install, extract the prior release and then the new
+archive into the same temporary home. Confirm the resulting install matches the new archive and
+that Baiji user data outside `baiji/` remains present:
+
+```bash
+UPGRADE_TEST="$(mktemp -d)"
+trap 'rm -rf "$UPGRADE_TEST"' EXIT
+mkdir -p "$UPGRADE_TEST/home/.config/baiji" "$UPGRADE_TEST/home/.local/share/baiji"
+touch "$UPGRADE_TEST/home/.config/baiji/upgrade-test" \
+  "$UPGRADE_TEST/home/.local/share/baiji/upgrade-test"
+tar -xjf baiji-v0.1-alpha.tar.bz2 -C "$UPGRADE_TEST/home"
+tar -xjf "$ARCHIVE" -C "$UPGRADE_TEST/home"
+tar -djf "$ARCHIVE" -C "$UPGRADE_TEST/home"
+test -f "$UPGRADE_TEST/home/.config/baiji/upgrade-test"
+test -f "$UPGRADE_TEST/home/.local/share/baiji/upgrade-test"
+```
+
 Smoke-test the CLI on the Frame:
 
 ```bash

scripts/compile-cross-sdk.sh

@@ -27,7 +27,7 @@ case "$DEBUG_SYMBOLS" in
 esac
 INSTALL_PREFIX="${INSTALL_PREFIX:-/home/steamos/baiji}"
 BUILD_DIR="$PWD/state/build-baiji"
-STAGE_DIR="$PWD/state/stage-frame"
+STAGE_DIR="${STAGE_DIR:-$PWD/state/stage-frame}"
 SDK="$PWD/state/flatpak-home/.local/share/flatpak/runtime/org.kde.Sdk/aarch64/6.10/active/files"
 FLATPAK_USER_DIR="$PWD/state/flatpak-home/.local/share/flatpak"
 SDK_OVERLAY="$PWD/state/sdk-overlay"