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/PROMPT

@@ -0,0 +1,27 @@
+You are Codex, collaborating with a human on the TSYSDevStack ToolboxStack project.
+
+- Seed context:
+  - `SEED` captures the initial scope. Edit it once to define goals, then treat it as read-only unless the high-level objectives change.
+  - Start each session by reading it (`cat SEED`) and summarize progress or adjustments here in PROMPT.
+
+Context snapshot ({{toolbox_name}}):
+- Working directory: artifacts/ToolboxStack/{{toolbox_name}}
+- Image: tsysdevstack-toolboxstack-{{toolbox_name}} (extends from tsysdevstack-toolboxstack-toolbox-base:release-current)
+- Container user: toolbox (non-root, UID/GID mapped to host)
+- Mounted workspace: current repo at /workspace (rw)
+
+Current state:
+- Extends from the standard toolbox-base image, inheriting all base tooling (shells, CLIs, package managers).
+- aqua packages are baked into the base image during the build process for consistency, reproducibility and performance.
+- AI CLI tools from the base are available, with host directories mounted for configuration persistence.
+- See ../PROMPT for shared toolbox contribution expectations (documentation sync, build cadence, commit/push discipline, Conventional Commits, atomic history).
+
+Collaboration checklist:
+1. Translate SEED goals into concrete tooling decisions; mirror outcomes in README.md and this PROMPT (do not rewrite SEED unless the scope resets).
+2. Prefer aqua-managed CLIs and mise-managed runtimes for reproducibility.
+3. After each tooling change, update README/PROMPT, run ./build.sh, commit (Conventional Commit message, focused diff), and push only once the build succeeds per ../PROMPT.
+4. Record verification steps (build/test commands) as they are performed.
+5. Maintain UID/GID mapping and non-root execution.
+
+Active focus:
+- Initialize {{toolbox_name}} using the toolbox-template scaffolding; evolve the Dockerfile/tooling inventory to satisfy the SEED goals.