Copy bundled browser extension assets into runtime image

The new runtime stage no longer includes assets/chrome-extension, so openclaw browser extension install will fail in built images with Bundled Chrome extension is missing. The CLI resolves its source bundle from assets/chrome-extension (see src/cli/browser-cli-extension.ts), and previously this directory was present because the full repo was copied into the image; after this change only selected paths are copied.

Useful? React with 👍 / 👎.

assets/ was already in .dockerignore, so it was never in the Docker image. The chrome extension install from a container would have failed before our changes too.

ARG OPENCLAW_VARIANT belongs in the runtime stage, not base-slim

Per Dockerfile multi-stage semantics, the ARG OPENCLAW_VARIANT on line 69 sits between FROM ... AS base-slim (line 66) and FROM base-${OPENCLAW_VARIANT} (line 70), so it is scoped to the base-slim stage and effectively unused.

The FROM base-${OPENCLAW_VARIANT} substitution works today because the global ARG OPENCLAW_VARIANT=default declared on line 14 (before any FROM) is available to all FROM instructions. However, if a future maintainer needs to reference OPENCLAW_VARIANT inside a RUN command in the runtime stage, the variable would silently expand to an empty string.

Consider moving the re-declaration to after the runtime FROM:

This is a comment left during a code review.
Path: Dockerfile
Line: 69-70

Comment:
**`ARG OPENCLAW_VARIANT` belongs in the runtime stage, not `base-slim`**

Per Dockerfile multi-stage semantics, the `ARG OPENCLAW_VARIANT` on line 69 sits between `FROM ... AS base-slim` (line 66) and `FROM base-${OPENCLAW_VARIANT}` (line 70), so it is scoped to the `base-slim` stage and effectively unused.

The `FROM base-${OPENCLAW_VARIANT}` substitution works today because the global `ARG OPENCLAW_VARIANT=default` declared on line 14 (before any `FROM`) is available to all `FROM` instructions. However, if a future maintainer needs to reference `OPENCLAW_VARIANT` inside a `RUN` command in the runtime stage, the variable would silently expand to an empty string.

Consider moving the re-declaration to after the runtime `FROM`:

```suggestion
FROM base-${OPENCLAW_VARIANT}
ARG OPENCLAW_VARIANT
```

How can I resolve this? If you propose a fix, please make it concise.

added, updated

Fail the image build when A2UI bundling fails

This fallback turns any pnpm canvas:a2ui:bundle failure into a successful build by writing a stub bundle and deleting the real A2UI sources, so the subsequent pnpm build can pass while shipping an image with missing/placeholder canvas UI assets. In environments where bundling fails for reasons other than QEMU flakiness (for example toolchain regressions), CI will silently publish degraded images instead of surfacing a hard failure.

Useful? React with 👍 / 👎.

This is actually a new graceful degradation path — previously, A2UI bundle failures under QEMU cross-compilation would fail the entire build. CI builds natively on both arch amd64, arm64, so this isn't a fallback path for released images.

added a comment to clarify!