Merge @rrnewton's e2e testing scripts

.devcontainer/.gitignore

@@ -0,0 +1,5 @@
+Dockerfile
+home/
+*~
+.session_title.txt
+slot.txt

.devcontainer/CLAUDE.md.stub

@@ -0,0 +1,94 @@
+
+
+Coding conventions
+========================================
+
+PREFER STRONG TYPES. For example, in Rust do not use "u32" or "String" where you can have a more specific type or at least a type alias. "String" makes it very unclear which values are legal. We want explicit Enums to lock down the possibilities for our state, and we want separate types for numerical IDs and distinct, non-overlapping uses of basic integers.
+
+Delete trailing spaces. Don't leave empty lines that consist only of whitespace. (Double newline is fine.)
+
+Add README.md files for every major subdirectory/subsystem.  For example `src/system1/`, `src/system2/`, etc.
+
+Read the PROJECT_VISION, if this is a high-performance project, e.g. in Rust, we should follow for high-performance Rust (unboxing, minimizing allocation, etc). In particular, adhere to the below programming patterns / avoid anti-patterns, which generally fall under the principle of "zero copy":
+
+- Avoid clone: instead take a temporary reference to the object and manage lifetimes appropriately.
+- Avoid collect: instead take an iterator with references to the original collection without copying.
+
+Read OPTIMIZATION.md for more details.
+
+Workflow: Tasks and Commits
+========================================
+
+Commit to git with each unit of work.
+
+Task Tracking
+----------------------------------------
+
+We use "beads" to track our issues locally under version control. Review `bd quickstart` to learn how to use it. 
+
+Every time we do a git commit, update our beads issues to reflect:
+- What was just completed (check off items in lists, close completed task(s))
+- What's next (update the in tracking issues that track the granular issues)
+- Mention in the commit any new issues created to document bugs found or future work.
+
+The beads database is our primary tracking mechanism, so if we lose conversation history we can start again from there.  You should periodically do documentation work, usually before committing, to make sure information in the issues is up-to-date.
+
+### Beads CONVENTIONS for this project
+
+Do NOT read or modify files inside the `./.beads/` private database, except when fixing merge conflicts in markdown files that you can read.
+
+Prefer the MCP client to the CLI tool. ALWAYS `bd update` existing issues, never introduce duplicates with spurious `bd create`.
+
+The issue prefix may be customized (`foobar-1`, `foobar-2`), but here we will refer `bd-1` as example issue names
+
+#### Tracking issues and Priorities
+
+- Issues labeled "human" are created by me and will always have 0 priority.
+- Issue bd-1, at priority 0, is the OVERALL tracking issue. It primarily references other tracking issues
+  and reiterate some of these conventions. We want to keep it pretty short.
+
+- The next tracking issues, e.g. bd-2 and on have priority 1 and are topic-specific trackers:
+  - Optimization tracking
+  - Feature completeness
+  - Cross-cutting codebase issues (refactorings, change of dependencies/conventions, etc)
+ - All tracking issues refer to granular issues by name in their text, e.g. "bd-42"
+ - All other granular issues will have priority 3 to 4 unless they are seen as a critical bug, which will bump them to priority 2.
+
+#### Mark transient information
+
+We often record transient information, like benchmark results, that quickly gets out of date. We want to label such information so we can tell how old it is. In addition to YYYY-MM-DD, our convention is to use:
+  `git rev-list --count HEAD`
+which prints out the number of commits in the repo (or equivalently the ./gitdepth.sh script), and then format the timestamp as `YYYY-MM-DD_#DEPTH(387498cecf)` e.g. `2025-10-22_#161(387498cecf)`. That's our full timestamp
+for any transient information that derives from a specific commit.
+Sometimes this requires us to split our commits into (1) functionality and then (2) documentation-update.
+
+#### Reference issues in code TODO
+
+We don't want TODO items to be in floating code alone. For anything but the most trivial TODOs, we adopt the convention of referencing issues that tracks the TODO:
+
+```
+// TODO(bd-13): brief summary here
+```
+
+Then, the commit that fixes the issue both removes the comment and closes the issue in beads.
+
+#### Use description field only, not notes
+
+When creating or updating issues with `bd`, always put ALL content in the description field. Do NOT use the --notes field, as it creates duplication and confusion between what's in description vs notes. Keep information consolidated in the description field only, but you may use labels for classification.
+
+Clean Start: Before beginning work on a task
+--------------------------------------------
+
+Make sure we start in a clean state. Check that we have no uncommitted changes in our working copy. Perform `git pull origin main` to make sure we are starting with the latest version. Check that `make validate` passes in our starting state.
+
+If github MCP is configured and github actions workflows exist for this project, check the github actions CI status for the most recent commit and make sure it not red (if it's still pending, ignore and proceed). If
+there's a CI failure, then fixing THAT becomes our task. Finally, check that `make validate` passes locally in our starting state.
+
+Pre-Commit: checks before committing to git
+--------------------------------------------
+
+Run `make validate` and ensure that it passes or fix any problems before committing.
+
+Also include a `Test Results Summary` section in every commit message that summarizes how many tests passed of what kind.
+
+If you validate some changes with a new manual or temporary test, that test should be added to either the unit tests, examples, or e2e tests and it should be called consistently from both `make validate` and Github CI.

.devcontainer/Dockerfile.claude

@@ -0,0 +1,21 @@
+
+
+ARG CLAUDE_CODE_VERSION=latest
+
+ARG GIT_DELTA_VERSION=0.18.2
+RUN ARCH=$(dpkg --print-architecture) && \
+  wget "https://github.com/dandavison/delta/releases/download/${GIT_DELTA_VERSION}/git-delta_${GIT_DELTA_VERSION}_${ARCH}.deb" && \
+  sudo dpkg -i "git-delta_${GIT_DELTA_VERSION}_${ARCH}.deb" && \
+  rm "git-delta_${GIT_DELTA_VERSION}_${ARCH}.deb"
+
+# Install Claude
+RUN npm install -g @anthropic-ai/claude-code@${CLAUDE_CODE_VERSION}
+
+# Copy and set up firewall script
+COPY init-firewall.sh /usr/local/bin/
+USER root
+RUN chmod +x /usr/local/bin/init-firewall.sh && \
+  echo "node ALL=(root) NOPASSWD: /usr/local/bin/init-firewall.sh" > /etc/sudoers.d/node-firewall && \
+  chmod 0440 /etc/sudoers.d/node-firewall
+ENV IS_SANDBOX=1
+# End claude-related dependencies and setup.

.devcontainer/Dockerfile.copilot

@@ -0,0 +1,2 @@
+RUN npm install -g @github/copilot
+

.devcontainer/Dockerfile.gemini

@@ -0,0 +1,2 @@
+
+RUN npm install -g @google/gemini-cli

.devcontainer/Dockerfile.postfix

@@ -0,0 +1,8 @@
+# Set the working directory to the custom WORKDIR
+# Create /workspace as a symlink to WORKDIR (for backward compatibility)
+# Only create symlink if WORKDIR is not /workspace
+ARG WORKDIR=/workspace
+RUN if [ "$WORKDIR" != "/workspace" ]; then \
+      ln -s ${WORKDIR} /workspace; \
+    fi
+WORKDIR ${WORKDIR}

.devcontainer/Dockerfile.prefix

@@ -0,0 +1,126 @@
+
+# [RRN] node image has too old versions for certain packages we use:
+# FROM node:25
+FROM ubuntu:25.10
+
+# [RRN] TZ confuses happy-coder
+# ARG TZ
+# ENV TZ="$TZ"
+
+# Stolen from the nodejs/docker/node Dockerfile:
+# RUN groupadd --gid 1000 node \
+#   && useradd --uid 1000 --gid node --shell /bin/bash --create-home node
+
+# Install basic development tools and iptables/ipset
+RUN apt-get update && apt-get install -y --no-install-recommends \
+  less \
+  git \
+  procps \
+  sudo \
+  fzf \
+  zsh \
+  man-db \
+  unzip \
+  gnupg2 \
+  gh \
+  iptables \
+  ipset \
+  iproute2 \
+  dnsutils \
+  aggregate \
+  jq \
+  nano \
+  vim \
+  wget \
+  curl
+  # [RRN ] Don't clean because we want to keep apt and I don't mind if claude
+  # installs either:
+  # && apt-get clean && rm -rf /var/lib/apt/lists/*
+
+# Installs a TON of stufF:
+# RUN apt-get install -y npm
+
+# Going to a newer version for github copilot
+RUN apt-get install -y ca-certificates && \
+    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
+
+ARG NODE_VERSION=24
+
+RUN . "$HOME/.nvm/nvm.sh" && nvm install ${NODE_VERSION} && \
+    nvm alias default ${NODE_VERSION} && nvm use default && \
+    which node && node -v && npm -v 
+
+# Hack to discover the minor version: e.g. /bin/versions/node/v24.11.0/bin/node
+RUN cd /bin/versions/node/ && ln -s v24* 24
+ENV PATH=$PATH:/bin/versions/node/24/bin/
+
+# Install global packages
+# ENV NPM_CONFIG_PREFIX=/usr/local/share/npm-global
+# ENV PATH=$PATH:/usr/local/share/npm-global/bin
+
+# [RRN] Differ in the non-root user we use from the node image:
+# ENV MYUSER=node
+ENV MYUSER=ubuntu
+
+# Ensure default node user has access to /usr/local/share
+RUN mkdir -p /usr/local/share/npm-global && \
+  chown -R $MYUSER:$MYUSER /usr/local/share
+
+ARG USERNAME=$MYUSER
+
+# [RRN] Seems unimportant. We mount home dir from host anyway.
+# Persist bash history.
+# RUN SNIPPET="export PROMPT_COMMAND='history -a' && export HISTFILE=/commandhistory/.bash_history" \
+  # && mkdir /commandhistory \
+  # && touch /commandhistory/.bash_history \
+  # && chown -R $USERNAME /commandhistory
+
+# Set `DEVCONTAINER` environment variable to help with orientation
+ENV DEVCONTAINER=true
+
+# [RRN] Uh, I don't know why claude needs to be opinionated about shell..
+# Set the default shell to zsh rather than sh
+# ENV SHELL=/bin/zsh
+
+# Set the default editor and visual
+ENV EDITOR=nano
+ENV VISUAL=nano
+
+# Default powerline10k theme
+# ARG ZSH_IN_DOCKER_VERSION=1.2.0
+# RUN sh -c "$(wget -O- https://github.com/deluan/zsh-in-docker/releases/download/v${ZSH_IN_DOCKER_VERSION}/zsh-in-docker.sh)" -- \
+#   -p git \
+#   -p fzf \
+#   -a "source /usr/share/doc/fzf/examples/key-bindings.zsh" \
+#   -a "source /usr/share/doc/fzf/examples/completion.zsh" \
+#   -a "export PROMPT_COMMAND='history -a' && export HISTFILE=/commandhistory/.bash_history" \
+#   -x
+
+
+# [RRN] basic additiions I like everywhere.
+# psmisc has killall:
+RUN apt-get install -y time parallel hyperfine bc emacs gnuplot psmisc ssh
+
+# [RRN] Python is so universal for scripting...
+RUN apt-get install -y python3 pip python3-venv
+RUN python3 -m venv /opt/venv
+RUN /opt/venv/bin/python3 -m pip install uv
+# End shared, non-project configuration.
+
+# [RRN] Run my version, but cannot do it in a one-liner because of build step:
+RUN . "$HOME/.nvm/nvm.sh" && \
+    npm install -g happy-coder
+# Shelving my version for now which just added --set-title.
+    # git clone --depth=1 https://github.com/rrnewton/happy-cli.git /tmp/happy && \
+    #   cd /tmp/happy && npm install && npm run build && npm install -g . && \
+    #   rm -rf /tmp/happy
+
+
+# Create workspace and config directories and set permissions
+#RUN mkdir -p /workspace /home/$MYUSER/.claude && \
+#  chown -R $MYUSER:$MYUSER /workspace /home/$MYUSER/.claude
+
+# WORKDIR /workspace
+
+# USER $MYUSER
+ENV SHELL=/bin/bash

.devcontainer/Dockerfile.project

@@ -0,0 +1,43 @@
+USER root
+
+# Install yarn
+RUN npm install -g yarn
+
+# Install system dependencies for happy-server
+RUN apt-get update && apt-get install -y \
+    postgresql \
+    postgresql-contrib \
+    redis-server \
+    lsof \
+    nmap \
+    wget 
+#    && rm -rf /var/lib/apt/lists/*
+
+# Install MinIO server
+RUN wget -q https://dl.min.io/server/minio/release/linux-amd64/minio \
+    && chmod +x minio \
+    && mv minio /usr/local/bin/
+
+# Install MinIO client (mc)
+RUN wget -q https://dl.min.io/client/mc/release/linux-amd64/mc \
+    && chmod +x mc \
+    && mv mc /usr/local/bin/
+
+# Install Playwright for browser automation testing
+RUN npm install -g playwright \
+    && npx playwright install chromium \
+    && npx playwright install-deps chromium
+
+# Expose ports for Happy services
+# happy-server API
+EXPOSE 3005
+# happy web client (Expo)
+EXPOSE 8081
+# MinIO API
+EXPOSE 9000
+# MinIO Console
+EXPOSE 9001
+# PostgreSQL
+EXPOSE 5432
+# Redis
+EXPOSE 6379   

.devcontainer/Dockerfile.rust

@@ -0,0 +1,14 @@
+
+# Keep it out of the home dir because we will mount that from host:
+RUN apt-get install rustup
+ENV CARGO_HOME=/opt/cargo
+ENV RUSTUP_HOME=/opt/multirust
+RUN mkdir -p "$CARGO_HOME" && rustup toolchain install nightly
+# RUN mkdir -p "$CARGO_HOME" && rustup toolchain install stable
+
+# Install my minibeads tool for issue tracking
+RUN cargo install --git https://github.com/rrnewton/minibeads --tag v0.15 && \
+    ln -s /opt/cargo/bin/mb /opt/cargo/bin/bd
+
+# RUN apt-get install -y heaptrack
+# RUN cargo install cargo-heaptrack cargo-nextest