Enhance Docker suitability assessment and update test execution guidelines

- Updated SKILL.md for test-run to clarify the use of Docker and added a Docker Suitability Check to ensure proper execution environment.
- Revised SKILL.md for test-spec to include a detailed Docker Suitability Assessment, outlining disqualifying factors and decision-making steps for test execution.
- Adjusted the autopilot state to reflect the current status of test execution as in_progress.

These changes improve the clarity and reliability of the testing process, ensuring that users are informed of potential constraints when using Docker.

.cursor/skills/test-run/SKILL.md

@@ -21,8 +21,8 @@ Run the project's test suite and report results. This skill is invoked by the au
 
 Check in order — first match wins:
 
-1. `scripts/run-tests.sh` exists → use it
-2. `docker-compose.test.yml` or equivalent test environment exists → spin it up first, then detect runner below
+1. `scripts/run-tests.sh` exists → use it (the script already encodes the correct execution strategy)
+2. `docker-compose.test.yml` exists → run the Docker Suitability Check (see below). Docker is preferred; use it unless hardware constraints prevent it.
 3. Auto-detect from project files:
    - `pytest.ini`, `pyproject.toml` with `[tool.pytest]`, or `conftest.py` → `pytest`
    - `*.csproj` or `*.sln` → `dotnet test`
@@ -32,6 +32,37 @@ Check in order — first match wins:
 
 If no runner detected → report failure and ask user to specify.
 
+#### Docker Suitability Check
+
+Docker is the preferred test environment. Before using it, verify no constraints prevent easy Docker execution:
+
+1. Check `_docs/02_document/tests/environment.md` for a "Test Execution" decision (if the test-spec skill already assessed this, follow that decision)
+2. If no prior decision exists, check for disqualifying factors:
+   - Hardware bindings: GPU, MPS, CUDA, TPU, FPGA, sensors, cameras, serial devices, host-level drivers
+   - Host dependencies: licensed software, OS-specific services, kernel modules, proprietary SDKs
+   - Data/volume constraints: large files (> 100MB) impractical to copy into a container
+   - Network/environment: host networking, VPN, specific DNS/firewall rules
+   - Performance: Docker overhead would invalidate benchmarks or latency measurements
+3. If any disqualifying factor found → fall back to local test runner. Present to user using Choose format:
+
+```
+══════════════════════════════════════
+ DECISION REQUIRED: Docker is preferred but factors
+ preventing easy Docker execution detected
+══════════════════════════════════════
+ Factors detected:
+ - [list factors]
+══════════════════════════════════════
+ A) Run tests locally (recommended)
+ B) Run tests in Docker anyway
+══════════════════════════════════════
+ Recommendation: A — detected constraints prevent
+ easy Docker execution
+══════════════════════════════════════
+```
+
+4. If no disqualifying factors → use Docker (preferred default)
+
 ### 2. Run Tests
 
 1. Execute the detected test runner