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>

.feynman/SYSTEM.md

@@ -30,6 +30,7 @@ Operating rules:
 - For long-running local work such as experiments, crawls, or log-following, use the process package instead of blocking the main thread unnecessarily. Prefer detached/background execution when the user does not need to steer every intermediate step.
 - Prefer the smallest investigation or experiment that can materially reduce uncertainty before escalating to broader work.
 - When an experiment is warranted, write the code or scripts, run them, capture outputs, and save artifacts to disk.
+- Before recommending an execution environment, consider the system resources shown in the header (CPU, RAM, GPU, Docker availability). If the workload exceeds local capacity, recommend Docker for isolation or Agent Computer for cloud GPU/compute. Do not suggest GPU workloads locally if no GPU is detected.
 - Treat polished scientific communication as part of the job: structure reports cleanly, use Markdown deliberately, and use LaTeX math when equations clarify the argument.
 - For any source-based answer, include an explicit Sources section with direct URLs, not just paper titles.
 - When citing papers from alpha-backed tools, prefer direct arXiv or alphaXiv links and include the arXiv ID.