docs: [#220] update documentation with real command outputs and state management warnings

- Updated docs/e2e-testing/manual-testing.md:
  * Replaced all fake command output with real output from test runs
  * Removed all references to non-existent 'deploy' command
  * Updated state machine to reflect actual workflow (provision → configure → release → run)
  * Added comprehensive warnings about manual state editing dangers
  * Added 'Checking Logs for Diagnosis' section with examples
  * Updated command durations with real timing data
  * Fixed all command sequences and recovery procedures

- Updated docs/user-guide/quick-start.md:
  * Replaced fake output with real command output
  * Updated complete workflow to show correct 5-step process
  * Changed Step 6 from 'test' to 'release' command
  * Added Step 7 'run' command (was missing)
  * Renumbered cleanup to Step 8
  * Updated Quick Reference with correct command sequence
  * Fixed all timing information with real test data

- Updated docs/e2e-testing/README.md:
  * Added manual-testing.md to documentation structure
  * Added link to manual testing guide in 'Learn More' section
  * Updated description to distinguish automated vs manual testing

- Updated AGENTS.md:
  * Added Manual E2E Testing section with link to manual-testing.md
  * Listed key topics covered in the manual testing guide

All markdown linting checks pass. Documentation now reflects actual system behavior with accurate command outputs, correct workflows, and proper warnings about state management.

Author: josecelano

AGENTS.md

@@ -135,5 +135,10 @@ These principles should guide all development decisions, code reviews, and featu
   - `cargo run --bin e2e-deployment-workflow-tests` - Software installation, configuration, release, and run workflow tests (GitHub runner-compatible)
   - Pre-commit hook runs the split tests (`e2e-infrastructure-lifecycle-tests` + `e2e-deployment-workflow-tests`) for GitHub Copilot compatibility
   - See [`docs/e2e-testing/`](docs/e2e-testing/) for detailed information about CI limitations
+- **Manual E2E Testing**: For step-by-step manual testing with CLI commands, see [`docs/e2e-testing/manual-testing.md`](docs/e2e-testing/manual-testing.md). This guide covers:
+  - Complete manual test workflow from template creation to deployment
+  - Handling interrupted commands and state recovery
+  - Troubleshooting common issues
+  - Cleanup procedures for both application and LXD resources
 
 Follow the project conventions and ensure all checks pass.

docs/e2e-testing/README.md

@@ -6,11 +6,12 @@ This guide explains how to run and understand the End-to-End (E2E) tests for the
 
 - **[README.md](README.md)** - This overview and quick start guide
 - **[architecture.md](architecture.md)** - E2E testing architecture, design decisions, and Docker strategy
-- **[running-tests.md](running-tests.md)** - How to run tests, command-line options, and prerequisites
+- **[running-tests.md](running-tests.md)** - How to run automated tests, command-line options, and prerequisites
+- **[manual-testing.md](manual-testing.md)** - Complete guide for running manual E2E tests with CLI commands
 - **[test-suites.md](test-suites.md)** - Detailed description of each test suite and what they validate
 - **[troubleshooting.md](troubleshooting.md)** - Common issues, debugging techniques, and cleanup procedures
 - **[contributing.md](contributing.md)** - Guidelines for extending E2E tests
-- **[advanced.md](advanced.md)** - Advanced techniques including manual testing and cross-environment registration
+- **[advanced.md](advanced.md)** - Advanced techniques including cross-environment registration
 
 ## 🧪 What are E2E Tests?
 
@@ -66,6 +67,7 @@ For detailed prerequisites and manual setup, see [running-tests.md](running-test
 ## 📚 Learn More
 
 - **New to E2E testing?** Start with [test-suites.md](test-suites.md) to understand what each test does
+- **Want to run manual tests?** Follow [manual-testing.md](manual-testing.md) for step-by-step CLI workflow
 - **Running into issues?** Check [troubleshooting.md](troubleshooting.md)
 - **Want to understand the architecture?** Read [architecture.md](architecture.md)
 - **Adding new tests?** See [contributing.md](contributing.md)