Add Daytona guide for Omni and Claude Engineer

[GawainTheCoder]

/claim #36

Summary

• add a Daytona article for running Omni Engineer and Claude Engineer in repeatable sandboxes
• include a workflow-compliant PNG diagram, a new AI Engineer definition, and a first-time author profile
• link the guide to companion Dev Container PRs:
  • Add Daytona devcontainer Doriandarko/omni-engineer#26
  • Add Daytona devcontainer and Anthropic model env Doriandarko/claude-engineer#250

Why this is reproducible

• the guide uses current Daytona CLI commands: create, exec, ssh, preview-url, and stop
• the Dev Containers install from each repository's requirements.txt, copy .env.example, and pass provider keys through remoteEnv
• Claude Engineer's model ID is configurable through ANTHROPIC_MODEL, so the guide keeps working when Anthropic model availability differs by account
• the article calls out the current Omni Engineer entrypoint, main.py, so readers do not follow stale README references from older branches
• the article uses the verified Daytona CLI v0.173 daytona exec --cwd ... -- <command> form for commands that need a repository working directory
• the final content diff follows Daytona's file naming workflow, including the top-level assets/..._img1.png pattern

Validation

• npm ci
• npx markdownlint articles/20260511_running_omni_and_claude_engineer_inside_daytona.md
• git diff --check
• Daytona file naming check from .github/workflows/content-check.yml against origin/main...HEAD
• python3 -m json.tool .devcontainer/devcontainer.json for both companion Dev Container files
• python3 -m py_compile config.py for the Claude Engineer model configuration change
• Daytona cloud runtime validation on 2026-05-11:
  • logged into Daytona CLI v0.173.0 and set the default organization region to us
  • created codex-omni-bounty36 and codex-claude-bounty36 sandboxes
  • cloned GawainTheCoder/omni-engineer:add-daytona-devcontainer and GawainTheCoder/claude-engineer:add-daytona-devcontainer
  • verified expected files: .devcontainer/devcontainer.json, .env.example, main.py, ce3.py, app.py, and requirements.txt
  • installed dependencies with python3 -m pip install -r requirements.txt in both sandboxes
  • ran python3 -m pip check in both sandboxes; both returned No broken requirements found.
  • ran python3 -m py_compile main.py and python3 -m py_compile ce3.py app.py
  • smoke-tested python3 main.py, python3 ce3.py, and python3 app.py
  • verified daytona preview-url codex-claude-bounty36 --port 5000 and received HTTP 200 from the proxied Flask UI
  • sent a live Anthropic Messages API smoke test from the Daytona Claude sandbox and received the expected READY response
  • sent the same prompt through Claude Engineer's Assistant().chat(...) path using an account-visible ANTHROPIC_MODEL and received the expected READY response

[GawainTheCoder]

Added Daytona runtime validation after re-running the workflow in cloud sandboxes.

Verified:

• Daytona CLI v0.173.0 login and us default region
• codex-omni-bounty36 and codex-claude-bounty36 sandbox creation
• clone/setup of the companion Dev Container branches
• dependency installs and python3 -m pip check in both sandboxes
• python3 -m py_compile main.py and python3 -m py_compile ce3.py app.py
• Omni CLI startup via python3 main.py
• Claude CLI startup via python3 ce3.py
• Claude Flask UI startup via python3 app.py
• Daytona preview-url for port 5000, with HTTP 200 returned by the proxied UI
• live Anthropic Messages API smoke test from inside Daytona returned the expected READY response
• Claude Engineer's Assistant().chat(...) path returned READY when using an Anthropic model visible to the test account

Follow-up from validation: the original Claude Engineer default model was not available to the test Anthropic account, so I updated the companion Claude PR to support ANTHROPIC_MODEL and updated the article with the model-override troubleshooting path. No provider secrets are included in the PR.

I also updated the article commands to use the verified Daytona CLI v0.173 daytona exec --cwd ... -- <command> form for commands that need a repository working directory.