ompbox: add Oh My Pi as a new harness

[guimou]

Summary

Adds Oh My Pi (omp, https://github.com/can1357/oh-my-pi) as the fifth harness: launcher ompbox, image quay.io/guimou/ompbox, pin file OMP_VERSION (18.1.14), overlay firewall-domains-omp.txt, flag --omp-version.

Install

Prebuilt, self-contained release binary (omp-linux-x64 / omp-linux-arm64, glibc only) downloaded from GitHub Releases and verified against the release SHA256SUMS.txt. No npm/bun. Native addons (~340 MB) are extracted at build time; the startup update check is disabled through /etc/codebox/omp-config.yml, loaded via PI_CONFIG_FILES.

State layout (why it differs from the other launchers)

Verified by running omp 18.1.14 locally:

• ~/.omp/agent/agent.db is a WAL-mode SQLite file holding OAuth tokens, /login API keys, settings, usage stats and the memory store keyed by cwd. Inside the container cwd is always /workspace, so the DB cannot be shared across projects, and WAL sidecars rule out a single-file bind mount. The whole agent dir is per project: ~/.omp/ompbox-projects/<project>/agent.
• config.yml is saved via write-then-rename, so it is copied into the per-project dir at launch and refreshed when the host file is newer (cxbox config.toml pattern).
• Shared config dirs (commands rules prompts instructions skills hooks tools extensions) are bind-mounted read-write from ~/.omp/agent; shared prompt/config files (SYSTEM.md APPEND_SYSTEM.md RULES.md TITLE_SYSTEM.md AGENTS.md models.yml mcp.json keybindings.json) read-only when present on the host.
• --with-credentials mounts ~/.omp/.env and ~/.omp/agent/.env read-only (dotenv API keys). OAuth logins done inside the container stay per project.

Engine change

New optional ENV_PASSTHROUGH_EXCLUDE_REGEX in lib/box-common.sh. ompbox uses it to forward OMP_*/PI_* while keeping out the state-relocating vars (PI_CODING_AGENT_DIR, PI_CONFIG_DIR, PI_CONFIG_FILES, PI_PROFILE, OMP_PROFILE, PI_INSTALL_DIR). cxbox now uses it for CODEX_HOME, which its comment already claimed was not forwarded but the ^(CODEX_|…) regex did forward.

Also

CI workflows (release, build-and-push, tests, build-pod), k8s/Containerfile, k8s/gen-egress-firewall.sh, golden tests (4 new scenarios), .gitignore (.omp/), docs.

Test plan

• tests/render-test.sh: 28/28 ok, no existing golden changed
• shellcheck clean (CI file list)
• Dockerfile omp arm logic run standalone: checksum OK, omp --version → omp/18.1.14
• CI image build for omp (no podman in the dev environment)
• First real run: ./ompbox --local after build, /login, resume, --with-credentials

[guimou]

Second commit: the weekly release run now bumps *_VERSION to the latest upstream releases before building (direct commit to main, same run). Requires a one-time repo change before the next Monday run: add the GitHub Actions app as a bypass actor on the PR for main ruleset, otherwise the push is rejected and the run fails at the bump job. Details in docs/development.md → Release workflow.

[guimou]

Update: on a personal repo the Actions app cannot be a ruleset bypass actor, so the bump job now pushes with a write-enabled deploy key (the "Deploy keys" entry in your bypass list) and marks the bump commit [skip ci]. One-time setup before the next Monday run:

ssh-keygen -t ed25519 -N '' -C 'ccbox release bump' -f bump-key
gh repo deploy-key add bump-key.pub --title 'release bump' --allow-write
gh secret set BUMP_DEPLOY_KEY < bump-key
rm bump-key bump-key.pub

then Settings → Rules → Rulesets → PR for main → Add bypass → tick Deploy keys. Without the secret the bump job fails with an explicit error (nothing gets built). Details in docs/development.md.