chore(filesystem): reflect major filesystem restructuring changes

- Renamed DocStack to dockstack
- Transformed toolbox-template into toolbox-qadocker with new functionality
- Removed NewToolbox.sh script
- Updated PROMPT and configuration files across all toolboxes
- Consolidated audit and testing scripts
- Updated QWEN.md to reflect new filesystem structure as authoritative source
- Merged PROMPT content into QWEN.md as requested

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

The filesystem structure has been intentionally restructured and is now the authoritative source of truth for the project organization.

ToolboxStack/output/toolbox-QADocker/AUDIT_CHECKLIST.md

@@ -1,101 +1,120 @@
-# 🛡️ Docker QA Toolbox Audit Checklist
+# 🧰 Toolbox Template Audit Checklist
 
-This checklist ensures the Docker QA toolbox meets all security, functionality, and maintainability requirements for Docker image auditing.
+This checklist ensures the toolbox-template provides a solid foundation for creating new toolboxes that extend from toolbox-base.
 
-## 🔒 Security Audit
+## 🏗️ Structure Audit
 
-- [ ] All packages installed with specific versions (no `latest` tags)
-- [ ] All external downloads verified with checksums/signatures
-- [ ] No root access possible at runtime (sudo removed)
-- [ ] Non-root user properly configured with UID/GID mapping
-- [ ] No hardcoded secrets or credentials in image
-- [ ] Minimal attack surface (unnecessary packages removed)
-- [ ] Regular security scanning implemented (Trivy integration)
-- [ ] Base image (Ubuntu) regularly updated
-- [ ] All aqua packages verified through registry
-- [ ] Docker socket access properly secured
+- [ ] Template Dockerfile properly extends from toolbox-base:release-current
+- [ ] Template Dockerfile follows best practices for extension
+- [ ] Template docker-compose.yml properly inherits from base configuration
+- [ ] Template build.sh script properly wraps docker build with UID/GID mapping
+- [ ] Template run.sh script properly manages container lifecycle
+- [ ] Template devcontainer.json properly references base configuration
+- [ ] Template SEED file properly defines extension objectives
+- [ ] Template PROMPT file properly guides contributors
+- [ ] Template README.md properly documents usage and customization
+- [ ] Template aqua.yaml properly extends from base tooling
 
-## 🛠️ Functionality Audit
+## 🔧 Consistency Audit
 
-- [ ] All Docker QA tools properly installed and accessible
-- [ ] All tools respond to `--version` flag correctly
-- [ ] Aqua proxy mechanism properly configured
-- [ ] Docker access to host daemon working correctly
-- [ ] Security scanning tools (Trivy, Hadolint) functional
-- [ ] Dockerfile linting tools working properly
-- [ ] Shell configurations properly set up (zsh, bash)
-- [ ] Environment variables properly configured
-- [ ] PATH correctly set for all tools
-- [ ] User home directory properly configured
-- [ ] Workspace directory properly set up with correct permissions
+- [ ] Template inherits all base security practices
+- [ ] Template follows same build process patterns as base
+- [ ] Template uses same user model as base (non-root with UID/GID mapping)
+- [ ] Template workspace mounting consistent with base
+- [ ] Template runtime behavior consistent with base
+- [ ] Template error handling consistent with base
+- [ ] Template documentation style consistent with base
+- [ ] Template testing approach consistent with base
+- [ ] Template customization points clearly defined
+- [ ] Template extension patterns well-documented
 
-## 🏗️ Build Process Audit
+## 🛡️ Security Audit
 
-- [ ] Dockerfile follows best practices
-- [ ] Multi-stage build optimizations implemented
-- [ ] Build cache properly utilized
-- [ ] Build arguments properly validated
-- [ ] Error handling in build scripts comprehensive
-- [ ] Build verification tests implemented
-- [ ] Image tagging strategy consistent
-- [ ] Release process properly documented
+- [ ] Template maintains all base security guarantees
+- [ ] Template doesn't introduce security vulnerabilities
+- [ ] Template doesn't weaken base security model
+- [ ] Template properly validates user inputs
+- [ ] Template properly handles file permissions
+- [ ] Template doesn't expose additional attack surfaces
+- [ ] Template properly manages secrets/configuration
+- [ ] Template follows principle of least privilege
+- [ ] Template properly isolates user processes
+- [ ] Template maintains non-root execution model
 
 ## 🧪 Testing Audit
 
-- [ ] Automated testing of all installed tools
-- [ ] Integration tests for Docker daemon access
-- [ ] Regression tests for known issues
-- [ ] Security scanning of built images
-- [ ] Performance benchmarks
-- [ ] Security scanning during build
+- [ ] Template includes testing framework
+- [ ] Template tests verify proper extension from base
+- [ ] Template tests validate added functionality
+- [ ] Template tests check for regression issues
+- [ ] Template tests cover error conditions
+- [ ] Template tests verify security properties
+- [ ] Template tests run automatically during build
+- [ ] Template tests provide clear failure diagnostics
+- [ ] Template tests cover all customization points
+- [ ] Template tests align with base testing philosophy
 
 ## 📚 Documentation Audit
 
-- [ ] README.md accurately reflects current state
-- [ ] All tools properly documented
-- [ ] Usage examples for Docker QA workflows provided
-- [ ] Troubleshooting guide included
-- [ ] Contribution guidelines clear
-- [ ] License information up to date
+- [ ] Template README.md clearly explains purpose and usage
+- [ ] Template README.md properly documents customization options
+- [ ] Template README.md links to base documentation
+- [ ] Template README.md includes quick start guide
+- [ ] Template README.md covers troubleshooting
+- [ ] Template README.md explains extension patterns
+- [ ] Template README.md documents versioning strategy
+- [ ] Template README.md covers maintenance procedures
+- [ ] Template README.md explains collaboration guidelines
+- [ ] Template README.md maintains consistent style with base
 
 ## 🔄 Maintenance Audit
 
-- [ ] Dependency update strategy defined
-- [ ] Version pinning strategy consistent
-- [ ] Backward compatibility maintained
-- [ ] Deprecation policy established
-- [ ] Release notes properly maintained
-- [ ] Issue tracking process defined
+- [ ] Template properly tracks base image updates
+- [ ] Template provides clear upgrade paths
+- [ ] Template maintains backward compatibility
+- [ ] Template follows same release cadence as base
+- [ ] Template properly handles dependency updates
+- [ ] Template includes update automation where appropriate
+- [ ] Template documents breaking changes
+- [ ] Template provides migration guides when needed
+- [ ] Template follows same versioning scheme as base
+- [ ] Template maintains consistent issue tracking
 
-## 🎯 Specialized QA Features Audit
+## 🎯 Usability Audit
 
-- [ ] Trivy vulnerability scanning functional
-- [ ] Hadolint Dockerfile linting operational
-- [ ] Dockerfilelint working correctly
-- [ ] Docker history/inspect tools accessible
-- [ ] Image layer analysis capabilities present
-- [ ] Best practices validation tools available
-
-## 📈 Performance Audit
-
-- [ ] Image size optimized
-- [ ] Startup time acceptable
-- [ ] Memory footprint reasonable
-- [ ] CPU usage within expected bounds
-- [ ] Docker scanning performance adequate
+- [ ] Template is easy to copy and customize
+- [ ] Template provides clear extension points
+- [ ] Template includes helpful examples
+- [ ] Template reduces boilerplate code
+- [ ] Template provides sensible defaults
+- [ ] Template includes proper error messages
+- [ ] Template supports common customization patterns
+- [ ] Template includes helpful documentation
+- [ ] Template follows intuitive naming conventions
+- [ ] Template minimizes configuration complexity
 
 ## 🌐 Compatibility Audit
 
-- [ ] Works on all supported platforms
-- [ ] Docker daemon access functional across platforms
-- [ ] Backward compatibility with Docker versions maintained
-- [ ] Integration with common CI/CD tools verified
+- [ ] Template works with all supported platforms
+- [ ] Template maintains cross-platform consistency
+- [ ] Template integrates well with base tooling
+- [ ] Template supports common development workflows
+- [ ] Template handles various project structures
+- [ ] Template works with popular IDEs/editors
+- [ ] Template supports CI/CD integration
+- [ ] Template compatible with common deployment methods
+- [ ] Template supports popular version control systems
+- [ ] Template integrates with common development tools
 
-## 🧹 Cleanup Audit
+## 🧹 Cleanliness Audit
 
-- [ ] Temporary files properly removed
-- [ ] Build artifacts cleaned up
-- [ ] Cache directories properly managed
-- [ ] Log files rotated or removed
-- [ ] Orphaned processes prevented
-- [ ] Resource leaks eliminated
+- [ ] Template includes no unnecessary files
+- [ ] Template follows consistent file organization
+- [ ] Template includes proper .gitignore
+- [ ] Template avoids duplicating base functionality
+- [ ] Template includes proper licensing information
+- [ ] Template maintains clean directory structure
+- [ ] Template includes appropriate comments/documentation
+- [ ] Template avoids hardcoded values where possible
+- [ ] Template follows consistent naming conventions
+- [ ] Template includes proper attribution where needed