Bump opencode 1.15.13 -> 1.16.2, pick up pi 0.79.0

Bump OPENCODE_VERSION in Dockerfile.variant to 1.16.2 (rolls up the
1.16.0/1.16.1/1.16.2 upstream releases of 2026-06-05). The pi-bearing
variants pick up pi 0.78.1 -> 0.79.0 via CI's resolve-versions job.

Preemptively raise smoke size thresholds +150 MB on opencode-bearing
variants (base/omos/with-pi/omos-with-pi) and +100 MB on pi-only ahead
of the combined minor opencode + pi bump. base (2506) and omos (3206)
were on ~94 MB headroom and minor bumps have tripped these before
(v1.15.0, v1.15.4); restores ~250 MB headroom to avoid a partial publish.

Promote CHANGELOG Unreleased -> v1.16.2.

CHANGELOG.md

@@ -8,7 +8,52 @@ Tags follow `v{opencode_version}[letter]` — bare tag for the first build on a
 
 ## Unreleased
 
-_(no changes since v1.15.13e)_
+_(no changes since v1.16.2)_
+
+## v1.16.2 — 2026-06-08
+
+First container build on the `opencode-ai@1.16.x` minor release (rolls up
+`1.16.0` → `1.16.1` → `1.16.2`, all published 2026-06-05). Also picks up
+**pi `0.78.1` → `0.79.0`** (resolved fresh by CI's `resolve-versions` job) in
+the `with-pi`, `omos-with-pi`, and `pi-only` variants.
+
+### Bumped: opencode-ai 1.15.13 → 1.16.2
+
+`OPENCODE_VERSION` ARG in `Dockerfile.variant`. Highlights from the upstream
+release (full notes: <https://github.com/anomalyco/opencode/releases>):
+
+- **1.16.0** — ~38% faster startup (@StarpTech); managed workspace cloning that
+  keeps dirty/untracked files; move sessions between workspaces/directories;
+  proper OpenAI-via-Bedrock support; skill discovery + file-based agent loading;
+  `run --replay` for interactive session replay. Plus TUI/desktop polish and
+  numerous bugfixes (shell cancellation races, Windows path normalization, ACP
+  cancel/abort).
+- **1.16.1** — internal/no user-visible notes (empty release body).
+- **1.16.2** — reasoning summaries only run on supporting providers (avoids
+  GPT-5 request failures); edit operations refuse loose matches that could
+  overwrite the wrong code; Bedrock hang-before-first-token fix; diff-viewer
+  hunk navigation; subagents can be backgrounded; Snowflake Cortex provider.
+
+### Picks up: pi 0.78.1 → 0.79.0
+
+Resolved at build time for the pi-bearing variants. Headlines: project-trust
+prompting for project-local settings/resources/instructions/packages (with
+`--approve`/`--no-approve` and a `project_trust` extension event), cache-hit
+rate in the interactive footer, richer SDK/RPC extension surfaces, plus a
+stack of TUI and provider fixes. Full notes ship in the npm tarball's
+`CHANGELOG.md`.
+
+### Smoke size thresholds bumped +150 MB (preemptive)
+
+Ahead of the combined minor opencode + pi bump, all opencode-bearing variant
+thresholds in `scripts/smoke-test.sh` were raised: `base` 2600 → 2750,
+`omos` 3300 → 3450, `with-pi` 2900 → 3050, `omos-with-pi` 3900 → 4050; and
+`pi-only` 2750 → 2850 (+100, pi-only carries only the pi bump). Both `base`
+(last 2506 MB) and `omos` (last 3206 MB) were on ~94 MB headroom, and a minor
+opencode bump has tripped these ceilings before (v1.15.0 omos, v1.15.4
+omos-with-pi), causing a partial publish + letter-suffix recovery cycle.
+Restoring ~250 MB headroom avoids that. CI's smoke size print records actual
+landed sizes — tighten later if they come in well under.
 
 ## v1.15.13e — 2026-06-04
 

Dockerfile.variant

@@ -42,7 +42,7 @@ ARG USER_NAME=developer
 # edit, so the cache-hit class of bug that bit pi-devbox v0.74.0..
 # v0.75.5 cannot apply here.
 ARG INSTALL_OPENCODE=true
-ARG OPENCODE_VERSION=1.15.13
+ARG OPENCODE_VERSION=1.16.2
 RUN if [ "${INSTALL_OPENCODE}" = "true" ]; then \
       NPM_CONFIG_PREFIX=/usr npm install -g opencode-ai@${OPENCODE_VERSION} && \
       opencode --version ; \

scripts/smoke-test.sh

@@ -392,13 +392,20 @@ echo "  Uncompressed size: ${SIZE_MB} MB"
 # deliberately zero-headroom 2500 ceiling and skipping promote-base-latest.
 # omos variant to ~3.1 GB. Functional smoke checks all pass; this is a
 # guardrail, not a performance limit.
-THRESHOLD=2600
+# v1.16.2: all thresholds bumped +150 MB preemptively ahead of the combined
-[ "$VARIANT" = "omos" ] && THRESHOLD=3300
+# opencode 1.15.13->1.16.2 (minor) + pi 0.78.1->0.79.0 (minor) bump. Both
-[ "$VARIANT" = "with-pi" ] && THRESHOLD=2900
+# base (2506/2600) and omos (3206/3300) were sitting on ~94 MB headroom and
-[ "$VARIANT" = "omos-with-pi" ] && THRESHOLD=3900
+# a minor opencode bump has tripped them before (v1.15.0 omos, v1.15.4
+# omos-with-pi). Restoring ~250 MB headroom avoids a partial-publish +
+# letter-suffix recovery cycle. CI's smoke size print + resolved-versions
+# table records the actual landed sizes; tighten later if they come in low.
+THRESHOLD=2750
+[ "$VARIANT" = "omos" ] && THRESHOLD=3450
+[ "$VARIANT" = "with-pi" ] && THRESHOLD=3050
+[ "$VARIANT" = "omos-with-pi" ] && THRESHOLD=4050
 # pi-only = with-pi minus opencode (its platform binary is ~145 MB), so it
 # lands a bit under base. Threshold 2750 leaves the same headroom pattern.
-[ "$VARIANT" = "pi-only" ] && THRESHOLD=2750
+[ "$VARIANT" = "pi-only" ] && THRESHOLD=2850
 if [ "$SIZE_MB" -gt "$THRESHOLD" ]; then
   fail "image size ${SIZE_MB} MB exceeds threshold ${THRESHOLD} MB for variant=$VARIANT"
 else