[AZ-233] Update Docker Compose and enhance test documentation

- Modified the Docker Compose configuration to include an input root for replay tests and added an environment variable for enabling SITL.
- Enhanced documentation for various testing processes, including the addition of a Runtime Completeness Decomposition Gate and clarifications on internal module testing requirements.
- Updated the implementation completeness report to reflect the current state and added new test cases for performance and resilience scenarios.

Co-authored-by: Cursor <cursoragent@cursor.com>

_docs/02_document/tests/environment.md

@@ -44,9 +44,12 @@
 
 ## Consumer Application
 
-**Tech stack**: Python replay harness with pytest-style assertions and MAVLink log parsing.
+**Tech stack**: Python replay harness with pytest-style assertions, Docker/compose orchestration, deterministic cache/SITL/QGC stubs, and CSV/Markdown report generation.
 
-**Entry point**: `run-blackbox-replay` command to be created during implementation; this planning artifact defines required behavior, not code.
+**Entry points**:
+- Local functional suite: `python3 -m pytest`
+- Replay harness: `python -m e2e.replay.run_replay --output-dir <dir> --input-root <fixture-root>`
+- Docker replay gate: `docker compose -f docker-compose.test.yml run --build --rm replay-consumer`
 
 ### Communication With System Under Test
 
@@ -81,7 +84,7 @@
 
 **Columns**: Test ID, Test Name, Input Dataset, Execution Time (ms), Result, Error Distance (m), Source Label, Covariance 95% Semi-Major (m), `GPS_INPUT.fix_type`, Error Message.
 
-**Output path**: `./test-results/blackbox-report.csv` and `./test-results/fdr-validation-summary.md`.
+**Output path**: `data/test-results/<run-id>/blackbox-report.csv` and `data/test-results/<run-id>/fdr-validation-summary.md` on the host; `/app/data/test-results/<run-id>/...` inside the replay container.
 
 ## Test Execution
 
@@ -107,6 +110,8 @@ Use Docker or local host replay for deterministic, reproducible tests that do no
 
 Docker/replay mode is suitable for PR checks and nightly validation, but it does not prove Jetson latency, memory, thermal, or camera-driver behavior.
 
+Current Docker replay smoke evidence is expected to pass `FT-P-01`, `NFT-PERF-INFRA`, `NFT-RES-INFRA`, and `NFT-SEC-INFRA`. `NFT-RES-LIM-INFRA` remains blocked on local non-Jetson runners with an explicit target-hardware prerequisite.
+
 ### Local Hardware Mode
 
 Use local Jetson hardware for release gates: