Qualify v1.2 Linux Docker and interactive setup

[BrettKinny]

This was generated by AI during triage.

Type: HITL

Parent

• Release v1.2.1 from one qualified Candidate #125

What to build

Qualify the v1.2 Candidate through the real Linux Docker desktop and
interactive setup paths that headless CI cannot represent truthfully. Exercise
fresh and retained-home lifecycle behavior, destructive-operation safeguards,
interactive Selection semantics, shells, and the user-facing tools added or
changed for v1.2.

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

Acceptance criteria

• Fresh install, launch, interactive setup, exit/resume, rebuild, uninstall, and purge behave as documented.
• A retained v1.1 Managed home upgrades without losing authentication, history, or Selection state; Box-tier tools reconcile from observed state.
• A non-1000 host UID/GID and custom install, Workspace, and Managed-home names retain correct ownership through rebuild and purge.
• Purge refuses unrelated colliding resources and an unavailable runtime returns a clear nonzero partial-cleanup result.
• Cancelled and intentionally empty Selections remain distinct; a deliberately failed install does not publish stale Selection or aliases.
• Elio, Herdr, and Oh My Pi install through their production paths, launch, survive Box replacement as appropriate to their Tool tiers, and report observable versions.
• The managed Zellij default detaches sessions when a client disappears without overwriting an explicit user on_force_close choice.
• Bash, Zsh, and Fish initialize the documented prompt, navigation, alias, mise, and Bash-only binding behavior.
• Representative editors, TUIs, multiplexers, and assistants render and accept input.
• Results and failures are attached here and reflected in the v1.2 UAT checklist.

Blocked by

• Release v1.2.1 from one qualified Candidate #125

[BrettKinny]

This was generated by AI during triage.

v1.2.1-rc1 Linux lifecycle UAT found a second NO-PROMOTE blocker after the automated Candidate passed.

Candidate identity:

• source: 28481ae
• image digest: sha256:98adcc2bfceffe9d730220eef64e0843817cedae1fbaadacfa5e3f8241544430

Exact failure: a Docker Box using PUID=12345, PGID=23456, a named /home/dev volume, and the lifecycle-managed /home/dev/.bashrc read-only bind exited 12. GNU usermod attempted to re-own the account home during the UID change and failed at the read-only child mount. Control probes passed without the managed-file bind and with the ordinary 1000:1000 identity.

Fix-forward PR #142 adds canonical-home recovery plus a required production-capability regression that verifies passwd home, Managed-home ownership/writability, profile integrity, and restart idempotence. rc1 remains rejected; the corrected immutable Candidate will be v1.2.1-rc2 or later.

[BrettKinny]

This was generated by AI during triage.

v1.2.1 Linux Docker qualification: FAIL / NO-PROMOTE

Candidate:

• v1.2.1-rc4
• source 1748be59528750335d33f717d4b8dc1707c24945
• digest sha256:d56eb3c6bf4c8a2f1903b5105cec80e4eef862cd10b62d987756b56937e086eb
• physical Arch Linux x86_64; Docker client/server 29.6.2; Box Ubuntu 26.04; xterm-256color

Confirmed blocker:

• Host installer identity was 1000:1000; requested Box identity was 4242:4243.
• First start recursively traversed host bind mounts beneath /home/dev and changed private Git/config ownership to 4242:4243.
• Exact rebuild and retained-home reinstall failed: mktemp .../.squarebox/identity/git/.git-config.XXXXXX: Permission denied.
• Exact purge removed the image and Managed home, then returned 1 because it could not remove the foreign-owned install tree.
• Dedicated bug: Reject unsafe unprivileged Linux PUID/PGID overrides #145.

Passed before or with explicitly recorded UAT-only ownership remediation:

• Exact release identity, labels, mounts, state mode, non-1000 Box identity, and writable runtime ownership.
• Real Gum render/cancel preserved no Selection; intentional empty AI Selection remained distinct.
• Production OMP 17.2.0, Elio 1.11.2, Herdr 0.7.5, Zellij 0.44.3, and tmux 3.6 installs/version probes.
• Elio rendered and accepted q; explicit Zellij on_force_close "quit" survived reconcile/replacement.
• Exit/resume and, after controlled repair only, Workspace/Managed-home/auth/history/tool persistence.
• Purge refused an unrelated unlabeled collision; unavailable Podman returned clear nonzero partial-cleanup diagnostics.

Not claimed: retained v1.1 migration, full Bash/Zsh/Fish matrix, deliberately failed production tool install, or the broader editor/TUI/assistant input matrix.

Cleanup verified: every UAT-created container, volume, helper, image tag, and temporary path was removed. The pre-existing unlabeled squarebox-home volume remains untouched.

Decision: NO-PROMOTE rc4. Fix #145, publish rc5, then rerun genuine non-1000 Linux qualification and all incomplete criteria here.

[BrettKinny]

This was generated by AI during triage.

v1.2.1-rc5 focused Linux Docker requalification: PASS / PARTIAL

Candidate:

• exact source 8f56f759acdf735c50e1bd0464dd852c28618deb
• exact digest sha256:861dd7c2ae0e69ae18641bb3817ed0647570c5527b3b3354bfc8f073817b55f5
• Candidate E2E run 30633759703: all 12 jobs passed
• immutable prerelease; 10/10 assets attested and checksum-clean; 26/26 required Evidence

#145 regression:

• Published rc5 installer invoked by physical Linux account 1000:1000 with requested 4242:4243 returned exactly 64.
• Diagnostic reported both invoking and requested identities.
• Rejection occurred before install-path creation and before any Docker call; isolated HOME/Workspace and the unique volume were untouched.

Matching-ID lifecycle:

• Fresh install with 1000:1000, launch/identity, exit-resume, exact state-derived rebuild, uninstall retaining home, reinstall, persistence, and exact purge all passed.
• Rebuild replaced the Box while preserving Managed-home and Workspace markers.
• Private Git, Starship, Lazygit, and Workspace ownership remained 1000:1000 throughout.
• Purge returned 0 and removed only the recorded Box, image refs, install tree, and unique sqbx-rc5-uat-sbIPy9-home volume.
• Pre-existing unlabeled squarebox-home remained untouched; its before/after metadata SHA-256 was byte-identical: 137695938ad939ed553e473dfa99954fac1c9f02d2be1a7ee671fefb5864d57d.

Harness notes:

• One interactive first-run path required Ctrl-C because scripted commands were consumed by the setup wizard. Stopping that interactive PID 1 escalated to SIGKILL after Docker timeout (137); subsequent lifecycle and persistence checks passed, so this was not an image crash.
• A first rebuild inherited host XDG_CONFIG_HOME and refreshed only the isolated Squarebox private Git name/email copy. Ownership stayed correct and no host file changed; later commands pinned isolated XDG.

Outcome: #145 is fixed and the published rc5 regression passes. This issue stays open: genuine non-1000 account lifecycle, retained v1.1 migration, full Bash/Zsh/Fish, failed production install, and the broader interactive tool matrix remain incomplete.

[BrettKinny]

This was generated by AI during triage.

v1.1.0 retained-home upgrade to v1.2.1-rc5: PASS / scoped

A real isolated Linux Docker lifecycle exercised the published v1.1.0 adapter, upgraded that same Install identity to the published rc5 adapter, then performed an exact rc5 rebuild. This closes the mechanical retained-home migration slice; it does not claim real GitHub credentials or human prompt behavior.

Identity:

• v1.1.0 source 2e6176d9e15739b3f7faedb3aafea523fd203a51
• v1.1.0 digest sha256:0e240dc74f3bc49b49d9a276a50477412be81b0aac704452bf7adab1bac25780
• rc5 source 8f56f759acdf735c50e1bd0464dd852c28618deb
• rc5 digest sha256:861dd7c2ae0e69ae18641bb3817ed0647570c5527b3b3354bfc8f073817b55f5
• Install ID 941955f8-1bf3-4b9a-8f99-e4c830a5e5ca remained unchanged
• unique Managed-home volume sqrbx-retained-v11-rc5-ooDdw0

Passed:

• The v1.1.0 install resolved its exact published source/digest and started under the historical fixed squarebox container name after a zero-container preflight.
• Upgrade resolved the exact rc5 source/digest and replaced the container while retaining the same Install ID.
• Managed-home, GitHub-auth sentinel, Selection, and external Workspace markers all survived the upgrade.
• VERSION reported v1.2.1-rc5; relevant retained files and paths remained owned by 1000:1000.
• Exact state-derived rc5 rebuild replaced the container again and preserved the same source, digest, image, Install ID, markers, and ownership.

Cleanup:

• Exact uninstall.sh --purge --yes removed the UAT container, unique volume, image alias, install tree, and harness.
• Final audit found zero containers and no sqrbx-retained-v11-rc5-* volume or test image refs.
• The external Workspace was verified preserved before its exact temporary root was removed.
• Pre-existing unlabeled squarebox-home remained present with unchanged creation metadata.
• The original checkout remained clean and unchanged.

#126 remains open for genuine non-1000-host ownership, real authentication/prompt behavior, full shell/interactive-tool coverage, and the remaining safety/transactional slices.

[BrettKinny]

This was generated by AI during triage.

v1.2.1-rc5 genuine non-1000 Linux VM qualification: PASS / scoped

A disposable KVM-backed Ubuntu VM exercised the published rc5 lifecycle through a genuine non-1000 login and an independent Docker daemon. This closes the ownership/lifecycle slice; it does not claim the remaining human interactive terminal matrix.

Environment and identity:

• Ubuntu 24.04.4 guest from the official cloud image; published SHA-256 verified as d1940f7d69d343355e183dff1e08a59852d32e7309baa7a4bad8365b11b005ac
• genuine SSH login uat, UID/GID 2000:2000, shell /bin/bash, groups uat sudo docker
• independent guest Docker 29.1.3 with cgroup v2
• rc5 source 8f56f759acdf735c50e1bd0464dd852c28618deb
• rc5 digest sha256:861dd7c2ae0e69ae18641bb3817ed0647570c5527b3b3354bfc8f073817b55f5
• Install ID 238b13f4-441d-495b-87e3-8de110b77074

Passed:

• Candidate release assets and release.json checksum/source/digest identity verified before install.
• Fresh install recorded PUID/PGID 2000, exact tag/source/ref/digest, correct ownership labels, and the genuine guest identity.
• After normal Box startup readiness, dev, Managed home, private lifecycle paths, and external Workspace were all owned and writable as 2000:2000.
• Exact rebuild replaced the container while retaining the same Install ID, source, digest, and image.
• Managed-home, GitHub-auth sentinel, Selection, and Workspace markers survived rebuild; VERSION remained v1.2.1-rc5; checked ownership remained 2000:2000.
• Exact uninstall.sh --purge --yes removed the guest container, unique Managed-home volume, image refs/alias, and install tree while preserving the external Workspace as documented.

Harness diagnosis:

• An initial immediate docker exec briefly raced entrypoint ownership reconciliation and saw .bash_profile unreadable. A second instrumentation attempt accidentally polled before starting the intentionally stopped Box.
• Correct sequencing—docker start, then readiness polling—passed on poll attempt 2 for both initial start and rebuild. This was a harness ordering artifact, not persistent rc5 ownership failure; normal attached Squarebox startup follows the entrypoint.

Cleanup:

• Guest powered off cleanly; the QEMU utility container/image, VM disks, cloud-init seed, ephemeral SSH keys, logs, and temporary root were removed.
• Port 22222 is free and the host has zero containers.
• No host virtualization packages were installed.
• Pre-existing unlabeled squarebox-home remains unchanged and the original checkout remains clean.

#126 remains open only for the human interactive/authentication/shell/tool observations that cannot be represented truthfully by this automated VM run.