Add system resource detection, Docker execution skill, and environment-aware recommendations

- TUI header now shows CPU cores, RAM, GPU, and Docker availability
- System prompt uses resource info to recommend execution environments
- Docker skill for running experiment code in isolated containers
- Renamed docker-sandbox skill to docker (Feynman stays on host, code runs in containers)
- Updated README and website to cite Docker alongside Agent Computer

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

prompts/autoresearch.md

@@ -25,6 +25,7 @@ Ask the user where to run:
 - **Local** — run in the current working directory
 - **New git branch** — create a branch so main stays clean
 - **Virtual environment** — create an isolated venv/conda env first
+- **Docker** — run experiment code inside an isolated Docker container
 - **Cloud** — delegate to a remote Agent Computer machine via `/delegate`
 
 Do not proceed without a clear answer.

prompts/replicate.md

@@ -13,6 +13,7 @@ Design a replication plan for: $@
 3. **Environment** — Before running anything, ask the user where to execute:
    - **Local** — run in the current working directory
    - **Virtual environment** — create an isolated venv/conda env first
+   - **Docker** — run experiment code inside an isolated Docker container
    - **Cloud** — delegate to a remote Agent Computer machine via `/delegate`
    - **Plan only** — produce the replication plan without executing
 4. **Execute** — If the user chose an execution environment, implement and run the replication steps there. Save notes, scripts, and results to disk in a reproducible layout.