[feafel]

What

Removes the Go toolchain and Foundry from docker/dockerfiles/Dockerfile.bedrock-init:

-# Install Go.
-RUN curl -sSL https://golang.org/dl/go1.21.6.linux-amd64.tar.gz | tar -v -C /usr/local -xz
-RUN cp /usr/local/go/bin/go /usr/bin/go
-
-# Install Foundry.
-RUN curl -L https://foundry.paradigm.xyz | bash
-RUN /root/.foundry/bin/foundryup
-RUN rsync -a /root/.foundry/bin/ /usr/bin/

and updates the README sentence that claimed the container installs Foundry.

Why

Nothing in the image uses either toolchain:

consumer	what it actually needs
scripts/init-bedrock.sh	curl, tar, sha256sum, openssl, mkdir, dirname
scripts/utils.sh	aria2c (aria2), unzstd (zstd), lz4, coreutils

grep across scripts/, docker/ and the repo history finds no cast, forge, anvil or go invocation — they were never referenced by any container-side script. They look cargo-culted from the upstream simple-optimism-node template this repo was forked from.

Effect: every docker compose up --build builds a smaller image (~1.2 GB less to pull/extract on first boot, which matters because the first boot is already dominated by a 250-400 GB snapshot download), and the build loses a curl | bash step that fetched a third-party installer.

progress.sh still needs cast, but it runs on the host — that is unchanged and the README now says so directly.

Verification

• no references to the removed toolchains anywhere in the repo (git grep -nE '\b(cast|forge|anvil)\b' over tracked files → only progress.sh, which is host-side)
• docker-compose.yml untouched; the image still installs everything init-bedrock.sh/utils.sh call
• YAML files parse; README wording updated

Not verified: an actual docker build (no Docker in this environment) — the change only deletes two RUN blocks that nothing depends on.