docs: verify compatibility with OpenShell 0.0.113 and apple/container 1.3.0

[vyncint]

Tested the newer upstreams as asked. No driver change was needed — this is documentation only.

OpenShell 0.0.111 → 0.0.113

compute_driver.proto is byte-identical between the two tags, so there was no contract risk. Verified live: setup derived supervisor:0.0.113 and pulled it, then create → Ready → exec → policy-blocked egress → clean delete.

(Aside worth knowing: supervisor:0.0.112 returns 404 on ghcr — not every OpenShell release publishes a supervisor image. That is exactly the case the driver's fallback covers, and why deriving the tag from the gateway version needs one.)

apple/container 1.2.2 → 1.3.0

A minor release, so I read its notes against our code before touching anything:

Upstream change	Effect here
⌨️ --scheme auto removed for image operations	none — the driver never passes --scheme
tmpfsMounts() refactored	the driver does use --tmpfs, so this needed testing
New default Kata kernel (3.32.0-debug)	touches ensureKernel() and --kernel
maskedPaths/readonlyPaths no longer defaulted	could change in-guest behaviour

I captured a baseline on 1.2.2 before the upgrade so the comparison would mean something. Everything matched afterwards:

Check	1.2.2 baseline	1.3.0
create → Ready	Ready	Ready
exec kernel	6.18.15 aarch64	6.18.15 aarch64
workload uid	998	998
policy egress	blocked	blocked
tmpfs mount	tmpfs on /scratch type tmpfs (rw,relatime), writable	identical
restart adoption	Ready + exec	Ready + exec
delete	clean	clean, 0 VMs left

The existing default.kernel-arm64 → vmlinux-6.18.15-186 survived the upgrade untouched, so ensureKernel() correctly skips re-downloading — the new default kernel only affects fresh installs.

Also found (not fixed here)

apple/container's update-container.sh runs sudo installer … >/dev/null 2>&1 || error "Installer failed", which swallows the real error. Run unprivileged, the mid-script sudo prompt is easy to miss and you get a bare Error: Installer failed with no cause. Running the whole script under sudo avoids it. That is upstream's script, not ours, but it is worth knowing when update --all --container-version is used.

Verification

go build, go test -race, golangci-lint (0 issues), shellcheck install.sh, goreleaser check, govulncheck/gosec/gitleaks — all clean.