Validate v1.1 Linux Docker and interactive setup

[BrettKinny]

This was generated by AI during triage.

Type: HITL

What to build

Run the v1.1 Candidate through the real Linux Docker desktop and interactive setup paths that cannot be represented truthfully by headless CI. Exercise fresh install, v1.0 Managed-home adoption, Box replacement, destructive-operation safeguards, interactive selections, and terminal applications on one supported Linux desktop.

Record the Candidate version, source SHA, image digest, distribution, architecture, Docker version, terminal, and pass/fail evidence in this issue.

Acceptance criteria

• Fresh Bash install, launch, interactive setup, exit/resume, rebuild, uninstall, and purge behave as documented.
• A v1.0 Managed home upgrades with explicit adoption, no repeated prompts, preserved authentication/history, refreshed managed config, and reconciled Box-tier Selections.
• A host UID/GID other than 1000 plus custom install/Workspace/Managed-home paths retain correct ownership and survive rebuild.
• Purge refuses colliding unrelated resources; an unavailable Docker daemon returns a clear nonzero partial-cleanup result.
• Cancel and confirmed-empty selections remain distinct; a deliberately failed assistant install leaves aliases targeting an observed assistant.
• GitHub device authentication and decline state survive Box replacement.
• Claude, Copilot, Gemini, Codex, OpenCode, Pi, and Paseo launch after selection; Copilot uses the supported copilot command.
• Bash, Zsh, and Fish initialize the documented prompt/navigation/alias behavior, including Bash-only fzf bindings.
• Lazygit, Yazi, gh-dash, Helix, gum, fzf, tmux, Zellij, and Neovim/LazyVim render and accept input; the timezone mount does not wedge package installation.
• Results and any failures are attached here and the v1.1 manual UAT checklist is updated.

Blocked by

None - can start immediately.

[BrettKinny]

Partial physical Linux Docker evidence from the v1.1.0-rc8 Tower deployment. This does not close the issue.

Candidate identity:

• Version: v1.1.0-rc8
• Source SHA: 09b80b6
• Multi-architecture digest: sha256:6252490bab55ca56747f1c540efaef801b6a3ba197220ba3552a0b5eccfd1c51
• Release: https://github.com/SquareWaveSystems/squarebox/releases/tag/v1.1.0-rc8
• Qualification run: https://github.com/SquareWaveSystems/squarebox/actions/runs/29489931250

Physical host/runtime:

• Unraid 7.3.1, x86_64
• Docker client/server 29.5.2
• Long-lived Compose deployment under /mnt/user/appdata/squarebox
• Host identity mapped to uid 99, gid 100

Passed on Tower:

• Replaced the prior RC4 Box with the exact published RC8 digest without rebuilding.
• Preserved the existing squarebox_squarebox-home volume and /mnt/user/appdata/squarebox/workspace bind through force recreation.
• Persistence markers in both stores survived recreation and a subsequent container restart.
• /home/dev and /workspace remained writable as dev 99:100.
• The saved Fish selection reconciled during replacement; fish is available after restart.
• VERSION and image metadata report v1.1.0-rc8; Compose and container config retain the exact digest.
• Pre-deployment Compose and environment backups remain on the host.

Still outstanding here: fresh Linux desktop lifecycle, interactive assistant and TUI matrix, destructive-operation safeguards, device-auth persistence, and the remaining documented Bash/Zsh/Fish terminal behavior. Issue remains open.