docs: fix incorrect e2e test binary references from e2e-tests to e2e-tests-full

Author: josecelano

.github/copilot-instructions.md

@@ -44,10 +44,10 @@ This is a deployment infrastructure proof-of-concept for the Torrust ecosystem.
 3. **Before committing**: Always run these verifications - all must pass before staging files or creating commits, regardless of the tool or method used:
 
    ```bash
-   cargo machete               # Run cargo machete (MANDATORY - no unused dependencies)
-   cargo run --bin linter all  # Run linters (comprehensive - stable & nightly toolchains)
-   cargo test                  # Run tests
-   cargo run --bin e2e-tests   # Run e2e tests
+   cargo machete                    # Run cargo machete (MANDATORY - no unused dependencies)
+   cargo run --bin linter all       # Run linters (comprehensive - stable & nightly toolchains)
+   cargo test                       # Run tests
+   cargo run --bin e2e-tests-full   # Run comprehensive e2e tests
    ```
 
    This applies to **any** method of committing:
@@ -67,8 +67,8 @@ This is a deployment infrastructure proof-of-concept for the Torrust ecosystem.
 - **Build**: `cargo build`
 - **Test**: `cargo test`
 - **Unit Tests**: When writing unit tests, follow conventions described in [`docs/contributing/testing.md`](../docs/contributing/testing.md)
-- **E2E Tests**: `cargo run --bin e2e-tests` (unified) or individual tests:
-  - `cargo run --bin e2e-provision-tests` - Infrastructure provisioning
-  - `cargo run --bin e2e-config-tests` - Configuration testing
+- **E2E Tests**: `cargo run --bin e2e-tests-full` (comprehensive - all tests) or individual tests:
+  - `cargo run --bin e2e-provision-tests` - Infrastructure provisioning tests
+  - `cargo run --bin e2e-config-tests` - Configuration validation tests
 
 Follow the project conventions and ensure all checks pass.

README.md

@@ -115,17 +115,17 @@ cargo run --bin linter shellcheck  # Shell script linting
 Use the E2E tests binary to run automated infrastructure tests:
 
 ```bash
-# Run the E2E tests
-cargo run --bin e2e-tests
+# Run the comprehensive E2E tests
+cargo run --bin e2e-tests-full
 
 # Keep the test environment after completion
-cargo run --bin e2e-tests -- --keep
+cargo run --bin e2e-tests-full -- --keep
 
 # Use custom templates directory
-cargo run --bin e2e-tests -- --templates-dir ./custom/templates
+cargo run --bin e2e-tests-full -- --templates-dir ./custom/templates
 
 # See all available options
-cargo run --bin e2e-tests -- --help
+cargo run --bin e2e-tests-full -- --help
 ```
 
 ### Manual Deployment Steps

docs/contributing/README.md

@@ -37,7 +37,7 @@ cargo run --bin linter all
 
 # 4. Run tests
 cargo test
-cargo run --bin e2e-tests
+cargo run --bin e2e-tests-full
 
 # 5. Commit with conventional format (include issue number)
 git add .

docs/contributing/commit-process.md

@@ -103,7 +103,7 @@ cargo run --bin linter shellcheck # Shell scripts
 cargo test
 
 # Run E2E tests (if applicable to your changes)
-cargo run --bin e2e-tests
+cargo run --bin e2e-tests-full
 ```
 
 ## 📋 Commit Quality Guidelines

docs/contributing/debugging.md

@@ -10,7 +10,7 @@ The project uses tracing for logging. You can control the logging level using th
 
 ```bash
 # Run with debug level logging (recommended for debugging)
-RUST_LOG=debug cargo run --bin e2e-tests
+RUST_LOG=debug cargo run --bin e2e-tests-full
 ```
 
 ## 📄 Capturing Output for Analysis
@@ -19,7 +19,7 @@ Since e2e test output can be very long, use `tee` to see output in real-time whi
 
 ```bash
 # See output and save to file simultaneously
-RUST_LOG=debug cargo run --bin e2e-tests 2>&1 | tee debug-output.log
+RUST_LOG=debug cargo run --bin e2e-tests-full 2>&1 | tee debug-output.log
 ```
 
 You can then search the captured output for specific patterns:

docs/deployment-overview.md

@@ -74,7 +74,7 @@ torrust-deploy status           # List all environments (future)
 
 ```bash
 # Simulate current working functionality through E2E tests
-cargo run --bin e2e-tests
+cargo run --bin e2e-tests-full
 
 # This runs equivalent to:
 # provision: Creates LXD container with OpenTofu

docs/refactors/domain-driven-module-organization.md

@@ -271,7 +271,7 @@ Once this complete DDD layer foundation is established, we can:
   - [x] Run `cargo build` and fix compilation errors
   - [x] Run `cargo test` and fix test issues (including doc tests)
   - [x] Run `cargo run --bin linter all` and fix linting issues
-  - [x] Run `cargo run --bin e2e-tests` for integration verification
+  - [x] Run `cargo run --bin e2e-tests-full` for integration verification
 
 ### Future Phases (Ready for Implementation)
 

docs/refactors/e2e-config-tests-cleanup.md

@@ -272,7 +272,7 @@ cargo run --bin linter all
 
 # Run tests
 cargo test
-cargo run --bin e2e-tests
+cargo run --bin e2e-tests-full
 
 # Check for unused dependencies
 cargo machete
@@ -284,7 +284,7 @@ cargo machete
 # Same commands as pre-refactor
 cargo run --bin linter all
 cargo test
-cargo run --bin e2e-tests
+cargo run --bin e2e-tests-full
 cargo machete
 
 # Additional checks