refactor: [#232] Reorganize external tool issues under new external-issues folder

Consolidates external tool issue documentation into a unified structure for better
organization and discoverability.

Changes:
- Created new docs/external-issues/ directory as parent folder
- Moved docs/github-actions-issues/ → docs/external-issues/github-actions/
- Moved docs/tracker-issues/ → docs/external-issues/tracker/
- Created docs/external-issues/README.md with overview and scope guidelines
- Updated all relative path references in moved documentation
- Updated docs/README.md to reflect new structure
- Updated AGENTS.md navigation table
- Updated quick navigation: "Fix a CI issue" → "Fix external tool issues"

Benefits:
- Clearer separation between internal and external issues
- Easier to add new external tool issue categories
- Consistent naming (external-issues instead of mixed naming)
- Better navigation and discoverability

Related to #232 (documentation organization during MySQL implementation)

Author: josecelano

AGENTS.md

@@ -220,7 +220,7 @@ The project has comprehensive documentation organized in the [`docs/`](docs/) di
 | Write unit tests          | [`docs/contributing/testing/unit-testing.md`](docs/contributing/testing/unit-testing.md) |
 | Understand a decision     | [`docs/decisions/README.md`](docs/decisions/README.md)                                   |
 | Plan a new feature        | [`docs/features/README.md`](docs/features/README.md)                                     |
-| Fix a CI issue            | [`docs/github-actions-issues/README.md`](docs/github-actions-issues/README.md)           |
+| Fix external tool issues  | [`docs/external-issues/README.md`](docs/external-issues/README.md)                       |
 | Work with templates       | [`docs/contributing/templates.md`](docs/contributing/templates.md)                       |
 | Handle errors properly    | [`docs/contributing/error-handling.md`](docs/contributing/error-handling.md)             |
 | Handle output properly    | [`docs/contributing/output-handling.md`](docs/contributing/output-handling.md)           |

docs/README.md

@@ -36,7 +36,7 @@ docs/
 ├── refactors/            🔄 Refactoring plans and tracking
 ├── implementation-plans/ 📝 Step-by-step plans for complex changes
 ├── issues/               📋 Issue templates and specifications
-├── github-actions-issues/ ⚠️ CI/CD troubleshooting
+├── external-issues/      ⚠️ External tool issues (GitHub Actions, Tracker)
 └── analysis/             📊 Code analysis (presentation layer structure)
 ```
 
@@ -82,7 +82,7 @@ docs/
 | Write unit tests          | [`contributing/testing/unit-testing.md`](contributing/testing/unit-testing.md) |
 | Understand a decision     | [`decisions/README.md`](decisions/README.md)                                   |
 | Plan a new feature        | [`features/README.md`](features/README.md)                                     |
-| Fix a CI issue            | [`github-actions-issues/README.md`](github-actions-issues/README.md)           |
+| Fix external tool issues  | [`external-issues/README.md`](external-issues/README.md)                       |
 | Work with templates       | [`contributing/templates.md`](contributing/templates.md)                       |
 | Handle errors properly    | [`contributing/error-handling.md`](contributing/error-handling.md)             |
 | Handle output properly    | [`contributing/output-handling.md`](contributing/output-handling.md)           |
@@ -246,9 +246,11 @@ Ansible testing strategy, Docker vs LXD, E2E testing, UX patterns, MVVM analysis
 
 - [`issues/`](issues/) - Templates for epics, issues, and specifications
 
-**CI/CD Troubleshooting:**
+**External Tool Issues:**
 
-- [`github-actions-issues/README.md`](github-actions-issues/README.md) - GitHub Actions runner issues
+- [`external-issues/README.md`](external-issues/README.md) - Issues with external tools (GitHub Actions, Tracker)
+- [`external-issues/github-actions/`](external-issues/github-actions/) - GitHub Actions CI/CD issues
+- [`external-issues/tracker/`](external-issues/tracker/) - Torrust Tracker issues
 
 **Code Analysis:**
 

docs/external-issues/README.md

@@ -0,0 +1,64 @@
+# External Issues Documentation
+
+This directory contains documentation about issues found in **external tools and services** during development and testing of the Torrust Tracker Deployer, not issues with the deployer application itself.
+
+## Purpose
+
+When developing and testing the deployer, we sometimes discover issues, limitations, or unexpected behaviors in external tools and services we depend on. This folder documents those findings for reference, workarounds, and potential upstream fixes.
+
+## Subdirectories
+
+### [`github-actions/`](github-actions/)
+
+Issues related to GitHub Actions CI/CD environment:
+
+- Runner limitations
+- Network connectivity issues
+- Resource constraints
+- CI-specific environment problems
+
+### [`tracker/`](tracker/)
+
+Issues related to the Torrust Tracker application and container:
+
+- Tracker container behavior issues
+- Tracker configuration problems
+- Tracker entrypoint script issues
+- Tracker application bugs discovered during deployment
+- Tracker API inconsistencies
+- Tracker database driver issues
+
+## Scope
+
+**IN SCOPE** (belongs here):
+
+- External tool bugs or limitations
+- Third-party service issues
+- Dependency behavior that affects the deployer
+- Upstream issues requiring workarounds
+- External API inconsistencies
+
+**OUT OF SCOPE** (belongs elsewhere):
+
+- Deployer bugs → GitHub Issues in this repository
+- Infrastructure code issues → Code fixes in `src/`
+- Template rendering problems → Code fixes in `src/infrastructure/templating/`
+- Ansible playbook issues → Code fixes in `templates/ansible/`
+- Development workflow issues → `docs/contributing/known-issues.md`
+
+## Document Format
+
+Each issue should be documented with:
+
+1. **Problem Description**: Clear explanation of the issue
+2. **Root Cause**: Analysis of why it happens
+3. **Impact**: How it affects the deployer
+4. **Current Workaround**: How we handle it in the deployer
+5. **Recommended Solution**: Proposed fix for the upstream project
+6. **References**: Links to relevant external documentation or issues
+
+## Related Documentation
+
+- [Contributing Guidelines](../contributing/README.md)
+- [Known Issues](../contributing/known-issues.md) (deployer-specific issues)
+- [Documentation Index](../README.md)

docs/github-actions-issues/README.md …external-issues/github-actions/README.mddocs/github-actions-issues/README.md renamed to docs/external-issues/github-actions/README.md docs/github-actions-issues/README.md renamed to docs/external-issues/github-actions/README.md

@@ -20,7 +20,7 @@ When testing the deployer, we sometimes discover issues, limitations, or unexpec
 **OUT OF SCOPE** (belongs elsewhere):
 
 - Deployer bugs → GitHub Issues in this repository
-- Infrastructure provisioning issues → `docs/github-actions-issues/` or `docs/contributing/known-issues.md`
+- Infrastructure provisioning issues → `docs/external-issues/github-actions/` or `docs/contributing/known-issues.md`
 - Template rendering problems → Code fixes in `src/infrastructure/templating/`
 - Ansible playbook issues → Code fixes in `templates/ansible/`
 
@@ -43,4 +43,5 @@ Each issue should be documented with:
 
 - [Torrust Tracker Repository](https://github.com/torrust/torrust-tracker)
 - [Torrust Tracker Container Images](https://hub.docker.com/r/torrust/tracker)
-- [Contributing Guidelines](../contributing/README.md)
+- [External Issues Overview](../README.md)
+- [Contributing Guidelines](../../contributing/README.md)

…actions-issues/docker-apt-cache-issue.md …github-actions/docker-apt-cache-issue.mddocs/github-actions-issues/docker-apt-cache-issue.md renamed to docs/external-issues/github-actions/docker-apt-cache-issue.md docs/github-actions-issues/docker-apt-cache-issue.md renamed to docs/external-issues/github-actions/docker-apt-cache-issue.md

@@ -200,7 +200,7 @@ fi
 - **Tracker Entrypoint**: <https://github.com/torrust/torrust-tracker/blob/develop/share/container/entry_script_sh>
 - **Demo Compose**: <https://github.com/torrust/torrust-demo/blob/main/compose.yaml>
 - **Configuration Override Pattern**: Uses `TORRUST_TRACKER_CONFIG_OVERRIDE_*` prefix for environment variable overrides
-- **Related**: Environment variable naming decision - [`docs/decisions/environment-variable-prefix.md`](../decisions/environment-variable-prefix.md)
+- **Related**: Environment variable naming decision - [`docs/decisions/environment-variable-prefix.md`](../../decisions/environment-variable-prefix.md)
 
 ## Action Items
 
@@ -212,6 +212,6 @@ fi
 
 ## Related Documentation
 
-- **Our Environment Variable Injection**: [`docs/decisions/environment-variable-injection-in-docker-compose.md`](../decisions/environment-variable-injection-in-docker-compose.md)
-- **Template System**: [`docs/technical/template-system-architecture.md`](../technical/template-system-architecture.md)
-- **Output Handling**: [`docs/contributing/output-handling.md`](../contributing/output-handling.md)
+- **Our Environment Variable Injection**: [`docs/decisions/environment-variable-injection-in-docker-compose.md`](../../decisions/environment-variable-injection-in-docker-compose.md)
+- **Template System**: [`docs/technical/template-system-architecture.md`](../../technical/template-system-architecture.md)
+- **Output Handling**: [`docs/contributing/output-handling.md`](../../contributing/output-handling.md)